RFC1610 - Internet Official Protocol Standards(2)

时间:2005-02-14 来源: 作者: 点击:
NNTP Network News Transfer Protocol Elective 977 [Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] Applicability Statements: OSPF - RFC1370 is an
  
NNTP Network News Transfer Protocol Elective 977

[Note: an asterisk at the end of a line indicates a change from the
previous edition of this document.]

Applicability Statements:

OSPF - RFC1370 is an applicability statement for OSPF.

6.6. Telnet Options

For convenience, all the Telnet Options are collected here with both
their state and status.

Protocol Name Number State Status RFCSTD
======== ===================================== ===== ====== ==== ===
TOPT-BIN Binary Transmission 0 Std Rec 856 27
TOPT-ECHO Echo 1 Std Rec 857 28
TOPT-RECN Reconnection 2 Prop Ele ...
TOPT-SUPP Suppress Go Ahead 3 Std Rec 858 29
TOPT-APRX Approx Message Size Negotiation 4 Prop Ele ...
TOPT-STAT Status 5 Std Rec 859 30
TOPT-TIM Timing Mark 6 Std Rec 860 31
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 736
TOPT-SUPO SUPDUP Output 22 Prop Ele 749
TOPT-SNDL Send Location 23 Prop Ele 779
TOPT-TERM Terminal Type 24 Prop Ele 1091
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-RFCRemote Flow Control 33 Prop Ele 1372
TOPT-LINE Linemode 34 Draft Ele 1184
TOPT-XDL X Display Location 35 Prop Ele 1096
TOPT-ENVIR Telnet Environment Option 36 Hist Not 1408
TOPT-AUTH Telnet Authentication Option 37 Exp Ele 1416
TOPT-ENVIR Telnet Environment Option 39 Prop Ele 1572
TOPT-EXTOP Extended-Options-List 255 Std Rec 861 32

[Note: an asterisk at the end of a line indicates a change from the
previous edition of this document.]

6.7. Experimental Protocols

All Experimental protocols have the Limited Use status.

Protocol Name RFC
======== ===================================== =====
FOOBAR FTP Operation Over Big Address Records 1639*
DNS-NSAP DNS NSAP RRs 1637*
X500-CHART Charting Networks in the X.500 Directory 1609*
X500-DIR Representing IP Information in the X.500 Directory 1608*
SNMP-DPI SNMP Distributed Protocol Interface 1592
CLNP-TUBA Use of ISO CLNP in TUBA Environments 1561
REM-PRINT TPC.INT Subdomain Remote Printing - Technical 1528
EHF-MAIL Encoding Header Field for Internet Messages 1505
REM-PRT An Experiment in Remote Printing 1486
RAP Internet Route Access Protocol 1476
TP/IX TP/IX: The Next Internet 1475
X400 Routing Coordination for X.400 Services 1465
DNS Storing Arbitrary Attributes in DNS 1464
IRCP Internet Relay Chat Protocol 1459
TOS-LS Link Security TOS 1455
SIFT/UFT Sender-Initiated/Unsolicited File Transfer 1440
DIR-ARP Directed ARP 1433
TEL-SPX Telnet Authentication: SPX 1412
TEL-KER Telnet Authentication: Kerberos V4 1411
MAP-MAIL X.400 Mapping and Mail-11 1405
TRACE-IP Traceroute Using an IP Option 1393
DNS-IP Experiment in DNS Based IP Routing 1383
RMCP Remote Mail Checking Protocol 1339
TCP-HIPER TCP Extensions for High Performance 1323
MSP2 Message Send Protocol 2 1312
DSLCP Dynamically Switched Link Control 1307
-------- X.500 and Domains 1279
IN-ENCAP Internet Encapsulation Protocol 1241
CLNS-MIB CLNS-MIB 1238
CFDP Coherent File Distribution Protocol 1235
SNMP-DPI SNMP Distributed Program Interface 1228
IP-AX.25 IP Encapsulation of AX.25 Frames 1226
ALERTS Managing Asynchronously Generated Alerts 1224
MPP Message Posting Protocol 1204
ST-II Stream Protocol 1190
SNMP-BULK Bulk Table Retrieval with the SNMP 1187
DNS-RR New DNS RR Definitions 1183
IMAP2 Interactive Mail Access Protocol 1176
NTP-OSI NTP over OSI Remote Operations 1165

