📄 rfc1250.txt
字号:
Internet Activities Board [Page 17] RFC 1250 IAB Standards August 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-I Management Information Base Recommended 1156MIB-II Management Information Base-II Recommended 1213*SNMP 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 822DNS-MX Mail Routing and the Domain System Recommended 974CONTENT 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 868Applicability Statements: 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. EvenInternet Activities Board [Page 18] RFC 1250 IAB Standards August 1991 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-I, MIB-II 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-I (RFC-1156), the extensions in MIB-II (RFC-1213), 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 1188IP-IPX Transmission of 802.2 over IPX Networks Elective 1132Applicability 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.Internet Activities Board [Page 19] RFC 1250 IAB Standards August 19916.4. Draft Standard ProtocolsProtocol Name Status RFC======== ===================================== ============== =====OSPF2 Open Shortest Path First Routing V2 Elective 1247*POP3 Post Office Protocol, Version 3 Elective 1225*Concise-MIB Concise MIB Definitions Elective 1212*FINGER Finger Protocol Elective 1196IP-FDDI Internet Protocol on FDDI Networks Elective 1188TOPT-LINE Telnet Linemode Option Elective 1184PPP 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,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 783Applicability Statements: 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". 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.Internet Activities Board [Page 20] RFC 1250 IAB Standards August 19916.5. Proposed Standard ProtocolsProtocol Name Status RFC======== ===================================== ============== =====OSPF-MIB OSPF Version 2 MIB Elective 1248,1252*AT-MIB Appletalk MIB Elective 1243*OSI-UDP OSI TS on UDP Elective 1240*STD-MIBs Reassignment of Exp MIBs to Std MIBs Elective 1239*OSI-NSAP Guidelines for OSI NSAP Allocation Elective 1237*IPX-IP Tunneling IPX Traffic through IP Nets Elective 1234*DS3-MIB DS3 Interface Objects Elective 1233*DS1-MIB DS1 Interface Objects Elective 1232*802.5-MIB IEEE 802.5 Token Ring MIB Elective 1231*802.4-MIP IEEE 802.4 Token Bus MIB Elective 1230*GINT-MIB Extensions to the Generic-Interface MIB Elective 1229*PPP-EXT PPP Extensions for Bridging Elective 1220*OIM-MIB-II OSI Internet Management: MIB-II Elective 1214IP-SMDS IP Datagrams over the SMDS Service Elective 1209IP-ARCNET Transmitting IP Traffic over ARCNET Nets Elective 1201IS-IS OSI IS-IS for TCP/IP Dual Environments Elective 1195IP-MTU Path MTU Discovery Elective 1191CMOT Common Management Information Services Elective 1189 and Protocol over TCP/IPPPP-INIT PPP Initial Configuration Options Elective 1172BGP Border Gateway Protocol Elective 1163,1164IP-CMPRS Compressing TCP/IP Headers Elective 1144ISO-TS-ECHO Echo for ISO-8473 Elective 1139SUN-NFS Network File System Protocol Elective 1094SUN-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 734Applicability Statements: 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.Internet Activities Board [Page 21] RFC 1250 IAB Standards August 19916.6. Telnet OptionsFor convenience all the Telnet Options are collected here with boththeir state and status.Protocol Name Number State Status RFC======== ===================================== ============== =====TOPT-BIN Binary Transmission 0 Std Rec 856*TOPT-ECHO Echo 1 Std Rec 857*TOPT-RECN Reconnection 2 Prop Ele ...*TOPT-SUPP Suppress Go Ahead 3 Std Rec 858*TOPT-APRX Approx Message Size Negotiation 4 Prop Ele ...*TOPT-STAT Status 5 Std Rec 859*TOPT-TIM Timing Mark 6 Std Rec 860*TOPT-REM Remote Controlled Trans and Echo 7 Prop Ele 726*TOPT-OLW Output Line Width 8 Prop Ele ...*TOPT-OPS Output Page Size 9 Prop Ele ...*TOPT-OCRD Output Carriage-Return Disposition 10 Prop Ele 652*TOPT-OHT Output Horizontal Tabstops 11 Prop Ele 653*TOPT-OHTD Output Horizontal Tab Disposition 12 Prop Ele 654*TOPT-OFD Output Formfeed Disposition 13 Prop Ele 655*TOPT-OVT Output Vertical Tabstops 14 Prop Ele 656*TOPT-OVTD Output Vertical Tab Disposition 15 Prop Ele 657*TOPT-OLD Output Linefeed Disposition 16 Prop Ele 658*TOPT-EXT Extended ASCII 17 Prop Ele 698*TOPT-LOGO Logout 18 Prop Ele 727*TOPT-BYTE Byte Macro 19 Prop Ele 735*TOPT-DATA Data Entry Terminal 20 Prop Ele 1043*TOPT-SUP SUPDUP 21 Prop Ele 734*TOPT-SUPO SUPDUP Output 22 Prop Ele 749*TOPT-SNDL Send Location 23 Prop Ele 779*TOPT-TERM Terminal Type 24 Prop Ele 930*TOPT-EOR End of Record 25 Prop Ele 885*TOPT-TACACS TACACS User Identification 26 Prop Ele 927*TOPT-OM Output Marking 27 Prop Ele 933*TOPT-TLN Terminal Location Number 28 Prop Ele 946*TOPT-3270 Telnet 3270 Regime 29 Prop Ele 1041*TOPT-X.3 X.3 PAD 30 Prop Ele 1053*TOPT-NAWS Negotiate About Window Size 31 Prop Ele 1073*TOPT-TS Terminal Speed 32 Prop Ele 1079*TOPT-RFC Remote Flow Control 33 Prop Ele 1080*TOPT-LINE Linemode 34 Draft Ele 1184*TOPT-XDL X Display Location 35 Prop Ele 1096*TOPT-EXTOP Extended-Options-List 255 Std Rec 861*Internet Activities Board [Page 22] RFC 1250 IAB Standards August 19916.7. Experimental ProtocolsProtocol Name Status RFC======== ===================================== ============== =====IN-ENCAP Internet Encapsulation Protocol Limited Use 1241*CLNS-MIB CLNS-MIB Limited Use 1238*CFDP Coherent File Distribution Protocol Limited Use 1235*SNMP-DPI SNMP Distributed Program Interface Limited Use 1228*SNMP-MUX SNMP MUX Protocol and MIB Limited Use 1227*IP-AX25 IP Encapsulation of AX.25 Frames Limited Use 1226*ALERTS Managing Asynchronously Generated Alerts Limited Use 1224*MPP Message Posting Protocol Limited Use 1204ST-II Stream Protocol Limited Use 1190SNMP-BULK Bulk Table Retrieval with the SNMP Limited Use 1187DNS-RR New DNS RR Definitions Limited Use 1183NTP-OSI NTP over OSI Remote Operations Limited Use 1165MSP Message Send Protocol Limited Use 1159EHF-MAIL Encoding Header Field for Mail Elective 1154DMF-MAIL Digest Message Format for Mail Elective 1153RDP Reliable Data Protocol Limited Use 908,1151-------- Mapping between X.400(88) and RFC-822 Elective 1148TCP-ACO TCP Alternate Checksum Option Not Recommended 1146⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -