rfc1140.txt
字号:
1153 - Digest Message Format
This is a new Elective Experimental protocol.
1152 - Workshop Report: Internet Research Steering Group Workshop
on Very-High-Speed Networks
This is an information document and does not specify any
level of standard.
1151 - Version 2 of the Reliable Data Protocol (RDP)
This is an update to a Not-recommended Experimental
protocol.
1150 - FYI on FYI
This is an information document and does not specify any
level of standard.
1149 - A Standard for the Transmission of IP Datagrams on Avian
Carriers
This describes an implementation technique, and does not
Internet Activities Board [Page 14]
RFC 1140 IAB Standards May 1990
specify any level of standard.
1148 - Mapping between X.400(88) and RFC 822
This is a new Elective Experimental protocol (corrects
editing errors in 1138).
1147 - FYI on a Network Management Tool Catalog
This is an information document and does not specify any
level of standard.
1146 - TCP Alternative Checksum Options
This is a new Not-recommended Experimental protocol
(corrects editing errors in 1145).
1145 - TCP Alternate Checksum Options
This is a new Not-recommended Experimental protocol.
1144 - Compressing TCP/IP Headers for Low-Speed Serial Links
This is a new Elective Proposed Standard protocol.
1143 - The Q Method of Implementing TELNET Option Negotiation
This describes an implementation technique.
1142 - < not issued yet >
1141 - Incremental Updating of the Internet Checksum
This describes an implementation technique.
1140 - IAB Official Protocol Standards
This memo.
1139 - An Echo Function for ISO 8473
This is a new Elective Proposed Standard protocol.
1138 - Mapping between X.400(88) and RFC 822
This is a new Elective Experimental protocol (replaced by
1148).
Internet Activities Board [Page 15]
RFC 1140 IAB Standards May 1990
1137 - Mapping Between Full RFC 822 and RFC 822 with Restricted
Encoding
This is a new Elective Experimental protocol.
1136 - Administrative Domains and Routing Domains: A Model for
Routing in the Internet
This is a discussion document and does not specify any
level of standard.
1135 - The Helminthiasis of the Internet
This is a discussion document and does not specify any
level of standard.
1134 - The Point-to-Point Protocol: A Proposal for Multi-Protocol
Transmission of Datagrams Over Point-to-Point Links
This is a new Elective Proposed Standard protocol.
1133 - Routing between the NSFNET and the DDN
This is a discussion document and does not specify any
level of standard.
1132 - A Standard for the Transmission of 802.2 Packets over IPX
Networks
This is a new Elective Network-Specific Standard protocol,
that is, a full Standard for a network-specific situation.
1131 - The OSPF Specification
This is a new Elective Proposed Standard protocol.
1060 - Assigned Numbers
The status report on assigned numbers and protocol
parameters.
Internet Activities Board [Page 16]
RFC 1140 IAB Standards May 1990
6.1.2. Other Changes:
The following are changes to protocols listed in the previous
edition.
1058 - Routing Information Protocol (RIP)
Advanced to Elective Draft Standard protocol.
1045 - Versatile Message Transaction Protocol (VMTP)
Moved to Elective Experimental protocol.
1006 - ISO Transport Service on top of the TCP (TP-TCP)
Advanced to Elective Draft Standard protocol.
996 - Statistics Server (STATSRV)
Moved to Not Recommended Historic protocol.
954 - WhoIs Protocol (NICNAME)
Advanced to Elective Draft Standard protocol.
937 - Post Office Protocol, Version 2 (POP2)
Moved to Not Recommended Historic protocol.
916 - Reliable Asynchronous Transfer Protocol (RATP)
Moved to Not Recommended Historic protocol.
914 - Thinwire Protocol (THINWIRE)
Moved to Not Recommended Historic protocol.
818 - Remote Telnet Service (RTELNET)
Moved to Not Recommended Historic protocol.
569 - Network Standard Text Editor (NETED)
Moved to Not Recommended Historic protocol.
407 - Remote Job Entry (RJE)
Moved to Not Recommended Historic protocol.
Internet Activities Board [Page 17]
RFC 1140 IAB Standards May 1990
6.2. Standard Protocols
Protocol Name Status RFC
======== ===================================== ============== ====
-------- Assigned Numbers Required 1060
-------- Gateway Requirements Required 1009
-------- Host Requirements - Communications Required 1122
-------- Host Requirements - Applications Required 1123
IP Internet Protocol Required 791
as amended by:
-------- IP Subnet Extension Required 950
-------- IP Broadcast Datagrams Required 919
-------- IP Broadcast Datagrams with Subnets Required 922
ICMP Internet Control Message Protocol Required 792
IGMP Internet Group Multicast Protocol Recommended 1112
UDP User Datagram Protocol Recommended 768
TCP Transmission Control Protocol Recommended 793
SMI Structure of Management Information Recommended 1155
MIB Management Information Base Recommended 1156
SNMP Simple Network Management Protocol Recommended 1157
DOMAIN Domain Name System Recommended 1034,1035
TELNET Telnet Protocol Recommended 854
FTP File Transfer Protocol Recommended 959
SMTP Simple Mail Transfer Protocol Recommended 821
MAIL Format of Electronic Mail Messages Recommended 822
CONTENT Content Type Header Field Recommended 1049
EGP Exterior Gateway Protocol Recommended 904
ECHO Echo Protocol Recommended 862
NTP Network Time Protocol Recommended 1119
NETBIOS NetBIOS Service Protocols Elective 1001,1002
DISCARD Discard Protocol Elective 863
CHARGEN Character Generator Protocol Elective 864
QUOTE Quote of the Day Protocol Elective 865
USERS Active Users Protocol Elective 866
DAYTIME Daytime Protocol Elective 867
TIME Time Server Protocol Elective 868
Notes:
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. It
Internet Activities Board [Page 18]
RFC 1140 IAB Standards May 1990
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. This implies
implementation of the Internet MIB (RFC-1156) and at least one of the
two recommended management protocols SNMP (RFC-1157) or CMOT (RFC-
1095). It should be noted that, at this time, SNMP is a full
Internet standard and CMOT is a draft standard. See also the Host
and Gateway Requirements RFCs for more specific information on the
applicability of this standard.
6.3. Network-Specific Standard Protocols
Protocol Name Status RFC
======== ===================================== =============== ====
ARP Address Resolution Protocol Elective 826
RARP A Reverse Address Resolution Protocol Elective 903
IP-ARPA Internet Protocol on ARPANET Elective BBN 1822
IP-WB Internet Protocol on Wideband Network Elective 907
IP-X25 Internet Protocol on X.25 Networks Elective 877
IP-E Internet Protocol on Ethernet Networks Elective 894
IP-EE Internet Protocol on Exp. Ethernet Nets Elective 895
IP-IEEE Internet Protocol on IEEE 802 Elective 1042
IP-DC Internet Protocol on DC Networks Elective 891
IP-HC Internet Protocol on Hyperchannel Elective 1044
IP-ARC Internet Protocol on ARCNET Elective 1051
IP-SLIP Transmission of IP over Serial Lines Elective 1055
IP-NETBIOS Transmission of IP over NETBIOS Elective 1088
IP-FDDI Transmission of IP over FDDI Elective 1103
IP-IPX Transmission of 802.2 over IPX Networks Elective 1132
Notes:
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 1140 IAB Standards May 1990
6.4. Draft Standard Protocols
Protocol Name Status RFC
======== ===================================== =============== ====
-------- Mail Privacy: Procedures Elective 1113
-------- Mail Privacy: Key Management Elective 1114
-------- Mail Privacy: Algorithms Elective 1115
CMOT Common Management Information Services Recommended 1095
and Protocol over TCP/IP
BOOTP Bootstrap Protocol Recommended 951,1048,1084
RIP Routing Information Protocol Elective 1058
TP-TCP ISO Transport Service on top of the TCP Elective 1006
NICNAME WhoIs Protocol Elective 954
TFTP Trivial File Transfer Protocol Elective 783
Notes:
CMOT -- The Internet Activities Board recommends that all IP and TCP
implementations be network manageable. This implies implementation
of the Internet MIB (RFC-1156) and at least one of the two
recommended management protocols SNMP (RFC-1157) or CMOT (RFC-1095).
It should be noted that, at this time, SNMP is a full Internet
standard and CMOT is a draft standard. See also the Host and Router
Requirements RFCs for more specific information on the applicability
of this standard.
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".
Internet Activities Board [Page 20]
RFC 1140 IAB Standards May 1990
6.5. Proposed Standard Protocols
Protocol Name Status RFC
======== ===================================== =============== ====
MIB-II MIB-II Elective xxxx
IP-CMPRS Compressing TCP/IP Headers Elective 1144
-------- Echo for ISO-8473 Elective 1139
PPP Point to Point Protocol Elective 1134
OSPF Open Shortest Path First Routing Elective 1131
SUN-NFS Network File System Protocol Elective 1094
POP3 Post Office Protocol, Version 3 Elective 1081,1082
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -