📄 rfc1250.txt
字号:
-------- 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 1203VMTP 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.8. Informational ProtocolsProtocol Name Status RFC======= ==================================== =============== =====DIXIE DIXIE Protocol Specification Limited Use 1249*IP-X.121 IP to X.121 Address Mapping for DDN Limited Use 1236*OSI-HYPER OSI and LLC1 on HYPERchannel Limited Use 1223*HAP2 Host Access Protocol Limited Use 1221*SUBNETASGN On the Assignment of Subnet Numbers Limited Use 1219*SNMP-TRAPS Defining Traps for use with SNMP Limited Use 1215DAS Directory Assistance Service Limited Use 1202Internet Activities Board [Page 23]RFC 1250 IAB Standards August 1991MD4 MD4 Message Digest Algorithm Limited Use 1186LPDP Line Printer Daemon Protocol Limited Use 11796.9. 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 916HFEP Host - Front End Protocol Not Recommended 929*THINWIRE 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 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. Contacts: 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.EDUInternet Activities Board [Page 24]RFC 1250 IAB Standards August 1991 Vinton G. Cerf Chair of the IAB Corporation for National Research Initiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 1-703-620-8990 VCerf@NRI.RESTON.VA.US 7.1.2. Internet Engineering Task Force (IETF) Contact Contacts: Phill Gross Chair of the IETF Advanced Network and Services 100 Clearbrook Road Elmsford, NY 10523 1-914-789-5300 PGross@NRI.RESTON.VA.US Greg Vaudreuil IESG Secretary Corporation for National Research Initiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 1-703-620-8990 gvaudre@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.EDUInternet Activities Board [Page 25]RFC 1250 IAB Standards August 19917.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 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".Internet Activities Board [Page 26]RFC 1250 IAB Standards August 19917.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.MIL 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 NISC.SRI.COM, 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 MAIL-SERVER@NISC.SRI.COM andInternet Activities Board [Page 27]RFC 1250 IAB Standards August 1991 in the body of the message indicate the file name, as in "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 Information about other sources for RFCs and the procedures for copying RFCs form those sources may be found in the file "in- notes/rfc-retrieval.txt" on the host VENERA.ISI.EDU.8. 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 28]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -