rfc2902.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 900 行 · 第 1/3 页

      encouraged within the Internet
   3. Encourage funding of better tools for remotely controlled traffic
      sources and pro-active problem detection.

3.2. Action Items for IETF Working Group Chairs

   1. NAT: Forward our concerns, problems and suggestions to the
      appropriate working groups
   2. We recommend that IETF should work the issue of Constraint Based
      Routing.
   3. The IETF should encourage work on "wire speed" authentication,
      pair-wise authentication of routers in routing protocols, and
      Byzantine robustness in routing protocols.




Deering, et al.              Informational                     [Page 11]

RFC 2902       Overview of the 1998 IAB Routing Workshop     August 2000


   4. Concerns about the Routing Policy Specification Language (RPSL)
      should go to the Routing Policy Systems (RPS) working group chair.
   5. The group recommends a BOF be held on Measuring Path
      Characteristics.  The BOF should consider the data exchange format
      of measurement and mechanisms to distribution of data mechanism.
      It is noted that the IPPM working group is dealing with issues
      within the measurement problem space.
   6. There is layer two work which should be done to support the
      multiple parallel trunks which is outside the scope of the IETF.
      Layer three routing should support richer metrics in OSPF.
   7. SNMP version 3 working groups should be notified about the issues
      about authentication, scope, and rate limiting.
   8. A BOF should be held to plan work on anycast.  A document on
      anycast should be part of the proposed working group charter.

3.3. Action Items for the IRTF Routing Research Group

   1. We recommend that the IRTF Routing Research working group try to
      encourage more analysis of routing data, not just the collection
      of more data.

   2. Encourage evaluation and written reports on the evaluation of
      multicast protocols and mechanisms for different types of
      protocols

   3. The IRTF Routing Research group chair and the Routing Area
      Director should discuss Load Sensitive IGP routing and determine
      whether it is ready for the IETF.

4. Security Considerations

   Security considerations were an important part of the discussions at
   the workshop, but the workshop decided not to publish a summary of
   these discussions.  Other documents that address the issues of
   routing infrastructure security have recently been published.

A. Participants

      (Email addresses as of the meeting date.)

      Harald Alvestrand               [e-mail]
      Fred Baker                      [e-mail]
      Jeff Burgan                     [e-mail]
      Brian Carpenter                 [e-mail]
      Noel Chiappa                    [e-mail]
      Rob Coltun                      [e-mail]
      Steve Deering                   [e-mail]
      Deborah Estrin                  [e-mail]



Deering, et al.              Informational                     [Page 12]

RFC 2902       Overview of the 1998 IAB Routing Workshop     August 2000


      Dino Farinacci                  [e-mail]
      Paul Francis                    [e-mail]
      Elise Gerich                    [e-mail]
      Joel Halpern                    [e-mail]
      Sue Hares                       [e-mail]
      Cyndi Jung                      [e-mail]
      Dave Katz                       [e-mail]
      Tony Li                         [e-mail]
      Peter Lothberg                  [e-mail]
      Louis Mamakos                   [e-mail]
      Dave Meyer                      [e-mail]
      Keith Moore                     [e-mail]
      Bob Moskowitz                   [e-mail]
      Thomas Narten                   [e-mail]
      Vern Paxson                     [e-mail]
      Charles E. Perkins              [e-mail]
      Radia Perlman                   [e-mail]
      Yakov Rekhter                   [e-mail]
      Allyn Romanow                   [e-mail]
      Martha Steenstrup               [e-mail]
      George Swallow                  [e-mail]

References

   [1]  Alaettinoglu, C., Bates, T., Gerich, E., Karrenberg, D., Meyer,
        D., Terpstra, M. and C. Villamizar, "Routing Policy
        Specification Language (RPSL)", RFC 2280, January 1998.

   [2]  Ballardie, A., "Core Based Trees (CBT) Multicast Routing
        Architecture", RFC 2201, September 1997.

   [3]  Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z. and W.
        Weiss, "An Architecture for Differentiated Service",  RFC 2475,
        December 1998.

   [4]  Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S.,
        Handley, M., Jacobson,  V., Liu, C., Sharma, P. and L. Wei,
        "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol
        Specification", RFC 2362, June 1998.

   [5]  Holbrook, H., Cheriton, D, "EXPRESS Multicast", SIGCOMM 99,
        September 1999.

   [6]  Charlie Kaufman, Radia Perlman, and Mike Speciner.  Network
        Security:  Private Communication in a Public World, pages 462--
        465.  Prentice-Hall, Inc., 1995.





Deering, et al.              Informational                     [Page 13]

RFC 2902       Overview of the 1998 IAB Routing Workshop     August 2000


   [7]  W. Leland and M. Zekauskas (chairs).  IP Performance Metrics
        (IPPM), October 1997.  http://www.ietf.org/html.charters/ippm-
        charter.html.

   [8]  Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994.

   [9]  Nichols, K., Blake, S., Baker, F. and D. Black, "Definition of
        the Differentiated Services Field (DS Field) in the IPv4 and
        IPv6 Headers", RFC 2474, December 1998.

   [10]  H. Sandick and E. Crawley (chairs).  QoS Routing (qosr), April
        1997.  http://www.ietf.org/html.charters/qosr-charter.html.

   [11] C. Villamizar and C. Alaettinoglu (chairs).  Routing Policy
        Syntax (RPS), July 1995. http://www.ietf.org/html.charters/rps-
        charter.html.

   [12] Waitzman, D., Partridge, C. and S. Deering, "Distance Vector
        Multicast Routing Protocol", RFC 1075, November 1988.
































Deering, et al.              Informational                     [Page 14]

RFC 2902       Overview of the 1998 IAB Routing Workshop     August 2000


Authors' Addresses

   Questions about this memo can be directed to:

   Stephen E. Deering
   Cisco Systems, Inc.
   170 West Tasman Drive
   San Jose, CA 95134-1706
   USA

   Phone:  [phone]
   EMail:  [e-mail]


   Susan Hares
   Merit, Inc.
   1071 Beal Avenue,
   Ann Arbor, MI 48109
   USA

   Phone:  [phone]
   EMail:  [e-mail]


   Radia Perlman
   Sun Microsystems Laboratories
   2 Elizabeth Drive
   Chelmsford, MA 01824
   USA

   Phone:  [phone]
   EMail:  [e-mail]


   Charles E. Perkins
   Nokia Research Center
   313 Fairchild Drive
   Mountain View, CA 94043
   USA

   Phone:  [phone]
   EMail:  [e-mail]
   Fax:    [phone]








Deering, et al.              Informational                     [Page 15]

RFC 2902       Overview of the 1998 IAB Routing Workshop     August 2000


Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Deering, et al.              Informational                     [Page 16]