📄 rfc1200.txt
字号:
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 Protocols
Protocol 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 Environments
IP-MTU Path MTU Discovery Elective 1191*
CMOT Common Management Information Services Elective 1189*
and Protocol over TCP/IP
PPP-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 1139
OSPF Open Shortest Path First Routing Elective 1131
TOPT-ENV Telnet Environment Option Elective 1116*
SUN-NFS Network File System Protocol Elective 1094
POP3 Post Office Protocol, Version 3 Elective 1081,1082
SUN-RPC Remote Procedure Call Protocol Elective 1057
PCMAIL Pcmail Transport Protocol Elective 1056
NFILE A File Access Protocol Elective 1037
-------- Mapping between X.400(84) and RFC-822 Elective 987,1026
NNTP Network News Transfer Protocol Elective 977
HOSTNAME HOSTNAME Protocol Elective 953
SFTP Simple File Transfer Protocol Elective 913
RLP Resource Location Protocol Elective 887
SUPDUP SUPDUP Protocol Elective 734
Notes:
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 25]
RFC 1200 IAB Standards April 1991
6.6. Experimental Protocols
Protocol Name Status RFC
======== ===================================== =============== ====
MPP Message Posting Protocol Limited Use 1204*
ST-II Stream Protocol Limited Use 1190*
SNMP-BULK Bulk Table Retrieval with the SNMP Limited Use 1187*
DNS-RR New DNS RR Definitions Limited Use 1183*
NTP-OSI NTP over OSI Remote Operations Limited Use 1165*
MSP Message Send Protocol Limited Use 1159*
EHF-MAIL Encoding Header Field for Mail Elective 1154
DMF-MAIL Digest Message Format for Mail Elective 1153
RDP Reliable Data Protocol Limited Use 908,1151
-------- Mapping between X.400(88) and RFC-822 Elective 1148
TCP-ACO TCP Alternate Checksum Option Not Recommended 1146
-------- Mapping full 822 to Restricted 822 Elective 1137
IP-DVMRP IP Distance Vector Multicast Routing Not Recommended 1075
TCP-LDP TCP Extensions for Long Delay Paths Limited Use 1072
IMAP2 Interactive Mail Access Protocol Limited Use 1176,1064
IMAP3 Interactive Mail Access Protocol Limited Use 1203*
VMTP Versatile Message Transaction Protocol Elective 1045
COOKIE-JAR Authentication Scheme Not Recommended 1004
NETBLT Bulk Data Transfer Protocol Not Recommended 998
IRTP Internet Reliable Transaction Protocol Not Recommended 938
AUTH Authentication Service Not Recommended 931
LDP Loader Debugger Protocol Not Recommended 909
NVP-II Network Voice Protocol Limited Use ISI-memo
PVP Packet Video Protocol Limited Use ISI-memo
6.7. Informational Protocols
Protocol Name RFC
======= ===================================== ====
SNMP-TRAPS A Convention for Defining Traps for use with SNMP 1215*
DAS Directory Assistance Service 1202*
------- FYI on the X Window System 1198*
ODA Office Document Architecture 1197*
MD4 MD4 Message Digest Algorithm 1186*
LPDP Line Printer Daemon Protocol 1179*
Internet Activities Board [Page 26]
RFC 1200 IAB Standards April 1991
6.8. Historic Protocols
Protocol Name Status RFC
======= ===================================== =============== ====
SGMP Simple Gateway Monitoring Protocol Not Recommended 1028
HEMS High Level Entity Management Protocol Not Recommended 1021
STATSRV Statistics Server Not Recommended 996
POP2 Post Office Protocol, Version 2 Not Recommended 937
RATP Reliable Asynchronous Transfer Protocol Not Recommended 916
THINWIRE Thinwire Protocol Not Recommended 914
HMP Host Monitoring Protocol Not Recommended 869
GGP Gateway Gateway Protocol Not Recommended 823
RTELNET Remote Telnet Service Not Recommended 818
CLOCK DCNET Time Server Protocol Not Recommended 778
MPM Internet Message Protocol Not Recommended 759
NETRJS Remote Job Service Not Recommended 740
NETED Network Standard Text Editor Not Recommended 569
RJE Remote Job Entry Not Recommended 407
XNET Cross Net Debugger Not Recommended IEN-158
NAMESERVER Host Name Server Protocol Not Recommended IEN-116
MUX Multiplexing Protocol Not Recommended IEN-90
GRAPHICS Graphics Protocol Not Recommended NIC-24308
7. Contacts
7.1. IAB, IETF, and IRTF Contacts
7.1.1. Internet Activities Board (IAB) Contact
Contact:
Bob Braden
Executive Director of the IAB
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
1-213-822-1511
Braden@ISI.EDU
Please send your comments about this list of protocols and especially
about the Draft Standard Protocols to the Internet Activities Board
care of Bob Braden, IAB Executive Director.
Internet Activities Board [Page 27]
RFC 1200 IAB Standards April 1991
7.1.2. Internet Engineering Task Force (IETF) Contact
Contact:
Phill Gross
Chair of the IETF
Corporation for National Research Initiatives (NRI)
1895 Preston White Drive, Suite 100
Reston, VA 22091
1-703-620-8990
PGross@NRI.RESTON.VA.US
7.1.3. Internet Research Task Force (IRTF) Contact
Contact:
David D. Clark
Chair of the IRTF
Massachusetts Institute of Technology
Laboratory for Computer Science
545 Main Street
Cambridge, MA 02139
1-617-253-6003
ddc@LCS.MIT.EDU
7.2. Internet Assigned Numbers Authority Contact
Contact:
Joyce K. Reynolds
Internet Assigned Numbers Authority
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
1-213-822-1511
IANA@ISI.EDU
The protocol standards are managed for the IAB by the Internet
Assigned Numbers Authority.
Please refer to the documents "Assigned Numbers" (RFC-1060) and
"Official Internet Protocols" (RFC-1011) for further information
Internet Activities Board [Page 28]
RFC 1200 IAB Standards April 1991
about the status of protocol documents. There are two documents that
summarize the requirements for host and gateways in the Internet,
"Host Requirements" (RFC-1122 and RFC-1123) and "Gateway
Requirements" (RFC-1009).
How to obtain the most recent edition of this "IAB Official
Protocol Standards" memo:
The file "in-notes/iab-standards.txt" may be copied via FTP
from the VENERA.ISI.EDU computer using the FTP username
"anonymous" and FTP password "guest".
7.3. Request for Comments Editor Contact
Contact:
Jon Postel
RFC Editor
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
1-213-822-1511
Postel@ISI.EDU
Documents may be submitted via electronic mail to the RFC Editor for
consideration for publication as RFC. If you are not familiar with
the format or style requirements please request the "Instructions for
RFC Authors". In general, the style of any recent RFC may be used as
a guide.
7.4. The Network Information Center and
Requests for Comments Distribution Contact
Contact:
DDN Network Information Center
SRI International
Room EJ291
333 Ravenswood Avenue
Menlo Park, CA 94025
1-800-235-3155
1-415-859-3695
NIC@NIC.DDN.MIL
Internet Activities Board [Page 29]
RFC 1200 IAB Standards April 1991
The Network Information Center (NIC) provides many information
services for the Internet community. Among them is maintaining the
Requests for Comments (RFC) library.
RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname
RFC:RFCnnnn.TXT where "nnnn" refers to the number of the RFC. A list
of all RFCs may be obtained by copying the file RFC:RFC-INDEX.TXT.
Log in with FTP username ANONYMOUS and password GUEST.
The NIC also provides an automatic mail service for those sites which
cannot use FTP. Address the request to SERVICE@NIC.DDN.MIL and in
the subject field of the message indicate the file name, as in
"Subject: SEND RFC:RFCnnnn.TXT".
Some RFCs are now available in PostScript, these may be obtained from
the NIC in a similar fashion by substituting ".PS" for ".TXT".
How to obtain the most recent edition of this "IAB Official
Protocol Standards" memo:
The file RFC:IAB-STANDARDS.TXT may b⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -