📄 rfc1780.txt
字号:
level of standard. 1743 - IEEE 802.5 MIB using SMIv2 A Draft Standard protocol. 1742 - AppleTalk Management Information Base II A Proposed Standard protocol. 1741 - MIME Content Type for BinHex Encoded Files This is an information document and does not specify any level of standard. 1740 - MIME Encapsulation of Macintosh Files - MacMIME A Proposed Standard protocol. 1739 - A Primer On Internet and TCP/IP Tools This is an information document and does not specify any level of standard. 1738 - Uniform Resource Locators (URL) A Proposed Standard protocol. 1737 - Functional Requirements for Uniform Resource Names This is an information document and does not specify any level of standard. 1736 - Functional Recommendations for Internet Resource Locators This is an information document and does not specify any level of standard.Internet Architecture Board [Page 18]RFC 1780 Internet Standards March 1995 1735 - NBMA Address Resolution Protocol (NARP) An Experimental protocol. 1734 - POP3 AUTHentication command A Proposed Standard protocol. 1733 - Distributed Electronic Mail Models In IMAP4 This is an information document and does not specify any level of standard. 1732 - IMAP4 Compatibility with IMAP2 and IMAP2bis This is an information document and does not specify any level of standard. 1731 - IMAP4 Authentication Mechanisms A Proposed Standard protocol. 1730 - Internet Message Access Protocol - Version 4 A Proposed Standard protocol. 1729 - Using the Z39.50 Information Retrieval Protocol This is an information document and does not specify any level of standard. 1728 - Resource Transponders This is an information document and does not specify any level of standard. 1727 - A Vision of an Integrated Internet Information Service This is an information document and does not specify any level of standard. 1726 - Technical Criteria for Choosing IP The Next Generation (IPng) This is an information document and does not specify any level of standard.Internet Architecture Board [Page 19]RFC 1780 Internet Standards March 1995 1719 - A Direction for IPng This is an information document and does not specify any level of standard.6.1.2. Other Changes: The following are changes to protocols listed in the previous edition. 1657 - Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2904 - Exterior Gateway Protocol Elevated to Draft Standard. 1009 - Gateway Requirements Moved to Historic.Internet Architecture Board [Page 20]RFC 1780 Internet Standards March 19956.2. Standard ProtocolsProtocol Name Status RFC STD *======== ===================================== ======== ==== === =-------- Internet Official Protocol Standards Req 1720 1-------- Assigned Numbers Req 1700 2-------- Host Requirements - Communications Req 1122 3-------- Host Requirements - Applications Req 1123 3IP Internet Protocol Req 791 5 as amended by:---------------- IP Subnet Extension Req 950 5-------- IP Broadcast Datagrams Req 919 5-------- IP Broadcast Datagrams with Subnets Req 922 5ICMP Internet Control Message Protocol Req 792 5IGMP Internet Group Multicast Protocol Rec 1112 5UDP User Datagram Protocol Rec 768 6TCP Transmission Control Protocol Rec 793 7TELNET Telnet Protocol Rec 854,855 8FTP File Transfer Protocol Rec 959 9SMTP Simple Mail Transfer Protocol Rec 821 10MAIL Format of Electronic Mail Messages Rec 822 11CONTENT Content Type Header Field Rec 1049 11NTPV2 Network Time Protocol (Version 2) Rec 1119 12DOMAIN Domain Name System Rec 1034,1035 13DNS-MX Mail Routing and the Domain System Rec 974 14SNMP Simple Network Management Protocol Rec 1157 15SMI Structure of Management Information Rec 1155 16Concise-MIB Concise MIB Definitions Rec 1212 16MIB-II Management Information Base-II Rec 1213 17NETBIOS NetBIOS Service Protocols Ele 1001,1002 19ECHO Echo Protocol Rec 862 20DISCARD Discard Protocol Ele 863 21CHARGEN Character Generator Protocol Ele 864 22QUOTE Quote of the Day Protocol Ele 865 23USERS Active Users Protocol Ele 866 24DAYTIME Daytime Protocol Ele 867 25TIME Time Server Protocol Ele 868 26TFTP Trivial File Transfer Protocol Ele 1350 33RIP Routing Information Protocol Ele 1058 34TP-TCP ISO Transport Service on top of the TCP Ele 1006 35ETHER-MIB Ethernet MIB Ele 1643 50PPP Point-to-Point Protocol (PPP) Ele 1661 51PPP-HDLC PPP in HDLC Framing Ele 1662 51[Note: an asterisk at the end of a line indicates a change from theprevious edition of this document.]Internet Architecture Board [Page 21]RFC 1780 Internet Standards March 1995Applicability Statements: IGMP -- The Internet Architecture 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. It is expected that IGMP will become recommended for all hosts and gateways at some future date. SMI, MIB-II SNMP -- The Internet Architecture Board recommends that all IP and TCP implementations be network manageable. At the current time, this implies implementation of the Internet MIB-II (RFC-1213), and at least the recommended management protocol SNMP (RFC-1157). 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 devpeloping 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".Internet Architecture Board [Page 22]RFC 1780 Internet Standards March 19956.3. Network-Specific Standard ProtocolsAll Network-Specific Standards have Elective status.Protocol Name State RFC STD *======== ===================================== ===== ===== === =IP-ATM Classical IP and ARP over ATM Prop 1577IP-FR Multiprotocol over Frame Relay Draft 1490ATM-ENCAP Multiprotocol Encapsulation over ATM Prop 1483IP-TR-MC IP Multicast over Token-Ring LANs Prop 1469IP-FDDI Transmission of IP and ARP over FDDI Net Std 1390 36IP-HIPPI IP and ARP on HIPPI Prop 1374IP-X.25 X.25 and ISDN in the Packet Mode Draft 1356IP-SMDS IP Datagrams over the SMDS Service Draft 1209IP-FDDI Internet Protocol on FDDI Networks Draft 1188ARP Address Resolution Protocol Std 826 37RARP A Reverse Address Resolution Protocol Std 903 38IP-ARPA Internet Protocol on ARPANET Std BBN1822 39IP-WB Internet Protocol on Wideband Network Std 907 40IP-E Internet Protocol on Ethernet Networks Std 894 41IP-EE Internet Protocol on Exp. Ethernet Nets Std 895 42IP-IEEE Internet Protocol on IEEE 802 Std 1042 43IP-DC Internet Protocol on DC Networks Std 891 44IP-HC Internet Protocol on Hyperchannel Std 1044 45IP-ARC Transmitting IP Traffic over ARCNET Nets Std 1201 46IP-SLIP Transmission of IP over Serial Lines Std 1055 47IP-NETBIOS Transmission of IP over NETBIOS Std 1088 48IP-IPX Transmission of 802.2 over IPX Networks Std 1132 49[Note: an asterisk at the end of a line indicates a change from theprevious edition of this document.]Applicability Statements: 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.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -