rfc1130.txt

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

POP2       Post Office Protocol, Version 2          Elective         937
SFTP       Simple File Transfer Protocol            Elective         913
RLP        Resource Location Protocol               Elective         887
RTELNET    Remote Telnet Service                    Elective         818
FINGER     Finger Protocol                          Elective         742
SUPDUP     SUPDUP Protocol                          Elective         734
NETED      Network Standard Text Editor             Elective         569
RJE        Remote Job Entry                         Elective         407

6.6.  Experimental Protocols

Protocol   Name                                     Status           RFC
--------   ----                                     ------           ---
BGP        Border Gateway Protocol                  Not Recommended 1105
IP-DVMRP   IP Distance Vector Multicast Routing     Not Recommended 1075
TCP-LDP    TCP Extensions for Long Delay Paths      Not Recommended 1072
IP-MTU     IP MTU Discovery Options                 Not Recommended 1063
NETBLT     Bulk Data Transfer Protocol              Not Recommended  998
IMAP2      Interactive Mail Access Protocol         Not Recommended 1064
COOKIE-JAR Authentication Scheme                    Not Recommended 1004
IRTP       Internet Reliable Transaction Protocol   Not Recommended  938
AUTH       Authentication Service                   Not Recommended  931
RATP       Reliable Asynchronous Transfer Protocol  Not Recommended  916
THINWIRE   Thinwire Protocol                        Not Recommended  914
LDP        Loader Debugger Protocol                 Not Recommended  909
RDP        Reliable Data Protocol                   Not Recommended  908
ST         Stream Protocol                       Not Recommended IEN 119
NVP-II     Network Voice Protocol               Not Recommended ISI memo







Internet Activities Board                                      [Page 12]

RFC 1130                     IAB Standards                  October 1989


6.7.  Historic Protocols

Protocol   Name                                     Status           RFC
--------   ----                                     ------           ---
SGMP       Simple Gateway Monitoring Protocol       Not Recommended 1028
HEMS       High Level Entity Management Protocol    Not Recommended 1021
HMP        Host Monitoring Protocol                 Not Recommended  869
GGP        Gateway Gateway Protocol                 Not Recommended  823
CLOCK      DCNET Time Server Protocol               Not Recommended  778
MPM        Internet Message Protocol                Not Recommended  759
NETRJS     Remote Job Service                       Not Recommended  740
XNET       Cross Net Debugger                    Not Recommended IEN 158
NAMESERVER Host Name Server Protocol             Not Recommended IEN 116
MUX        Multiplexing Protocol                 Not Recommended IEN  90
GRAPHICS   Graphics Protocol                   Not Recommended NIC 24308

7.  Contacts

7.1.  Internet Activities Board Contact

      Contact:

         Jon Postel
         USC Information Sciences Institute
         4676 Admiralty Way
         Marina del Rey, CA  90292-6695

         1-213-822-1511

         [e-mail]

   Please send your comments about this list of protocols and especially
   about the Draft Standard Protocols to the Internet Activities Board.

7.2.  Internet Assigned Numbers Authority Contact

      Contact:

         Joyce K. Reynolds
         Internet Assigned Numbers Authority
         USC Information Sciences Institute
         4676 Admiralty Way
         Marina del Rey, CA  90292-6695

         1-213-822-1511

         [e-mail]




Internet Activities Board                                      [Page 13]

RFC 1130                     IAB Standards                  October 1989


   The protocol standards are managed for the IAB by the Internet
   Assigned Numbers Authority.

   Please refer to the documents "Assigned Numbers" (RFC-1010) and
   "Official Internet Protocols" (RFC-1011) for further information
   about the status of protocol documents.  There are two documents that
   summarize the requirements for host and gateways in the Internet,
   "Host Requirements" (RFC-1122 and RFC-1123) and "Gateway
   Requirements" (RFC-1009).

      How to obtain the most recent edition of this "IAB Official
      Protocol Standards" memo:

         The file "in-notes/iab-standards.txt" may be copied via FTP
         from the VENERA.ISI.EDU computer using the FTP username
         "anonymous" and FTP password "guest".


7.3.  Request for Comments Editor Contact

      Contact:

         Jon Postel
         RFC Editor
         USC Information Sciences Institute
         4676 Admiralty Way
         Marina del Rey, CA  90292-6695

         1-213-822-1511

         [e-mail]

   Documents may be submitted via electronic mail to the RFC Editor for
   consideration for publication as RFC.  If you are not familiar with
   the format or style requirements please request the "Instructions for
   RFC Authors".  In general, the style of any recent RFC may be used as
   a guide.














Internet Activities Board                                      [Page 14]

RFC 1130                     IAB Standards                  October 1989


7.4.  The Network Information Center and
       Requests for Comments Distribution Contact

      Contact:

         DDN Network Information Center
         SRI International
         Room EJ291
         333 Ravenswood Avenue
         Menlo Park, CA  94025

         1-800-235-3155
         1-415-859-3695

         [e-mail]

   The Network Information Center (NIC) provides many information
   services for the Internet community.  Among them is maintaining the
   Requests for Comments (RFC) library.

   RFCs can be obtained via FTP from NIC.DDN.MIL with the pathname
   RFC:RFCnnnn.TXT where "nnnn" refers to the number of the RFC. A list
   of all RFCs may be obtained by copying the file RFC:RFC-INDEX.TXT.
   Log in with FTP username ANONYMOUS and password GUEST.

   The NIC also provides an automatic mail service for those sites which
   cannot use FTP.  Address the request to [e-mail] and in
   the subject field of the message indicate the RFC number, as in
   "Subject: RFC nnnn".

      How to obtain the most recent edition of this "IAB Official
      Protocol Standards" memo:

         The file RFC:IAB-STANDARDS.TXT may be copied via FTP from the
         NIC.DDN.MIL computer following the same procedures used to
         obtain RFCs.















Internet Activities Board                                      [Page 15]

RFC 1130                     IAB Standards                  October 1989


7.5.  Other Sources for Requests for Comments

      NSF Network Service Center (NNSC)

         NSF Network Service Center (NNSC)
         BBN Systems and Technology Corporation
         10 Moulton St.
         Cambridge, MA 02238

         617-873-3400

         [e-mail]

      NSF Network Information Service (NIS)

         NSF Network Information Service
         Merit Inc.
         University of Michigan
         1075 Beal Avenue
         Ann Arbor, MI 48109

         313-763-4897

         [e-mail]

      CSNET Coordination and Information Center (CIC)

         CSNET Coordination and Information Center
         Bolt Beranek and Newman Inc.
         10 Moulton Street
         Cambridge, MA 02238

         617-873-2777

         [e-mail]

8.  Security Considerations:

   Security issues are not addressed in this memo.












Internet Activities Board                                      [Page 16]

RFC 1130                     IAB Standards                  October 1989


9.  Author's Address:

   Jon Postel
   USC/Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, CA 90292

   Phone: [phone]

   Email: [e-mail]









































Internet Activities Board                                      [Page 17]