Debian Codegraph @

rfc1880.html

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