Debian Codegraph @

rfc2400.html

raw
1 <pre>Network Working Group Internet Architecture Board
2 Request for Comments: 2400 J. Postel
3 Obsoletes: <a href="./rfc2300">2300</a>, <a href="./rfc2200">2200</a>, <a href="./rfc2000">2000</a>, <a href="./rfc1920">1920</a>, <a href="./rfc1880">1880</a>, J. Reynolds
4 <a href="./rfc1800">1800</a>, <a href="./rfc1780">1780</a>, <a href="./rfc1720">1720</a>, <a href="./rfc1610">1610</a>, <a href="./rfc1600">1600</a>, <a href="./rfc1540">1540</a>, <a href="./rfc1500">1500</a>, <a href="./rfc1410">1410</a>, Editors
5 1360, 1280, 1250, 1200, 1140, 1130, 1100, 1083 September 1998
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 Copyright Notice
21
22 Copyright (C) The Internet Society (1998). All Rights Reserved.
23
24 Table of Contents
25
26 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
27 <a href="#section-1">1</a>. The Standardization Process . . . . . . . . . . . . . . . <a href="#page-3">3</a>
28 <a href="#section-2">2</a>. The Request for Comments Documents . . . . . . . . . . . . <a href="#page-5">5</a>
29 <a href="#section-3">3</a>. Other Reference Documents . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
30 <a href="#section-3.1">3.1</a>. Assigned Numbers . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
31 <a href="#section-3.2">3.2</a>. Gateway Requirements . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
32 <a href="#section-3.3">3.3</a>. Host Requirements . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
33 <a href="#section-3.4">3.4</a>. The MIL-STD Documents . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
34 <a href="#section-4">4</a>. Explanation of Terms . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
35 <a href="#section-4.1">4.1</a>. Definitions of Protocol State (Maturity Level) . . . . . <a href="#page-8">8</a>
36 <a href="#section-4.1.1">4.1.1</a>. Standard Protocol . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
37 <a href="#section-4.1.2">4.1.2</a>. Draft Standard Protocol . . . . . . . . . . . . . . . <a href="#page-8">8</a>
38 <a href="#section-4.1.3">4.1.3</a>. Proposed Standard Protocol . . . . . . . . . . . . . . <a href="#page-8">8</a>
39 <a href="#section-4.1.4">4.1.4</a>. Experimental Protocol . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
40 <a href="#section-4.1.5">4.1.5</a>. Informational Protocol . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
41 <a href="#section-4.1.6">4.1.6</a>. Historic Protocol . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
42 <a href="#section-4.2">4.2</a>. Definitions of Protocol Status (Requirement Level) . . . <a href="#page-9">9</a>
43 <a href="#section-4.2.1">4.2.1</a>. Required Protocol . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
44 <a href="#section-4.2.2">4.2.2</a>. Recommended Protocol . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
45 <a href="#section-4.2.3">4.2.3</a>. Elective Protocol . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
46 <a href="#section-4.2.4">4.2.4</a>. Limited Use Protocol . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
47 <a href="#section-4.2.5">4.2.5</a>. Not Recommended Protocol . . . . . . . . . . . . . . . <a href="#page-9">9</a>
48 <a href="#section-5">5</a>. The Standards Track . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
49
50
51
52 <span class="grey">Internet Architecture Board Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
55
56
57 <a href="#section-5.1">5.1</a>. The RFC Processing Decision Table . . . . . . . . . . . <a href="#page-10">10</a>
58 <a href="#section-5.2">5.2</a>. The Standards Track Diagram . . . . . . . . . . . . . . <a href="#page-11">11</a>
59 <a href="#section-6">6</a>. The Protocols . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
60 <a href="#section-6.1">6.1</a>. Recent Changes . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
61 <a href="#section-6.1.1">6.1.1</a>. New RFCs . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
62 <a href="#section-6.1.2">6.1.2</a>. Other Changes . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
63 <a href="#section-6.2">6.2</a>. Standard Protocols . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
64 <a href="#section-6.3">6.3</a>. Network-Specific Standard Protocols . . . . . . . . . . <a href="#page-23">23</a>
65 <a href="#section-6.4">6.4</a>. Draft Standard Protocols . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
66 <a href="#section-6.5">6.5</a>. Proposed Standard Protocols . . . . . . . . . . . . . . <a href="#page-26">26</a>
67 <a href="#section-6.6">6.6</a>. Telnet Options . . . . . . . . . . . . . . . . . . . . . <a href="#page-33">33</a>
68 <a href="#section-6.7">6.7</a>. Experimental Protocols . . . . . . . . . . . . . . . . . <a href="#page-35">35</a>
69 <a href="#section-6.8">6.8</a>. Informational Protocols . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
70 <a href="#section-6.9">6.9</a>. Historic Protocols . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
71 <a href="#section-6.10">6.10</a> Obsolete Protocols . . . . . . . . . . . . . . . . . . . <a href="#page-41">41</a>
72 <a href="#section-7">7</a>. Contacts . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-42">42</a>
73 <a href="#section-7.1">7.1</a>. IAB, IETF, and IRTF Contacts . . . . . . . . . . . . . . <a href="#page-42">42</a>
74 <a href="#section-7.1.1">7.1.1</a>. Internet Architecture Board (IAB) Contact . . . . . . <a href="#page-42">42</a>
75 <a href="#section-7.1.2">7.1.2</a>. Internet Engineering Task Force (IETF) Contact . . . . <a href="#page-42">42</a>
76 <a href="#section-7.1.3">7.1.3</a>. Internet Research Task Force (IRTF) Contact . . . . . <a href="#page-43">43</a>
77 <a href="#section-7.2">7.2</a>. Internet Assigned Numbers Authority (IANA) Contact . . . <a href="#page-44">44</a>
78 <a href="#section-7.3">7.3</a>. Request for Comments Editor Contact . . . . . . . . . . <a href="#page-45">45</a>
79 <a href="#section-7.4">7.4</a>. Network Information Center Contact . . . . . . . . . . . <a href="#page-45">45</a>
80 <a href="#section-7.5">7.5</a>. Sources for Requests for Comments . . . . . . . . . . . <a href="#page-46">46</a>
81 <a href="#section-8">8</a>. Security Considerations . . . . . . . . . . . . . . . . . <a href="#page-46">46</a>
82 <a href="#section-9">9</a>. Author's Address . . . . . . . . . . . . . . . . . . . . . <a href="#page-46">46</a>
83 <a href="#section-10">10</a>. Full Copyright Statement . . . . . . . . . . . . . . . . . <a href="#page-47">47</a>
84
85 Introduction
86
87 A discussion of the standardization process and the RFC document
88 series is presented first, followed by an explanation of the terms.
89 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
90 standardization. Finally, there are pointers to references and
91 contacts for further information.
92
93 This memo is intended to be issued every one hundred RFCs; please be
94 sure the copy you are reading is current. Current copies may be
95 obtained from the Requests for Comments Editor (RFC-EDITOR) or from
96 the Internet Assigned Numbers Authority (IANA) (see the contact
97 information at the end of this memo).
98
99 See <a href="#section-6.1">Section 6.1</a> for a description of recent changes. In the official
100 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
101 denotes that it is new to this document or has been moved from one
102 protocol level to another, or differs from the previous edition of
103 this document.
104
105
106
107
108 <span class="grey">Internet Architecture Board Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</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="./rfc2026">RFC-2026</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.
161
162
163
164 <span class="grey">Internet Architecture Board Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</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
216
217
218
219
220 <span class="grey">Internet Architecture Board Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
223
224
225 Few protocols are required to be implemented in all systems; this is
226 because there is such a variety of possible systems, for example,
227 gateways, routers, terminal servers, workstations, and multi-user
228 hosts. The requirement level shown in this document is only a one
229 word label, which may not be sufficient to characterize the
230 implementation requirements for a protocol in all situations. For
231 some protocols, this document contains an additional status paragraph
232 (an applicability statement). In addition, more detailed status
233 information may be contained in separate requirements documents (see
234 <a href="#section-3">Section 3</a>).
235
236 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Request for Comments Documents</span>
237
238 The documents called Request for Comments (or RFCs) are the working
239 notes of the "Network Working Group", that is the Internet research
240 and development community. A document in this series may be on
241 essentially any topic related to computer communication, and may be
242 anything from a meeting report to the specification of a standard.
243
244 Notice:
245
246 All standards are published as RFCs, but not all RFCs specify
247 standards.
248
249 Anyone can submit a document for publication as an RFC. Submissions
250 must be made via electronic mail to the RFC Editor (see the contact
251 information at the end of this memo, and see <a href="./rfc2223">RFC 2223</a>).
252
253 While RFCs are not refereed publications, they do receive technical
254 review from the task forces, individual technical experts, or the RFC
255 Editor, as appropriate.
256
257 The RFC series comprises a wide range of documents, ranging from
258 informational documents of general interests to specifications of
259 standard Internet protocols. In cases where submission is intended
260 to document a proposed standard, draft standard, or standard
261 protocol, the RFC Editor will publish the document only with the
262 approval of the IESG. For documents describing experimental work,
263 the RFC Editor will notify the IESG before publication, allowing for
264 the possibility of review by the relevant IETF working group or IRTF
265 research group and provide those comments to the author. See <a href="#section-5.1">Section</a>
266 <a href="#section-5.1">5.1</a> for more detail.
267
268 Once a document is assigned an RFC number and published, that RFC is
269 never revised or re-issued with the same number. There is never a
270 question of having the most recent version of a particular RFC.
271 However, a protocol (such as File Transfer Protocol (FTP)) may be
272 improved and re-documented many times in several different RFCs. It
273
274
275
276 <span class="grey">Internet Architecture Board Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
279
280
281 is important to verify that you have the most recent RFC on a
282 particular protocol. This "Internet Official Protocol Standards"
283 memo is the reference for determining the correct RFC for the current
284 specification of each protocol.
285
286 The RFCs are available from the RFC-EDITOR, and a number of other
287 sites. For more information about obtaining RFCs, see Sections <a href="#section-7.4">7.4</a>
288 and 7.5.
289
290 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Other Reference Documents</span>
291
292 There are three other reference documents of interest in checking the
293 current status of protocol specifications and standardization. These
294 are the Assigned Numbers, the Gateway Requirements, and the Host
295 Requirements. Note that these documents are revised and updated at
296 different times; in case of differences between these documents, the
297 most recent must prevail.
298
299 Also, one should be aware of the MIL-STD publications on IP, TCP,
300 Telnet, FTP, and SMTP. These are described in <a href="#section-3.4">Section 3.4</a>.
301
302 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Assigned Numbers</span>
303
304 The "Assigned Numbers" document lists the assigned values of the
305 parameters used in the various protocols. For example, IP protocol
306 codes, TCP port numbers, Telnet Option Codes, ARP hardware types, and
307 Terminal Type names. Assigned Numbers was most recently issued as
308 <a href="./rfc1700">RFC-1700</a>.
309
310 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Requirements for IP Version 4 Routers</span>
311
312 This document reviews the specifications that apply to gateways and
313 supplies guidance and clarification for any ambiguities.
314 Requirements for IP Version 4 Routers is <a href="./rfc1812">RFC-1812</a>.
315
316 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Host Requirements</span>
317
318 This pair of documents reviews and updates the specifications that
319 apply to hosts, and it supplies guidance and clarification for any
320 ambiguities. Host Requirements was issued as <a href="./rfc1122">RFC-1122</a> and <a href="./rfc1123">RFC-1123</a>.
321
322 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. The MIL-STD Documents</span>
323
324 The DoD MIL-STD Internet specifications are out of date and have been
325 discontinued. The DoD's Joint Technical Architecture (JTA) lists the
326 current set of IETF STDs and RFCs that the DoD intends to use in all
327 new and upgraded Command, Control, Communications, Computers, and
328 Intelligence (C4I) acquisitions. A copy of the JTA can be obtained
329
330
331
332 <span class="grey">Internet Architecture Board Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
335
336
337 from <a href="http://www-jta.itsi.disa.mil">http://www-jta.itsi.disa.mil</a>.
338
339 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Explanation of Terms</span>
340
341 There are two independent categorization of protocols. The first is
342 the "maturity level" or STATE of standardization, one of "standard",
343 "draft standard", "proposed standard", "experimental",
344 "informational" or "historic". The second is the "requirement level"
345 or STATUS of this protocol, one of "required", "recommended",
346 "elective", "limited use", or "not recommended".
347
348 The status or requirement level is difficult to portray in a one word
349 label. These status labels should be considered only as an
350 indication, and a further description, or applicability statement,
351 should be consulted.
352
353 When a protocol is advanced to proposed standard or draft standard,
354 it is labeled with a current status.
355
356 At any given time a protocol occupies a cell of the following matrix.
357 Protocols are likely to be in cells in about the following
358 proportions (indicated by the relative number of Xs). A new protocol
359 is most likely to start in the (proposed standard, elective) cell, or
360 the (experimental, limited use) cell.
361
362 S T A T U S
363 Req Rec Ele Lim Not
364 +-----+-----+-----+-----+-----+
365 Std | X | XXX | XXX | | |
366 S +-----+-----+-----+-----+-----+
367 Draft | X | X | XXX | | |
368 T +-----+-----+-----+-----+-----+
369 Prop | | X | XXX | | |
370 A +-----+-----+-----+-----+-----+
371 Info | | | | | |
372 T +-----+-----+-----+-----+-----+
373 Expr | | | | XXX | |
374 E +-----+-----+-----+-----+-----+
375 Hist | | | | | XXX |
376 +-----+-----+-----+-----+-----+
377
378 What is a "system"?
379
380 Some protocols are particular to hosts and some to gateways; a few
381 protocols are used in both. The definitions of the terms below
382 will refer to a "system" which is either a host or a gateway (or
383 both). It should be clear from the context of the particular
384 protocol which types of systems are intended.
385
386
387
388 <span class="grey">Internet Architecture Board Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
391
392
393 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Definitions of Protocol State</span>
394
395 Every protocol listed in this document is assigned to a "maturity
396 level" or STATE of standardization: "standard", "draft standard",
397 "proposed standard", "experimental", or "historic".
398
399 4.1.1. Standard Protocol
400
401 The IESG has established this as an official standard protocol for
402 the Internet. These protocols are assigned STD numbers (see <a href="./rfc1311">RFC-</a>
403 <a href="./rfc1311">1311</a>). These are separated into two groups: (1) IP protocol and
404 above, protocols that apply to the whole Internet; and (2)
405 network-specific protocols, generally specifications of how to do
406 IP on particular types of networks.
407
408 4.1.2. Draft Standard Protocol
409
410 The IESG is actively considering this protocol as a possible
411 Standard Protocol. Substantial and widespread testing and comment
412 are desired. Comments and test results should be submitted to the
413 IESG. There is a possibility that changes will be made in a Draft
414 Standard Protocol before it becomes a Standard Protocol.
415
416 4.1.3. Proposed Standard Protocol
417
418 These are protocol proposals that may be considered by the IESG
419 for standardization in the future. Implementation and testing by
420 several groups is desirable. Revision of the protocol
421 specification is likely.
422
423 4.1.4. Experimental Protocol
424
425 A system should not implement an experimental protocol unless it
426 is participating in the experiment and has coordinated its use of
427 the protocol with the developer of the protocol.
428
429 Typically, experimental protocols are those that are developed as
430 part of an ongoing research project not related to an operational
431 service offering. While they may be proposed as a service
432 protocol at a later stage, and thus become proposed standard,
433 draft standard, and then standard protocols, the designation of a
434 protocol as experimental may sometimes be meant to suggest that
435 the protocol, although perhaps mature, is not intended for
436 operational use.
437
438
439
440
441
442
443
444 <span class="grey">Internet Architecture Board Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
447
448
449 4.1.5. Informational Protocol
450
451 Protocols developed by other standard organizations, or vendors,
452 or that are for other reasons outside the purview of the IESG, may
453 be published as RFCs for the convenience of the Internet community
454 as informational protocols.
455
456 4.1.6. Historic Protocol
457
458 These are protocols that are unlikely to ever become standards in
459 the Internet either because they have been superseded by later
460 developments or due to lack of interest.
461
462 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Definitions of Protocol Status</span>
463
464 This document lists a "requirement level" or STATUS for each
465 protocol. The status is one of "required", "recommended",
466 "elective", "limited use", or "not recommended".
467
468 4.2.1. Required Protocol
469
470 A system must implement the required protocols.
471
472 4.2.2. Recommended Protocol
473
474 A system should implement the recommended protocols.
475
476 4.2.3. Elective Protocol
477
478 A system may or may not implement an elective protocol. The
479 general notion is that if you are going to do something like this,
480 you must do exactly this. There may be several elective protocols
481 in a general area, for example, there are several electronic mail
482 protocols, and several routing protocols.
483
484 4.2.4. Limited Use Protocol
485
486 These protocols are for use in limited circumstances. This may be
487 because of their experimental state, specialized nature, limited
488 functionality, or historic state.
489
490 4.2.5. Not Recommended Protocol
491
492 These protocols are not recommended for general use. This may be
493 because of their limited functionality, specialized nature, or
494 experimental or historic state.
495
496
497
498
499
500 <span class="grey">Internet Architecture Board Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
503
504
505 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. The Standards Track</span>
506
507 This section discusses in more detail the procedures used by the RFC
508 Editor and the IESG in making decisions about the labeling and
509 publishing of protocols as standards.
510
511 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. The RFC Processing Decision Table</span>
512
513 Here is the current decision table for processing submissions by the
514 RFC Editor. The processing depends on who submitted it, and the
515 status they want it to have.
516
517 +==========================================================+
518 |**************| S O U R C E |
519 +==========================================================+
520 | Desired | IAB | IESG | IRSG | Other |
521 | Status | | | | |
522 +==========================================================+
523 | | | | | |
524 | Standard | Bogus | Publish | Bogus | Bogus |
525 | or | (2) | (1) | (2) | (2) |
526 | Draft | | | | |
527 | Standard | | | | |
528 +--------------+----------+----------+----------+----------+
529 | | | | | |
530 | | Refer | Publish | Refer | Refer |
531 | Proposed | (3) | (1) | (3) | (3) |
532 | Standard | | | | |
533 | | | | | |
534 +--------------+----------+----------+----------+----------+
535 | | | | | |
536 | | Notify | Publish | Notify | Notify |
537 | Experimental | (4) | (1) | (4) | (4) |
538 | Protocol | | | | |
539 | | | | | |
540 +--------------+----------+----------+----------+----------+
541 | | | | | |
542 | Information | Publish | Publish |Discretion|Discretion|
543 | or Opinion | (1) | (1) | (5) | (5) |
544 | Paper | | | | |
545 | | | | | |
546 +==========================================================+
547
548 (1) Publish.
549
550 (2) Bogus. Inform the source of the rules. RFCs specifying
551 Standard, or Draft Standard must come from the IESG, only.
552
553
554
555
556 <span class="grey">Internet Architecture Board Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
559
560
561 (3) Refer to an Area Director for review by a WG. Expect to see
562 the document again only after approval by the IESG.
563
564 (4) Notify both the IESG and IRSG. If no concerns are raised in
565 two weeks then do Discretion (5), else RFC Editor to resolve
566 the concerns or do Refer (3).
567
568 (5) RFC Editor's discretion. The RFC Editor decides if a review
569 is needed and if so by whom. RFC Editor decides to publish or
570 not.
571
572 Of course, in all cases the RFC Editor can request or make minor
573 changes for style, format, and presentation purposes.
574
575 The IESG has designated the IESG Secretary as its agent for
576 forwarding documents with IESG approval and for registering concerns
577 in response to notifications (4) to the RFC Editor. Documents from
578 Area Directors or Working Group Chairs may be considered in the same
579 way as documents from "other".
580
581 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. The Standards Track Diagram</span>
582
583 There is a part of the STATUS and STATE categorization that is called
584 the standards track. Actually, only the changes of state are
585 significant to the progression along the standards track, though the
586 status assignments may change as well.
587
588 The states illustrated by single line boxes are temporary states,
589 those illustrated by double line boxes are long term states. A
590 protocol will normally be expected to remain in a temporary state for
591 several months (minimum six months for proposed standard, minimum
592 four months for draft standard). A protocol may be in a long term
593 state for many years.
594
595 A protocol may enter the standards track only on the recommendation
596 of the IESG; and may move from one state to another along the track
597 only on the recommendation of the IESG. That is, it takes action by
598 the IESG to either start a protocol on the track or to move it along.
599
600 Generally, as the protocol enters the standards track a decision is
601 made as to the eventual STATUS, requirement level or applicability
602 (elective, recommended, or required) the protocol will have, although
603 a somewhat less stringent current status may be assigned, and it then
604 is placed in the the proposed standard STATE with that status. So
605 the initial placement of a protocol is into state 1. At any time the
606 STATUS decision may be revisited.
607
608
609
610
611
612 <span class="grey">Internet Architecture Board Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
615
616
617 |
618 +&lt;----------------------------------------------+
619 | ^
620 V 0 | 4
621 +-----------+ +===========+
622 | enter |--&gt;----------------+--------------&gt;|experiment |
623 +-----------+ | +=====+=====+
624 | |
625 V 1 |
626 +-----------+ V
627 | proposed |--------------&gt;+
628 +---&gt;+-----+-----+ |
629 | | |
630 | V 2 |
631 +&lt;---+-----+-----+ V
632 | draft std |--------------&gt;+
633 +---&gt;+-----+-----+ |
634 | | |
635 | V 3 |
636 +&lt;---+=====+=====+ V
637 | standard |--------------&gt;+
638 +=====+=====+ |
639 |
640 V 5
641 +=====+=====+
642 | historic |
643 +===========+
644
645 The transition from proposed standard (1) to draft standard (2) can
646 only be by action of the IESG and only after the protocol has been
647 proposed standard (1) for at least six months.
648
649 The transition from draft standard (2) to standard (3) can only be by
650 action of the IESG and only after the protocol has been draft
651 standard (2) for at least four months.
652
653 Occasionally, the decision may be that the protocol is not ready for
654 standardization and will be assigned to the experimental state (4).
655 This is off the standards track, and the protocol may be resubmitted
656 to enter the standards track after further work. There are other
657 paths into the experimental and historic states that do not involve
658 IESG action.
659
660 Sometimes one protocol is replaced by another and thus becomes
661 historic, or it may happen that a protocol on the standards track is
662 in a sense overtaken by another protocol (or other events) and
663 becomes historic (state 5).
664
665
666
667
668 <span class="grey">Internet Architecture Board Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
671
672
673 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. The Protocols</span>
674
675 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>
676 - 6.10 list the standards in groups by protocol state.
677
678 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Recent Changes</span>
679
680 <span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>. New RFCs:</span>
681
682 2428 - FTP Extensions for IPv6 and NATs
683
684 A Proposed Standard protocol.
685
686 2427 - Multiprotocol Interconnect over Frame Relay
687
688 A Standard protocol.
689
690 2426 - vCard MIME Directory Profile
691
692 A Proposed Standard protocol.
693
694 2425 - A MIME Content-Type for Directory Information
695
696 A Proposed Standard protocol.
697
698 2424 - Content Duration MIME Header Definition
699
700 A Proposed Standard protocol.
701
702 2423 - VPIM Voice Message MIME Sub-type Registration
703
704 A Proposed Standard protocol.
705
706 2422 - Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type
707 Registration
708
709 A Proposed Standard protocol.
710
711 2421 - Voice Profile for Internet Mail - version 2
712
713 A Proposed Standard protocol.
714
715 2420 - The PPP Triple-DES Encryption Protocol (3DESE)
716
717 A Proposed Standard protocol.
718
719
720
721
722
723
724 <span class="grey">Internet Architecture Board Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
727
728
729 2419 - The PPP DES Encryption Protocol, Version 2 (DESE-bis)
730
731 A Proposed Standard protocol.
732
733 2418 - IETF Working Group Guidelines and Procedures
734
735 This is a Best Current Practices document and does not
736 specify any level of standard.
737
738 2417 - Definitions of Managed Objects for Multicast over UNI
739 3.0/3.1 based ATM Network
740
741 A Proposed Standard protocol.
742
743 2416 - When TCP Starts Up With Four Packets Into Only Three
744 Buffers
745
746 This is an information document and does not specify any
747 level of standard.
748
749 2415 - Simulation Studies of Increased Initial TCP Window Size
750
751 This is an information document and does not specify any
752 level of standard.
753
754 2414 - Increasing TCP's Initial Window
755
756 An Experimental protocol.
757
758 2413 - Dublin Core Metadata for Resource Discovery
759
760 This is an information document and does not specify any
761 level of standard.
762
763 2412 - Not yet issued.
764
765 2411 - Not yet issued.
766
767 2410 - Not yet issued.
768
769 2409 - Not yet issued.
770
771 2408 - Not yet issued.
772
773 2407 - Not yet issued.
774
775
776
777
778
779
780 <span class="grey">Internet Architecture Board Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
783
784
785 2406 - Not yet issued.
786
787 2405 - Not yet issued.
788
789 2404 - Not yet issued.
790
791 2403 - Not yet issued.
792
793 2402 - Not yet issued.
794
795 2401 - Not yet issued.
796
797 2400 - This memo.
798
799 2399 - Not yet issued.
800
801 2398 - Some Testing Tools for TCP Implementors
802
803 This is an information document and does not specify any
804 level of standard.
805
806 2397 - The "data" URL scheme
807
808 A Proposed Standard protocol.
809
810 2396 - Uniform Resource Identifiers (URI): Generic Syntax
811
812 A Draft Standard protocol.
813
814 2395 - Not yet issued.
815
816 2394 - Not yet issued.
817
818 2393 - Not yet issued.
819
820 2392 - Content-ID and Message-ID Uniform Resource Locators
821
822 A Proposed Standard protocol.
823
824 2391 - Load Sharing using IP Network Address Translation (LSNAT)
825
826 This is an information document and does not specify any
827 level of standard.
828
829 2390 - Inverse Address Resolution Protocol
830
831 A Draft Standard protocol.
832
833
834
835
836 <span class="grey">Internet Architecture Board Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
839
840
841 2389 - Feature negotiation mechanism for the File Transfer
842 Protocol
843
844 A Proposed Standard protocol.
845
846 2388 - Returning Values from Forms: multipart/form-data
847
848 A Proposed Standard protocol.
849
850 2387 - The MIME Multipart/Related Content-type
851
852 A Proposed Standard protocol.
853
854 2386 - A Framework for QoS-based Routing in the Internet
855
856 This is an information document and does not specify any
857 level of standard.
858
859 2385 - Protection of BGP Sessions via the TCP MD5 Signature Option
860
861 A Proposed Standard protocol.
862
863 2384 - POP URL Scheme
864
865 A Proposed Standard protocol.
866
867 2383 - ST2+ over ATM Protocol Specification - UNI 3.1 Version
868
869 This is an information document and does not specify any
870 level of standard.
871
872 2382 - A Framework for Integrated Services and RSVP over ATM
873
874 This is an information document and does not specify any
875 level of standard.
876
877 2381 - Interoperation of Controlled-Load Service and Guaranteed
878 Service with ATM
879
880 A Proposed Standard protocol.
881
882 2380 - RSVP over ATM Implementation Requirements
883
884 A Proposed Standard protocol.
885
886
887
888
889
890
891
892 <span class="grey">Internet Architecture Board Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
895
896
897 2379 - RSVP over ATM Implementation Guidelines
898
899 This is a Best Current Practices document and does not
900 specify any level of standard.
901
902 2378 - Not yet issued.
903
904 2377 - Not yet issued.
905
906 2376 - XML Media Types
907
908 This is an information document and does not specify any
909 level of standard.
910
911 2375 - IPv6 Multicast Address Assignments
912
913 This is an information document and does not specify any
914 level of standard.
915
916 2374 - An IPv6 Aggregatable Global Unicast Address Format
917
918 A Proposed Standard protocol.
919
920 2373 - IP Version 6 Addressing Architecture
921
922 A Proposed Standard protocol.
923
924 2372 - Transaction Internet Protocol - Requirements and
925 Supplemental Information
926
927 This is an information document and does not specify any
928 level of standard.
929
930 2371 - Transaction Internet Protocol Version 3.0
931
932 A Proposed Standard protocol.
933
934 2370 - The OSPF Opaque LSA Option
935
936 A Proposed Standard protocol.
937
938 2369 - The Use of URLs as Meta-Syntax for Core Mail List Commands
939 and their Transport through Message Header Field
940
941 A Proposed Standard protocol.
942
943
944
945
946
947
948 <span class="grey">Internet Architecture Board Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
951
952
953 2368 - The mailto URL scheme
954
955 A Proposed Standard protocol.
956
957 2367 - PF_KEY Key Management API, Version 2
958
959 This is an information document and does not specify any
960 level of standard.
961
962 2366 - Definitions of Managed Objects for Multicast over UNI
963 3.0/3.1 based ATM Networks
964
965 A Proposed Standard protocol.
966
967 2365 - Administratively Scoped IP Multicast
968
969 This is a Best Current Practices document and does not
970 specify any level of standard.
971
972 2364 - PPP Over AAL
973
974 A Proposed Standard protocol.
975
976 2363 - PPP Over FUNI
977
978 A Proposed Standard protocol.
979
980 2362 - Protocol Independent Multicast-Sparse Mode (PIM-SM):
981 Protocol Specification
982
983 An Experimental protocol.
984
985 2361 - WAVE and AVI Codec Registries
986
987 This is an information document and does not specify any
988 level of standard.
989
990 2360 - Guide for Internet Standards Writers
991
992 This is a Best Current Practices document and does not
993 specify any level of standard.
994
995 2359 - IMAP4 UIDPLUS extension
996
997 A Proposed Standard protocol.
998
999
1000
1001
1002
1003
1004 <span class="grey">Internet Architecture Board Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1007
1008
1009 2358 - Definitions of Managed Objects for the Ethernet-like
1010 Interface Types
1011
1012 A Proposed Standard protocol.
1013
1014 2357 - IETF Criteria for Evaluating Reliable Multicast Transport
1015 and Application Protocols
1016
1017 This is an information document and does not specify any
1018 level of standard.
1019
1020 2356 - Sun's SKIP Firewall Traversal for Mobile IP
1021
1022 This is an information document and does not specify any
1023 level of standard.
1024
1025 2355 - TN3270 Enhancements
1026
1027 A Draft Standard protocol.
1028
1029 2354 - Options for Repair of Streaming Media
1030
1031 This is an information document and does not specify any
1032 level of standard.
1033
1034 2353 - APPN/HPR in IP Networks APPN Implementers' Workshop Closed
1035 Pages Document
1036
1037 This is an information document and does not specify any
1038 level of standard.
1039
1040 2350 - Expectations for Computer Security Incident Response
1041
1042 This is a Best Current Practices document and does not
1043 specify any level of standard.
1044
1045 2340 - Nortel's Virtual Network Switching (VNS) Overview
1046
1047 This is an information document and does not specify any
1048 level of standard.
1049
1050 2336 - Classical IP and ARP over ATM to NHRP Transition
1051
1052 This is an information document and does not specify any
1053 level of standard.
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Internet Architecture Board Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1063
1064
1065 <span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>. Other Changes:</span>
1066
1067 The following are changes to protocols listed in the previous
1068 edition.
1069
1070 2073 - An IPv6 Provider-Based Unicast Address Format
1071
1072 Moved to Historic.
1073
1074 1884 - IP Version 6 Addressing Architecture
1075
1076 Moved to Historic.
1077
1078 0658 - Telnet Output Linefeed Disposition
1079
1080 Moved to Historic.
1081
1082 0657 - Telnet Output Vertical Tab Disposition Option
1083
1084 Moved to Historic.
1085
1086 0656 - Telnet Output Vertical Tabstops Option
1087
1088 Moved to Historic.
1089
1090 0655 - Telnet Output Formfeed Disposition Option
1091
1092 Moved to Historic.
1093
1094 0654 - Telnet Output Horizontal Tab Disposition Option
1095
1096 Moved to Historic.
1097
1098 0653 - Telnet Output Horizontal Tabstops Option
1099
1100 Moved to Historic.
1101
1102 0652 - Telnet Output Carriage-Return Disposition Option
1103
1104 Moved to Historic.
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Internet Architecture Board Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1119
1120
1121 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Standard Protocols</span>
1122
1123 Protocol Name Status RFC STD *
1124 ======== ===================================== ======== ==== === =
1125 -------- Internet Official Protocol Standards Req 2400 1
1126 -------- Assigned Numbers Req 1700 2
1127 -------- Host Requirements - Communications Req 1122 3
1128 -------- Host Requirements - Applications Req 1123 3
1129 IP Internet Protocol Req 791 5
1130 as amended by:--------
1131 -------- IP Subnet Extension Req 950 5
1132 -------- IP Broadcast Datagrams Req 919 5
1133 -------- IP Broadcast Datagrams with Subnets Req 922 5
1134 ICMP Internet Control Message Protocol Req 792 5
1135 IGMP Internet Group Multicast Protocol Rec 1112 5
1136 UDP User Datagram Protocol Rec 768 6
1137 TCP Transmission Control Protocol Rec 793 7
1138 TELNET Telnet Protocol Rec 854,855 8
1139 FTP File Transfer Protocol Rec 959 9
1140 SMTP Simple Mail Transfer Protocol Rec 821 10
1141 SMTP-SIZE SMTP Service Ext for Message Size Rec 1870 10
1142 SMTP-EXT SMTP Service Extensions Rec 1869 10
1143 MAIL Format of Electronic Mail Messages Rec 822 11
1144 CONTENT Content Type Header Field Rec 1049 11
1145 NTPV2 Network Time Protocol (Version 2) Rec 1119 12
1146 DOMAIN Domain Name System Rec 1034,1035 13
1147 DNS-MX Mail Routing and the Domain System Rec 974 14
1148 SNMP Simple Network Management Protocol Rec 1157 15
1149 SMI Structure of Management Information Rec 1155 16
1150 Concise-MIB Concise MIB Definitions Rec 1212 16
1151 MIB-II Management Information Base-II Rec 1213 17
1152 NETBIOS NetBIOS Service Protocols Ele 1001,1002 19
1153 ECHO Echo Protocol Rec 862 20
1154 DISCARD Discard Protocol Ele 863 21
1155 CHARGEN Character Generator Protocol Ele 864 22
1156 QUOTE Quote of the Day Protocol Ele 865 23
1157 USERS Active Users Protocol Ele 866 24
1158 DAYTIME Daytime Protocol Ele 867 25
1159 TIME Time Server Protocol Ele 868 26
1160 TFTP Trivial File Transfer Protocol Ele 1350 33
1161 TP-TCP ISO Transport Service on top of the TCP Ele 1006 35
1162 ETHER-MIB Ethernet MIB Ele 1643 50
1163 PPP Point-to-Point Protocol (PPP) Ele 1661 51
1164 PPP-HDLC PPP in HDLC Framing Ele 1662 51
1165 IP-SMDS IP Datagrams over the SMDS Service Ele 1209 52
1166 POP3 Post Office Protocol, Version 3 Ele 1939 53
1167 OSPF2 Open Shortest Path First Routing V2 Ele 2328 54
1168 IP-FR Multiprotocol over Frame Relay Ele 2427 55*
1169
1170
1171
1172 <span class="grey">Internet Architecture Board Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1175
1176
1177 [Note: an asterisk at the end of a line indicates a change from the
1178 previous edition of this document.]
1179
1180 Applicability Statements:
1181
1182 IGMP -- The Internet Architecture Board intends to move towards
1183 general adoption of IP multicasting, as a more efficient solution
1184 than broadcasting for many applications. The host interface has been
1185 standardized in <a href="./rfc1112">RFC-1112</a>; however, multicast-routing gateways are in
1186 the experimental stage and are not widely available. An Internet
1187 host should support all of <a href="./rfc1112">RFC-1112</a>, except for the IGMP protocol
1188 itself which is optional; see <a href="./rfc1122">RFC-1122</a> for more details. Even
1189 without IGMP, implementation of <a href="./rfc1112">RFC-1112</a> will provide an important
1190 advance: IP-layer access to local network multicast addressing. It
1191 is expected that IGMP will become recommended for all hosts and
1192 gateways at some future date.
1193
1194 SMI, MIB-II SNMP -- The Internet Architecture Board recommends that
1195 all IP and TCP implementations be network manageable. At the current
1196 time, this implies implementation of the Internet MIB-II (<a href="./rfc1213">RFC-1213</a>),
1197 and at least the recommended management protocol SNMP (<a href="./rfc1157">RFC-1157</a>).
1198
1199 RIP -- The Routing Information Protocol (RIP) is widely implemented
1200 and used in the Internet. However, both implementors and users
1201 should be aware that RIP has some serious technical limitations as a
1202 routing protocol. The IETF is currently devpeloping several
1203 candidates for a new standard "open" routing protocol with better
1204 properties than RIP. The IAB urges the Internet community to track
1205 these developments, and to implement the new protocol when it is
1206 standardized; improved Internet service will result for many users.
1207
1208 TP-TCP -- As OSI protocols become more widely implemented and used,
1209 there will be an increasing need to support interoperation with the
1210 TCP/IP protocols. The Internet Engineering Task Force is formulating
1211 strategies for interoperation. <a href="./rfc1006">RFC-1006</a> provides one interoperation
1212 mode, in which TCP/IP is used to emulate TP0 in order to support OSI
1213 applications. Hosts that wish to run OSI connection-oriented
1214 applications in this mode should use the procedure described in <a href="./rfc1006">RFC-</a>
1215 <a href="./rfc1006">1006</a>. In the future, the IAB expects that a major portion of the
1216 Internet will support both TCP/IP and OSI (inter-)network protocols
1217 in parallel, and it will then be possible to run OSI applications
1218 across the Internet using full OSI protocol "stacks".
1219
1220 OSPF -- <a href="./rfc1370">RFC 1370</a> is an applicability statement for OSPF.
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Internet Architecture Board Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1231
1232
1233 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Network-Specific Standard Protocols</span>
1234
1235 All Network-Specific Standards have Elective status.
1236
1237 Protocol Name State RFC STD *
1238 ======== ===================================== ===== ===== === =
1239 IP-ATM Classical IP and ARP over ATM Prop 2225
1240 ATM-ENCAP Multiprotocol Encapsulation over ATM Prop 1483
1241 IP-TR-MC IP Multicast over Token-Ring LANs Prop 1469
1242 IP-FDDI Transmission of IP and ARP over FDDI Net Std 1390 36
1243 IP-X.25 X.25 and ISDN in the Packet Mode Draft 1356
1244 ARP Address Resolution Protocol Std 826 37
1245 RARP A Reverse Address Resolution Protocol Std 903 38
1246 IP-ARPA Internet Protocol on ARPANET Std BBN1822 39
1247 IP-WB Internet Protocol on Wideband Network Std 907 40
1248 IP-E Internet Protocol on Ethernet Networks Std 894 41
1249 IP-EE Internet Protocol on Exp. Ethernet Nets Std 895 42
1250 IP-IEEE Internet Protocol on IEEE 802 Std 1042 43
1251 IP-DC Internet Protocol on DC Networks Std 891 44
1252 IP-HC Internet Protocol on Hyperchannel Std 1044 45
1253 IP-ARC Transmitting IP Traffic over ARCNET Nets Std 1201 46
1254 IP-SLIP Transmission of IP over Serial Lines Std 1055 47
1255 IP-NETBIOS Transmission of IP over NETBIOS Std 1088 48
1256 IP-IPX Transmission of 802.2 over IPX Networks Std 1132 49
1257 IP-HIPPI IP over HIPPI Draft 2067
1258
1259 [Note: an asterisk at the end of a line indicates a change from the
1260 previous edition of this document.]
1261
1262 Applicability Statements:
1263
1264 It is expected that a system will support one or more physical
1265 networks and for each physical network supported the appropriate
1266 protocols from the above list must be supported. That is, it is
1267 elective to support any particular type of physical network, and for
1268 the physical networks actually supported it is required that they be
1269 supported exactly according to the protocols in the above list. See
1270 also the Host and Gateway Requirements RFCs for more specific
1271 information on network-specific ("link layer") protocols.
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Internet Architecture Board Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1287
1288
1289 <span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Draft Standard Protocols</span>
1290
1291 Protocol Name Status RFC
1292 ======== ===================================== ============== =====
1293 URI-GEN URI: Generic Syntax Elective 2396*
1294 IARP Inverse Address Resolution Protocol Elective 2390*
1295 TFTP-Opt TFTP Options Elective 2349
1296 TFTP-Blk TFTP Blocksize Option Elective 2348
1297 TFTP-Ext TFTP Option Extension Elective 2347
1298 ONE-PASS One-Time Password System Elective 2289
1299 SMTP-Pipe SMTP Serv. Ext. for Command Pipelining Elective 2197
1300 DHCP-BOOTP DHCP Options and BOOTP Extensions Recommended 2132
1301 DHCP Dynamic Host Configuration Protocol Elective 2131
1302 FRAME-MIB Management Information Base for Frame Elective 2115
1303 ------- Clarifications and Extensions BOOTP Elective 1542
1304 DHCP-BOOTP Interoperation Between DHCP and BOOTP Elective 1534
1305 BOOTP Bootstrap Protocol Recommended 951,2132
1306 MIME-CONF MIME Conformance Criteria Elective 2049
1307 MIME-MSG MIME Msg Header Ext for Non-ASCII Elective 2047
1308 MIME-MEDIA MIME Media Types Elective 2046
1309 MIME Multipurpose Internet Mail Extensions Elective 2045
1310 PPP-CHAP PPP Challenge Handshake Authentication Elective 1994
1311 PPP-MP PPP Multilink Protocol Elective 1990
1312 PPP-LINK PPP Link Quality Monitoring Elective 1989
1313 COEX-MIB Coexistence between SNMPV1 &amp; SNMPV2 Elective 1908
1314 SNMPv2-MIB MIB for SNMPv2 Elective 1907
1315 TRANS-MIB Transport Mappings for SNMPv2 Elective 1906
1316 OPS-MIB Protocol Operations for SNMPv2 Elective 1905
1317 CONF-MIB Conformance Statements for SNMPv2 Elective 1904
1318 CONV-MIB Textual Conventions for SNMPv2 Elective 1903
1319 SMIV2 SMI for SNMPv2 Elective 1902
1320 CON-MD5 Content-MD5 Header Field Elective 1864
1321 OSPF-MIB OSPF Version 2 MIB Elective 1850
1322 STR-REP String Representation ... Elective 1779
1323 X.500syn X.500 String Representation ... Elective 1778
1324 X.500lite X.500 Lightweight ... Elective 1777
1325 BGP-4-APP Application of BGP-4 Elective 1772
1326 BGP-4 Border Gateway Protocol 4 Elective 1771
1327 PPP-DNCP PPP DECnet Phase IV Control Protocol Elective 1762
1328 RMON-MIB Remote Network Monitoring MIB Elective 1757
1329 802.5-MIB IEEE 802.5 Token Ring MIB Elective 1748
1330 RIP2-MIB RIP Version 2 MIB Extension Elective 1724
1331 RIP2 RIP Version 2-Carrying Additional Info. Elective 1723
1332 RIP2-APP RIP Version 2 Protocol App. Statement Elective 1722
1333 SIP-MIB SIP Interface Type MIB Elective 1694
1334 ------- Def Man Objs Parallel-printer-like Elective 1660
1335 ------- Def Man Objs RS-232-like Elective 1659
1336 ------- Def Man Objs Character Stream Elective 1658
1337
1338
1339
1340 <span class="grey">Internet Architecture Board Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1343
1344
1345 BGP-4-MIB BGP-4 MIB Elective 1657
1346 SMTP-8BIT SMTP Service Ext or 8bit-MIMEtransport Elective 1652
1347 OSI-NSAP Guidelines for OSI NSAP Allocation Elective 1629
1348 ISO-TS-ECHO Echo for ISO-8473 Elective 1575
1349 DECNET-MIB DECNET MIB Elective 1559
1350 BRIDGE-MIB BRIDGE-MIB Elective 1493
1351 NTPV3 Network Time Protocol (Version 3) Elective 1305
1352 IP-MTU Path MTU Discovery Elective 1191
1353 FINGER Finger Protocol Elective 1288
1354 NICNAME WhoIs Protocol Elective 954
1355
1356 [Note: an asterisk at the end of a line indicates a change from the
1357 previous edition of this document.]
1358
1359 Applicability Statements:
1360
1361 PPP -- Point to Point Protocol is a method of sending IP over serial
1362 lines, which are a type of physical network. It is anticipated that
1363 PPP will be advanced to the network-specifics standard protocol state
1364 in the future.
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 Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1399
1400
1401 <span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Proposed Standard Protocols</span>
1402
1403 Protocol Name Status RFC
1404 ======== ===================================== ============== =====
1405 -------- FTP Extensions for IPv6 and NATs Elective 2428*
1406 MIME-VCARD vCard MIME Directory Profile Elective 2426*
1407 TXT-DIR MIME Content-Type for Directory Info Elective 2425*
1408 CONT-DUR Content-Duration MIME Header Elective 2424*
1409 MIME-VPIM VPIM Voice Message Elective 2423*
1410 MIME-ADPCM Toll Quality Voice - 32 kbit/s ADPC Elective 2422*
1411 MIME-VP2 Voice Profile for Internet Mail V2 Elective 2421*
1412 -------- Multicast/UNI 3.0/3.1 based ATM MIB Elective 2417*
1413 DATA-URL "data" URL scheme Elective 2397*
1414 CIDMID-URL Content-ID and Message-ID URLs Elective 2392*
1415 FTP-FNEGO Feature negotiation mechanism for FTP Elective 2389*
1416 -------- MIME Multipart/form-data Elective 2388*
1417 MIME-RELAT MIME Multipart/Related Content-type Elective 2387*
1418 -------- Protection of BGP Sessions via TCP MD5 Elective 2385*
1419 POP-URL POP URL Scheme Elective 2384*
1420 -------- Interoperation of CLS and GS with ATM Elective 2381*
1421 -------- RSVP over ATM Imple. Requirements Elective 2380*
1422 -------- IPv6 Aggreg. Global Unicast Addr. Format Elective 2374*
1423 -------- IPv6 Addressing Architecture Elective 2373*
1424 TIPV3 Transaction Internet Protocol V3 Elective 2371*
1425 OSPF-LSA OSPF Opaque LSA Option Elective 2370*
1426 -------- Use of URLs as Meta-Syntax... Elective 2369*
1427 URLMAILTO mailto URL scheme Elective 2368*
1428 PPP-AAL PPP Over AAL Elective 2364*
1429 PPP-FUNI PPP Over FUNI Elective 2363*
1430 IMAP4UIDPL IMAP4 UIDPLUS Extension Elective 2359*
1431 -------- Ethernet-like Interface Types MIB Elective 2358*
1432 MOBILIPREV Reverse Tunneling for Mobile IP Elective 2344
1433 IMAP4NAME IMAP4 Namespace Elective 2342
1434 VRRP Virtual Router Redundancy Protocol Elective 2338
1435 NHRP-SCSP Distributed NHRP Service Using SCSP Elective 2335
1436 SCSP Server Cache Synchronization Protocol Elective 2334
1437 NHRP-APP NHRP Protocol Applicability Statement Elective 2333
1438 NHRP NBMA Next Hop Resolution Protocol Elective 2332
1439 UNI-SIG ATM Sig Support (IPOA) UNI Signalling Elective 2331
1440 SDP Session Description Protocol Elective 2327
1441 RTSP Real Time Streaming Protocol Elective 2326
1442 IPOA-MIB Classical IP and ARP Over ATM MIB Elective 2320
1443 DNS-NCACHE Negative Caching of DNS Queries Elective 2308
1444 SMFAX-IM Simple Mode of FAX Using Internet Mail Elective 2305
1445 MINFAX-IM Minimal FAX addr format in Internet Mail Elective 2304
1446 MIN-PSTN Min. PSTN addr format in Internet Mail Elective 2303
1447 TIFF Tag Image File Format Elective 2302
1448 FFIF File Format for Internet Fax Elective 2301
1449
1450
1451
1452 <span class="grey">Internet Architecture Board Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1455
1456
1457 EMF-MDN Extensible Message Format for MDN Elective 2298
1458 OR-ADD O/R Address hierarchy in X.500 Elective 2294
1459 SUBTABLE Tables and Subtrees in X.500 Elective 2293
1460 -------- Mobile-IPv4 Config Opt for PPP IPCP Elective 2290
1461 SLM-APP System-Level Managed Objects for Apps Elective 2287
1462 PPP-EAP PPP Extensible Authentication Protocol Elective 2284
1463 MEXT-BGP4 Multiprotocol Extensions for BGP-4 Elective 2283
1464 RPSL Routing Policy Specification Language Elective 2280
1465 UTF-8 UTF-8 transformation format of ISO 10646 Elective 2279
1466 VACM-SNMP View-based Access Control Model for SMMP Elective 2275
1467 USM-SNMPV3 User-based Security Model for SNMPv3 Elective 2274
1468 SNMPV3-APP SNMPv3 Applications Elective 2273
1469 MPD-SNMP Message Processing &amp; Dispatching SNMP Elective 2272
1470 ARCH-SNMP Architecture Describing SNMP Frameworks Elective 2271
1471 -------- IEEE 802.12 Repeater MIB Elective 2266
1472 AGENTX Agent Extensibility Protocol Elective 2257
1473 -------- Summary of the X.500(96) with LDAPv3 Elective 2256
1474 LDAP-URL LDAP URL Format Elective 2255
1475 STR-LDAP String Rep of LDAP Search Filters Elective 2254
1476 LDAP3-UTF8 LDAPv3: UTF-8 String Rep Elective 2253
1477 LDAP3-ATD LDAP3-: Attribute Syntax Definitions Elective 2252
1478 LDAPV3 Lightweight Directory Access Protocol Elective 2251
1479 RTP-MPEG RTP Payload Format for MPEG1/MPEG2 Elective 2250
1480 MAIL-MIB Mail Monitoring MIB Elective 2249
1481 NSM-MIB Network Services Monitoring MIB Elective 2248
1482 -------- Using Domains LDAP/X.500 Dist. Names Elective 2247
1483 SASL-ANON Anonymous SASL Mechanism Elective 2245
1484 ACAP Application Configuration Access Elective 2244
1485 OTP-ER OTP Extended Responses Elective 2243
1486 NETWAREIP NetWare/IP Domain Name and Information Elective 2242
1487 DHCP-NDS DHCP Options for Novell Directory Serv. Elective 2241
1488 MAUS-MIB IEEE 802.3 Medium Attachment Units MIB Elective 2239
1489 HPR-MIB Definitions of Managed Objects for HPR Elective 2238
1490 IGMP Internet Group Management Protocol V2 Elective 2236
1491 ABNF Augmented BNF for Syntax Specifications Elective 2234
1492 INTERGRMIB Interfaces Group MIB Elective 2233
1493 DLUR-MIB Definitions of Managed Objects for DLUR Elective 2232
1494 MIME-EXT MIME Parameter Value &amp; Encoded Word Ext Elective 2231
1495 FTPSECEXT FTP Security Extensions Elective 2228
1496 --------- Simple Hit-Metering, Usage-Limiting HTTP Elective 2227
1497 --------- IP Broadcast over ATM Networks Elective 2226
1498 SASL Simple Authentication and Security Layer Elective 2222
1499 IMAP4LOGIN IMAP4 Login Referrals Elective 2221
1500 --------- Schema for Internet White Pages Service Elective 2218
1501 --------- Characterization Parameters for ISNE Elective 2215
1502 --------- Integrated Services MIB Guar Serv Ext Elective 2214
1503 --------- Integrated Services MIB using SMIv2 Elective 2213
1504 GQOS Spec. of Guaranteed Quality of Service Elective 2212
1505
1506
1507
1508 <span class="grey">Internet Architecture Board Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1511
1512
1513 --------- Spec. of Controlled-Load Net Ele Serv Elective 2211
1514 RSVP-IS Use of RSVP with IETF Integrated Serv Elective 2210
1515 RSVP-MPR RSVP Messaging Processing Rules Elective 2209
1516 RSVP-APP RSVP Applicability Statement Elective 2208
1517 RSVP-IPSEC RSVP Extensions for IPSEC Data Flows Elective 2207
1518 RSVP-MIB RSVP Management Information Base Elective 2206
1519 RSVP Resource ReSerVation Protocol V1 Elective 2205
1520 RPCSEC-GSS RPCSEC_GSS Protocol Specification Elective 2203
1521 RTP-RAD RTP Payload for Redundant Audio Data Elective 2198
1522 IMAPPOPAU IMAP/POP AUTHorize Extension Elective 2195
1523 IMAP4MAIL IMAP4 Mailbox Referrals Elective 2193
1524 IMAP-URL IMAP URL Scheme Elective 2192
1525 --------- RTP Payload Format for H.263 Video ST Elective 2190
1526 --------- The Content-Disposition Header Field Elective 2183
1527 DNS-CLAR Clarifications to the DNS Specification Elective 2181
1528 IMAP4-IDLE IMAP4 IDLE command Elective 2177
1529 SLP Service Location Protocol Elective 2165
1530 --------- X.500/LDAP Directory/MIXER Address Map. Elective 2164
1531 DNS-MCGAM Using DNS to Distribute MCGAM Elective 2163
1532 --------- Carrying PostScript in X.400 and MIME Elective 2160
1533 --------- A MIME Body Part for FAX Elective 2159
1534 --------- X.400 Image Body Parts Elective 2158
1535 --------- Mapping between X.400 and <a href="./rfc822">RFC-822</a>/MIME Elective 2157
1536 MIXER Mime Internet X.400 Enhanced Relay Elective 2156
1537 APPN-MIB Definitions of Managed Objects for APPN Elective 2155
1538 IPv6-Jumbo TCP and UDP over IPv6 Jumbograms Elective 2147
1539 MAIL-SERV Mailbox Names for Common Services Elective 2142
1540 URN-SYNTAX URN Syntax Elective 2141
1541 RADIUS Remote Authentication Dial In Service Elective 2138
1542 SDNSDU Secure Domain Name System Dynamic Update Elective 2137
1543 DNS-UPDATE Dynamic Updates in the DNS Elective 2136
1544 DC-MIB Dial Control MIB using SMIv2 Elective 2128
1545 ISDN-MIB ISDN MIB using SMIv2 Elective 2127
1546 ITOT ISO Transport Service on top of TCP Elective 2126
1547 BAP-BACP PPP-BAP, PPP-BACP Elective 2125
1548 VEMMI-URL VEMMI URL Specification Elective 2122
1549 ROUT-ALERT IP Router Alert Option Elective 2113
1550 MHTML MIME E-mail Encapsulation Elective 2110
1551 HTTP-STATE HTTP State Management Mechanism Elective 2109
1552 802.3-MIB 802.3 Repeater MIB using SMIv2 Elective 2108
1553 PPP-NBFCP PPP NetBIOS Frames Control Protocol Elective 2097
1554 TABLE-MIB IP Forwarding Table MIB Elective 2096
1555 RIP-TRIG Trigger RIP Elective 2091
1556 IMAP4-LIT IMAP4 non-synchronizing literals Elective 2088
1557 IMAP4-QUO IMAP4 QUOTA extension Elective 2087
1558 IMAP4-ACL IMAP4 ACL Extension Elective 2086
1559 HMAC-MD5 HMAC-MD5 IP Auth. with Replay Prevention Elective 2085
1560 RIP2-MD5 RIP-2 MD5 Authentication Elective 2082
1561
1562
1563
1564 <span class="grey">Internet Architecture Board Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1567
1568
1569 RIPNG-IPV6 RIPng for IPv6 Elective 2080
1570 URI-ATT URI Attribute Type and Object Class Elective 2079
1571 GSSAP Generic Security Service Application Elective 2078
1572 MIME-MODEL Model Primary MIME Types Elective 2077
1573 RMON-MIB Remote Network Monitoring MIB Elective 2074
1574 HTML-INT HTML Internationalization Elective 2070
1575 DAA Digest Access Authentication Elective 2069
1576 HTTP-1.1 Hypertext Transfer Protocol -- HTTP/1.1 Elective 2068
1577 DNS-SEC Domain Name System Security Extensions Elective 2065
1578 IMAPV4 Internet Message Access Protocol v4rev1 Elective 2060
1579 URLZ39.50 Uniform Resource Locators for Z39.50 Elective 2056
1580 SNANAU-APP SNANAU APPC MIB using SMIv2 Elective 2051
1581 PPP-SNACP PPP SNA Control Protocol Elective 2043
1582 ENTITY-MIB Entity MIB using SMIv2 Elective 2037
1583 RTP-JPEG RTP Payload Format for JPEG-compressed Elective 2035
1584 SMTP-ENH SMTP Enhanced Error Codes Elective 2034
1585 RTP-H.261 RTP Payload Format for H.261 Elective 2032
1586 RTP-CELLB RTP Payload Format of Sun's CellB Elective 2029
1587 SPKM Simple Public-Key GSS-API Mechanism Elective 2025
1588 DLSW-MIB DLSw MIB using SMIv2 Elective 2024
1589 IPV6-PPP IP Version 6 over PPP Elective 2023
1590 MULTI-UNI Multicast over UNI 3.0/3.1 based ATM Elective 2022
1591 RMON-MIB RMON MIB using SMIv2 Elective 2021
1592 802.12-MIB IEEE 802.12 Interface MIB Elective 2020
1593 IPV6-FDDI Transmission of IPv6 Packets Over FDDI Elective 2019
1594 TCP-ACK TCP Selective Acknowledgement Options Elective 2018
1595 URL-ACC URL Access-Type Elective 2017
1596 MIME-PGP MIME Security with PGP Elective 2015
1597 MIB-UDP SNMPv2 MIB for UDP Elective 2013
1598 MIB-TCP SNMPv2 MIB for TCP Elective 2012
1599 MIB-IP SNMPv2 MIB for IP Elective 2011
1600 MOBILEIPMIBMobile IP MIB Definition using SMIv2 Elective 2006
1601 MOBILEIPAPPApplicability Statement for IP Mobility Elective 2005
1602 MINI-IP Minimal Encapsulation within IP Elective 2004
1603 IPENCAPIP IP Encapsulation within IP Elective 2003
1604 MOBILEIPSUPIP Mobility Support Elective 2002
1605 TCPSLOWSRT TCP Slow Start, Congestion Avoidance... Elective 2001
1606 BGP-COMM BGP Communities Attribute Elective 1997
1607 DNS-NOTIFY Mech. for Notification of Zone Changes Elective 1996
1608 DNS-IZT Incremental Zone Transfer in DNS Elective 1995
1609 SMTP-ETRN SMTP Service Extension ETRN Elective 1985
1610 SNA Serial Number Arithmetic Elective 1982
1611 MTU-IPV6 Path MTU Discovery for IP version 6 Elective 1981
1612 PPP-FRAME PPP in Frame Relay Elective 1973
1613 IPV6-ETHER Transmission IPv6 Packets Over Ethernet Elective 1972
1614 IPV6-AUTO IPv6 Stateless Address Autoconfiguation Elective 1971
1615 IPV6-ND Neighbor Discovery for IP Version 6 Elective 1970
1616 PPP-ECP PPP Encryption Control Protocol Elective 1968
1617
1618
1619
1620 <span class="grey">Internet Architecture Board Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1623
1624
1625 GSSAPI-KER Kerberos Version 5 GSS-API Mechanism Elective 1964
1626 PPP-CCP PPP Compression Control Protocol Elective 1962
1627 GSSAPI-SOC GSS-API Auth for SOCKS Version 5 Elective 1961
1628 LDAP-STR String Rep. of LDAP Search Filters Elective 1960
1629 LDAP-URL LDAP URL Format Elective 1959
1630 TRANS-IPV6 Transition Mechanisms IPv6 Hosts/Routers Elective 1933
1631 AUTH-SOCKS Username Authentication for SOCKS V5 Elective 1929
1632 SOCKSV5 SOCKS Protocol Version 5 Elective 1928
1633 WHOIS++M How to Interact with a Whois++ Mesh Elective 1914
1634 WHOIS++A Architecture of Whois++ Index Service Elective 1913
1635 DSN Delivery Status Notifications Elective 1894
1636 EMS-CODE Enhanced Mail System Status Codes Elective 1893
1637 MIME-RPT Multipart/Report Elective 1892
1638 SMTP-DSN SMTP Delivery Status Notifications Elective 1891
1639 RTP-AV RTP Audio/Video Profile Elective 1890
1640 RTP Transport Protocol for Real-Time Apps Elective 1889
1641 DNS-IPV6 DNS Extensions to support IPv6 Elective 1886
1642 ICMPv6 ICMPv6 for IPv6 Elective 1885
1643 IPV6 IPv6 Specification Elective 1883
1644 HTML Hypertext Markup Language - 2.0 Elective 1866
1645 MIME-Sec MIME Object Security Services Elective 1848
1646 MIME-Encyp MIME: Signed and Encrypted Elective 1847
1647 WHOIS++ Architecture of the WHOIS++ service Elective 1835
1648 -------- Binding Protocols for ONC RPC Version 2 Elective 1833
1649 XDR External Data Representation Standard Elective 1832
1650 RPC Remote Procedure Call Protocol V. 2 Elective 1831
1651 -------- ESP DES-CBC Transform Ele/Req 1829
1652 -------- IP Authentication using Keyed MD5 Ele/Req 1828
1653 ESP IP Encapsulating Security Payload Ele/Req 1827
1654 IPV6-AH IP Authentication Header Ele/Req 1826
1655 -------- Security Architecture for IP Ele/Req 1825
1656 RREQ Requirements for IP Version 4 Routers Elective 1812
1657 URL Relative Uniform Resource Locators Elective 1808
1658 CLDAP Connection-less LDAP Elective 1798
1659 OSPF-DC Ext. OSPF to Support Demand Circuits Elective 1793
1660 OSI-Dir OSI User Friendly Naming ... Elective 1781
1661 MIME-EDI MIME Encapsulation of EDI Objects Elective 1767
1662 Lang-Tag Tags for Identification of Languages Elective 1766
1663 XNSCP PPP XNS IDP Control Protocol Elective 1764
1664 BVCP PPP Banyan Vines Control Protocol Elective 1763
1665 Print-MIB Printer MIB Elective 1759
1666 ATM-SIG ATM Signaling Support for IP over ATM Elective 1755
1667 IPNG Recommendation for IP Next Generation Elective 1752
1668 802.5-SSR 802.5 SSR MIB using SMIv2 Elective 1749
1669 SDLCSMIv2 SNADLC SDLC MIB using SMIv2 Elective 1747
1670 BGP4/IDRP BGP4/IDRP for IP/OSPF Interaction Elective 1745
1671 AT-MIB Appletalk MIB Elective 1742
1672 MacMIME MIME Encapsulation of Macintosh files Elective 1740
1673
1674
1675
1676 <span class="grey">Internet Architecture Board Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1679
1680
1681 URL Uniform Resource Locators Elective 1738
1682 POP3-AUTH POP3 AUTHentication command Elective 1734
1683 IMAP4-AUTH IMAP4 Authentication Mechanisms Elective 1731
1684 RDBMS-MIB RDMS MIB - using SMIv2 Elective 1697
1685 MODEM-MIB Modem MIB - using SMIv2 Elective 1696
1686 ATM-MIB ATM Management Version 8.0 using SMIv2 Elective 1695
1687 TMUX Transport Multiplexing Protocol Elective 1692
1688 SNANAU-MIB SNA NAUs MIB using SMIv2 Elective 1666
1689 PPP-TRANS PPP Reliable Transmission Elective 1663
1690 -------- Postmaster Convention X.400 Operations Elective 1648
1691 PPP-BCP PPP Bridging Control Protocol Elective 1638
1692 UPS-MIB UPS Management Information Base Elective 1628
1693 PPP-SONET PPP over SONET/SDH Elective 1619
1694 PPP-ISDN PPP over ISDN Elective 1618
1695 DNS-R-MIB DNS Resolver MIB Extensions Elective 1612
1696 DNS-S-MIB DNS Server MIB Extensions Elective 1611
1697 FR-MIB Frame Relay Service MIB Elective 1604
1698 PPP-X25 PPP in X.25 Elective 1598
1699 OSPF-NSSA The OSPF NSSA Option Elective 1587
1700 OSPF-Multi Multicast Extensions to OSPF Elective 1584
1701 SONET-MIB MIB SONET/SDH Interface Type Elective 1595
1702 RIP-DC Extensions to RIP to Support Demand Cir. Elective 1582
1703 -------- Evolution of the Interfaces Group of MIB-II Elective 1573
1704 PPP-LCP PPP LCP Extensions Elective 1570
1705 X500-MIB X.500 Directory Monitoring MIB Elective 1567
1706 CIPX Compressing IPX Headers Over WAM Media Elective 1553
1707 IPXCP PPP Internetworking Packet Exchange Control Elective 1552
1708 SRB-MIB Source Routing Bridge MIB Elective 1525
1709 CIDR-STRA CIDR Address Assignment... Elective 1519
1710 CIDR-ARCH CIDR Architecture... Elective 1518
1711 CIDR-APP CIDR Applicability Statement Elective 1517
1712 -------- 802.3 MAU MIB Elective 1515
1713 HOST-MIB Host Resources MIB Elective 1514
1714 -------- Token Ring Extensions to RMON MIB Elective 1513
1715 FDDI-MIB FDDI Management Information Base Elective 1512
1716 KERBEROS Kerberos Network Authentication Ser (V5) Elective 1510
1717 GSSAPI Generic Security Service API: C-bindings Elective 1509
1718 DASS Distributed Authentication Security... Elective 1507
1719 -------- X.400 Use of Extended Character Sets Elective 1502
1720 HARPOON Rules for Downgrading Messages... Elective 1496
1721 Equiv X.400/MIME Body Equivalences Elective 1494
1722 IDPR Inter-Domain Policy Routing Protocol Elective 1479
1723 IDPR-ARCH Architecture for IDPR Elective 1478
1724 PPP/Bridge MIB Bridge PPP MIB Elective 1474
1725 PPP/IP MIB IP Network Control Protocol of PPP MIB Elective 1473
1726 PPP/SEC MIB Security Protocols of PPP MIB Elective 1472
1727 PPP/LCP MIB Link Control Protocol of PPP MIB Elective 1471
1728 X25-MIB Multiprotocol Interconnect on X.25 MIB Elective 1461
1729
1730
1731
1732 <span class="grey">Internet Architecture Board Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1735
1736
1737 SNMPv2 Introduction to SNMPv2 Elective 1441
1738 PEM-KEY PEM - Key Certification Elective 1424
1739 PEM-ALG PEM - Algorithms, Modes, and Identifiers Elective 1423
1740 PEM-CKM PEM - Certificate-Based Key Management Elective 1422
1741 PEM-ENC PEM - Message Encryption and Auth Elective 1421
1742 SNMP-IPX SNMP over IPX Elective 1420
1743 SNMP-AT SNMP over AppleTalk Elective 1419
1744 SNMP-OSI SNMP over OSI Elective 1418
1745 FTP-FTAM FTP-FTAM Gateway Specification Elective 1415
1746 IDENT-MIB Identification MIB Elective 1414
1747 IDENT Identification Protocol Elective 1413
1748 DS3/E3-MIB DS3/E3 Interface Type Elective 1407
1749 DS1/E1-MIB DS1/E1 Interface Type Elective 1406
1750 BGP-OSPF BGP OSPF Interaction Elective 1403
1751 -------- Route Advertisement In BGP2 And BGP3 Elective 1397
1752 SNMP-X.25 SNMP MIB Extension for X.25 Packet Layer Elective 1382
1753 SNMP-LAPB SNMP MIB Extension for X.25 LAPB Elective 1381
1754 PPP-ATCP PPP AppleTalk Control Protocol Elective 1378
1755 PPP-OSINLCP PPP OSI Network Layer Control Protocol Elective 1377
1756 SNMP-PARTY-MIB Administration of SNMP Elective 1353
1757 SNMP-SEC SNMP Security Protocols Elective 1352
1758 SNMP-ADMIN SNMP Administrative Model Elective 1351
1759 TOS Type of Service in the Internet Elective 1349
1760 PPP-IPCP PPP Control Protocol Elective 1332
1761 ------- X.400 1988 to 1984 downgrading Elective 1328
1762 TCP-EXT TCP Extensions for High Performance Elective 1323
1763 NETFAX File Format for the Exchange of Images Elective 1314
1764 FDDI-MIB FDDI-MIB Elective 1285
1765 ------- Encoding Network Addresses Elective 1277
1766 ------- Replication and Distributed Operations Elective 1276
1767 ------- COSINE and Internet X.500 Schema Elective 1274
1768 BGP-MIB Border Gateway Protocol MIB (Version 3) Elective 1269
1769 ICMP-ROUT ICMP Router Discovery Messages Elective 1256
1770 OSI-UDP OSI TS on UDP Elective 1240
1771 STD-MIBs Reassignment of Exp MIBs to Std MIBs Elective 1239
1772 IPX-IP Tunneling IPX Traffic through IP Nets Elective 1234
1773 IS-IS OSI IS-IS for TCP/IP Dual Environments Elective 1195
1774 IP-CMPRS Compressing TCP/IP Headers Elective 1144
1775 NNTP Network News Transfer Protocol Elective 977
1776
1777 [Note: an asterisk at the end of a line indicates a change from the
1778 previous edition of this document.]
1779
1780 [Note: Ele/Req indicates elective for use with IPv4 and required for use
1781 with IPv6.]
1782
1783 Applicability Statements:
1784
1785
1786
1787
1788 <span class="grey">Internet Architecture Board Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1791
1792
1793 <span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. Telnet Options</span>
1794
1795 For convenience, all the Telnet Options are collected here with both
1796 their state and status.
1797
1798 Protocol Name Number State Status RFC STD
1799 ======== ===================================== ===== ====== ==== ===
1800 TOPT-BIN Binary Transmission 0 Std Rec 856 27
1801 TOPT-ECHO Echo 1 Std Rec 857 28
1802 TOPT-RECN Reconnection 2 Prop Ele ...
1803 TOPT-SUPP Suppress Go Ahead 3 Std Rec 858 29
1804 TOPT-APRX Approx Message Size Negotiation 4 Prop Ele ...
1805 TOPT-STAT Status 5 Std Rec 859 30
1806 TOPT-TIM Timing Mark 6 Std Rec 860 31
1807 TOPT-REM Remote Controlled Trans and Echo 7 Prop Ele 726
1808 TOPT-OLW Output Line Width 8 Prop Ele ...
1809 TOPT-OPS Output Page Size 9 Prop Ele ...
1810 TOPT-OCRD Output Carriage-Return Disposition 10 Hist Ele 652 *
1811 TOPT-OHT Output Horizontal Tabstops 11 Hist Ele 653 *
1812 TOPT-OHTD Output Horizontal Tab Disposition 12 Hist Ele 654 *
1813 TOPT-OFD Output Formfeed Disposition 13 Hist Ele 655 *
1814 TOPT-OVT Output Vertical Tabstops 14 Hist Ele 656 *
1815 TOPT-OVTD Output Vertical Tab Disposition 15 Hist Ele 657 *
1816 TOPT-OLD Output Linefeed Disposition 16 Hist Ele 658 *
1817 TOPT-EXT Extended ASCII 17 Prop Ele 698
1818 TOPT-LOGO Logout 18 Prop Ele 727
1819 TOPT-BYTE Byte Macro 19 Prop Ele 735
1820 TOPT-DATA Data Entry Terminal 20 Prop Ele 1043
1821 TOPT-SUP SUPDUP 21 Prop Ele 736
1822 TOPT-SUPO SUPDUP Output 22 Prop Ele 749
1823 TOPT-SNDL Send Location 23 Prop Ele 779
1824 TOPT-TERM Terminal Type 24 Prop Ele 1091
1825 TOPT-EOR End of Record 25 Prop Ele 885
1826 TOPT-TACACS TACACS User Identification 26 Prop Ele 927
1827 TOPT-OM Output Marking 27 Prop Ele 933
1828 TOPT-TLN Terminal Location Number 28 Prop Ele 946
1829 TOPT-3270 Telnet 3270 Regime 29 Prop Ele 1041
1830 TOPT-X.3 X.3 PAD 30 Prop Ele 1053
1831 TOPT-NAWS Negotiate About Window Size 31 Prop Ele 1073
1832 TOPT-TS Terminal Speed 32 Prop Ele 1079
1833 TOPT-RFC Remote Flow Control 33 Prop Ele 1372
1834 TOPT-LINE Linemode 34 Draft Ele 1184
1835 TOPT-XDL X Display Location 35 Prop Ele 1096
1836 TOPT-ENVIR Telnet Environment Option 36 Hist Not 1408
1837 TOPT-AUTH Telnet Authentication Option 37 Exp Ele 1416
1838 TOPT-ENVIR Telnet Environment Option 39 Prop Ele 1572
1839 TOPT-TN3270E TN3270 Enhancements 40 Draft Ele 2355 *
1840 TOPT-AUTH Telnet XAUTH 41 Exp
1841
1842
1843
1844 <span class="grey">Internet Architecture Board Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1847
1848
1849 TOPT-CHARSET Telnet CHARSET 42 Exp 2066
1850 TOPR-RSP Telnet Remote Serial Port 43 Exp
1851 TOPT-COMPORT Telnet Com Port Control 44 Exp 2217
1852 TOPT-SLE Telnet Suppress Local Echo 45 Exp *
1853 TOPT-STARTTLS Telnet Start TLS 46 Exp *
1854 TOPT-KERMIT Telnet KERMIT 47 Exp *
1855 TOPT-SEND-URL Send-URL 48 Exp *
1856 TOPT-EXTOP Extended-Options-List 255 Std Rec 861 32
1857
1858 [Note: an asterisk at the end of a line indicates a change from the
1859 previous edition of this document.]
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
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 Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1903
1904
1905 <span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. Experimental Protocols</span>
1906
1907 All Experimental protocols have the Limited Use status.
1908
1909 Protocol Name RFC
1910 ======== ===================================== =====
1911 TCP-WIN Increasing TCP's Initial Window 2414*
1912 PIM-SM Protocol Independent Multicast-Sparse Mode 2362*
1913 ------- Domain Names and Company Name Retrieva 2345
1914 RTP-MPEG RTP Payload Format for Bundled MPEG 2343
1915 ------- Intra-LIS IP Multicast/Routers over ATM using PIM 2337
1916 ------- Safe Response Header Field 2310
1917 LDAP-NIS Approach Using LDAP as a Network Information Service 2307
1918 HTTP-RVSA HTTP Remote Variant Selection Algorithm 2296
1919 TCN-HTTP Transparent Content Negotiation in HTTP 2295
1920 ------- Core Based Trees (CBT) Multicast Routing Architecture 2201
1921 ------- Core Based Trees (CBT version 2) Multicast Routing 2189
1922 ------- Trivial Convention using HTTP in URN Resolution 2169
1923 ------- Resolution of URIs using DNS 2168
1924 MAP-MAIL X.400 Mapping and Mail-11 2162
1925 MIME-ODA A MIME Body Part for ODA 2161
1926 OSPF-DIG OSPF with Digital Signature 2154
1927 GKMP-ARCH Group Key Management Protocol (GKMP) Architecture 2094
1928 GKMP-SPEC Group Key Management Protocol (GKMP) Specification 2093
1929 IP-SCSI Encapsulating IP with the SCSI 2143
1930 X.500-NAME Managing the X.500 Root Naming Context 2120
1931 TFTP-MULTI TFTP Multicast Option 2090
1932 IP-Echo IP Echo Host Service 2075
1933 METER-MIB Traffic Flow Measurement Meter MIB 2064
1934 TFM-ARCH Traffic Flow Measurement Architecture 2063
1935 DNS-SRV Location of Services in the DNS 2052
1936 URAS Uniform Resource Agents 2016
1937 GPS-AR GPS-Based Addressing and Routing 2009
1938 ETFTP Enhanced Trivial File Transfer Protocol 1986
1939 BGP-RR BGP Route Reflection 1966
1940 BGP-ASC Autonomous System Confederations for BGP 1965
1941 SMKD Scalable Multicast Key Distribution 1949
1942 HTML-TBL HTML Tables 1942
1943 SNMPV2SM User-based Security Model for SNMPv2 1910
1944 SNMPV2AI SNMPv2 Administrative Infrastructure 1909
1945 SNMPV2CB Introduction to Community-based SNMPv2 1901
1946 ------- IPv6 Testing Address Allocation 1897
1947 DNS-LOC Location Information in the DNS 1876
1948 SGML-MT SGML Media Types 1874
1949 CONT-MT Access Type Content-ID 1873
1950 UNARP ARP Extension - UNARP 1868
1951 ------- Form-based File Upload in HTML 1867
1952 ------- BGP/IDRP Route Server Alternative 1863
1953
1954
1955
1956 <span class="grey">Internet Architecture Board Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
1959
1960
1961 ------- IP Authentication using Keyed SHA 1852
1962 ESP3DES ESP Triple DES Transform 1851
1963 ------- SMTP 521 Reply Code 1846
1964 ------- SMTP Serv. Ext. for Checkpoint/Restart 1845
1965 ------- SMTP Serv. Ext. Large and Binary MIME Msgs. 1830
1966 ST2 Stream Protocol Version 2 1819
1967 ------- Content-Disposition Header 1806
1968 ------- Schema Publishing in X.500 Directory 1804
1969 ------- X.400-MHS use X.500 to support X.400-MHS Routing 1801
1970 ------- Class A Subnet Experiment 1797
1971 TCP/IPXMIB TCP/IPX Connection Mib Specification 1792
1972 ------- TCP And UDP Over IPX Networks With Fixed Path MTU 1791
1973 ICMP-DM ICMP Domain Name Messages 1788
1974 CLNP-MULT Host Group Extensions for CLNP Multicasting 1768
1975 OSPF-OVFL OSPF Database Overflow 1765
1976 RWP Remote Write ProtocolL - Version 1.0 1756
1977 NARP NBMA Address Resolution Protocol 1735
1978 DNS-ENCODE DNS Encoding of Geographical Location 1712
1979 TCP-POS An Extension to TCP: Partial Order Service 1693
1980 T/TCP TCP Extensions for Transactions 1644
1981 MIME-UNI Using Unicode with MIME 1641
1982 FOOBAR FTP Operation Over Big Address Records 1639
1983 X500-CHART Charting Networks in the X.500 Directory 1609
1984 X500-DIR Representing IP Information in the X.500 Directory 1608
1985 SNMP-DPI SNMP Distributed Protocol Interface 1592
1986 CLNP-TUBA Use of ISO CLNP in TUBA Environments 1561
1987 REM-PRINT TPC.INT Subdomain Remote Printing - Technical 1528
1988 EHF-MAIL Encoding Header Field for Internet Messages 1505
1989 RAP Internet Route Access Protocol 1476
1990 TP/IX TP/IX: The Next Internet 1475
1991 X400 Routing Coordination for X.400 Services 1465
1992 DNS Storing Arbitrary Attributes in DNS 1464
1993 IRCP Internet Relay Chat Protocol 1459
1994 TOS-LS Link Security TOS 1455
1995 SIFT/UFT Sender-Initiated/Unsolicited File Transfer 1440
1996 DIR-ARP Directed ARP 1433
1997 TEL-SPX Telnet Authentication: SPX 1412
1998 TEL-KER Telnet Authentication: Kerberos V4 1411
1999 TRACE-IP Traceroute Using an IP Option 1393
2000 DNS-IP Experiment in DNS Based IP Routing 1383
2001 RMCP Remote Mail Checking Protocol 1339
2002 TCP-HIPER TCP Extensions for High Performance 1323
2003 MSP2 Message Send Protocol 2 1312
2004 DSLCP Dynamically Switched Link Control 1307
2005 -------- X.500 and Domains 1279
2006 IN-ENCAP Internet Encapsulation Protocol 1241
2007 CLNS-MIB CLNS-MIB 1238
2008 CFDP Coherent File Distribution Protocol 1235
2009
2010
2011
2012 <span class="grey">Internet Architecture Board Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2015
2016
2017 IP-AX.25 IP Encapsulation of AX.25 Frames 1226
2018 ALERTS Managing Asynchronously Generated Alerts 1224
2019 MPP Message Posting Protocol 1204
2020 SNMP-BULK Bulk Table Retrieval with the SNMP 1187
2021 DNS-RR New DNS RR Definitions 1183
2022 IMAP2 Interactive Mail Access Protocol 1176
2023 NTP-OSI NTP over OSI Remote Operations 1165
2024 DMF-MAIL Digest Message Format for Mail 1153
2025 RDP Reliable Data Protocol 908,1151
2026 TCP-ACO TCP Alternate Checksum Option 1146
2027 IP-DVMRP IP Distance Vector Multicast Routing 1075
2028 VMTP Versatile Message Transaction Protocol 1045
2029 COOKIE-JAR Authentication Scheme 1004
2030 NETBLT Bulk Data Transfer Protocol 998
2031 IRTP Internet Reliable Transaction Protocol 938
2032 LDP Loader Debugger Protocol 909
2033 RLP Resource Location Protocol 887
2034 NVP-II Network Voice Protocol ISI-memo
2035 PVP Packet Video Protocol ISI-memo
2036
2037 [Note: an asterisk at the end of a line indicates a change from the
2038 previous edition of this document.]
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068 <span class="grey">Internet Architecture Board Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2071
2072
2073 <span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a>. Informational Protocols</span>
2074
2075 Information protocols have no status.
2076
2077 Protocol Name RFC
2078 ======= ==================================== =====
2079 -------- ST2+ over ATM Protocol Spec - UNI 3.1 Version 2383*
2080 -------- Mapping Airline Reservation, Ticketing, Messaging 2351
2081 KOI8-U Ukrainian Character Set KOI8-U 2319
2082 TEXT-CSS The text/css Media Type 2318
2083 PKCS-7 PKCS #7: Cryptographic Message Syntax Version 1.5 2315
2084 PKCS-10 PKCS #10: Certification Request Syntax Version 1.5 2314
2085 PKCS-1 PKCS #1: RSA Encryption Version 1.5 2313
2086 SMIME-CERT S/MIME Version 2 Certificate Handling 2312
2087 SMIME-MSG S/MIME Version 2 Message Specification 2311
2088 TIFF Tag Image File Format F Profile for Facsimile 2302
2089 GSMP Ipsilon's General Switch Management Protocol 2297
2090 HSRP Cisco Hot Standby Router Protocol (HSRP) 2281
2091 RC2-ENCRP A Description of the RC2(r) Encryption Algorithm 2268
2092 SNQP Simple Nomenclator Query Protocol 2259
2093 -------- Japanese Character Encoding for Internet Messages 2237
2094 KEYX-DNS Key Exchange Delegation Record for the DNS 2230
2095 DSP A Dictionary Server Protocol 2229
2096 NFS-URL NFS URL Scheme 2224
2097 APP-MARC The Application/MARC Content-type 2220
2098 ODETTE-FTP ODETTE File Transfer Protocol 2204
2099 ESRO AT&amp;T/Neda's Efficient Short Remote Operations Protocol 2188
2100 ICP Internet Cache Protocol Version 2 2186
2101 IPV4-MAPOS IPv4 over MAPOS Version 1 2176
2102 MAPOS-SONET Multiple Access Protocol over SONET/SDH Version 1 2171
2103 RWHOIS Referral Whois Protocol 2167
2104 PPP-EXT PPP Vendor Extensions 2153
2105 UTF-7 UTF-7 2152
2106 CAST-128 CAST-128 Encryption Algorithm 2144
2107 RADIUS-ACC RADIUS Accounting 2139
2108 DLSCAP Data Link Switching Client Access Protocol 2114
2109 PNG Portable Network Graphics Version 1.0 2083
2110 RC5 RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms 2040
2111 SNTP Simple Network Time Protocol v4 for IPv4, IPv6 and OSI 2030
2112 PGP-MEF PGP Message Exchange Formats 1991
2113 PPP-DEFL PPP Deflate Protocol 1979
2114 PPP-PRED PPP Predictor Compression Protocol 1978
2115 PPP-BSD PPP BSD Compression Protocol 1977
2116 PPP-DCE PPP for Data Compression in DCE 1976
2117 PPP-MAG PPP Magnalink Variable Resource Compression 1975
2118 PPP-STAC PPP Stac LZS Compression Protocol 1974
2119 GZIP GZIP File Format Specification Version 4.3 1952
2120 DEFLATE DEFLATE Compressed Data Format Specification V. 1.3 1951
2121
2122
2123
2124 <span class="grey">Internet Architecture Board Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2127
2128
2129 ZLIB ZLIB Compressed Data Format Specification V. 3.3 1950
2130 HTTP-1.0 Hypertext Transfer Protocol -- HTTP/1.0 1945
2131 -------- text/enriched MIME Content-type 1896
2132 -------- Application/CALS-1840 Content-type 1895
2133 -------- PPP IPCP Extensions for Name Server Addresses 1877
2134 SNPP Simple Network Paging Protocol - Version 2 1861
2135 -------- ISO Transport Class 2 Non-use Explicit Flow Control 1859
2136 over TCP <a href="./rfc1006">RFC1006</a> extension
2137 -------- IP in IP Tunneling 1853
2138 -------- PPP Network Control Protocol for LAN Extension 1841
2139 TESS The Exponential Security System 1824
2140 NFSV3 NFS Version 3 Protocol Specification 1813
2141 -------- A Format for Bibliographic Records 1807
2142 ------- Data Link Switching: Switch-to-Switch Protocol 1795
2143 BGP-4 Experience with the BGP-4 Protocol 1773
2144 SDMD IPv4 Option for Sender Directed MD Delivery 1770
2145 SNOOP Snoop Version 2 Packet Capture File Format 1761
2146 BINHEX MIME Content Type for BinHex Encoded Files 1741
2147 DNS-NSAP DNS NSAP Resource Records 1706
2148 RADIO-PAGE TPC.INT Subdomain: Radio Paging -- Technical Procedures 1703
2149 GRE-IPv4 Generic Routing Encapsulation over IPv4 1702
2150 GRE Generic Routing Encapsulatio 1701
2151 ADSNA-IP Advanced SNA/IP: A Simple SNA Transport Protocol 1538
2152 TACACS Terminal Access Control Protocol 1492
2153 MD4 MD4 Message Digest Algorithm 1320
2154 SUN-NFS Network File System Protocol 1094
2155 SUN-RPC Remote Procedure Call Protocol Version 2 1057
2156 GOPHER The Internet Gopher Protocol 1436
2157 LISTSERV Listserv Distribute Protocol 1429
2158 ------- Replication Requirements 1275
2159 PCMAIL Pcmail Transport Protocol 1056
2160 MTP Multicast Transport Protocol 1301
2161 BSD Login BSD Login 1282
2162 DIXIE DIXIE Protocol Specification 1249
2163 IP-X.121 IP to X.121 Address Mapping for DDN 1236
2164 OSI-HYPER OSI and LLC1 on HYPERchannel 1223
2165 HAP2 Host Access Protocol 1221
2166 SUBNETASGN On the Assignment of Subnet Numbers 1219
2167 SNMP-TRAPS Defining Traps for use with SNMP 1215
2168 DAS Directory Assistance Service 1202
2169 LPDP Line Printer Daemon Protocol 1179
2170
2171 [Note: an asterisk at the end of a line indicates a change from the
2172 previous edition of this document.]
2173
2174
2175
2176
2177
2178
2179
2180 <span class="grey">Internet Architecture Board Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2183
2184
2185 <span class="h3"><a class="selflink" id="section-6.9" href="#section-6.9">6.9</a>. Historic Protocols</span>
2186
2187 All Historic protocols have Not Recommended status.
2188
2189 Protocol Name RFC STD
2190 ======== ===================================== ===== ===
2191 IPV6-UNI IPv6 Provider-Based Unicast Address Elective 2073 *
2192 IPV6-Addr IPv6 Addressing Architecture Elective 1884 *
2193 L2F Cisco Layer Two Forwarding Protocol 2341
2194 IPSO DoD Security Options for IP Elective 1108
2195 SNMPv2 Manager-to-Manager MIB Elective 1451
2196 SNMPv2 Party MIB for SNMPv2 Elective 1447
2197 SNMPv2 Security Protocols for SNMPv2 Elective 1446
2198 SNMPv2 Administrative Model for SNMPv2 Elective 1445
2199 RIP Routing Information Protocol Ele 1058 34
2200 -------- Mapping full 822 to Restricted 822 1137
2201 BGP3 Border Gateway Protocol 3 (BGP-3) 1267,1268
2202 -------- Gateway Requirements Req 1009 4
2203 EGP Exterior Gateway Protocol Rec 904 18
2204 SNMP-MUX SNMP MUX Protocol and MIB 1227
2205 OIM-MIB-II OSI Internet Management: MIB-II 1214
2206 IMAP3 Interactive Mail Access Protocol Version 3 1203
2207 SUN-RPC Remote Procedure Call Protocol Version 1 1050
2208 802.4-MIP IEEE 802.4 Token Bus MIB 1230
2209 CMOT Common Management Information Services 1189
2210 -------- Mail Privacy: Procedures 1113
2211 -------- Mail Privacy: Key Management 1114
2212 -------- Mail Privacy: Algorithms 1115
2213 NFILE A File Access Protocol 1037
2214 HOSTNAME HOSTNAME Protocol 953
2215 SFTP Simple File Transfer Protocol 913
2216 SUPDUP SUPDUP Protocol 734
2217 BGP Border Gateway Protocol 1163,1164
2218 MIB-I MIB-I 1156
2219 SGMP Simple Gateway Monitoring Protocol 1028
2220 HEMS High Level Entity Management Protocol 1021
2221 STATSRV Statistics Server 996
2222 POP2 Post Office Protocol, Version 2 937
2223 RATP Reliable Asynchronous Transfer Protocol 916
2224 HFEP Host - Front End Protocol 929
2225 THINWIRE Thinwire Protocol 914
2226 HMP Host Monitoring Protocol 869
2227 GGP Gateway Gateway Protocol 823
2228 RTELNET Remote Telnet Service 818
2229 CLOCK DCNET Time Server Protocol 778
2230 MPM Internet Message Protocol 759
2231 NETRJS Remote Job Service 740
2232 NETED Network Standard Text Editor 569
2233
2234
2235
2236 <span class="grey">Internet Architecture Board Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2239
2240
2241 RJE Remote Job Entry 407
2242 XNET Cross Net Debugger IEN-158
2243 NAMESERVER Host Name Server Protocol IEN-116
2244 MUX Multiplexing Protocol IEN-90
2245 GRAPHICS Graphics Protocol NIC-24308
2246
2247 [Note: an asterisk at the end of a line indicates a change from the
2248 previous edition of this document.]
2249
2250 <span class="h3"><a class="selflink" id="section-6.10" href="#section-6.10">6.10</a>. Obsolete Protocols</span>
2251
2252 Some of the protocols listed in this memo are described in RFCs that
2253 are obsoleted by newer RFCs. "Obsolete" or "obsoleted" is not an
2254 official state or status of protocols. This subsection is for
2255 information only.
2256
2257 While it may seem to be obviously wrong to have an obsoleted RFC in
2258 the list of standards, there may be cases when an older standard is
2259 in the process of being replaced. This process may take a year or
2260 two.
2261
2262 Many obsoleted protocols are of little interest and are dropped from
2263 this memo altogether. Some obsoleted protocols have received enough
2264 recognition that it seems appropriate to list them under their
2265 current status and with the following reference to their current
2266 replacement.
2267
2268 RFC RFC Status Title *
2269 ==== ==== ========= =================================== =
2270 1305 obsoletes 1119 Stan/Rec Network Time Protocol version 2
2271
2272 Thanks to Lynn Wheeler for compiling the information in this
2273 subsection.
2274
2275 [Note: an asterisk at the end of a line indicates a change from the
2276 previous edition of this document.]
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292 <span class="grey">Internet Architecture Board Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2295
2296
2297 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Contacts</span>
2298
2299 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. IAB, IETF, and IRTF Contacts</span>
2300
2301 7.1.1. Internet Architecture Board (IAB) Contact
2302
2303 Please send your comments about this list of protocols and especially
2304 about the Draft Standard Protocols to the Internet Architecture Board
2305 care of Abel Winerib, IAB Executive Director.
2306
2307 Contacts:
2308
2309 Abel Winerib
2310 Executive Director of the IAB
2311 Intel, JF2-64
2312 2111 NE 25th Avenue
2313 Hillsboro, OR 97124
2314
2315 1-503-696-8972
2316
2317 [email protected]
2318
2319
2320 Brian E. Carpenter
2321 Chair of the IAB
2322 IBM United Kingdon Laboratories
2323 Hursley Park
2324 Winchester
2325 Hampshire SO21 2JN
2326
2327 +44 1962 816833
2328
2329 [email protected]
2330
2331
2332 7.1.2. Internet Engineering Task Force (IETF) Contact
2333
2334 Contacts:
2335
2336 Fred Baker
2337 Chair of the IETF
2338 cisco Systems, Inc.
2339 519 Lado Drive
2340 Santa Barbara, CA 93111
2341
2342 1-805-681-0115
2343
2344 [email protected]
2345
2346
2347
2348 <span class="grey">Internet Architecture Board Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2351
2352
2353 Steve Coya
2354 IESG Secretary
2355 Corporation for National Research Initiatives
2356 1895 Preston White Drive, Suite 100
2357 Reston, VA 22091
2358
2359 1-703-620-8990
2360
2361 [email protected]
2362
2363 Steve Coya
2364 Executive Director of the IETF
2365 Corporation for National Research Initiatives
2366 1895 Preston White Drive, Suite 100
2367 Reston, VA 22091
2368
2369 1-703-620-8990
2370
2371 [email protected]
2372
2373
2374 7.1.3. Internet Research Task Force (IRTF) Contact
2375
2376 Contact:
2377
2378 Abel Winerib
2379 Chair of the IRTF
2380 Intel, JF2-64
2381 2111 NE 25th Avenue
2382 Hillsboro, OR 97124
2383
2384 1-503-696-8972
2385
2386 [email protected]
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404 <span class="grey">Internet Architecture Board Standards Track [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2407
2408
2409 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Internet Assigned Numbers Authority Contact</span>
2410
2411 Contact:
2412
2413 Joyce K. Reynolds
2414 Internet Assigned Numbers Authority
2415 USC/Information Sciences Institute
2416 4676 Admiralty Way
2417 Marina del Rey, CA 90292-6695
2418
2419 1-310-822-1511
2420
2421 [email protected]
2422
2423 The protocol standards are managed by the Internet Assigned Numbers
2424 Authority.
2425
2426 Please refer to the document "Assigned Numbers" (<a href="./rfc1700">RFC-1700</a>) for
2427 further information about the status of protocol documents. There
2428 are two documents that summarize the requirements for host and
2429 gateways in the Internet, "Host Requirements" (<a href="./rfc1122">RFC-1122</a> and <a href="./rfc1123">RFC-1123</a>)
2430 and "Requirements for IP Version 4 Routers" (<a href="./rfc1812">RFC-1812</a>).
2431
2432 How to obtain the most recent edition of this "Internet Official
2433 Protocol Standards" memo:
2434
2435 The file "in-notes/std/std1.txt" may be copied via FTP from the
2436 FTP.ISI.EDU computer using the FTP username "anonymous" and FTP
2437 password "guest".
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460 <span class="grey">Internet Architecture Board Standards Track [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2463
2464
2465 <span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Request for Comments Editor Contact</span>
2466
2467 Contact:
2468
2469 Jon Postel
2470 RFC Editor
2471 USC/Information Sciences Institute
2472 4676 Admiralty Way
2473 Marina del Rey, CA 90292-6695
2474
2475 1-310-822-1511
2476
2477 [email protected]
2478
2479 Documents may be submitted via electronic mail to the RFC Editor for
2480 consideration for publication as RFC. If you are not familiar with
2481 the format or style requirements please request the "Instructions for
2482 RFC Authors". In general, the style of any recent RFC may be used as
2483 a guide.
2484
2485 <span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. The Network Information Center and</span>
2486 <span class="h3"> Requests for Comments Distribution Contact</span>
2487
2488 RFCs can be obtained via FTP from FTP.ISI.EDU, with the pathname in-
2489 notes/rfcnnnn.txt (where "nnnn" refers to the number of the RFC).
2490 Login with FTP username "anonymous" and password "[email protected]".
2491
2492 RFCs can also be obtained via electronic mail from ISI.EDU by using
2493 the RFC-INFO service. Address the request to "[email protected]" with
2494 a message body of:
2495
2496 Retrieve: RFC
2497 Doc-ID: RFCnnnn
2498
2499 (Where "nnnn" refers to the number of the RFC (always use 4 digits -
2500 the DOC-ID of <a href="./rfc822">RFC 822</a> is "<a href="./rfc0822">RFC0822</a>")). The [email protected] server
2501 provides other ways of selecting RFCs based on keywords and such; for
2502 more information send a message to "[email protected]" with the
2503 message body "help: help".
2504
2505 contact: [email protected]
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516 <span class="grey">Internet Architecture Board Standards Track [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2519
2520
2521 <span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Sources for Requests for Comments</span>
2522
2523 Details on many sources of RFCs via FTP or EMAIL may be obtained by
2524 sending an EMAIL message to "[email protected]" with the message body
2525 "help: ways_to_get_rfcs". For example:
2526
2527 To: [email protected]
2528 Subject: getting rfcs
2529
2530 help: ways_to_get_rfcs
2531
2532 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
2533
2534 Security issues are not addressed in this memo.
2535
2536 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Authors' Addresses</span>
2537
2538 Jon Postel
2539 USC/Information Sciences Institute
2540 4676 Admiralty Way
2541 Marina del Rey, CA 90292
2542
2543 Phone: 310-822-1511
2544 Fax: 310-823-6714
2545
2546 EMail: [email protected]
2547
2548
2549 Joyce K. Reynolds
2550 USC/Information Sciences Institute
2551 4676 Admiralty Way
2552 Marina del Rey, CA 90292
2553
2554 Phone: 310-822-1511
2555 Fax: 310-823-6714
2556
2557 EMail: [email protected]
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572 <span class="grey">Internet Architecture Board Standards Track [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc2400">RFC 2400</a> Internet Standards September 1998</span>
2575
2576
2577 Full Copyright Statement
2578
2579 Copyright (C) The Internet Society (1998). All Rights Reserved.
2580
2581 This document and translations of it may be copied and furnished to
2582 others, and derivative works that comment on or otherwise explain it
2583 or assist in its implementation may be prepared, copied, published
2584 and distributed, in whole or in part, without restriction of any
2585 kind, provided that the above copyright notice and this paragraph are
2586 included on all such copies and derivative works. However, this
2587 document itself may not be modified in any way, such as by removing
2588 the copyright notice or references to the Internet Society or other
2589 Internet organizations, except as needed for the purpose of
2590 developing Internet standards in which case the procedures for
2591 copyrights defined in the Internet Standards process must be
2592 followed, or as required to translate it into languages other than
2593 English.
2594
2595 The limited permissions granted above are perpetual and will not be
2596 revoked by the Internet Society or its successors or assigns.
2597
2598 This document and the information contained herein is provided on an
2599 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
2600 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
2601 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
2602 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
2603 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628 Internet Architecture Board Standards Track [Page 47]
2629 </pre>