DMF-MAIL Digest Message Format for Mail 1153
RDP Reliable Data Protocol 908,1151
TCP-ACO TCP Alternate Checksum Option 1146
-------- Mapping full 822 to Restricted 822 1137
IP-DVMRP IP Distance Vector Multicast Routing 1075
VMTP Versatile Message Transaction Protocol 1045
COOKIE-JAR Authentication Scheme 1004
NETBLT Bulk Data Transfer Protocol 998
IRTP Internet Reliable Transaction Protocol 938
LDP Loader Debugger Protocol 909
RLP Resource Location Protocol 887
NVP-II Network Voice Protocol ISI-memo
PVP Packet Video Protocol ISI-memo

[Note: an asterisk at the end of a line indicates a change from the
previous edition of this document.]

6.8. Informational Protocols

Information protocols have no status.

Protocol Name RFC
======= ==================================== =====
IPXWAN Novell IPX Over Various WAN Media 1634*
SNPP Simple Network Paging Protocol - Version 1(b) 1568
ADSNA-IP Advanced SNA/IP: A Simple SNA Transport Protocol 1538
AUBR Appletalk Update-Based Routing Protocol... 1504
TACACS Terminal Access Control Protocol 1492
SUN-NFS Network File System Protocol 1094
SUN-RPC Remote Procedure Call Protocol Version 2 1057
GOPHER The Internet Gopher Protocol 1436
------- Data Link Switching: Switch-to-Switch Protocol 1434
LISTSERV Listserv Distribute Protocol 1429
------- Replication Requirements 1275
PCMAIL Pcmail Transport Protocol 1056
MTP Multicast Transport Protocol 1301
BSD Login BSD Login 1282
DIXIE DIXIE Protocol Specification 1249
IP-X.121 IP to X.121 Address Mapping for DDN 1236
OSI-HYPER OSI and LLC1 on HYPERchannel 1223
HAP2 Host Access Protocol 1221
SUBNETASGN On the Assignment of Subnet Numbers 1219
SNMP-TRAPS Defining Traps for use with SNMP 1215
DAS Directory Assistance Service 1202
MD4 MD4 Message Digest Algorithm 1186
LPDP Line Printer Daemon Protocol 1179

[Note: an asterisk at the end of a line indicates a change from the
previous edition of this document.]

6.9. Historic Protocols

All Historic protocols have Not Recommended status.

Protocol Name RFC
======= ===================================== =====
SNMP-MUX SNMP MUX Protocol and MIB 1227
OIM-MIB-II OSI Internet Management: MIB-II 1214
IMAP3 Interactive Mail Access Protocol Version 3 1203
SUN-RPC Remote Procedure Call Protocol Version 1 1050
802.4-MIP IEEE 802.4 Token Bus MIB 1230
CMOT Common Management Information Services 1189
-------- Mail Privacy: Procedures 1113
-------- Mail Privacy: Key Management 1114
-------- Mail Privacy: Algorithms 1115
NFILE A File Access Protocol 1037
HOSTNAME HOSTNAME Protocol 953
SFTP Simple File Transfer Protocol 913
SUPDUP SUPDUP Protocol 734
BGP Border Gateway Protocol 1163,1164
MIB-I MIB-I 1156
SGMP Simple Gateway Monitoring Protocol 1028
HEMS High Level Entity Management Protocol 1021
STATSRV Statistics Server 996
POP2 Post Office Protocol, Version 2 937
RATP Reliable Asynchronous Transfer Protocol 916
HFEP Host - Front End Protocol 929
THINWIRE Thinwire Protocol 914
HMP Host Monitoring Protocol 869
GGP Gateway Gateway Protocol 823
RTELNET Remote Telnet Service 818
CLOCK DCNET Time Server Protocol 778
MPM Internet Message Protocol 759
NETRJS Remote Job Service 740
NETED Network Standard Text Editor 569
RJE Remote Job Entry 407
XNET Cross Net Debugger IEN-158
NAMESERVER Host Name Server Protocol IEN-116
MUX Multiplexing Protocol IEN-90
GRAPHICS Graphics Protocol NIC-24308

