📄 rfc1100.txt
字号:
RFC 1100 IAB Standards April 19896. The Protocols6.1. Standard ProtocolsProtocol Name Status RFC-------- ---- ------ --- Assigned Numbers Required 1010 Gateway Requirements Required 1009IP Internet Protocol Required 791 as amended by: IP Subnet Extension Required 950 IP Broadcast Datagrams Required 919 IP Broadcast Datagrams with Subnets Required 922ICMP Internet Control Message Protocol Required 792UDP User Datagram Protocol Recommended 768TCP Transmission Control Protocol Recommended 793DOMAIN Domain Name System Recommended 1034,1035TELNET Telnet Protocol Recommended 854FTP File Transfer Protocol Recommended 959SMTP Simple Mail Transfer Protocol Recommended 821MAIL Format of Electronic Mail Messages Recommended 822EGP Exterior Gateway Protocol Recommended 904NETBIOS NetBIOS Service Protocols Elective 1001,1002ECHO Echo Protocol Recommended 862DISCARD Discard Protocol Elective 863CHARGEN Character Generator Protocol Elective 864QUOTE Quote of the Day Protocol Elective 865USERS Active Users Protocol Elective 866DAYTIME Daytime Protocol Elective 867TIME Time Server Protocol Elective 868Internet Activities Board [Page 8]RFC 1100 IAB Standards April 19896.2. Specific Standard ProtocolsProtocol Name Status RFC-------- ---- ------ ---ARP Address Resolution Protocol Elective 826RARP A Reverse Address Resolution Protocol Elective 903IP-ARPA Internet Protocol on ARPANET Elective BBN 1822IP-WB Internet Protocol on Wideband Network Elective 907IP-X25 Internet Protocol on X.25 Networks Elective 877IP-E Internet Protocol on Ethernet Networks Elective 894IP-EE Internet Protocol on Exp. Ethernet Nets Elective 895IP-IEEE Internet Protocol on IEEE 802 Elective 1042IP-DC Internet Protocol on DC Networks Elective 891IP-HC Internet Protocol on Hyperchannnel Elective 1044IP-ARC Internet Protocol on ARCNET Elective 1051IP-SLIP Transmission of IP over Serial Lines Elective 1055IP-NETBIOS Transmission of IP over NETBIOS Elective 1088Note: It is expected that a system will support one or more physicalnetworks and for each physical network supported the appropriateprotocols from the above list must be supported. That is, it iselective to support any particular type of physical network, and for thephysical networks actually supported it is required that they besupported exactly according to the protocols in the above list.6.3. Draft Standard ProtocolsProtocol Name Status RFC-------- ---- ------ ---SNMP Simple Network Management Protocol Recommended 1098CMOT Common Management Information Services Recommended 1095 and Protocol over TCP/IPMIB Management Information Base Recommended 1066SMI Structure of Management Information Recommended 1065NTP Network Time Protocol Elective 1059IGMP Internet Group Multicast Protocol Recommended 1054BOOTP Bootstrap Protocol Recommended 951,1048,1084The Internet Activities Board has designated two different networkmanagement protocols with the same status of "Draft Standard" and"Recommended". The two protocols are the Common Management InformationServices and Protocol over TCP/IP (CMOT) [RFC-1095] and the SimpleNetwork Management Protocol (SNMP) [RFC-1098]. The IAB intends each ofthese two protocols to receive the attention of implementers andexperimenters. The IAB seeks reports of experience with these twoprotocols from system builders and users. By this action, the IABrecommends that all IP and TCP implementations be network manageable(e.g., implement the Internet MIB [RFC-1066], and that implementationsInternet Activities Board [Page 9]RFC 1100 IAB Standards April 1989that are network manageable are expected to adopt and implement at leastone of these two Internet Draft Standards.6.4. Proposed ProtocolsProtocol Name Status RFC-------- ---- ------ ---SUN-NFS Network File System Protocol Elective 1094POP3 Post Office Protocol, Version 3 Elective 1081,1082RIP Routing Information Protocol Elective 1058SUN-RPC Remote Procedure Call Protocol Elective 1057PCMAIL Pcmail Transport Protocol Elective 1056VMTP Versatile Message Transaction Protocol Elective 1045NFILE A File Access Protocol Elective 1037 Mapping between X.400 and RFC-822 Elective 987,1026STATSRV Statistics Server Elective 996NNTP Network News Transfer Protocol Elective 977NICNAME WhoIs Protocol Elective 954HOSTNAME HOSTNAME Protocol Elective 953POP2 Post Office Protocol, Version 2 Elective 937SFTP Simple File Transfer Protocol Elective 913RLP Resource Location Protocol Elective 887RTELNET Remote Telnet Service Elective 818TFTP Trivial File Transfer Protocol Elective 783FINGER Finger Protocol Elective 742SUPDUP SUPDUP Protocol Elective 734NETED Network Standard Text Editor Elective 569RJE Remote Job Entry Elective 407Internet Activities Board [Page 10]RFC 1100 IAB Standards April 19896.5. Experimental ProtocolsProtocol Name Status RFC-------- ---- ------ ---IP-DVMRP IP Distance Vector Multicast Routing Not Recommended 1075IP-MTU IP MTU Discovery Options Not Recommended 1063NETBLT Bulk Data Transfer Protocol Not Recommended 998IMAP2 Interactive Mail Access Protocol Not Recommended 1064COOKIE-JAR Authentication Scheme Not Recommended 1004IRTP Internet Reliable Transaction Protocol Not Recommended 938AUTH Authentication Service Not Recommended 931RATP Reliable Asynchronous Transfer Protocol Not Recommended 916THINWIRE Thinwire Protocol Not Recommended 914LDP Loader Debugger Protocol Not Recommended 909RDP Reliable Data Protocol Not Recommended 908ST Stream Protocol Not Recommended IEN 119NVP-II Network Voice Protocol Not Recommended ISI memo6.6. Historic ProtocolsProtocol Name Status RFC-------- ---- ------ ---SGMP Simple Gateway Monitoring Protocol Not Recommended 1028HEMS High Level Entity Management Protocol Not Recommended 1021HMP Host Monitoring Protocol Not Recommended 869GGP Gateway Gateway Protocol Not Recommended 823CLOCK DCNET Time Server Protocol Not Recommended 778MPM Internet Message Protocol Not Recommended 759NETRJS Remote Job Service Elective 740XNET Cross Net Debugger Elective IEN 158NAMESERVER Host Name Server Protocol Not Recommended IEN 116MUX Multiplexing Protocol Not Recommended IEN 90GRAPHICS Graphics Protocol Not Recommended NIC 24308Internet Activities Board [Page 11]RFC 1100 IAB Standards April 19897. Contacts7.1. Internet Activities Board Contact Contact: Jon Postel Deputy Internet Architect USC Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292-6695 1-213-822-1511 Postel@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 the Deputy Internet Architect.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 JKRey@ISI.EDU 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 in preparation) and "Gateway Requirements" (RFC-1009).Internet Activities Board [Page 12]RFC 1100 IAB Standards April 1989 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 Contact Contact: SRI International DDN Network Information Center 333 Ravenswood Avenue Menlo Park, CA 94025 1-800-235-3155 1-415-859-3695 NIC@SRI-NIC.ARPA 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 SRI-NIC.ARPA with the pathname RFC:RFCnnnn.TXT where "nnnn" refers to the number of the RFC. A listInternet Activities Board [Page 13]RFC 1100 IAB Standards April 1989 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@SRI-NIC.ARPA 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 SRI-NIC.ARPA computer following the same procedures used to obtain RFCs.Author's Address: Jon Postel USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (213) 822-1511 Email: Postel@ISI.EDUInternet Activities Board [Page 14]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -