📄 rfc1200.txt
字号:
1165 - Network Time Protocol (NTP) over the OSI Remote Operations Service An Experimental protocol. 1164 - Application of the Border Gateway Protocol in the Internet A Proposed Standard protocol. 1163 - A Border Gateway Protocol (BGP) A Proposed Standard protocol.Internet Activities Board [Page 19]RFC 1200 IAB Standards April 1991 1162 - Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base This memo does not specify a standard for the Internet community. However, after experimentation, if sufficient consensus is reached in the Internet community, then a subsequent revision of this document... 1161 - SNMP over OSI An experimental means for running the Simple Network Management Protocol (SNMP) over OSI transports. 1160 - The Internet Activities Board This is an information document and does not specify any level of standard. 1159 - Message Send Protocol An Experimental protocol.6.1.2. Other Changes: The following are changes to protocols listed in the previous edition. 1213 - Management Information Base for Network Management of TCP/IP-based internets: MIB-II Advanced to Draft Standard protocol. 1196 - The Finger User Information Protocol Advanced to Draft Standard protocol. 1191 - Path MTU Discovery Advanced to Proposed Standard protocol. 1189 - The Common Management Information Services and Protocols for the Internet Moved to Proposed Standard protocol.Internet Activities Board [Page 20]RFC 1200 IAB Standards April 1991 1188 - A Proposed Standard for the Transmission of IP Datagrams over FDDI Networks Advanced to Draft Standard protocol. 1184 - Telnet Linemode Option Advanced to Draft Standard protocol. 1171 - The Point-to-Point Protocol for the Transmission of Multi-Protocol Datagrams Over Point-to-Point Links Advanced to Draft Standard protocol. 1163 - A Border Gateway Protocol (BGP) Advanced to Proposed Standard protocol.Internet Activities Board [Page 21]RFC 1200 IAB Standards April 19916.2. Standard ProtocolsProtocol Name Status RFC======== ===================================== ============== ====-------- Assigned Numbers Required 1060-------- 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 1112UDP User Datagram Protocol Recommended 768TCP Transmission Control Protocol Recommended 793SMI Structure of Management Information Recommended 1155MIB Management Information Base Recommended 1156SNMP Simple Network Management Protocol Recommended 1157DOMAIN 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 868Notes: IGMP -- The Internet Activities Board intends to move towards general adoption of IP multicasting, as a more efficient solution than broadcasting for many applications. The host interface has been standardized in RFC-1112; however, multicast-routing gateways are in the experimental stage and are not widely available. An Internet host should support all of RFC-1112, except for the IGMP protocol itself which is optional; see RFC-1122 for more details. Even without IGMP, implementation of RFC-1112 will provide an important advance: IP-layer access to local network multicast addressing. ItInternet Activities Board [Page 22]RFC 1200 IAB Standards April 1991 is expected that IGMP will become recommended for all hosts and gateways at some future date. SMI, MIB, SNMP -- The Internet Activities Board recommends that all IP and TCP implementations be network manageable. At the current time, this implies implementation of the Internet MIB (RFC-1156), the MIB extension MIB-II (RFC-1158, a Draft Standard), and at least the recommended management protocol SNMP (RFC-1157).6.3. Network-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 Hyperchannel 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 1103IP-IPX Transmission of 802.2 over IPX Networks Elective 1132Notes: It is expected that a system will support one or more physical networks and for each physical network supported the appropriate protocols from the above list must be supported. That is, it is elective to support any particular type of physical network, and for the physical networks actually supported it is required that they be supported exactly according to the protocols in the above list. See also the Host and Gateway Requirements RFCs for more specific information on network-specific ("link layer") protocols.Internet Activities Board [Page 23]RFC 1200 IAB Standards April 19916.4. Draft Standard ProtocolsProtocol Name Status RFC======== ===================================== =============== ====FINGER Finger Protocol Elective 1196*IP-FDDI Internet Protocol on FDDI Networks Elective 1188*TOPT-LINE Telnet Linemode Option Elective 1184*MIB-II MIB-II Elective 1213*PPP Point to Point Protocol Elective 1171*-------- Mail Privacy: Procedures Elective 1113-------- Mail Privacy: Key Management Elective 1114-------- Mail Privacy: Algorithms Elective 1115BOOTP Bootstrap Protocol Recommended 951,1048,1084RIP Routing Information Protocol Elective 1058TP-TCP ISO Transport Service on top of the TCP Elective 1006NICNAME WhoIs Protocol Elective 954TFTP Trivial File Transfer Protocol Elective 783Notes: RIP -- The Routing Information Protocol (RIP) is widely implemented and used in the Internet. However, both implementors and users should be aware that RIP has some serious technical limitations as a routing protocol. The IETF is currently developing several candidates for a new standard "open" routing protocol with better properties than RIP. The IAB urges the Internet community to track these developments, and to implement the new protocol when it is standardized; improved Internet service will result for many users. TP-TCP -- As OSI protocols become more widely implemented and used, there will be an increasing need to support interoperation with the TCP/IP protocols. The Internet Engineering Task Force is formulating strategies for interoperation. RFC-1006 provides one interoperation mode, in which TCP/IP is used to emulate TP0 in order to support OSI applications. Hosts that wish to run OSI connection-oriented applications in this mode should use the procedure described in RFC- 1006. In the future, the IAB expects that a major portion of the Internet will support both TCP/IP and OSI (inter-)network protocols in parallel, and it will then be possible to run OSI applications across the Internet using full OSI protocol "stacks". MIB-II -- This memo defines a mandatory extension to the base MIB (RFC-1156) and is a Draft Standard for the Internet community. The extensions described here are currently Elective, but when they become a standard, they will have the same status as RFC-1156, that is, Recommended. See also the note on SMI, MIB and SNMP under Standards.Internet Activities Board [Page 24]RFC 1200 IAB Standards April 1991 PPP -- Point to Point Protocol is a method of sending IP over serial lines, which are a type of physical network. It is anticipated that PPP will be advanced to the network-specific standard protocol state in the future.6.5. Proposed Standard ProtocolsProtocol Name Status RFC======== ===================================== =============== ====OIM-MIB-II OSI Internet Management: MIB-II Elective 1214*Concise-MIB Concise MIB Definitions Elective 1212*IP-SMDS IP Datagrams over the SMDS Service Elective 1209*IP-ARCNET Transmitting IP Traffic over ARCNET Networks Elective 1201*IS-IS Use of OSI IS-IS for Routing in TCP/IP Elective 1195* and Dual EnvironmentsIP-MTU Path MTU Discovery Elective 1191*CMOT Common Management Information Services Elective 1189* and Protocol over TCP/IPPPP-INIT PPP Initial Configuration Options Elective 1172*BGP Border Gateway Protocol Elective 1163,1164*IP-CMPRS Compressing TCP/IP Headers Elective 1144-------- Echo for ISO-8473 Elective 1139OSPF Open Shortest Path First Routing Elective 1131TOPT-ENV Telnet Environment Option Elective 1116*SUN-NFS Network File System Protocol Elective 1094POP3 Post Office Protocol, Version 3 Elective 1081,1082SUN-RPC Remote Procedure Call Protocol Elective 1057PCMAIL Pcmail Transport Protocol Elective 1056NFILE A File Access Protocol Elective 1037-------- Mapping between X.400(84) and RFC-822 Elective 987,1026NNTP Network News Transfer Protocol Elective 977HOSTNAME HOSTNAME Protocol Elective 953SFTP Simple File Transfer Protocol Elective 913RLP Resource Location Protocol Elective 887SUPDUP SUPDUP Protocol Elective 734Notes: IP-SMDS and IP-ARCNET -- These define methods of sending IP over particular network types. It is anticipated that these will be advanced to the network specific standard protocol state in the future.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -