rfc2555.txt

中、英文RFC文档大全打包下载完全版 .

   others, who served on the NWG or authored RFCs, an extreme debt of
   gratitude for their contributions and dedication.

   At no time was the controversy worse than it was when DoD adopted
   TCP/IP as its official host-to-host protocols for communications
   networks.  In March 1982, a military directive was issued by the
   Under Secretary of Defense, Richard DeLauer.  It simply stated that
   the use of TCP and IP was mandatory for DoD communications networks.
   Bear in mind that a military directive is not something you discuss -
   the time for discussion is long over when one is issued.  Rather a
   military directive is something you DO.  The ARPANET and its
   successor, the Defense Data Network, were military networks, so the
   gauntlet was down and the race was on to prove whether the new
   technology could do the job on a real operational network.  You have
   no idea what chaos and controversy that little 2-page directive
   caused on the network.  (But that's a story for another time.)
   However, that directive, along with RFCs 791 and 793 (IP and TCP)
   gave the RFCs as a group of technical documents stature and
   recognition throughout the world.  (And yes, TCP/IP certainly did do
   the job!)

   Jon and I were both government contractors, so of course followed the
   directions of our contracting officers.  He was mainly under contract
   to ARPA, whereas the NIC was mainly under contract to DCA.  BBN was
   another key contractor.  For the most part we all worked as a team.
   However, there was frequent turnover in military personnel assigned
   to both the ARPANET and the DDN, and we all collaborated to try to
   get all the new participants informed as to what was available to
   them when they joined the network.  We also tried to foster
   collaboration rather than duplication of effort, when it was
   appropriate.  The NWG (or IETF as it is now known) and the RFCs
   became the main vehicles for interagency collaboration as the DoD
   protocols began to be used on other government, academic, and
   commercial networks.

   I left SRI and the NIC project in 1989.  At that time there were
   about 30,000 hosts on what was becoming known as the Internet, and
   just over a 1000 RFCs had been issued.  Today there are millions of
   hosts on the Internet, and we are well past the 3000 mark for RFCs.
   It was great fun to be a part of what turned out to be a
   technological revolution.   It is heartwarming to see that the RFCs
   are still being issued by the IETF, and that they are still largely
   based on ideas that have been discussed and implemented; that the
   concepts of online working groups and distributed information servers
   are a way of life; that those little "links" (officially known as
   hypertext) have revolutionized the delivery of documents; and that
   the government, academia, and business are now all playing the same
   game for fun and profit.  (Oh yes, I'm happy to see that Steve's idea



RFC Editor, et al.           Informational                     [Page 13]

RFC 2555                    30 Years of RFCs                7 April 1999


   for integrated text and graphics has finally come to fruition,
   although that work took a little longer than 2 days.)

6. Favorite RFCs -- The First 30 Years - Celeste Anderson

   Five years ago, Jon Postel and I had wanted to publish a 25th RFC
   anniversary book, but, alas, we were both too busy working on other
   projects.  We determined then that we should commemorate the
   thirtieth anniversary by collecting together thirty "RFC Editors'
   Choice" RFCs based on original ideas expressed throughout the first
   30 years of their existence.

   Jon's untimely death in October 1998 prevented us from completing
   this goal.  We did, however, start to put online some of the early
   RFCs, including RFC 1.  We weren't sure whether we were going to try
   to make them look as close to the typewritten originals as possible,
   or to make a few adjustments and format them according to the latest
   RFC style.  Those of you who still have your copies of RFC 1 will
   note the concessions we made to NROFF the online version.  The hand-
   drawn diagrams of the early RFCs also present interesting challenges
   for conversion into ASCII format.

   There are still opportunities to assist the RFC Editor to put many of
   the early RFCs online.  Check the URL:
   http://www.rfc-editor.org/rfc-online.html for more information on this
   project.

   In memory of Jon, we are compiling a book for publication next year
   of "Favorite RFCs -- The First 30 Years".

   We have set up a web interface at

           http://www.rfc-editor.org/voterfc.html

   for tabulating votes and recording the responses.  We will accept
   email as well.  Please send your email responses to: [e-mail].
   We prefer votes accompanied by explanations for the vote choice.

   We reserve the right to add to the list several RFCs that Jon Postel
   had already selected for the collection.  Voting closes December 31,
   1999.










RFC Editor, et al.           Informational                     [Page 14]

RFC 2555                    30 Years of RFCs                7 April 1999


7. Security Considerations

   Security issues are not discussed in this commemorative RFC.

8. Acknowledgments

   Thank you to all the authors who contributed to this RFC on short
   notice.  Thanks also to Fred Baker and Eve Schooler who goaded us
   into action.  A special acknowledgment to Eitetsu Baumgardner, a
   student at USC, who NROFFed this document and who assisted in the
   formatting of RFCs 1, 54, and 62, converting hand-drawn diagrams into
   ASCII format.

9. Authors' Addresses

   Robert Braden
   USC/Information Sciences Institute
   4676 Admiralty Way #1001
   Marina del Rey, CA 90292

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


   Joyce K. Reynolds
   USC/Information Sciences Institute
   4676 Admiralty Way #1001
   Marina del Rey, CA 90292

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


   Steve Crocker
   Steve Crocker Associates, LLC
   5110 Edgemoor Lane
   Bethesda, MD 20814

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








RFC Editor, et al.           Informational                     [Page 15]

RFC 2555                    30 Years of RFCs                7 April 1999


   Vint Cerf
   MCI

   EMail: [e-mail]


   Jake Feinler
   SRI Network Information Center
   1972-1989

   EMail: [e-mail]


   Celeste Anderson
   USC/Information Sciences Institute
   4676 Admiralty Way #1001
   Marina del Rey, CA 90292

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






























RFC Editor, et al.           Informational                     [Page 16]

RFC 2555                    30 Years of RFCs                7 April 1999


10. APPENDIX - RFC 1

   The cover page said at the top:

     "Network Working Group
      Request for Comments"

   and then came an internal UCLA distribution list:

     V. Cerf, S. Crocker, M. Elie, G. Estrin, G. Fultz, A. Gomez,
     D. Karas, L. Kleinrock, J. Postel, M. Wingfield, R. Braden,
     and W. Kehl.

   followed by an "Off Campus" distribution list:

     A. Bhushan (MIT), S. Carr (Utah), G. Cole (SDC), W. English (SRI),
     K. Fry (Mitre), J. Heafner (Rand), R. Kahn (BBN), L. Roberts (ARPA),
     P. Rovner (MIT), and R. Stoughton (UCSB).

   The following title page had

     "Network Working Group
      Request for Comments: 1"

   at the top, and then:

               HOST SOFTWARE

               STEVE CROCKER
               7 APRIL 1969





















RFC Editor, et al.           Informational                     [Page 17]

RFC 2555                    30 Years of RFCs                7 April 1999


11. Full Copyright Statement

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
























RFC Editor, et al.           Informational                     [Page 18]