📄 rfc1200.txt
字号:
Internet Activities Board [Page 25]RFC 1200 IAB Standards April 19916.6. Experimental ProtocolsProtocol Name Status RFC======== ===================================== =============== ====MPP Message Posting Protocol Limited Use 1204*ST-II Stream Protocol Limited Use 1190*SNMP-BULK Bulk Table Retrieval with the SNMP Limited Use 1187*DNS-RR New DNS RR Definitions Limited Use 1183*NTP-OSI NTP over OSI Remote Operations Limited Use 1165*MSP Message Send Protocol Limited Use 1159*EHF-MAIL Encoding Header Field for Mail Elective 1154DMF-MAIL Digest Message Format for Mail Elective 1153RDP Reliable Data Protocol Limited Use 908,1151-------- Mapping between X.400(88) and RFC-822 Elective 1148TCP-ACO TCP Alternate Checksum Option Not Recommended 1146-------- Mapping full 822 to Restricted 822 Elective 1137IP-DVMRP IP Distance Vector Multicast Routing Not Recommended 1075TCP-LDP TCP Extensions for Long Delay Paths Limited Use 1072IMAP2 Interactive Mail Access Protocol Limited Use 1176,1064IMAP3 Interactive Mail Access Protocol Limited Use 1203*VMTP Versatile Message Transaction Protocol Elective 1045COOKIE-JAR Authentication Scheme Not Recommended 1004NETBLT Bulk Data Transfer Protocol Not Recommended 998IRTP Internet Reliable Transaction Protocol Not Recommended 938AUTH Authentication Service Not Recommended 931LDP Loader Debugger Protocol Not Recommended 909NVP-II Network Voice Protocol Limited Use ISI-memoPVP Packet Video Protocol Limited Use ISI-memo6.7. Informational ProtocolsProtocol Name RFC======= ===================================== ====SNMP-TRAPS A Convention for Defining Traps for use with SNMP 1215*DAS Directory Assistance Service 1202*------- FYI on the X Window System 1198*ODA Office Document Architecture 1197*MD4 MD4 Message Digest Algorithm 1186*LPDP Line Printer Daemon Protocol 1179*Internet Activities Board [Page 26]RFC 1200 IAB Standards April 19916.8. Historic ProtocolsProtocol Name Status RFC======= ===================================== =============== ====SGMP Simple Gateway Monitoring Protocol Not Recommended 1028HEMS High Level Entity Management Protocol Not Recommended 1021STATSRV Statistics Server Not Recommended 996POP2 Post Office Protocol, Version 2 Not Recommended 937RATP Reliable Asynchronous Transfer Protocol Not Recommended 916THINWIRE Thinwire Protocol Not Recommended 914HMP Host Monitoring Protocol Not Recommended 869GGP Gateway Gateway Protocol Not Recommended 823RTELNET Remote Telnet Service Not Recommended 818CLOCK DCNET Time Server Protocol Not Recommended 778MPM Internet Message Protocol Not Recommended 759NETRJS Remote Job Service Not Recommended 740NETED Network Standard Text Editor Not Recommended 569RJE Remote Job Entry Not Recommended 407XNET Cross Net Debugger Not Recommended IEN-158NAMESERVER Host Name Server Protocol Not Recommended IEN-116MUX Multiplexing Protocol Not Recommended IEN-90GRAPHICS Graphics Protocol Not Recommended NIC-243087. Contacts7.1. IAB, IETF, and IRTF Contacts 7.1.1. Internet Activities Board (IAB) Contact Contact: Bob Braden Executive Director of the IAB USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292-6695 1-213-822-1511 Braden@ISI.EDU Please send your comments about this list of protocols and especially about the Draft Standard Protocols to the Internet Activities Board care of Bob Braden, IAB Executive Director.Internet Activities Board [Page 27]RFC 1200 IAB Standards April 1991 7.1.2. Internet Engineering Task Force (IETF) Contact Contact: Phill Gross Chair of the IETF Corporation for National Research Initiatives (NRI) 1895 Preston White Drive, Suite 100 Reston, VA 22091 1-703-620-8990 PGross@NRI.RESTON.VA.US 7.1.3. Internet Research Task Force (IRTF) Contact Contact: David D. Clark Chair of the IRTF Massachusetts Institute of Technology Laboratory for Computer Science 545 Main Street Cambridge, MA 02139 1-617-253-6003 ddc@LCS.MIT.EDU7.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 IANA@ISI.EDU The protocol standards are managed for the IAB by the Internet Assigned Numbers Authority. Please refer to the documents "Assigned Numbers" (RFC-1060) and "Official Internet Protocols" (RFC-1011) for further informationInternet Activities Board [Page 28]RFC 1200 IAB Standards April 1991 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 Postel@ISI.EDU 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.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 NIC@NIC.DDN.MILInternet Activities Board [Page 29]RFC 1200 IAB Standards April 1991 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 SERVICE@NIC.DDN.MIL and in the subject field of the message indicate the file name, as in "Subject: SEND RFC:RFCnnnn.TXT". Some RFCs are now available in PostScript, these may be obtained from the NIC in a similar fashion by substituting ".PS" for ".TXT". 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.7.5. Other Sources for Requests for Comments 7.5.1. NSF Network Service Center (NNSC) NSF Network Service Center (NNSC) BBN Laboratories, Inc. 10 Moulton St. Cambridge, MA 02238 617-873-3400 NNSC@NNSC.NSF.NET 7.5.2. NSF Network Information Service (NIS) NSF Network Information Service Merit Computer Network University of Michigan 1075 Beal Avenue Ann Arbor, MI 48109 313-763-4897 INFO@NIS.NSF.NETInternet Activities Board [Page 30]RFC 1200 IAB Standards April 1991 7.5.3. CSNET Coordination and Information Center (CIC) CSNET Coordination and Information Center BBN Systems and Technologies Corporation 10 Moulton Street Cambridge, MA 02238 617-873-2777 INFO@SH.CS.NET8. Security Considerations Security issues are not addressed in this memo.9. Author's Address Jon Postel USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: 213-822-1511 Fax: 213-823-6714 Email: Postel@ISI.EDUInternet Activities Board [Page 31]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -