Debian Codegraph @

rfc1800.html

raw
1 <pre>Network Working Group Internet Architecture Board
2 Request for Comments: 1800 J. Postel, Editor
3 Obsoletes: RFCs <a href="./rfc1780">1780</a>, <a href="./rfc1720">1720</a>, <a href="./rfc1610">1610</a>, <a href="./rfc1600">1600</a>, July 1995
4 <a href="./rfc1540">1540</a>, <a href="./rfc1500">1500</a>, <a href="./rfc1410">1410</a>, <a href="./rfc1360">1360</a>, <a href="./rfc1280">1280</a>, <a href="./rfc1250">1250</a>,
5 1200, 1140, 1130, 1100, 1083
6 STD: 1
7 Category: Standards Track
8
9
10 <span class="h1">INTERNET OFFICIAL PROTOCOL STANDARDS</span>
11
12
13 Status of this Memo
14
15 This memo describes the state of standardization of protocols used in
16 the Internet as determined by the Internet Architecture Board (IAB).
17 This memo is an Internet Standard. Distribution of this memo is
18 unlimited.
19
20 Table of Contents
21
22 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
23 <a href="#section-1">1</a>. The Standardization Process . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
24 <a href="#section-2">2</a>. The Request for Comments Documents . . . . . . . . . . . . . <a href="#page-5">5</a>
25 <a href="#section-3">3</a>. Other Reference Documents . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
26 <a href="#section-3.1">3.1</a>. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
27 <a href="#section-3.2">3.2</a>. Gateway Requirements . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
28 <a href="#section-3.3">3.3</a>. Host Requirements . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
29 <a href="#section-3.4">3.4</a>. The MIL-STD Documents . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
30 <a href="#section-4">4</a>. Explanation of Terms . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
31 <a href="#section-4.1">4.1</a>. Definitions of Protocol State (Maturity Level) . . . . . . <a href="#page-9">9</a>
32 <a href="#section-4.1.1">4.1.1</a>. Standard Protocol . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
33 <a href="#section-4.1.2">4.1.2</a>. Draft Standard Protocol . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
34 <a href="#section-4.1.3">4.1.3</a>. Proposed Standard Protocol . . . . . . . . . . . . . . . <a href="#page-9">9</a>
35 <a href="#section-4.1.4">4.1.4</a>. Experimental Protocol . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
36 <a href="#section-4.1.5">4.1.5</a>. Informational Protocol . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
37 <a href="#section-4.1.6">4.1.6</a>. Historic Protocol . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
38 <a href="#section-4.2">4.2</a>. Definitions of Protocol Status (Requirement Level) . . . <a href="#page-10">10</a>
39 <a href="#section-4.2.1">4.2.1</a>. Required Protocol . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
40 <a href="#section-4.2.2">4.2.2</a>. Recommended Protocol . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
41 <a href="#section-4.2.3">4.2.3</a>. Elective Protocol . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
42 <a href="#section-4.2.4">4.2.4</a>. Limited Use Protocol . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
43 <a href="#section-4.2.5">4.2.5</a>. Not Recommended Protocol . . . . . . . . . . . . . . . <a href="#page-10">10</a>
44 <a href="#section-5">5</a>. The Standards Track . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
45 <a href="#section-5.1">5.1</a>. The RFC Processing Decision Table . . . . . . . . . . . <a href="#page-11">11</a>
46 <a href="#section-5.2">5.2</a>. The Standards Track Diagram . . . . . . . . . . . . . . <a href="#page-12">12</a>
47 <a href="#section-6">6</a>. The Protocols . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
48 <a href="#section-6.1">6.1</a>. Recent Changes . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
49
50
51
52 <span class="grey">Internet Architecture Board [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
55
56
57 <a href="#section-6.1.1">6.1.1</a>. New RFCs . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
58 <a href="#section-6.1.2">6.1.2</a>. Other Changes . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
59 <a href="#section-6.2">6.2</a>. Standard Protocols . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
60 <a href="#section-6.3">6.3</a>. Network-Specific Standard Protocols . . . . . . . . . . <a href="#page-20">20</a>
61 <a href="#section-6.4">6.4</a>. Draft Standard Protocols . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
62 <a href="#section-6.5">6.5</a>. Proposed Standard Protocols . . . . . . . . . . . . . . <a href="#page-22">22</a>
63 <a href="#section-6.6">6.6</a>. Telnet Options . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
64 <a href="#section-6.7">6.7</a>. Experimental Protocols . . . . . . . . . . . . . . . . . <a href="#page-27">27</a>
65 <a href="#section-6.8">6.8</a>. Informational Protocols . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
66 <a href="#section-6.9">6.9</a>. Historic Protocols . . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a>
67 <a href="#section-6.10">6.10</a> Obsolete Protocols . . . . . . . . . . . . . . . . . . . <a href="#page-31">31</a>
68 <a href="#section-7">7</a>. Contacts . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-32">32</a>
69 <a href="#section-7.1">7.1</a>. IAB, IETF, and IRTF Contacts . . . . . . . . . . . . . . <a href="#page-32">32</a>
70 <a href="#section-7.1.1">7.1.1</a>. Internet Architecture Board (IAB) Contact . . . . . . <a href="#page-32">32</a>
71 <a href="#section-7.1.2">7.1.2</a>. Internet Engineering Task Force (IETF) Contact . . . . <a href="#page-32">32</a>
72 <a href="#section-7.1.3">7.1.3</a>. Internet Research Task Force (IRTF) Contact . . . . . <a href="#page-33">33</a>
73 <a href="#section-7.2">7.2</a>. Internet Assigned Numbers Authority (IANA) Contact . . . <a href="#page-34">34</a>
74 <a href="#section-7.3">7.3</a>. Request for Comments Editor Contact . . . . . . . . . . <a href="#page-35">35</a>
75 <a href="#section-7.4">7.4</a>. Network Information Center Contact . . . . . . . . . . . <a href="#page-35">35</a>
76 <a href="#section-7.5">7.5</a>. Sources for Requests for Comments . . . . . . . . . . . <a href="#page-36">36</a>
77 <a href="#section-8">8</a>. Security Considerations . . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
78 <a href="#section-9">9</a>. Author's Address . . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
79
80 Introduction
81
82 A discussion of the standardization process and the RFC document
83 series is presented first, followed by an explanation of the terms.
84 Sections <a href="#section-6.2">6.2</a> - <a href="#section-6.10">6.10</a> contain the lists of protocols in each stage of
85 standardization. Finally are pointers to references and contacts for
86 further information.
87
88 This memo is intended to be issued approximately quarterly; please be
89 sure the copy you are reading is current. Current copies may be
90 obtained from the Network Information Center (INTERNIC) or from the
91 Internet Assigned Numbers Authority (IANA) (see the contact
92 information at the end of this memo). Do not use this edition after
93 31-Oct-95.
94
95 See <a href="#section-6.1">Section 6.1</a> for a description of recent changes. In the official
96 lists in sections <a href="#section-6.2">6.2</a> - <a href="#section-6.10">6.10</a>, an asterisk (*) next to a protocol
97 denotes that it is new to this document or has been moved from one
98 protocol level to another, or differs from the previous edition of
99 this document.
100
101
102
103
104
105
106
107
108 <span class="grey">Internet Architecture Board [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The Standardization Process</span>
114
115 The Internet Architecture Board maintains this list of documents that
116 define standards for the Internet protocol suite. See <a href="./rfc1601">RFC-1601</a> for
117 the charter of the IAB and <a href="./rfc1160">RFC-1160</a> for an explanation of the role
118 and organization of the IAB and its subsidiary groups, the Internet
119 Engineering Task Force (IETF) and the Internet Research Task Force
120 (IRTF). Each of these groups has a steering group called the IESG
121 and IRSG, respectively. The IETF develops these standards with the
122 goal of co-ordinating the evolution of the Internet protocols; this
123 co-ordination has become quite important as the Internet protocols
124 are increasingly in general commercial use. The definitive
125 description of the Internet standards process is found in <a href="./rfc1602">RFC-1602</a>.
126
127 The majority of Internet protocol development and standardization
128 activity takes place in the working groups of the IETF.
129
130 Protocols which are to become standards in the Internet go through a
131 series of states or maturity levels (proposed standard, draft
132 standard, and standard) involving increasing amounts of scrutiny and
133 testing. When a protocol completes this process it is assigned a STD
134 number (see <a href="./rfc1311">RFC-1311</a>). At each step, the Internet Engineering
135 Steering Group (IESG) of the IETF must make a recommendation for
136 advancement of the protocol.
137
138 To allow time for the Internet community to consider and react to
139 standardization proposals, a minimum delay of 6 months before a
140 proposed standard can be advanced to a draft standard and 4 months
141 before a draft standard can be promoted to standard.
142
143 It is general practice that no proposed standard can be promoted to
144 draft standard without at least two independent implementations (and
145 the recommendation of the IESG). Promotion from draft standard to
146 standard generally requires operational experience and demonstrated
147 interoperability of two or more implementations (and the
148 recommendation of the IESG).
149
150 In cases where there is uncertainty as to the proper decision
151 concerning a protocol a special review committee may be appointed
152 consisting of experts from the IETF, IRTF and the IAB with the
153 purpose of recommending an explicit action.
154
155 Advancement of a protocol to proposed standard is an important step
156 since it marks a protocol as a candidate for eventual standardization
157 (it puts the protocol "on the standards track"). Advancement to
158 draft standard is a major step which warns the community that, unless
159 major objections are raised or flaws are discovered, the protocol is
160 likely to be advanced to standard in six months.
161
162
163
164 <span class="grey">Internet Architecture Board [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
167
168
169 Some protocols have been superseded by better ones or are otherwise
170 unused. Such protocols are still documented in this memorandum with
171 the designation "historic".
172
173 Because it is useful to document the results of early protocol
174 research and development work, some of the RFCs document protocols
175 which are still in an experimental condition. The protocols are
176 designated "experimental" in this memorandum. They appear in this
177 report as a convenience to the community and not as evidence of their
178 standardization.
179
180 Other protocols, such as those developed by other standards
181 organizations, or by particular vendors, may be of interest or may be
182 recommended for use in the Internet. The specifications of such
183 protocols may be published as RFCs for the convenience of the
184 Internet community. These protocols are labeled "informational" in
185 this memorandum.
186
187 In addition to the working groups of the IETF, protocol development
188 and experimentation may take place as a result of the work of the
189 research groups of the Internet Research Task Force, or the work of
190 other individuals interested in Internet protocol development. The
191 the documentation of such experimental work in the RFC series is
192 encouraged, but none of this work is considered to be on the track
193 for standardization until the IESG has made a recommendation to
194 advance the protocol to the proposed standard state.
195
196 A few protocols have achieved widespread implementation without the
197 approval of the IESG. For example, some vendor protocols have become
198 very important to the Internet community even though they have not
199 been recommended by the IESG. However, the IAB strongly recommends
200 that the standards process be used in the evolution of the protocol
201 suite to maximize interoperability (and to prevent incompatible
202 protocol requirements from arising). The use of the terms
203 "standard", "draft standard", and "proposed standard" are reserved in
204 any RFC or other publication of Internet protocols to only those
205 protocols which the IESG has approved.
206
207 In addition to a state (like "Proposed Standard"), a protocol is also
208 assigned a status, or requirement level, in this document. The
209 possible requirement levels ("Required", "Recommended", "Elective",
210 "Limited Use", and "Not Recommended") are defined in <a href="#section-4.2">Section 4.2</a>.
211 When a protocol is on the standards track, that is in the proposed
212 standard, draft standard, or standard state (see <a href="#section-5">Section 5</a>), the
213 status shown in <a href="#section-6">Section 6</a> is the current status.
214
215 Few protocols are required to be implemented in all systems; this is
216 because there is such a variety of possible systems, for example,
217
218
219
220 <span class="grey">Internet Architecture Board [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
223
224
225 gateways, routers, terminal servers, workstations, and multi-user
226 hosts. The requirement level shown in this document is only a one
227 word label, which may not be sufficient to characterize the
228 implementation requirements for a protocol in all situations. For
229 some protocols, this document contains an additional status paragraph
230 (an applicability statement). In addition, more detailed status
231 information may be contained in separate requirements documents (see
232 <a href="#section-3">Section 3</a>).
233
234 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Request for Comments Documents</span>
235
236 The documents called Request for Comments (or RFCs) are the working
237 notes of the "Network Working Group", that is the Internet research
238 and development community. A document in this series may be on
239 essentially any topic related to computer communication, and may be
240 anything from a meeting report to the specification of a standard.
241
242 Notice:
243
244 All standards are published as RFCs, but not all RFCs specify
245 standards.
246
247 Anyone can submit a document for publication as an RFC. Submissions
248 must be made via electronic mail to the RFC Editor (see the contact
249 information at the end of this memo, and see <a href="./rfc1543">RFC 1543</a>).
250
251 While RFCs are not refereed publications, they do receive technical
252 review from the task forces, individual technical experts, or the RFC
253 Editor, as appropriate.
254
255 The RFC series comprises a wide range of documents, ranging from
256 informational documents of general interests to specifications of
257 standard Internet protocols. In cases where submission is intended
258 to document a proposed standard, draft standard, or standard
259 protocol, the RFC Editor will publish the document only with the
260 approval of the IESG. For documents describing experimental work,
261 the RFC Editor will notify the IESG before publication, allowing for
262 the possibility of review by the relevant IETF working group or IRTF
263 research group and provide those comments to the author. See <a href="#section-5.1">Section</a>
264 <a href="#section-5.1">5.1</a> for more detail.
265
266 Once a document is assigned an RFC number and published, that RFC is
267 never revised or re-issued with the same number. There is never a
268 question of having the most recent version of a particular RFC.
269 However, a protocol (such as File Transfer Protocol (FTP)) may be
270 improved and re-documented many times in several different RFCs. It
271 is important to verify that you have the most recent RFC on a
272 particular protocol. This "Internet Official Protocol Standards"
273
274
275
276 <span class="grey">Internet Architecture Board [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
279
280
281 memo is the reference for determining the correct RFC for the current
282 specification of each protocol.
283
284 The RFCs are available from the INTERNIC, and a number of other
285 sites. For more information about obtaining RFCs, see Sections <a href="#section-7.4">7.4</a>
286 and 7.5.
287
288 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Other Reference Documents</span>
289
290 There are three other reference documents of interest in checking the
291 current status of protocol specifications and standardization. These
292 are the Assigned Numbers, the Gateway Requirements, and the Host
293 Requirements. Note that these documents are revised and updated at
294 different times; in case of differences between these documents, the
295 most recent must prevail.
296
297 Also, one should be aware of the MIL-STD publications on IP, TCP,
298 Telnet, FTP, and SMTP. These are described in <a href="#section-3.4">Section 3.4</a>.
299
300 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Assigned Numbers</span>
301
302 The "Assigned Numbers" document lists the assigned values of the
303 parameters used in the various protocols. For example, IP protocol
304 codes, TCP port numbers, Telnet Option Codes, ARP hardware types, and
305 Terminal Type names. Assigned Numbers was most recently issued as
306 <a href="./rfc1700">RFC-1700</a>.
307
308 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Requirements for IP Version 4 Routers</span>
309
310 This document reviews the specifications that apply to gateways and
311 supplies guidance and clarification for any ambiguities.
312 Requirements for IP Version 4 Routers is <a href="./rfc1812">RFC-1812</a>.
313
314 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Host Requirements</span>
315
316 This pair of documents reviews and updates the specifications that
317 apply to hosts, and it supplies guidance and clarification for any
318 ambiguities. Host Requirements was issued as <a href="./rfc1122">RFC-1122</a> and <a href="./rfc1123">RFC-1123</a>.
319
320 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. The MIL-STD Documents</span>
321
322 The Internet community specifications for IP (<a href="./rfc791">RFC-791</a>) and TCP (<a href="./rfc793">RFC-</a>
323 <a href="./rfc793">793</a>) and the DoD MIL-STD specifications are intended to describe
324 exactly the same protocols. Any difference in the protocols
325 specified by these sets of documents should be reported to DISA and
326 to the IESG. It is strongly advised that the two sets of documents
327 be used together, along with <a href="./rfc1122">RFC-1122</a> and <a href="./rfc1123">RFC-1123</a>.
328
329
330
331
332 <span class="grey">Internet Architecture Board [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
335
336
337 Note that these MIL-STD are now somewhat out of date. The
338 Requirements for IP Version 4 Routers (<a href="./rfc1812">RFC-1812</a>) and Host
339 Requirements (<a href="./rfc1122">RFC-1122</a>, <a href="./rfc1123">RFC-1123</a>) take precedence over both earlier
340 RFCs and the MIL-STDs.
341
342 2045-13501 Internet Routing between Autonomous Systems
343
344 2045-14502-01 Internet Transport Profile for DoD
345 Communications, Part 1: Transport and Internet Services
346
347 2045-14502-04 Internet Transport Profile for DoD
348 Communications, Part 4: LAN Media-Independent Requirements
349
350 2045-14503 Internet Transport Service Supporting OSI
351 Applications
352
353 2045-44500 Tactical Communications
354
355 2045-17503-01 Internet Message Transfer Profile for DoD
356 Communications Part 1: Simple Mail Transfer Protocol
357
358 2045-17503-02 Internet Message Transfer Profile for DoD
359 Communications Part 2: Format of Text Messages
360
361 2045-17504 Internet File Transfer Profile for DoD
362 Communications
363
364 2045-17505 Internet Domain Name Service (DNS) Profile for DoD
365 Communications
366
367 2045-17506 Internet Remote Login (RLOGIN) Profile for DoD
368 Communications
369
370 2045-17507 Internet Network Management Profile for DoD
371 Communications
372
373 2045-38000 DoD Network Management for DoD Communications
374
375 These documents are available from the Naval Publications and Forms
376 Center. Requests can be initiated by telephone, telegraph, or mail;
377 however, it is preferred that private industry use form DD1425, if
378 possible.
379
380 Naval Publications and Forms Center, Code 3015
381 5801 Tabor Ave
382 Philadelphia, PA 19120
383 Phone: 1-215-697-3321 (order tape)
384 1-215-697-4834 (conversation)
385
386
387
388 <span class="grey">Internet Architecture Board [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
391
392
393 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Explanation of Terms</span>
394
395 There are two independent categorization of protocols. The first is
396 the "maturity level" or STATE of standardization, one of "standard",
397 "draft standard", "proposed standard", "experimental",
398 "informational" or "historic". The second is the "requirement level"
399 or STATUS of this protocol, one of "required", "recommended",
400 "elective", "limited use", or "not recommended".
401
402 The status or requirement level is difficult to portray in a one word
403 label. These status labels should be considered only as an
404 indication, and a further description, or applicability statement,
405 should be consulted.
406
407 When a protocol is advanced to proposed standard or draft standard,
408 it is labeled with a current status.
409
410 At any given time a protocol occupies a cell of the following matrix.
411 Protocols are likely to be in cells in about the following
412 proportions (indicated by the relative number of Xs). A new protocol
413 is most likely to start in the (proposed standard, elective) cell, or
414 the (experimental, limited use) cell.
415
416 S T A T U S
417 Req Rec Ele Lim Not
418 +-----+-----+-----+-----+-----+
419 Std | X | XXX | XXX | | |
420 S +-----+-----+-----+-----+-----+
421 Draft | X | X | XXX | | |
422 T +-----+-----+-----+-----+-----+
423 Prop | | X | XXX | | |
424 A +-----+-----+-----+-----+-----+
425 Info | | | | | |
426 T +-----+-----+-----+-----+-----+
427 Expr | | | | XXX | |
428 E +-----+-----+-----+-----+-----+
429 Hist | | | | | XXX |
430 +-----+-----+-----+-----+-----+
431
432 What is a "system"?
433
434 Some protocols are particular to hosts and some to gateways; a few
435 protocols are used in both. The definitions of the terms below
436 will refer to a "system" which is either a host or a gateway (or
437 both). It should be clear from the context of the particular
438 protocol which types of systems are intended.
439
440
441
442
443
444 <span class="grey">Internet Architecture Board [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
447
448
449 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Definitions of Protocol State</span>
450
451 Every protocol listed in this document is assigned to a "maturity
452 level" or STATE of standardization: "standard", "draft standard",
453 "proposed standard", "experimental", or "historic".
454
455 4.1.1. Standard Protocol
456
457 The IESG has established this as an official standard protocol for
458 the Internet. These protocols are assigned STD numbers (see <a href="./rfc1311">RFC-</a>
459 <a href="./rfc1311">1311</a>). These are separated into two groups: (1) IP protocol and
460 above, protocols that apply to the whole Internet; and (2)
461 network-specific protocols, generally specifications of how to do
462 IP on particular types of networks.
463
464 4.1.2. Draft Standard Protocol
465
466 The IESG is actively considering this protocol as a possible
467 Standard Protocol. Substantial and widespread testing and comment
468 are desired. Comments and test results should be submitted to the
469 IESG. There is a possibility that changes will be made in a Draft
470 Standard Protocol before it becomes a Standard Protocol.
471
472 4.1.3. Proposed Standard Protocol
473
474 These are protocol proposals that may be considered by the IESG
475 for standardization in the future. Implementation and testing by
476 several groups is desirable. Revision of the protocol
477 specification is likely.
478
479 4.1.4. Experimental Protocol
480
481 A system should not implement an experimental protocol unless it
482 is participating in the experiment and has coordinated its use of
483 the protocol with the developer of the protocol.
484
485 Typically, experimental protocols are those that are developed as
486 part of an ongoing research project not related to an operational
487 service offering. While they may be proposed as a service
488 protocol at a later stage, and thus become proposed standard,
489 draft standard, and then standard protocols, the designation of a
490 protocol as experimental may sometimes be meant to suggest that
491 the protocol, although perhaps mature, is not intended for
492 operational use.
493
494
495
496
497
498
499
500 <span class="grey">Internet Architecture Board [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
503
504
505 4.1.5. Informational Protocol
506
507 Protocols developed by other standard organizations, or vendors,
508 or that are for other reasons outside the purview of the IESG, may
509 be published as RFCs for the convenience of the Internet community
510 as informational protocols.
511
512 4.1.6. Historic Protocol
513
514 These are protocols that are unlikely to ever become standards in
515 the Internet either because they have been superseded by later
516 developments or due to lack of interest.
517
518 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Definitions of Protocol Status</span>
519
520 This document lists a "requirement level" or STATUS for each
521 protocol. The status is one of "required", "recommended",
522 "elective", "limited use", or "not recommended".
523
524 4.2.1. Required Protocol
525
526 A system must implement the required protocols.
527
528 4.2.2. Recommended Protocol
529
530 A system should implement the recommended protocols.
531
532 4.2.3. Elective Protocol
533
534 A system may or may not implement an elective protocol. The
535 general notion is that if you are going to do something like this,
536 you must do exactly this. There may be several elective protocols
537 in a general area, for example, there are several electronic mail
538 protocols, and several routing protocols.
539
540 4.2.4. Limited Use Protocol
541
542 These protocols are for use in limited circumstances. This may be
543 because of their experimental state, specialized nature, limited
544 functionality, or historic state.
545
546 4.2.5. Not Recommended Protocol
547
548 These protocols are not recommended for general use. This may be
549 because of their limited functionality, specialized nature, or
550 experimental or historic state.
551
552
553
554
555
556 <span class="grey">Internet Architecture Board [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
559
560
561 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. The Standards Track</span>
562
563 This section discusses in more detail the procedures used by the RFC
564 Editor and the IESG in making decisions about the labeling and
565 publishing of protocols as standards.
566
567 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. The RFC Processing Decision Table</span>
568
569 Here is the current decision table for processing submissions by the
570 RFC Editor. The processing depends on who submitted it, and the
571 status they want it to have.
572
573 +==========================================================+
574 |**************| S O U R C E |
575 +==========================================================+
576 | Desired | IAB | IESG | IRSG | Other |
577 | Status | | | | |
578 +==========================================================+
579 | | | | | |
580 | Standard | Bogus | Publish | Bogus | Bogus |
581 | or | (2) | (1) | (2) | (2) |
582 | Draft | | | | |
583 | Standard | | | | |
584 +--------------+----------+----------+----------+----------+
585 | | | | | |
586 | | Refer | Publish | Refer | Refer |
587 | Proposed | (3) | (1) | (3) | (3) |
588 | Standard | | | | |
589 | | | | | |
590 +--------------+----------+----------+----------+----------+
591 | | | | | |
592 | | Notify | Publish | Notify | Notify |
593 | Experimental | (4) | (1) | (4) | (4) |
594 | Protocol | | | | |
595 | | | | | |
596 +--------------+----------+----------+----------+----------+
597 | | | | | |
598 | Information | Publish | Publish |Discretion|Discretion|
599 | or Opinion | (1) | (1) | (5) | (5) |
600 | Paper | | | | |
601 | | | | | |
602 +==========================================================+
603
604 (1) Publish.
605
606 (2) Bogus. Inform the source of the rules. RFCs specifying
607 Standard, or Draft Standard must come from the IESG, only.
608
609
610
611
612 <span class="grey">Internet Architecture Board [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
615
616
617 (3) Refer to an Area Director for review by a WG. Expect to see
618 the document again only after approval by the IESG.
619
620 (4) Notify both the IESG and IRSG. If no concerns are raised in
621 two weeks then do Discretion (5), else RFC Editor to resolve
622 the concerns or do Refer (3).
623
624 (5) RFC Editor's discretion. The RFC Editor decides if a review
625 is needed and if so by whom. RFC Editor decides to publish or
626 not.
627
628 Of course, in all cases the RFC Editor can request or make minor
629 changes for style, format, and presentation purposes.
630
631 The IESG has designated the IESG Secretary as its agent for
632 forwarding documents with IESG approval and for registering concerns
633 in response to notifications (4) to the RFC Editor. Documents from
634 Area Directors or Working Group Chairs may be considered in the same
635 way as documents from "other".
636
637 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. The Standards Track Diagram</span>
638
639 There is a part of the STATUS and STATE categorization that is called
640 the standards track. Actually, only the changes of state are
641 significant to the progression along the standards track, though the
642 status assignments may change as well.
643
644 The states illustrated by single line boxes are temporary states,
645 those illustrated by double line boxes are long term states. A
646 protocol will normally be expected to remain in a temporary state for
647 several months (minimum six months for proposed standard, minimum
648 four months for draft standard). A protocol may be in a long term
649 state for many years.
650
651 A protocol may enter the standards track only on the recommendation
652 of the IESG; and may move from one state to another along the track
653 only on the recommendation of the IESG. That is, it takes action by
654 the IESG to either start a protocol on the track or to move it along.
655
656 Generally, as the protocol enters the standards track a decision is
657 made as to the eventual STATUS, requirement level or applicability
658 (elective, recommended, or required) the protocol will have, although
659 a somewhat less stringent current status may be assigned, and it then
660 is placed in the the proposed standard STATE with that status. So
661 the initial placement of a protocol is into state 1. At any time the
662 STATUS decision may be revisited.
663
664
665
666
667
668 <span class="grey">Internet Architecture Board [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
671
672
673 |
674 +&lt;----------------------------------------------+
675 | ^
676 V 0 | 4
677 +-----------+ +===========+
678 | enter |--&gt;----------------+--------------&gt;|experiment |
679 +-----------+ | +=====+=====+
680 | |
681 V 1 |
682 +-----------+ V
683 | proposed |--------------&gt;+
684 +---&gt;+-----+-----+ |
685 | | |
686 | V 2 |
687 +&lt;---+-----+-----+ V
688 | draft std |--------------&gt;+
689 +---&gt;+-----+-----+ |
690 | | |
691 | V 3 |
692 +&lt;---+=====+=====+ V
693 | standard |--------------&gt;+
694 +=====+=====+ |
695 |
696 V 5
697 +=====+=====+
698 | historic |
699 +===========+
700
701 The transition from proposed standard (1) to draft standard (2) can
702 only be by action of the IESG and only after the protocol has been
703 proposed standard (1) for at least six months.
704
705 The transition from draft standard (2) to standard (3) can only be by
706 action of the IESG and only after the protocol has been draft
707 standard (2) for at least four months.
708
709 Occasionally, the decision may be that the protocol is not ready for
710 standardization and will be assigned to the experimental state (4).
711 This is off the standards track, and the protocol may be resubmitted
712 to enter the standards track after further work. There are other
713 paths into the experimental and historic states that do not involve
714 IESG action.
715
716 Sometimes one protocol is replaced by another and thus becomes
717 historic, or it may happen that a protocol on the standards track is
718 in a sense overtaken by another protocol (or other events) and
719 becomes historic (state 5).
720
721
722
723
724 <span class="grey">Internet Architecture Board [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
727
728
729 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. The Protocols</span>
730
731 Sub<a href="#section-6.1">section 6.1</a> lists recent RFCs and other changes. Subsections <a href="#section-6.2">6.2</a>
732 - 6.10 list the standards in groups by protocol state.
733
734 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Recent Changes</span>
735
736 <span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>. New RFCs:</span>
737
738 1814 - Unique Addresses are Good
739
740 This is an information document and does not specify any
741 level of standard.
742
743 1813 - NFS Version 3 Protocol Specification
744
745 This is an information document and does not specify any
746 level of standard.
747
748 1812 - Requirements for IP Version 4 Routers
749
750 A Proposed Standard protocol.
751
752 1811 - U.S. Government Internet Domain Names
753
754 This is an information document and does not specify any
755 level of standard.
756
757 1810 - Report on MD5 Performance
758
759 This is an information document and does not specify any
760 level of standard.
761
762 1809 - Using the Flow Label Field in IPv6
763
764 This is an information document and does not specify any
765 level of standard.
766
767 1808 - Relative Uniform Resource Locators
768
769 A Proposed Standard protocol.
770
771 1807 - A Format for Bibliographic Records
772
773 This is an information document and does not specify any
774 level of standard.
775
776
777
778
779
780 <span class="grey">Internet Architecture Board [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
783
784
785 1806 - Communicating Presentation Information in Internet
786 Messages: The Content-Disposition Header
787
788 An Experimental protocol.
789
790 1805 - Location-Independent Data/Software Integrity Protocol
791
792 This is an information document and does not specify any
793 level of standard.
794
795 1804 - Schema Publishing in X.500 Directory
796
797 An Experimental protocol.
798
799 1803 - Recommendations for an X.500 Production Directory Service
800
801 This is an information document and does not specify any
802 level of standard.
803
804 1802 - Introducing Project Long Bud: Internet Pilot Project for
805 the Deployment of X.500 Directory Information in Support of
806 X.400 Routing
807
808 This is an information document and does not specify any
809 level of standard.
810
811 1801 - X.400-MHS use of the X.500 Directory to support X.400-MHS
812 Routing
813
814 An Experimental protocol.
815
816 1800 - Internet Official Protocol Standards
817
818 This memo.
819
820 1799 - Not yet issued.
821
822 1798 - Connection-less Lightweight Directory Access Protocol
823
824 A Proposed Standard protocol.
825
826 1797 - Class A Subnet Experiment
827
828 An Experimental protocol.
829
830
831
832
833
834
835
836 <span class="grey">Internet Architecture Board [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
839
840
841 1796 - Not All RFCs are Standards
842
843 This is an information document and does not specify any
844 level of standard.
845
846 1795 - Data Link Switching: Switch-to-Switch Protocol AIW DLSw
847 RIG: DLSw Closed Pages, DLSw Standard Version 1
848
849 This is an information document and does not specify any
850 level of standard.
851
852 1794 - DNS Support for Load Balancing
853
854 This is an information document and does not specify any
855 level of standard.
856
857 1793 - Extending OSPF to Support Demand Circuits
858
859 A Proposed Standard protocol.
860
861 1792 - TCP/IPX Connection Mib Specification
862
863 An Experimental protocol.
864
865 1791 - TCP And UDP Over IPX Networks With Fixed Path MTU
866
867 An Experimental protocol.
868
869 1790 - An Agreement between the Internet Society and Sun
870 Microsystems, Inc. in the Matter of ONC RPC and XDR
871 Protocols
872
873 This is an information document and does not specify any
874 level of standard.
875
876 1789 - INETPhone: Telephone Services and Servers on Internet
877
878 This is an information document and does not specify any
879 level of standard.
880
881 1788 - ICMP Domain Name Messages
882
883 An Experimental protocol.
884
885 1787 - Routing in a Multi-provider Internet
886
887 This is an information document and does not specify any
888 level of standard.
889
890
891
892 <span class="grey">Internet Architecture Board [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
895
896
897 1776 - The Address is the Message
898
899 This is an information document and does not specify any
900 level of standard.
901
902 <span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>. Other Changes:</span>
903
904 The following are changes to protocols listed in the previous
905 edition.
906
907 1268 - Application of the Border Gateway Protocol in the Internet
908
909 Moved to Historic.
910
911 1267 - A Border Gateway Protocol 3 (BGP-3)
912
913 Moved to Historic.
914
915 1209 - The Transmission of IP Datagrams over the SMDS Service
916
917 Elevated to Standard.
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Internet Architecture Board [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
951
952
953 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Standard Protocols</span>
954
955 Protocol Name Status RFC STD *
956 ======== ===================================== ======== ==== === =
957 -------- Internet Official Protocol Standards Req 1800 1
958 -------- Assigned Numbers Req 1700 2
959 -------- Host Requirements - Communications Req 1122 3
960 -------- Host Requirements - Applications Req 1123 3
961 IP Internet Protocol Req 791 5
962 as amended by:--------
963 -------- IP Subnet Extension Req 950 5
964 -------- IP Broadcast Datagrams Req 919 5
965 -------- IP Broadcast Datagrams with Subnets Req 922 5
966 ICMP Internet Control Message Protocol Req 792 5
967 IGMP Internet Group Multicast Protocol Rec 1112 5
968 UDP User Datagram Protocol Rec 768 6
969 TCP Transmission Control Protocol Rec 793 7
970 TELNET Telnet Protocol Rec 854,855 8
971 FTP File Transfer Protocol Rec 959 9
972 SMTP Simple Mail Transfer Protocol Rec 821 10
973 MAIL Format of Electronic Mail Messages Rec 822 11
974 CONTENT Content Type Header Field Rec 1049 11
975 NTPV2 Network Time Protocol (Version 2) Rec 1119 12
976 DOMAIN Domain Name System Rec 1034,1035 13
977 DNS-MX Mail Routing and the Domain System Rec 974 14
978 SNMP Simple Network Management Protocol Rec 1157 15
979 SMI Structure of Management Information Rec 1155 16
980 Concise-MIB Concise MIB Definitions Rec 1212 16
981 MIB-II Management Information Base-II Rec 1213 17
982 NETBIOS NetBIOS Service Protocols Ele 1001,1002 19
983 ECHO Echo Protocol Rec 862 20
984 DISCARD Discard Protocol Ele 863 21
985 CHARGEN Character Generator Protocol Ele 864 22
986 QUOTE Quote of the Day Protocol Ele 865 23
987 USERS Active Users Protocol Ele 866 24
988 DAYTIME Daytime Protocol Ele 867 25
989 TIME Time Server Protocol Ele 868 26
990 TFTP Trivial File Transfer Protocol Ele 1350 33
991 RIP Routing Information Protocol Ele 1058 34
992 TP-TCP ISO Transport Service on top of the TCP Ele 1006 35
993 ETHER-MIB Ethernet MIB Ele 1643 50
994 PPP Point-to-Point Protocol (PPP) Ele 1661 51
995 PPP-HDLC PPP in HDLC Framing Ele 1662 51
996
997 [Note: an asterisk at the end of a line indicates a change from the
998 previous edition of this document.]
999
1000
1001
1002
1003
1004 <span class="grey">Internet Architecture Board [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1007
1008
1009 Applicability Statements:
1010
1011 IGMP -- The Internet Architecture Board intends to move towards
1012 general adoption of IP multicasting, as a more efficient solution
1013 than broadcasting for many applications. The host interface has been
1014 standardized in <a href="./rfc1112">RFC-1112</a>; however, multicast-routing gateways are in
1015 the experimental stage and are not widely available. An Internet
1016 host should support all of <a href="./rfc1112">RFC-1112</a>, except for the IGMP protocol
1017 itself which is optional; see <a href="./rfc1122">RFC-1122</a> for more details. Even
1018 without IGMP, implementation of <a href="./rfc1112">RFC-1112</a> will provide an important
1019 advance: IP-layer access to local network multicast addressing. It
1020 is expected that IGMP will become recommended for all hosts and
1021 gateways at some future date.
1022
1023 SMI, MIB-II SNMP -- The Internet Architecture Board recommends that
1024 all IP and TCP implementations be network manageable. At the current
1025 time, this implies implementation of the Internet MIB-II (<a href="./rfc1213">RFC-1213</a>),
1026 and at least the recommended management protocol SNMP (<a href="./rfc1157">RFC-1157</a>).
1027
1028 RIP -- The Routing Information Protocol (RIP) is widely implemented
1029 and used in the Internet. However, both implementors and users
1030 should be aware that RIP has some serious technical limitations as a
1031 routing protocol. The IETF is currently devpeloping several
1032 candidates for a new standard "open" routing protocol with better
1033 properties than RIP. The IAB urges the Internet community to track
1034 these developments, and to implement the new protocol when it is
1035 standardized; improved Internet service will result for many users.
1036
1037 TP-TCP -- As OSI protocols become more widely implemented and used,
1038 there will be an increasing need to support interoperation with the
1039 TCP/IP protocols. The Internet Engineering Task Force is formulating
1040 strategies for interoperation. <a href="./rfc1006">RFC-1006</a> provides one interoperation
1041 mode, in which TCP/IP is used to emulate TP0 in order to support OSI
1042 applications. Hosts that wish to run OSI connection-oriented
1043 applications in this mode should use the procedure described in <a href="./rfc1006">RFC-</a>
1044 <a href="./rfc1006">1006</a>. In the future, the IAB expects that a major portion of the
1045 Internet will support both TCP/IP and OSI (inter-)network protocols
1046 in parallel, and it will then be possible to run OSI applications
1047 across the Internet using full OSI protocol "stacks".
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Internet Architecture Board [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1063
1064
1065 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Network-Specific Standard Protocols</span>
1066
1067 All Network-Specific Standards have Elective status.
1068
1069 Protocol Name State RFC STD *
1070 ======== ===================================== ===== ===== === =
1071 IP-ATM Classical IP and ARP over ATM Prop 1577
1072 IP-FR Multiprotocol over Frame Relay Draft 1490
1073 ATM-ENCAP Multiprotocol Encapsulation over ATM Prop 1483
1074 IP-TR-MC IP Multicast over Token-Ring LANs Prop 1469
1075 IP-FDDI Transmission of IP and ARP over FDDI Net Std 1390 36
1076 IP-HIPPI IP and ARP on HIPPI Prop 1374
1077 IP-X.25 X.25 and ISDN in the Packet Mode Draft 1356
1078 IP-FDDI Internet Protocol on FDDI Networks Draft 1188
1079 ARP Address Resolution Protocol Std 826 37
1080 RARP A Reverse Address Resolution Protocol Std 903 38
1081 IP-ARPA Internet Protocol on ARPANET Std BBN1822 39
1082 IP-WB Internet Protocol on Wideband Network Std 907 40
1083 IP-E Internet Protocol on Ethernet Networks Std 894 41
1084 IP-EE Internet Protocol on Exp. Ethernet Nets Std 895 42
1085 IP-IEEE Internet Protocol on IEEE 802 Std 1042 43
1086 IP-DC Internet Protocol on DC Networks Std 891 44
1087 IP-HC Internet Protocol on Hyperchannel Std 1044 45
1088 IP-ARC Transmitting IP Traffic over ARCNET Nets Std 1201 46
1089 IP-SLIP Transmission of IP over Serial Lines Std 1055 47
1090 IP-NETBIOS Transmission of IP over NETBIOS Std 1088 48
1091 IP-IPX Transmission of 802.2 over IPX Networks Std 1132 49
1092 IP-SMDS IP Datagrams over the SMDS Service Std 1209 52*
1093
1094 [Note: an asterisk at the end of a line indicates a change from the
1095 previous edition of this document.]
1096
1097 Applicability Statements:
1098
1099 It is expected that a system will support one or more physical
1100 networks and for each physical network supported the appropriate
1101 protocols from the above list must be supported. That is, it is
1102 elective to support any particular type of physical network, and for
1103 the physical networks actually supported it is required that they be
1104 supported exactly according to the protocols in the above list. See
1105 also the Host and Gateway Requirements RFCs for more specific
1106 information on network-specific ("link layer") protocols.
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Internet Architecture Board [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1119
1120
1121 <span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Draft Standard Protocols</span>
1122
1123 Protocol Name Status RFC
1124 ======== ===================================== ============== =====
1125 STR-REP String Representation ... Elective 1779
1126 X.500syn X.500 String Representation ... Elective 1778
1127 X.500lite X.500 Lightweight ... Elective 1777
1128 BGP-4-APP Application of BGP-4 Elective 1772
1129 BGP-4 Border Gateway Protocol 4 Elective 1771
1130 PPP-DNCP PPP DECnet Phase IV Control Protocol Elective 1762
1131 RMON-MIB Remote Network Monitoring MIB Elective 1757
1132 802.5-MIB IEEE 802.5 Token Ring MIB Elective 1748
1133 BGP-4-MIB BGP-4 MIB Elective 1657
1134 POP3 Post Office Protocol, Version 3 Elective 1725
1135 RIP2-MIB RIP Version 2 MIB Extension Elective 1724
1136 RIP2 RIP Version 2-Carrying Additional Info. Elective 1723
1137 RIP2-APP RIP Version 2 Protocol App. Statement Elective 1722
1138 SIP-MIB SIP Interface Type MIB Elective 1694
1139 ------- Def Man Objs Parallel-printer-like Elective 1660
1140 ------- Def Man Objs RS-232-like Elective 1659
1141 ------- Def Man Objs Character Stream Elective 1658
1142 SMTP-SIZE SMTP Service Ext for Message Size Elective 1653
1143 SMTP-8BIT SMTP Service Ext or 8bit-MIMEtransport Elective 1652
1144 SMTP-EXT SMTP Service Extensions Elective 1651
1145 OSI-NSAP Guidelines for OSI NSAP Allocation Elective 1629
1146 OSPF2 Open Shortest Path First Routing V2 Elective 1583
1147 ISO-TS-ECHO Echo for ISO-8473 Elective 1575
1148 DECNET-MIB DECNET MIB Elective 1559
1149 ------- Message Header Ext. of Non-ASCII Text Elective 1522
1150 MIME Multipurpose Internet Mail Extensions Elective 1521
1151 802.3-MIB IEEE 802.3 Repeater MIB Elective 1516
1152 BRIDGE-MIB BRIDGE-MIB Elective 1493
1153 NTPV3 Network Time Protocol (Version 3) Elective 1305
1154 IP-MTU Path MTU Discovery Elective 1191
1155 FINGER Finger Protocol Elective 1288
1156 BOOTP Bootstrap Protocol Recommended 951,1497
1157 NICNAME WhoIs Protocol Elective 954
1158
1159 [Note: an asterisk at the end of a line indicates a change from the
1160 previous edition of this document.]
1161
1162 Applicability Statements:
1163
1164 PPP -- Point to Point Protocol is a method of sending IP over serial
1165 lines, which are a type of physical network. It is anticipated that
1166 PPP will be advanced to the network-specifics standard protocol state
1167 in the future.
1168
1169
1170
1171
1172 <span class="grey">Internet Architecture Board [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1175
1176
1177 <span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Proposed Standard Protocols</span>
1178
1179 Protocol Name Status RFC
1180 ======== ===================================== ============== =====
1181 RREQ Requirements for IP Version 4 Routers Elective 1812*
1182 URL Relative Uniform Resource Locators Elective 1808*
1183 CLDAP Connection-less LDAP Elective 1798*
1184 OSPF-DC Ext. OSPF to Support Demand Circuits Elective 1793*
1185 TMUX Transport Multiplexing Protocol Elective 1692*
1186 TFTP-Opt TFTP Options Elective 1784
1187 TFTP-Blk TFTP Blocksize Option Elective 1783
1188 TFTP-Ext TFTP Option Extension Elective 1782
1189 OSI-Dir OSI User Friendly Naming ... Elective 1781
1190 MIME-EDI MIME Encapsulation of EDI Objects Elective 1767
1191 Lang-Tag Tags for Identification of Languages Elective 1766
1192 XNSCP PPP XNS IDP Control Protocol Elective 1764
1193 BVCP PPP Banyan Vines Control Protocol Elective 1763
1194 Print-MIB Printer MIB Elective 1759
1195 ATM-SIG ATM Signaling Support for IP over ATM Elective 1755
1196 IPNG Recommendation for IP Next Generation Elective 1752
1197 802.5-SSR 802.5 SSR MIB using SMIv2 Elective 1749
1198 SDLCSMIv2 SNADLC SDLC MIB using SMIv2 Elective 1747
1199 BGP4/IDRP BGP4/IDRP for IP/OSPF Interaction Elective 1745
1200 AT-MIB Appletalk MIB Elective 1742
1201 MacMIME MIME Encapsulation of Macintosh files Elective 1740
1202 URL Uniform Resource Locators Elective 1738
1203 POP3-AUTH POP3 AUTHentication command Elective 1734
1204 IMAP4-AUTH IMAP4 Authentication Mechanisms Elective 1731
1205 IMAP4 Internet Message Access Protocol V4 Elective 1730
1206 PPP-MP PPP Multilink Protocol Elective 1717
1207 RDBMS-MIB RDMS MIB - using SMIv2 Elective 1697
1208 MODEM-MIB Modem MIB - using SMIv2 Elective 1696
1209 ATM-MIB ATM Management Version 8.0 using SMIv2 Elective 1695
1210 SNANAU-MIB SNA NAUs MIB using SMIv2 Elective 1665
1211 PPP-TRANS PPP Reliable Transmission Elective 1663
1212 BGP-4-IMP BGP-4 Roadmap and Implementation Elective 1656
1213 -------- Postmaster Convention X.400 Operations Elective 1648
1214 TN3270-En TN3270 Enhancements Elective 1647
1215 PPP-BCP PPP Bridging Control Protocol Elective 1638
1216 UPS-MIB UPS Management Information Base Elective 1628
1217 AAL5-MTU Default IP MTU for use over ATM AAL5 Elective 1626
1218 PPP-SONET PPP over SONET/SDH Elective 1619
1219 PPP-ISDN PPP over ISDN Elective 1618
1220 DNS-R-MIB DNS Resolver MIB Extensions Elective 1612
1221 DNS-S-MIB DNS Server MIB Extensions Elective 1611
1222 FR-MIB Frame Relay Service MIB Elective 1604
1223 PPP-X25 PPP in X.25 Elective 1598
1224 OSPF-NSSA The OSPF NSSA Option Elective 1587
1225
1226
1227
1228 <span class="grey">Internet Architecture Board [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1231
1232
1233 OSPF-Multi Multicast Extensions to OSPF Elective 1584
1234 SONET-MIB MIB SONET/SDH Interface Type Elective 1595
1235 RIP-DC Extensions to RIP to Support Demand Cir. Elective 1582
1236 -------- Evolution of the Interfaces Group of MIB-II Elective 1573
1237 PPP-LCP PPP LCP Extensions Elective 1570
1238 X500-MIB X.500 Directory Monitoring MIB Elective 1567
1239 MAIL-MIB Mail Monitoring MIB Elective 1566
1240 NSM-MIB Network Services Monitoring MIB Elective 1565
1241 CIPX Compressing IPX Headers Over WAM Media Elective 1553
1242 IPXCP PPP Internetworking Packet Exchange Control Elective 1552
1243 CON-MD5 Content-MD5 Header Field Elective 1544
1244 DHCP-BOOTP Interoperation Between DHCP and BOOTP Elective 1534
1245 DHCP-BOOTP DHCP Options and BOOTP Vendor Extensions Elective 1533
1246 BOOTP Clarifications and Extensions BOOTP Elective 1532
1247 DHCP Dynamic Host Configuration Protocol Elective 1541*
1248 SRB-MIB Source Routing Bridge MIB Elective 1525
1249 CIDR-STRA CIDR Address Assignment... Elective 1519
1250 CIDR-ARCH CIDR Architecture... Elective 1518
1251 CIDR-APP CIDR Applicability Statement Elective 1517
1252 -------- 802.3 MAU MIB Elective 1515
1253 HOST-MIB Host Resources MIB Elective 1514
1254 -------- Token Ring Extensions to RMON MIB Elective 1513
1255 FDDI-MIB FDDI Management Information Base Elective 1512
1256 KERBEROS Kerberos Network Authentication Ser (V5) Elective 1510
1257 GSSAPI Generic Security Service API: C-bindings Elective 1509
1258 GSSAPI Generic Security Service Application... Elective 1508
1259 DASS Distributed Authentication Security... Elective 1507
1260 -------- X.400 Use of Extended Character Sets Elective 1502
1261 HARPOON Rules for Downgrading Messages... Elective 1496
1262 Mapping MHS/RFC-822 Message Body Mapping Elective 1495
1263 Equiv X.400/MIME Body Equivalences Elective 1494
1264 IDPR Inter-Domain Policy Routing Protocol Elective 1479
1265 IDPR-ARCH Architecture for IDPR Elective 1478
1266 PPP/Bridge MIB Bridge PPP MIB Elective 1474
1267 PPP/IP MIB IP Network Control Protocol of PPP MIB Elective 1473
1268 PPP/SEC MIB Security Protocols of PPP MIB Elective 1472
1269 PPP/LCP MIB Link Control Protocol of PPP MIB Elective 1471
1270 X25-MIB Multiprotocol Interconnect on X.25 MIB Elective 1461
1271 SNMPv2 Coexistence between SNMPv1 and SNMPv2 Elective 1452
1272 SNMPv2 Manager-to-Manager MIB Elective 1451
1273 SNMPv2 Management Information Base for SNMPv2 Elective 1450
1274 SNMPv2 Transport Mappings for SNMPv2 Elective 1449
1275 SNMPv2 Protocol Operations for SNMPv2 Elective 1448
1276 SNMPv2 Party MIB for SNMPv2 Elective 1447
1277 SNMPv2 Security Protocols for SNMPv2 Elective 1446
1278 SNMPv2 Administrative Model for SNMPv2 Elective 1445
1279 SNMPv2 Conformance Statements for SNMPv2 Elective 1444
1280 SNMPv2 Textual Conventions for SNMPv2 Elective 1443
1281
1282
1283
1284 <span class="grey">Internet Architecture Board [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1287
1288
1289 SNMPv2 SMI for SNMPv2 Elective 1442
1290 SNMPv2 Introduction to SNMPv2 Elective 1441
1291 PEM-KEY PEM - Key Certification Elective 1424
1292 PEM-ALG PEM - Algorithms, Modes, and Identifiers Elective 1423
1293 PEM-CKM PEM - Certificate-Based Key Management Elective 1422
1294 PEM-ENC PEM - Message Encryption and Auth Elective 1421
1295 SNMP-IPX SNMP over IPX Elective 1420
1296 SNMP-AT SNMP over AppleTalk Elective 1419
1297 SNMP-OSI SNMP over OSI Elective 1418
1298 FTP-FTAM FTP-FTAM Gateway Specification Elective 1415
1299 IDENT-MIB Identification MIB Elective 1414
1300 IDENT Identification Protocol Elective 1413
1301 DS3/E3-MIB DS3/E3 Interface Type Elective 1407
1302 DS1/E1-MIB DS1/E1 Interface Type Elective 1406
1303 BGP-OSPF BGP OSPF Interaction Elective 1403
1304 -------- Route Advertisement In BGP2 And BGP3 Elective 1397
1305 SNMP-X.25 SNMP MIB Extension for X.25 Packet Layer Elective 1382
1306 SNMP-LAPB SNMP MIB Extension for X.25 LAPB Elective 1381
1307 PPP-ATCP PPP AppleTalk Control Protocol Elective 1378
1308 PPP-OSINLCP PPP OSI Network Layer Control Protocol Elective 1377
1309 TABLE-MIB IP Forwarding Table MIB Elective 1354
1310 SNMP-PARTY-MIB Administration of SNMP Elective 1353
1311 SNMP-SEC SNMP Security Protocols Elective 1352
1312 SNMP-ADMIN SNMP Administrative Model Elective 1351
1313 TOS Type of Service in the Internet Elective 1349
1314 PPP-AUTH PPP Authentication Elective 1334
1315 PPP-LINK PPP Link Quality Monitoring Elective 1333
1316 PPP-IPCP PPP Control Protocol Elective 1332
1317 ------- X.400 1988 to 1984 downgrading Elective 1328
1318 ------- Mapping between X.400(1988) Elective 1327
1319 TCP-EXT TCP Extensions for High Performance Elective 1323
1320 FRAME-MIB Management Information Base for Frame Elective 1315
1321 NETFAX File Format for the Exchange of Images Elective 1314
1322 IARP Inverse Address Resolution Protocol Elective 1293
1323 FDDI-MIB FDDI-MIB Elective 1285
1324 ------- Encoding Network Addresses Elective 1277
1325 ------- Replication and Distributed Operations Elective 1276
1326 ------- COSINE and Internet X.500 Schema Elective 1274
1327 BGP-MIB Border Gateway Protocol MIB (Version 3) Elective 1269
1328 ICMP-ROUT ICMP Router Discovery Messages Elective 1256
1329 OSPF-MIB OSPF Version 2 MIB Elective 1253
1330 IPSO DoD Security Options for IP Elective 1108
1331 OSI-UDP OSI TS on UDP Elective 1240
1332 STD-MIBs Reassignment of Exp MIBs to Std MIBs Elective 1239
1333 IPX-IP Tunneling IPX Traffic through IP Nets Elective 1234
1334 GINT-MIB Extensions to the Generic-Interface MIB Elective 1229
1335 IS-IS OSI IS-IS for TCP/IP Dual Environments Elective 1195
1336 IP-CMPRS Compressing TCP/IP Headers Elective 1144
1337
1338
1339
1340 <span class="grey">Internet Architecture Board [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1343
1344
1345 NNTP Network News Transfer Protocol Elective 977
1346
1347 [Note: an asterisk at the end of a line indicates a change from the
1348 previous edition of this document.]
1349
1350 Applicability Statements:
1351
1352 OSPF - <a href="./rfc1370">RFC 1370</a> is an applicability statement for OSPF.
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Internet Architecture Board [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1399
1400
1401 <span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. Telnet Options</span>
1402
1403 For convenience, all the Telnet Options are collected here with both
1404 their state and status.
1405
1406 Protocol Name Number State Status RFC STD
1407 ======== ===================================== ===== ====== ==== ===
1408 TOPT-BIN Binary Transmission 0 Std Rec 856 27
1409 TOPT-ECHO Echo 1 Std Rec 857 28
1410 TOPT-RECN Reconnection 2 Prop Ele ...
1411 TOPT-SUPP Suppress Go Ahead 3 Std Rec 858 29
1412 TOPT-APRX Approx Message Size Negotiation 4 Prop Ele ...
1413 TOPT-STAT Status 5 Std Rec 859 30
1414 TOPT-TIM Timing Mark 6 Std Rec 860 31
1415 TOPT-REM Remote Controlled Trans and Echo 7 Prop Ele 726
1416 TOPT-OLW Output Line Width 8 Prop Ele ...
1417 TOPT-OPS Output Page Size 9 Prop Ele ...
1418 TOPT-OCRD Output Carriage-Return Disposition 10 Prop Ele 652
1419 TOPT-OHT Output Horizontal Tabstops 11 Prop Ele 653
1420 TOPT-OHTD Output Horizontal Tab Disposition 12 Prop Ele 654
1421 TOPT-OFD Output Formfeed Disposition 13 Prop Ele 655
1422 TOPT-OVT Output Vertical Tabstops 14 Prop Ele 656
1423 TOPT-OVTD Output Vertical Tab Disposition 15 Prop Ele 657
1424 TOPT-OLD Output Linefeed Disposition 16 Prop Ele 658
1425 TOPT-EXT Extended ASCII 17 Prop Ele 698
1426 TOPT-LOGO Logout 18 Prop Ele 727
1427 TOPT-BYTE Byte Macro 19 Prop Ele 735
1428 TOPT-DATA Data Entry Terminal 20 Prop Ele 1043
1429 TOPT-SUP SUPDUP 21 Prop Ele 736
1430 TOPT-SUPO SUPDUP Output 22 Prop Ele 749
1431 TOPT-SNDL Send Location 23 Prop Ele 779
1432 TOPT-TERM Terminal Type 24 Prop Ele 1091
1433 TOPT-EOR End of Record 25 Prop Ele 885
1434 TOPT-TACACS TACACS User Identification 26 Prop Ele 927
1435 TOPT-OM Output Marking 27 Prop Ele 933
1436 TOPT-TLN Terminal Location Number 28 Prop Ele 946
1437 TOPT-3270 Telnet 3270 Regime 29 Prop Ele 1041
1438 TOPT-X.3 X.3 PAD 30 Prop Ele 1053
1439 TOPT-NAWS Negotiate About Window Size 31 Prop Ele 1073
1440 TOPT-TS Terminal Speed 32 Prop Ele 1079
1441 TOPT-RFC Remote Flow Control 33 Prop Ele 1372
1442 TOPT-LINE Linemode 34 Draft Ele 1184
1443 TOPT-XDL X Display Location 35 Prop Ele 1096
1444 TOPT-ENVIR Telnet Environment Option 36 Hist Not 1408
1445 TOPT-AUTH Telnet Authentication Option 37 Exp Ele 1416
1446 TOPT-ENVIR Telnet Environment Option 39 Prop Ele 1572
1447 TOPT-EXTOP Extended-Options-List 255 Std Rec 861 32
1448
1449
1450
1451
1452 <span class="grey">Internet Architecture Board [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1455
1456
1457 [Note: an asterisk at the end of a line indicates a change from the
1458 previous edition of this document.]
1459
1460 <span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. Experimental Protocols</span>
1461
1462 All Experimental protocols have the Limited Use status.
1463
1464 Protocol Name RFC
1465 ======== ===================================== =====
1466 ------- Content-Disposition Header 1806*
1467 ------- Schema Publishing in X.500 Directory 1804*
1468 ------- X.400-MHS use X.500 to support X.400-MHS Routing 1801*
1469 ------- Class A Subnet Experiment 1797*
1470 TCP/IPXMIB TCP/IPX Connection Mib Specification 1792*
1471 ------- TCP And UDP Over IPX Networks With Fixed Path MTU 1791*
1472 ICMP-DM ICMP Domain Name Messages 1788*
1473 CLNP-MULT Host Group Extensions for CLNP Multicasting 1768
1474 OSPF-OVFL OSPF Database Overflow 1765
1475 RWP Remote Write ProtocolL - Version 1.0 1756
1476 NARP NBMA Address Resolution Protocol 1735
1477 DNS-DEBUG Tools for DNS debugging 1713
1478 DNS-ENCODE DNS Encoding of Geographical Location 1712
1479 TCP-POS An Extension to TCP: Partial Order Service 1693
1480 ------- DNS to Distribute <a href="./rfc1327">RFC1327</a> Mail Address Mapping Tables 1664
1481 T/TCP TCP Extensions for Transactions 1644
1482 UTF-7 A Mail-Safe Transformation Format of Unicode 1642
1483 MIME-UNI Using Unicode with MIME 1641
1484 FOOBAR FTP Operation Over Big Address Records 1639
1485 X500-CHART Charting Networks in the X.500 Directory 1609
1486 X500-DIR Representing IP Information in the X.500 Directory 1608
1487 SNMP-DPI SNMP Distributed Protocol Interface 1592
1488 CLNP-TUBA Use of ISO CLNP in TUBA Environments 1561
1489 REM-PRINT TPC.INT Subdomain Remote Printing - Technical 1528
1490 EHF-MAIL Encoding Header Field for Internet Messages 1505
1491 REM-PRT An Experiment in Remote Printing 1486
1492 RAP Internet Route Access Protocol 1476
1493 TP/IX TP/IX: The Next Internet 1475
1494 X400 Routing Coordination for X.400 Services 1465
1495 DNS Storing Arbitrary Attributes in DNS 1464
1496 IRCP Internet Relay Chat Protocol 1459
1497 TOS-LS Link Security TOS 1455
1498 SIFT/UFT Sender-Initiated/Unsolicited File Transfer 1440
1499 DIR-ARP Directed ARP 1433
1500 TEL-SPX Telnet Authentication: SPX 1412
1501 TEL-KER Telnet Authentication: Kerberos V4 1411
1502 MAP-MAIL X.400 Mapping and Mail-11 1405
1503 TRACE-IP Traceroute Using an IP Option 1393
1504 DNS-IP Experiment in DNS Based IP Routing 1383
1505
1506
1507
1508 <span class="grey">Internet Architecture Board [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1511
1512
1513 RMCP Remote Mail Checking Protocol 1339
1514 TCP-HIPER TCP Extensions for High Performance 1323
1515 MSP2 Message Send Protocol 2 1312
1516 DSLCP Dynamically Switched Link Control 1307
1517 -------- X.500 and Domains 1279
1518 IN-ENCAP Internet Encapsulation Protocol 1241
1519 CLNS-MIB CLNS-MIB 1238
1520 CFDP Coherent File Distribution Protocol 1235
1521 SNMP-DPI SNMP Distributed Program Interface 1228
1522 IP-AX.25 IP Encapsulation of AX.25 Frames 1226
1523 ALERTS Managing Asynchronously Generated Alerts 1224
1524 MPP Message Posting Protocol 1204
1525 ST-II Stream Protocol 1190
1526 SNMP-BULK Bulk Table Retrieval with the SNMP 1187
1527 DNS-RR New DNS RR Definitions 1183
1528 IMAP2 Interactive Mail Access Protocol 1176
1529 NTP-OSI NTP over OSI Remote Operations 1165
1530 DMF-MAIL Digest Message Format for Mail 1153
1531 RDP Reliable Data Protocol 908,1151
1532 TCP-ACO TCP Alternate Checksum Option 1146
1533 -------- Mapping full 822 to Restricted 822 1137
1534 IP-DVMRP IP Distance Vector Multicast Routing 1075
1535 VMTP Versatile Message Transaction Protocol 1045
1536 COOKIE-JAR Authentication Scheme 1004
1537 NETBLT Bulk Data Transfer Protocol 998
1538 IRTP Internet Reliable Transaction Protocol 938
1539 LDP Loader Debugger Protocol 909
1540 RLP Resource Location Protocol 887
1541 NVP-II Network Voice Protocol ISI-memo
1542 PVP Packet Video Protocol ISI-memo
1543
1544 [Note: an asterisk at the end of a line indicates a change from the
1545 previous edition of this document.]
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564 <span class="grey">Internet Architecture Board [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1567
1568
1569 <span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a>. Informational Protocols</span>
1570
1571 Information protocols have no status.
1572
1573 Protocol Name RFC
1574 ======= ==================================== =====
1575 NFSV3 NFS Version 3 Protocol Specification 1813*
1576 -------- A Format for Bibliographic Records 1807*
1577 SDMD IPv4 Option for Sender Directed MD Delivery 1770
1578 SNTP Simple Network Time Protocol 1769
1579 SNOOP Snoop Version 2 Packet Capture File Format 1761
1580 BINHEX MIME Content Type for BinHex Encoded Files 1741
1581 RWHOIS Referral Whois Protocol 1714
1582 DNS-NSAP DNS NSAP Resource Records 1706
1583 RADIO-PAGE TPC.INT Subdomain: Radio Paging -- Technical Procedures 1703
1584 GRE-IPv4 Generic Routing Encapsulation over IPv4 1702
1585 GRE Generic Routing Encapsulatio 1701
1586 SNPP Simple Network Paging Protocol - Version 2 1645
1587 IPXWAN Novell IPX Over Various WAN Media 1634
1588 ADSNA-IP Advanced SNA/IP: A Simple SNA Transport Protocol 1538
1589 AUBR Appletalk Update-Based Routing Protocol... <a href="#page-1504">1504</a>
1590 TACACS Terminal Access Control Protocol 1492
1591 SUN-NFS Network File System Protocol 1094
1592 SUN-RPC Remote Procedure Call Protocol Version 2 1057
1593 GOPHER The Internet Gopher Protocol 1436
1594 ------- Data Link Switching: Switch-to-Switch Protocol 1434
1595 LISTSERV Listserv Distribute Protocol 1429
1596 ------- Replication Requirements 1275
1597 PCMAIL Pcmail Transport Protocol 1056
1598 MTP Multicast Transport Protocol 1301
1599 BSD Login BSD Login 1282
1600 DIXIE DIXIE Protocol Specification 1249
1601 IP-X.121 IP to X.121 Address Mapping for DDN 1236
1602 OSI-HYPER OSI and LLC1 on HYPERchannel 1223
1603 HAP2 Host Access Protocol 1221
1604 SUBNETASGN On the Assignment of Subnet Numbers 1219
1605 SNMP-TRAPS Defining Traps for use with SNMP 1215
1606 DAS Directory Assistance Service 1202
1607 MD4 MD4 Message Digest Algorithm 1186
1608 LPDP Line Printer Daemon Protocol 1179
1609
1610 [Note: an asterisk at the end of a line indicates a change from the
1611 previous edition of this document.]
1612
1613
1614
1615
1616
1617
1618
1619
1620 <span class="grey">Internet Architecture Board [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1623
1624
1625 <span class="h3"><a class="selflink" id="section-6.9" href="#section-6.9">6.9</a>. Historic Protocols</span>
1626
1627 All Historic protocols have Not Recommended status.
1628
1629 Protocol Name RFC STD
1630 ======== ===================================== ===== ===
1631 BGP3 Border Gateway Protocol 3 (BGP-3) 1267,1268 *
1632 -------- Gateway Requirements Req 1009 4
1633 EGP Exterior Gateway Protocol Rec 904 18
1634 SNMP-MUX SNMP MUX Protocol and MIB 1227
1635 OIM-MIB-II OSI Internet Management: MIB-II 1214
1636 IMAP3 Interactive Mail Access Protocol Version 3 1203
1637 SUN-RPC Remote Procedure Call Protocol Version 1 1050
1638 802.4-MIP IEEE 802.4 Token Bus MIB 1230
1639 CMOT Common Management Information Services 1189
1640 -------- Mail Privacy: Procedures 1113
1641 -------- Mail Privacy: Key Management 1114
1642 -------- Mail Privacy: Algorithms 1115
1643 NFILE A File Access Protocol 1037
1644 HOSTNAME HOSTNAME Protocol 953
1645 SFTP Simple File Transfer Protocol 913
1646 SUPDUP SUPDUP Protocol 734
1647 BGP Border Gateway Protocol 1163,1164
1648 MIB-I MIB-I 1156
1649 SGMP Simple Gateway Monitoring Protocol 1028
1650 HEMS High Level Entity Management Protocol 1021
1651 STATSRV Statistics Server 996
1652 POP2 Post Office Protocol, Version 2 937
1653 RATP Reliable Asynchronous Transfer Protocol 916
1654 HFEP Host - Front End Protocol 929
1655 THINWIRE Thinwire Protocol 914
1656 HMP Host Monitoring Protocol 869
1657 GGP Gateway Gateway Protocol 823
1658 RTELNET Remote Telnet Service 818
1659 CLOCK DCNET Time Server Protocol 778
1660 MPM Internet Message Protocol 759
1661 NETRJS Remote Job Service 740
1662 NETED Network Standard Text Editor 569
1663 RJE Remote Job Entry 407
1664 XNET Cross Net Debugger IEN-158
1665 NAMESERVER Host Name Server Protocol IEN-116
1666 MUX Multiplexing Protocol IEN-90
1667 GRAPHICS Graphics Protocol NIC-24308
1668
1669 [Note: an asterisk at the end of a line indicates a change from the
1670 previous edition of this document.]
1671
1672
1673
1674
1675
1676 <span class="grey">Internet Architecture Board [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1679
1680
1681 <span class="h3"><a class="selflink" id="section-6.10" href="#section-6.10">6.10</a>. Obsolete Protocols</span>
1682
1683 Some of the protocols listed in this memo are described in RFCs that are
1684 obsoleted by newer RFCs. "Obsolete" or "obsoleted" is not an official
1685 state or status of protocols. This subsection is for information only.
1686
1687 While it may seem to be obviously wrong to have an obsoleted RFC in the
1688 list of standards, there may be cases when an older standard is in the
1689 process of being replaced. This process may take a year or two.
1690
1691 For example, the Network Time Protocol (NTP) [<a href="./rfc1119">RFC 1119</a>] is in its
1692 version 2 a full Standard, and in its version 3 is a Draft Standard [RFC
1693 1305]. Once version 3 is a full Standard, version 2 will be made
1694 Historic.
1695
1696 Many obsoleted protocols are of little interest and are dropped from
1697 this memo altogether. Some obsoleted protocols have received enough
1698 recognition that it seems appropriate to list them under their current
1699 status and with the following reference to their current replacement.
1700
1701 RFC RFC Status Title *
1702 ==== ==== ========= =================================== =
1703 <span class="h2"><a class="selflink" id="section-1661" href="#section-1661">1661</a> obsoletes 1548 </span>Draft /Ele The Point to Point Protocol (PPP) *
1704 <span class="h2"><a class="selflink" id="section-1305" href="#section-1305">1305</a> obsoletes 1119 </span>Std /Rec Network Time Protocol (Version 2)
1705 <span class="h2"><a class="selflink" id="section-1533" href="#section-1533">1533</a> obsoletes 1497 </span>Draft/Rec Bootstrap Protocol
1706 <span class="h2"><a class="selflink" id="section-1574" href="#section-1574">1574</a> obsoletes 1139 </span>Prop /Ele Echo for ISO-8473
1707 <span class="h2"><a class="selflink" id="section-1573" href="#section-1573">1573</a> obsoletes 1229 </span>Prop /Ele Extensions to the Generic-IF MIB
1708 <span class="h2"><a class="selflink" id="section-1559" href="#section-1559">1559</a> obsoletes 1289 </span>Prop /Ele DECNET MIB
1709 <span class="h2"><a class="selflink" id="section-1541" href="#section-1541">1541</a> obsoletes 1531 </span>Prop /Ele Dynamic Host Configuration Protocol
1710 <span class="h2"><a class="selflink" id="section-1592" href="#section-1592">1592</a> obsoletes 1228 </span>Exper/Lim SNMP Distributed Program Interface
1711 <span class="h2"><a class="selflink" id="section-1528" href="#section-1528">1528</a> obsoletes 1486 </span>Exper/Lim An Experiment in Remote Printing
1712 <span class="h2"><a class="selflink" id="section-1320" href="#section-1320">1320</a> obsoletes 1186 </span>Info / MD4 Message Digest Algorithm
1713 <span class="h2"><a class="selflink" id="section-1057" href="#section-1057">1057</a> obsoletes 1050 </span>Hist /Not Remote Procedure Call Version 1
1714 <span class="h2"><a class="selflink" id="section-1421" href="#section-1421">1421</a> obsoletes 1113 </span>Hist /Not Mail Privacy: Procedures
1715 <span class="h2"><a class="selflink" id="section-1422" href="#section-1422">1422</a> obsoletes 1114 </span>Hist /Not Mail Privacy: Key Management
1716 <span class="h2"><a class="selflink" id="section-1423" href="#section-1423">1423</a> obsoletes 1115 </span>Hist /Not Mail Privacy: Algorithms
1717 <span class="h2"><a class="selflink" id="section-1267" href="#section-1267">1267</a> obsoletes 1163 </span>Hist /Not Border Gateway Protocol
1718 <span class="h2"><a class="selflink" id="section-1268" href="#section-1268">1268</a> obsoletes 1164 </span>Hist /Not Border Gateway Protocol
1719
1720 Thanks to Lynn Wheeler of Britton Lee for compiling the information in
1721 this subsection.
1722
1723 [Note: an asterisk at the end of a line indicates a change from the
1724 previous edition of this document.]
1725
1726
1727
1728
1729
1730
1731
1732 <span class="grey">Internet Architecture Board [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1735
1736
1737 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Contacts</span>
1738
1739 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. IAB, IETF, and IRTF Contacts</span>
1740
1741 7.1.1. Internet Architecture Board (IAB) Contact
1742
1743 Please send your comments about this list of protocols and especially
1744 about the Draft Standard Protocols to the Internet Architecture Board
1745 care of Abel Winerib, IAB Executive Director.
1746
1747 Contacts:
1748
1749 Abel Winerib
1750 Executive Director of the IAB
1751 Intel, JF2-64
1752 2111 NE 25th Avenue
1753 Hillsboro, OR 97124
1754
1755 1-503-696-8972
1756
1757 [email protected]
1758
1759
1760 Christian Huitema
1761 Chair of the IAB
1762 INRIA, Sophia-Antipolis
1763 2004 Route des Lucioles
1764 BP 109
1765 F-06561 Valbonne Cedex
1766 France
1767
1768 +33 93 65 77 15
1769
1770 [email protected]
1771
1772 7.1.2. Internet Engineering Task Force (IETF) Contact
1773
1774 Contacts:
1775
1776 Paul Mockapetris
1777 Chair of the IETF
1778 USC/Information Sciences Institute
1779 4676 Admiralty Way
1780 Marina del Rey, CA 90292-6695
1781
1782 1-310-822-1511
1783
1784 [email protected]
1785
1786
1787
1788 <span class="grey">Internet Architecture Board [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1791
1792
1793 Steve Coya
1794 IESG Secretary
1795 Corporation for National Research Initiatives
1796 1895 Preston White Drive, Suite 100
1797 Reston, VA 22091
1798
1799 1-703-620-8990
1800
1801 [email protected]
1802
1803 Steve Coya
1804 Executive Director of the IETF
1805 Corporation for National Research Initiatives
1806 1895 Preston White Drive, Suite 100
1807 Reston, VA 22091
1808
1809 1-703-620-8990
1810
1811 [email protected]
1812
1813
1814 7.1.3. Internet Research Task Force (IRTF) Contact
1815
1816 Contact:
1817
1818 Abel Winerib
1819 Chair of the IRTF
1820 Intel, JF2-64
1821 2111 NE 25th Avenue
1822 Hillsboro, OR 97124
1823
1824 1-503-696-8972
1825
1826 [email protected]
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844 <span class="grey">Internet Architecture Board [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1847
1848
1849 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Internet Assigned Numbers Authority Contact</span>
1850
1851 Contact:
1852
1853 Joyce K. Reynolds
1854 Internet Assigned Numbers Authority
1855 USC/Information Sciences Institute
1856 4676 Admiralty Way
1857 Marina del Rey, CA 90292-6695
1858
1859 1-310-822-1511
1860
1861 [email protected]
1862
1863 The protocol standards are managed by the Internet Assigned Numbers
1864 Authority.
1865
1866 Please refer to the document "Assigned Numbers" (<a href="./rfc1700">RFC-1700</a>) for
1867 further information about the status of protocol documents. There
1868 are two documents that summarize the requirements for host and
1869 gateways in the Internet, "Host Requirements" (<a href="./rfc1122">RFC-1122</a> and <a href="./rfc1123">RFC-1123</a>)
1870 and "Requirements for IP Version 4 Routers" (<a href="./rfc1812">RFC-1812</a>).
1871
1872 How to obtain the most recent edition of this "Internet Official
1873 Protocol Standards" memo:
1874
1875 The file "in-notes/std/std1.txt" may be copied via FTP from the
1876 FTP.ISI.EDU computer using the FTP username "anonymous" and FTP
1877 password "guest".
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900 <span class="grey">Internet Architecture Board [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1903
1904
1905 <span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Request for Comments Editor Contact</span>
1906
1907 Contact:
1908
1909 Jon Postel
1910 RFC Editor
1911 USC/Information Sciences Institute
1912 4676 Admiralty Way
1913 Marina del Rey, CA 90292-6695
1914
1915 1-310-822-1511
1916
1917 [email protected]
1918
1919 Documents may be submitted via electronic mail to the RFC Editor for
1920 consideration for publication as RFC. If you are not familiar with
1921 the format or style requirements please request the "Instructions for
1922 RFC Authors". In general, the style of any recent RFC may be used as
1923 a guide.
1924
1925 <span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. The Network Information Center and</span>
1926 <span class="h3"> Requests for Comments Distribution Contact</span>
1927
1928 RFC's may be obtained from DS.INTERNIC.NET via FTP, WAIS, and
1929 electronic mail. Through FTP, RFC's are stored as rfc/rfcnnnn.txt
1930 or rfc/rfcnnnn.ps where 'nnnn' is the RFC number. Login as
1931 "anonymous" and provide your e-mail address as the password.
1932 Through WAIS, you may use either your local WAIS client or telnet
1933 to DS.INTERNIC.NET and login as "wais" (no password required) to
1934 access a WAIS client. Help information and a tutorial for using
1935 WAIS are available online. The WAIS database to search is "rfcs".
1936
1937 Directory and Database Services also provides a mail server
1938 interface. Send a mail message to [email protected] and
1939 include any of the following commands in the message body:
1940
1941 document-by-name rfcnnnn where 'nnnn' is the RFC number
1942 The text version is sent.
1943
1944 file /ftp/rfc/rfcnnnn.yyy where 'nnnn' is the RFC number.
1945 and 'yyy' is 'txt' or 'ps'.
1946
1947 help to get information on how to use
1948 the mailserver.
1949
1950 The InterNIC directory and database services collection of
1951 resource listings, internet documents such as RFCs, FYIs, STDs,
1952 and Internet Drafts, and publicly accessible databases are also
1953
1954
1955
1956 <span class="grey">Internet Architecture Board [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc1800">RFC 1800</a> Internet Standards July 1995</span>
1959
1960
1961 now available via Gopher. All our collections are WAIS indexed
1962 and can be searched from the Gopher menu.
1963
1964 To access the InterNIC Gopher Servers, please connect to
1965 "internic.net" port 70.
1966
1967 Contact: [email protected]
1968
1969 <span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Sources for Requests for Comments</span>
1970
1971 Details on many sources of RFCs via FTP or EMAIL may be obtained by
1972 sending an EMAIL message to "[email protected]" with the message body
1973 "help: ways_to_get_rfcs". For example:
1974
1975 To: [email protected]
1976 Subject: getting rfcs
1977
1978 help: ways_to_get_rfcs
1979
1980 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
1981
1982 Security issues are not addressed in this memo.
1983
1984 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Author's Address</span>
1985
1986 Jon Postel
1987 USC/Information Sciences Institute
1988 4676 Admiralty Way
1989 Marina del Rey, CA 90292
1990
1991 Phone: 310-822-1511
1992 Fax: 310-823-6714
1993
1994 Email: [email protected]
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012 Internet Architecture Board [Page 36]
2013 </pre>