rfc1264.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.


RFC 1264               Routing Protocol Criteria            October 1991


      - Test scenarios and test results showing that the major features
        of the protocols have been tested.

   The IESG will forward to the IAB its recommendation for advancement
   of the new routing protocol to Proposed Standard based on its
   evaluation of protocol specifications and this reports.

5.0 Requirements for Draft Standard

   1) Revisions to the Protocol and Usage documents showing changes and
      clarifications made based on experience gained in the time
      between when the protocol was made a Proposed Standard and it
      being submitted for Draft Standard.  The revised documents should
      include a section summarizing the changes made.

   2) The Management Information Base (MIB) must be at the Proposed
      Standard level of standardization.

   3) Two or more interoperable implementations must exist.  At least
      two must be written independently.

   4) There must be evidence that all features of the protocol have
      been tested, running between at least two implementations.  This
      must include that all of the security features have been
      demonstrated to operate, and that the mechanisms defined in the
      protocol actually provide the intended protection.

   5) There must be significant operational experience.  This must
      include running in a moderate number routers configured in a
      moderately complex topology, and must be part of the operational
      Internet.  All significant features of the protocol must be
      exercised.  In the case of an Interior Gateway Protocol (IGP),
      both interior and exterior routes must be carried (unless another
      mechanism is provided for the exterior routes).  In the case of
      a Exterior Gateway Protocol (EGP), it must carry the full
      complement of exterior routes.

   6) Two reports must be submitted to the IESG via the Routing Area
      Director.  The first report must document how requirements 1)
      through 5) of this document have been satisfied.  It must include:

      - Reference to the MIB for the protocol.

      - Description of the authentication mechanisms in the protocol.

      - List of implementations including origin of code.

      - Implementation experience.



Hinden                                                          [Page 5]

RFC 1264               Routing Protocol Criteria            October 1991


      - Test scenarios and test results showing that all features of the
        protocols have been tested.

      - Description of operational experience.  This must include
        topology, environment, time and duration, implementations
        involved, and overall results and conclusions gained from the
        operational experience.

   The second report must summarize the key features of the protocol and
   analyze how the protocol will perform and scale in the Internet.  The
   intent of this requirement is to understand the boundary conditions
   of the routing protocol.  The new routing protocol must be compared
   with the existing routing protocols (e.g., RIP, EGP, etc.) as
   appropriate.  The report should answer several questions:

      - What are the key features and algorithms of the protocol?

      - How much link bandwidth, router memory and router CPU cycles
        does the protocol consume under normal conditions?

      - For these metrics, how does the usage scale as the routing
        environment grows?  This should include topologies at least an
        order of magnitude larger than the current environment.

      - What are the limits of the protocol for these metrics? (I.e.,
        when will the routing protocol break?)

      - For what environments is the protocol well suited, and for what
        is it not suitable?

   The IESG will forward to the IAB its recommendation for advancement
   of the new routing protocol to Draft Standard based on its evaluation
   of protocol specifications and these reports.

6.0 Requirements for Standard

   1) Revisions to the Protocol and Usage documents showing changes and
      clarifications made based on experience gained in the time between
      when the protocol was made a Draft Standard and it being submitted
      for Standard.  The changes should be to clarify the protocol
      or provide guidance in its implementation.  No significant changes
      can be made to the protocol at this stage.  The revised documents
      should include a section summarizing the changes made.

   2) The Management Information Base (MIB) must be submitted for
      Standard at the same time as the routing protocol.

   3) Three or more interoperable implementations must exist.  At least



Hinden                                                          [Page 6]

RFC 1264               Routing Protocol Criteria            October 1991


      two must be written independently.

   4) There must be evidence that all features of the protocol have been
      tested, running between at least two independently written
      implementations.  This must include that all of the security
      features have been demonstrated to operate, and that the mechanisms
      defined in the protocol actually provide the intended protection.

   5) There must be significant operational experience.  This must
      include running in a large number routers configured in a complex
      topology, and must be part of the operational Internet.  The
      operational experience must include multi-vendor operation.  All
      significant features of the protocol must be exercised.  In the
      case of an Interior Gateway Protocol (IGP), both interior and
      exterior routes must be carried (unless another mechanism is
      provided for the exterior routes).  In the case of a Exterior
      Gateway Protocol (EGP), it must carry the full complement of
      exterior routes.

   6) Two reports must be submitted to the IESG via the Routing Area
      Director.  The first report must document how requirements 1)
      through 5) of this document have been satisfied.  It must include:

      - Reference to the MIB for the protocol.

      - Description of the authentication mechanisms in the protocol.

      - List of implementations including origin of code.

      - Implementation experience.

      - Test scenarios and test results showing that all features of the
        protocols have been tested.

      - Description of operational experience.  This must include
        topology, environment, time and duration, implementations
        involved, and overall results and conclusions gained from the
        operational experience.

   The second report should be a revision to the report prepared when
   the protocol was submitted for Draft Standard.  It must describe the
   additional knowledge and understanding gained in the time between
   when the protocol was made a Draft standard and when it was submitted
   for Standard.

   The IESG will forward to the IAB its recommendation for advancement
   of the new routing protocol to Standard based on its evaluation of
   protocol specifications and these reports.



Hinden                                                          [Page 7]

RFC 1264               Routing Protocol Criteria            October 1991


Security Considerations

   Security issues are not discussed in this memo.

Author's Address

   Robert M. Hinden
   Bolt Beranek and Newman, Inc.
   50 Moulton Street
   Cambridge, MA 02138

   Phone: [phone]

   EMail: [e-mail]





































Hinden                                                          [Page 8]