[Note: an asterisk at the end of a line indicates a change from the
previous edition of this document.]

6.10. Obsolete Protocols

Some of the protcols listed in this memo are described in RFCs that are
obsoleted by newer RFCs. "Obsolete" or "obsoleted" is not an official
state or status of protocols. This subsection is for information only.

While it may seem to be obviously wrong to have an obsoleted RFCin the
list of standards, there may be cases when an older standard is in the
process of being replaced. This process may take a year or two.

For example, the Network Time Protocol (NTP) [RFC1119] is in its
version 2 a full Standard, and in its version 3 is a Draft Standard [RFC
1305]. Once version 3 is a full Standard, version 2 will be made
Historic.

Many obsoleted protocols are of little interest and are dropped from
this memo altogether. Some obsoleted protocols have received enough
recognition that it seems appropriate to list them under their current
status and with the following reference to their current replacement.

RFCRFCStatus Title *
==== ==== ========= =================================== =
1305 obsoletes 1119 Std /Rec Network Time Protocol (Version 2)
1533 obsoletes 1497 Draft/Rec Bootstrap Protocol
1331 obsoletes 1171 Draft/Ele Point to Point Protocol
1574 obsoletes 1139 Prop /Ele Echo for ISO-8473
1573 obsoletes 1229 Prop /Ele Extensions to the Generic-IF MIB
1559 obsoletes 1289 Prop /Ele DECNET MIB
1548 obsoletes 1331 Prop /Ele Point-to-Point Protocol (PPP)
1541 obsoletes 1531 Prop /Ele Dynamic Host Configuration Protocol
1592 obsoletes 1228 Exper/Lim SNMP Distributed Program Interface
1528 obsoletes 1486 Exper/Lim An Experiment in Remote Printing
1320 obsoletes 1186 Info / MD4 Message Digest Algorithm
1057 obsoletes 1050 Hist /Not Remote Procedure Call Version 1
1421 obsoletes 1113 Hist /Not Mail Privacy: Procedures
1422 obsoletes 1114 Hist /Not Mail Privacy: Key Management
1423 obsoletes 1115 Hist /Not Mail Privacy: Algorithms
1267 obsoletes 1163 Hist /Not Border Gateway Protocol
1268 obsoletes 1164 Hist /Not Border Gateway Protocol

Thanks to Lynn Wheeler of Britton Lee for compiling the information in
this subsection.

[Note: an asterisk at the end of a line indicates a change from the
previous edition of this document.]

7. Contacts

7.1. IAB, IETF, and IRTF Contacts

7.1.1. Internet Architecture Board (IAB) Contact

Please send your comments about this list of protocols and especially
about the Draft Standard Protocols to the Internet Architecture Board
care of Abel Winerib, IAB Executive Director.

Contacts:

Abel Winerib
Executive Director of the IAB
Bellcore
445 South St., MRE2D-298
Morristown, NJ 07960-6438

1-201-829-4454

abel@BELLCORE.COM

Christian Huitema
Chair of the IAB
INRIA, Sophia-Antipolis
2004 Route des Lucioles
BP 109
F-06561 Valbonne Cedex
France

+33 93 65 77 15

