📄 rfc1130.txt
字号:
protocol and above, protocols that apply to the whole Internet; and (2) network-specific protocols, generally specifications of how to do IP on particular types of networks. 5.1.2. Draft Standard Protocol The IAB is actively considering this protocol as a possible Standard Protocol. Substantial and widespread testing and comment is desired. Comments and test results should be submitted to the IAB. There is a possibility that changes will be made in a Draft Standard Protocol before it becomes a Standard Protocol.Internet Activities Board [Page 6]RFC 1130 IAB Standards October 1989 5.1.3. Proposed Protocol These are protocol proposals that may be considered by the IAB for standardization in the future. Implementation and testing by several groups is desirable. Revisions of the protocol specification are likely. 5.1.4. Experimental Protocol A system should not implement an experimental protocol unless it is participating in the experiment and has coordinated its use of the protocol with the developer of the protocol. Typically, experimental protocols are those that are developed as part of a specific ongoing research project not related to an operational service offering. While they may be proposed as a service protocol at a later stage, and thus become proposed, draft, and then standard protocols, the designation of a protocol as experimental is meant to suggest that the protocol, although perhaps mature, is not intended for operational use. 5.1.5. Historic Protocol These are protocols that are unlikely to ever become standards in the Internet either because they have been superseded by later developments or due to lack of interest. These are protocols that are at an evolutionary dead end.5.2. Definitions of Protocol Status 5.2.1. Required Protocol All systems must implement the required protocols. 5.2.2. Recommended Protocol All systems should implement the recommended protocols. 5.2.3. Elective Protocol A system may or may not implement an elective protocol. The general notion is that if you are going to do something like this, you must do exactly this. 5.2.4. Not Recommended Protocol These protocols are not recommended for general use. This may be because of their limited functionality, specialized nature, orInternet Activities Board [Page 7]RFC 1130 IAB Standards October 1989 experimental or historic state.6. The Protocols This section list the standards in groups by protocol state.6.1. Recent Changes: The Host Requirements [RFC-1122, RFC-1123] is now a Required Standard. The Network Time Protocol [RFC-1119] is now a Recommended Standard. The Internet Group Multicast Protocol [RFC-1112] is now a Recommended Standard. The mail Content Type Header Field [RFC-1049] is now a Recommended Standard. The "Internet Numbers" list was recently issued as RFC-1117. The Telnet Linemode Option [RFC-1116] is now a Elective Proposed standard. The mail Privacy procedures [RFC-1113, RFC-1114, and RFC-1115] are now Elective Draft Standards. The Border Gateway Protocol [RFC-1105] is a Not-Recommended Experimental protocol. A procedure for sending IP over FDDI networks [RFC-1103] is now a Specific Standard. The Trivial File Transfer Protocol [RFC-783] is now a Elective Draft Standard.Internet Activities Board [Page 8]RFC 1130 IAB Standards October 19896.2. Standard ProtocolsProtocol Name Status RFC-------- ---- ------ --- Assigned Numbers Required 1010 Gateway Requirements Required 1009 Host Requirements - Communications Required 1122 Host Requirements - Applications Required 1123IP 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 792IGMP Internet Group Multicast Protocol Recommended 1054UDP 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 822CONTENT Content Type Header Field Recommended 1049EGP Exterior Gateway Protocol Recommended 904ECHO Echo Protocol Recommended 862NTP Network Time Protocol Recommended 1119NETBIOS NetBIOS Service Protocols Elective 1001,1002DISCARD 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 9]RFC 1130 IAB Standards October 19896.3. 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 1088IP-FDDI Transmission of IP over FDDI Elective 1103Note: 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.Internet Activities Board [Page 10]RFC 1130 IAB Standards October 19896.4. Draft Standard ProtocolsProtocol Name Status RFC-------- ---- ------ --- Mail Privacy: Procedures Elective 1113 Mail Privacy: Key Management Elective 1114 Mail Privacy: Algorithms Elective 1115SNMP 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 1065BOOTP Bootstrap Protocol Recommended 951,1048,1084TFTP Trivial File Transfer Protocol Elective 783The 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 implementationsthat are network manageable are expected to adopt and implement at leastone of these two Internet Draft Standards. The motivation for thisposition is discussed in RFCs 1052 and 1109.Internet Activities Board [Page 11]RFC 1130 IAB Standards October 19896.5. 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 953
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -