rfc2360.txt

RFC 的详细文档！

RFC 2360          Guide for Internet Standards Writers         June 1998


   o Does it specify behavior in the face of incorrect operation by
     other implementations?
   o Does it delineate which packets should be accepted for processing
     and which should be ignored?
   o If multiple descriptions of a requirement are given, does it
     identify one as binding?
   o How many optional features does it specify?  Does it separate them
     into option classes?
   o Have all combinations of options or option classes been examined
     for incompatibility?
   o Does it explain the rationale and use of options?
   o Have all mandatory and optional requirements be identified and
     documented by the accepted key words that define Internet
     requirement levels?
   o Does it conform to the current internationalization policies of
     the IETF?
   o Are the recommended meanings for common Internet terms used?
   o If not, are new or altered definitions for terms given in a
     glossary?

5  Security Considerations

   This document does not define a protocol or procedure that could be
   subject to an attack.  It establishes guidelines for the information
   that should be included in RFCs that are to be submitted to the
   standards track.  In the area of security, IETF standards authors are
   called on to define clearly the threats faced by the protocol and the
   way the protocol does or does not provide security assurances to the
   user.

6  References

   [RFC 791]   Postel, J., "Internet Protocol (IP)", STD 5, RFC 791
               September 1981.

   [RFC 904]   Mills, D., "Exterior Gateway Protocol formal
               specification", RFC 904, April 1984.

   [RFC 1058]  Hedrick, C., "Routing Information Protocol", STD 34,
               RFC 1058, June 1988.

   [RFC 1112]  Deering, S., "Host extensions for IP multicasting",
               STD 5, RFC 1112, August 1989.

   [RFC 1122]  Braden, R., "Requirements for Internet Hosts --
               Communication Layers", STD 3, RFC 1122, October 1989.





Scott                    Best Current Practice                 [Page 16]

RFC 2360          Guide for Internet Standards Writers         June 1998


   [RFC 1123]  Braden, R., "Requirements for Internet hosts --
               Application and Support", STD 3, RFC 1123, October 1989.

   [RFC 1311]  Postel, J., "Introduction to the STD Notes", RFC 1311,
               March 1992.

   [RFC 1350]  Sollins, K., "The TFTP Protocol (Revision 2)", STD 33,
               RFC 1350, July 1992.

   [RFC 1661]  Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51,
               RFC 1661, July 1994.

   [RFC 1662]  Simpson, W., "PPP in HLDC-like Framing", STD 51, RFC 1662,
               July 1994.

   [RFC 1700]  Reynolds, J., and J. Postel, "Assigned Numbers", STD 2,
               RFC 1700, October 1994.  (http://www.iana.org)

   [RFC 1939]  Meyers, J., and M. Rose, "Post Office Protocol - Version
               3", STD 53, RFC 1939, May 1996.

   [RFC 1958]  Carpenter, B., "Architectural Principles of the Internet",
               RFC 1958, June 1996.

   [RFC 1983]  Malkin, G., "Internet Users' Glossary", FYI 18, RFC 1983,
               August 1996.

   [RFC 2026]  Bradner, S., "The Internet Standards Process -- Revision 3",
               RFC 2026, October 1996.

   [RFC 2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Level", BCP 14, RFC 2119, March 1997.

   [RFC 2328]  Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.

   [RFC 2223]  Postel, J. and J. Reynolds, "Instructions to RFC Authors",
               RFC 2223, October 1997.

   [RFC 2277]  Alvestrand, H., "IETF Policy on Character Sets and
               Language", RFC 2277, January 1998.

   [RFC 2316]  Bellovin, S., "Report of the IAB Security Architecture
               Workshop", RFC 2316, April 1998.








Scott                    Best Current Practice                 [Page 17]

RFC 2360          Guide for Internet Standards Writers         June 1998


7  Acknowledgments

   Peter Desnoyers and Art Mellor began the work on this document.
   Others that contributed were:

     Bernard Aboba
     Harald T. Alvestrand
     Fred Baker
     Scott Bradner
     Brian Carpenter
     Robert Elz
     Dirk Fieldhouse
     Dale Francisco
     Gary Malkin
     Neal McBurnett
     Thomas Narten
     Craig Partridge
     Vern Paxson
     Mike O'Dell
     Henning Schulzrinne
     Kurt Starsinic
     James Watt

8  Editor's Address

   Gregor D. Scott
   Director, Defense Information Systems Agency
   ATTN: JIEO-JEBBC
   Ft. Monmouth, NJ  07703-5613
   USA

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

















Scott                    Best Current Practice                 [Page 18]

RFC 2360          Guide for Internet Standards Writers         June 1998


9  Appendix

CHANGES FROM DRAFT -06

   The following changes were made following IESG review:

   References to RFC 1543 were changed to RFC 2223 that obsoleted it.

   In section 2.1, "export control" was dropped as a valid reason for
   not selecting a security mechanism.  In addition, ambiguous or
   conflicting sentences were removed.

   In section 2.1 reference made to RFC 2315 as an additional source of
   information.

   Section 2.5 was changed to highlight the Change Log's purpose as
   assistance to implementers.

   The IANA Considerations section (2.13) was rewritten to highlight
   that the IANA guidelines document is work in progress but should be
   used when it becomes available.

   Section 3.4 Character Sets was deleted and replaced by section 2.17
   Internationalization.

   Spelling and grammar corrections were made.

CHANGES FROM DRAFT -05

   A sentence pointing to a pending document that further addresses IANA
   considerations was added to section 2.13.  The current draft of that
   document is draft-iesg-iana-considerations-02.txt.  A clause stating
   that the IANA established the assignment policies was removed since it
   appeared to conflict with the intent of the referenced ID.
   Placeholders for the BCP and RFC number have been added to the text
   and reference section.

   A new section (2.5) requiring change logs as documents progress along
   the standards track was added.

   References to RFC 2044 were changed to RFC 2279 that obsoleted it.

   Spelling and grammar corrections were made.

CHANGES FROM DRAFT -04

   A paragraph pointing to a pending document that further addresses
   security was updated.



Scott                    Best Current Practice                 [Page 19]

RFC 2360          Guide for Internet Standards Writers         June 1998


10  Full Copyright Statement

   Copyright (C) The Internet Society (1998).  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.
























Scott                    Best Current Practice                 [Page 20]