Christian.Huitema@MIRSA.INRIA.FR

7.1.2. Internet Engineering Task Force (IETF) Contact

Contacts:

Paul Mockapetris
Chair of the IETF
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695

1-310-822-1511

pvm@ISI.EDU

John Stewart
IESG Secretary
Corporation for National Research Initiatives
1895 Preston White Drive, Suite 100
Reston, VA 22091

1-703-620-8990

jstewart@CNRI.RESTON.VA.US

Steve Coya
Executive Director of the IETF
Corporation for National Research Initiatives
1895 Preston White Drive, Suite 100
Reston, VA 22091

1-703-620-8990

scoya@CNRI.RESTON.VA.US

7.1.3. Internet Research Task Force (IRTF) Contact

Contact:

Jon Postel
Chair of the IRTF
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695

1-310-822-1511

Postel@ISI.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-310-822-1511

IANA@ISI.EDU

The protocol standards are managed by the Internet Assigned Numbers
Authority.

Please refer to the document "Assigned Numbers" (RFC-1340) for
further information 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 "Internet Official
Protocol Standards" memo:

The file "in-notes/std/std1.txt" may be copied via FTP from the
FTP.ISI.EDU computer using the FTP username "anonymous" and FTP
password "guest".

7.3. Request for Comments Editor Contact

Contact:

Jon Postel
RFCEditor
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695

1-310-822-1511

RFC-Editor@ISI.EDU

Documents may be submitted via electronic mail to the RFCEditor for
consideration for publication as RFC. If you are not familiar with
the format or style requirements please request the "Instructions for
RFCAuthors". In general, the style of any recent RFCmay be used as
a guide.

7.4. The Network Information Center and
Requests for Comments Distribution Contact

RFC's may be obtained from DS.INTERNIC.NET via FTP, WAIS, and
electronic mail. Through FTP, RFC's are stored as rfc/rfcnnnn.txt
or rfc/rfcnnnn.ps where 'nnnn' is the RFCnumber. Login as
"anonymous" and provide your e-mail address as the password.
Through WAIS, you may use either your local WAIS client or telnet
to DS.INTERNIC.NET and login as "wais" (no password required) to
access a WAIS client. Help information and a tutorial for using
WAIS are available online. The WAIS database to search is "rfcs".

Directory and Database Services also provides a mail server
interface. Send a mail message to mailserv@ds.internic.net and
include any of the following commands in the message body:

document-by-name rfcnnnn where 'nnnn' is the RFCnumber
The text version is sent.

file /ftp/rfc/rfcnnnn.yyy where 'nnnn' is the RFCnumber.
and 'yyy' is 'txt' or 'ps'.

help to get information on how to use
the mailserver.

The InterNIC directory and database services collection of
resource listings, internet documents such as RFCs, FYIs, STDs,
and Internet Drafts, and publicly accessible databases are also

now available via Gopher. All our collections are WAIS indexed
and can be searched from the Gopher menu.

To access the InterNIC Gopher Servers, please connect to
"internic.net" port 70.

Contact: admin@ds.internic.net

7.5. Sources for Requests for Comments

Details on many sources of RFCs via FTP or EMAIL may be obtained by
sending an EMAIL message to "rfc-info@ISI.EDU" with the message body
"help: ways_to_get_rfcs". For example:

To: rfc-info@ISI.EDU
Subject: getting rfcs

help: ways_to_get_rfcs

8. Security Considerations

Security issues are not addressed in this memo.

9. Author's Address

Jon Postel
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292

Phone: 310-822-1511
Fax: 310-823-6714
------分隔线----------------------------
顶一下
(0)
0%
踩一下
(0)
0%
------分隔线----------------------------
最新评论 查看所有评论
发表评论 查看所有评论
请自觉遵守互联网相关的政策法规,严禁发布色情、暴力、反动的言论。
评价:
表情:
用户名: 密码: 验证码:
推荐内容