Debian Codegraph @

rfc2200.html

raw
1 <pre>Network Working Group Internet Architecture Board
2 Request for Comments: 2200 J. Postel, Editor
3 Obsoletes: <a href="./rfc2000">2000</a>, <a href="./rfc1920">1920</a>, <a href="./rfc1880">1880</a>, <a href="./rfc1800">1800</a>, <a href="./rfc1780">1780</a>, June 1997
4 <a href="./rfc1720">1720</a>, <a href="./rfc1610">1610</a>, <a href="./rfc1600">1600</a>, <a href="./rfc1540">1540</a>, <a href="./rfc1500">1500</a>, <a href="./rfc1410">1410</a>, <a href="./rfc1360">1360</a>,
5 1280, 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-7">7</a>
31 <a href="#section-4.1">4.1</a>. Definitions of Protocol State (Maturity Level) . . . . . . <a href="#page-8">8</a>
32 <a href="#section-4.1.1">4.1.1</a>. Standard Protocol . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
33 <a href="#section-4.1.2">4.1.2</a>. Draft Standard Protocol . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
34 <a href="#section-4.1.3">4.1.3</a>. Proposed Standard Protocol . . . . . . . . . . . . . . . <a href="#page-8">8</a>
35 <a href="#section-4.1.4">4.1.4</a>. Experimental Protocol . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
36 <a href="#section-4.1.5">4.1.5</a>. Informational Protocol . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
37 <a href="#section-4.1.6">4.1.6</a>. Historic Protocol . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
38 <a href="#section-4.2">4.2</a>. Definitions of Protocol Status (Requirement Level) . . . <a href="#page-9">9</a>
39 <a href="#section-4.2.1">4.2.1</a>. Required Protocol . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
40 <a href="#section-4.2.2">4.2.2</a>. Recommended Protocol . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
41 <a href="#section-4.2.3">4.2.3</a>. Elective Protocol . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
42 <a href="#section-4.2.4">4.2.4</a>. Limited Use Protocol . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
43 <a href="#section-4.2.5">4.2.5</a>. Not Recommended Protocol . . . . . . . . . . . . . . . <a href="#page-9">9</a>
44 <a href="#section-5">5</a>. The Standards Track . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
45 <a href="#section-5.1">5.1</a>. The RFC Processing Decision Table . . . . . . . . . . . <a href="#page-10">10</a>
46 <a href="#section-5.2">5.2</a>. The Standards Track Diagram . . . . . . . . . . . . . . <a href="#page-11">11</a>
47 <a href="#section-6">6</a>. The Protocols . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
48 <a href="#section-6.1">6.1</a>. Recent Changes . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
55
56
57 <a href="#section-6.1.1">6.1.1</a>. New RFCs . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
58 <a href="#section-6.1.2">6.1.2</a>. Other Changes . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
59 <a href="#section-6.2">6.2</a>. Standard Protocols . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
60 <a href="#section-6.3">6.3</a>. Network-Specific Standard Protocols . . . . . . . . . . <a href="#page-20">20</a>
61 <a href="#section-6.4">6.4</a>. Draft Standard Protocols . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
62 <a href="#section-6.5">6.5</a>. Proposed Standard Protocols . . . . . . . . . . . . . . <a href="#page-22">22</a>
63 <a href="#section-6.6">6.6</a>. Telnet Options . . . . . . . . . . . . . . . . . . . . . <a href="#page-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-32">32</a>
66 <a href="#section-6.9">6.9</a>. Historic Protocols . . . . . . . . . . . . . . . . . . . <a href="#page-33">33</a>
67 <a href="#section-6.10">6.10</a> Obsolete Protocols . . . . . . . . . . . . . . . . . . . <a href="#page-35">35</a>
68 <a href="#section-7">7</a>. Contacts . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-35">35</a>
69 <a href="#section-7.1">7.1</a>. IAB, IETF, and IRTF Contacts . . . . . . . . . . . . . . <a href="#page-35">35</a>
70 <a href="#section-7.1.1">7.1.1</a>. Internet Architecture Board (IAB) Contact . . . . . . <a href="#page-35">35</a>
71 <a href="#section-7.1.2">7.1.2</a>. Internet Engineering Task Force (IETF) Contact . . . . <a href="#page-36">36</a>
72 <a href="#section-7.1.3">7.1.3</a>. Internet Research Task Force (IRTF) Contact . . . . . <a href="#page-37">37</a>
73 <a href="#section-7.2">7.2</a>. Internet Assigned Numbers Authority (IANA) Contact . . . <a href="#page-37">37</a>
74 <a href="#section-7.3">7.3</a>. Request for Comments Editor Contact . . . . . . . . . . <a href="#page-38">38</a>
75 <a href="#section-7.4">7.4</a>. Network Information Center Contact . . . . . . . . . . . <a href="#page-38">38</a>
76 <a href="#section-7.5">7.5</a>. Sources for Requests for Comments . . . . . . . . . . . <a href="#page-39">39</a>
77 <a href="#section-8">8</a>. Security Considerations . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
78 <a href="#section-9">9</a>. Author's Address . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</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 15-Oct-97.
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</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="./rfc2200">RFC 2200</a> Internet Standards June 1997</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="./rfc2200">RFC 2200</a> Internet Standards June 1997</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="./rfc2200">RFC 2200</a> Internet Standards June 1997</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 DoD MIL-STD Internet specifications are out of date and have been
323 discontinued. The DoD's Joint Technical Architecture (JTA) lists the
324 current set of IETF STDs and RFCs that the DoD intends to use in all
325 new and upgraded Command, Control, Communications, Computers, and
326 Intelligence (C4I) acquisitions. A copy of the JTA can be obtained
327 from <a href="http://www-jta.itsi.disa.mil">http://www-jta.itsi.disa.mil</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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
335
336
337 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Explanation of Terms</span>
338
339 There are two independent categorization of protocols. The first is
340 the "maturity level" or STATE of standardization, one of "standard",
341 "draft standard", "proposed standard", "experimental",
342 "informational" or "historic". The second is the "requirement level"
343 or STATUS of this protocol, one of "required", "recommended",
344 "elective", "limited use", or "not recommended".
345
346 The status or requirement level is difficult to portray in a one word
347 label. These status labels should be considered only as an
348 indication, and a further description, or applicability statement,
349 should be consulted.
350
351 When a protocol is advanced to proposed standard or draft standard,
352 it is labeled with a current status.
353
354 At any given time a protocol occupies a cell of the following matrix.
355 Protocols are likely to be in cells in about the following
356 proportions (indicated by the relative number of Xs). A new protocol
357 is most likely to start in the (proposed standard, elective) cell, or
358 the (experimental, limited use) cell.
359
360 S T A T U S
361 Req Rec Ele Lim Not
362 +-----+-----+-----+-----+-----+
363 Std | X | XXX | XXX | | |
364 S +-----+-----+-----+-----+-----+
365 Draft | X | X | XXX | | |
366 T +-----+-----+-----+-----+-----+
367 Prop | | X | XXX | | |
368 A +-----+-----+-----+-----+-----+
369 Info | | | | | |
370 T +-----+-----+-----+-----+-----+
371 Expr | | | | XXX | |
372 E +-----+-----+-----+-----+-----+
373 Hist | | | | | XXX |
374 +-----+-----+-----+-----+-----+
375
376 What is a "system"?
377
378 Some protocols are particular to hosts and some to gateways; a few
379 protocols are used in both. The definitions of the terms below
380 will refer to a "system" which is either a host or a gateway (or
381 both). It should be clear from the context of the particular
382 protocol which types of systems are intended.
383
384
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
391
392
393 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Definitions of Protocol State</span>
394
395 Every protocol listed in this document is assigned to a "maturity
396 level" or STATE of standardization: "standard", "draft standard",
397 "proposed standard", "experimental", or "historic".
398
399 4.1.1. Standard Protocol
400
401 The IESG has established this as an official standard protocol for
402 the Internet. These protocols are assigned STD numbers (see <a href="./rfc1311">RFC-</a>
403 <a href="./rfc1311">1311</a>). These are separated into two groups: (1) IP protocol and
404 above, protocols that apply to the whole Internet; and (2)
405 network-specific protocols, generally specifications of how to do
406 IP on particular types of networks.
407
408 4.1.2. Draft Standard Protocol
409
410 The IESG is actively considering this protocol as a possible
411 Standard Protocol. Substantial and widespread testing and comment
412 are desired. Comments and test results should be submitted to the
413 IESG. There is a possibility that changes will be made in a Draft
414 Standard Protocol before it becomes a Standard Protocol.
415
416 4.1.3. Proposed Standard Protocol
417
418 These are protocol proposals that may be considered by the IESG
419 for standardization in the future. Implementation and testing by
420 several groups is desirable. Revision of the protocol
421 specification is likely.
422
423 4.1.4. Experimental Protocol
424
425 A system should not implement an experimental protocol unless it
426 is participating in the experiment and has coordinated its use of
427 the protocol with the developer of the protocol.
428
429 Typically, experimental protocols are those that are developed as
430 part of an ongoing research project not related to an operational
431 service offering. While they may be proposed as a service
432 protocol at a later stage, and thus become proposed standard,
433 draft standard, and then standard protocols, the designation of a
434 protocol as experimental may sometimes be meant to suggest that
435 the protocol, although perhaps mature, is not intended for
436 operational use.
437
438
439
440
441
442
443
444 <span class="grey">Internet Architecture Board Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
447
448
449 4.1.5. Informational Protocol
450
451 Protocols developed by other standard organizations, or vendors,
452 or that are for other reasons outside the purview of the IESG, may
453 be published as RFCs for the convenience of the Internet community
454 as informational protocols.
455
456 4.1.6. Historic Protocol
457
458 These are protocols that are unlikely to ever become standards in
459 the Internet either because they have been superseded by later
460 developments or due to lack of interest.
461
462 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Definitions of Protocol Status</span>
463
464 This document lists a "requirement level" or STATUS for each
465 protocol. The status is one of "required", "recommended",
466 "elective", "limited use", or "not recommended".
467
468 4.2.1. Required Protocol
469
470 A system must implement the required protocols.
471
472 4.2.2. Recommended Protocol
473
474 A system should implement the recommended protocols.
475
476 4.2.3. Elective Protocol
477
478 A system may or may not implement an elective protocol. The
479 general notion is that if you are going to do something like this,
480 you must do exactly this. There may be several elective protocols
481 in a general area, for example, there are several electronic mail
482 protocols, and several routing protocols.
483
484 4.2.4. Limited Use Protocol
485
486 These protocols are for use in limited circumstances. This may be
487 because of their experimental state, specialized nature, limited
488 functionality, or historic state.
489
490 4.2.5. Not Recommended Protocol
491
492 These protocols are not recommended for general use. This may be
493 because of their limited functionality, specialized nature, or
494 experimental or historic state.
495
496
497
498
499
500 <span class="grey">Internet Architecture Board Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
503
504
505 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. The Standards Track</span>
506
507 This section discusses in more detail the procedures used by the RFC
508 Editor and the IESG in making decisions about the labeling and
509 publishing of protocols as standards.
510
511 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. The RFC Processing Decision Table</span>
512
513 Here is the current decision table for processing submissions by the
514 RFC Editor. The processing depends on who submitted it, and the
515 status they want it to have.
516
517 +==========================================================+
518 |**************| S O U R C E |
519 +==========================================================+
520 | Desired | IAB | IESG | IRSG | Other |
521 | Status | | | | |
522 +==========================================================+
523 | | | | | |
524 | Standard | Bogus | Publish | Bogus | Bogus |
525 | or | (2) | (1) | (2) | (2) |
526 | Draft | | | | |
527 | Standard | | | | |
528 +--------------+----------+----------+----------+----------+
529 | | | | | |
530 | | Refer | Publish | Refer | Refer |
531 | Proposed | (3) | (1) | (3) | (3) |
532 | Standard | | | | |
533 | | | | | |
534 +--------------+----------+----------+----------+----------+
535 | | | | | |
536 | | Notify | Publish | Notify | Notify |
537 | Experimental | (4) | (1) | (4) | (4) |
538 | Protocol | | | | |
539 | | | | | |
540 +--------------+----------+----------+----------+----------+
541 | | | | | |
542 | Information | Publish | Publish |Discretion|Discretion|
543 | or Opinion | (1) | (1) | (5) | (5) |
544 | Paper | | | | |
545 | | | | | |
546 +==========================================================+
547
548 (1) Publish.
549
550 (2) Bogus. Inform the source of the rules. RFCs specifying
551 Standard, or Draft Standard must come from the IESG, only.
552
553
554
555
556 <span class="grey">Internet Architecture Board Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
559
560
561 (3) Refer to an Area Director for review by a WG. Expect to see
562 the document again only after approval by the IESG.
563
564 (4) Notify both the IESG and IRSG. If no concerns are raised in
565 two weeks then do Discretion (5), else RFC Editor to resolve
566 the concerns or do Refer (3).
567
568 (5) RFC Editor's discretion. The RFC Editor decides if a review
569 is needed and if so by whom. RFC Editor decides to publish or
570 not.
571
572 Of course, in all cases the RFC Editor can request or make minor
573 changes for style, format, and presentation purposes.
574
575 The IESG has designated the IESG Secretary as its agent for
576 forwarding documents with IESG approval and for registering concerns
577 in response to notifications (4) to the RFC Editor. Documents from
578 Area Directors or Working Group Chairs may be considered in the same
579 way as documents from "other".
580
581 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. The Standards Track Diagram</span>
582
583 There is a part of the STATUS and STATE categorization that is called
584 the standards track. Actually, only the changes of state are
585 significant to the progression along the standards track, though the
586 status assignments may change as well.
587
588 The states illustrated by single line boxes are temporary states,
589 those illustrated by double line boxes are long term states. A
590 protocol will normally be expected to remain in a temporary state for
591 several months (minimum six months for proposed standard, minimum
592 four months for draft standard). A protocol may be in a long term
593 state for many years.
594
595 A protocol may enter the standards track only on the recommendation
596 of the IESG; and may move from one state to another along the track
597 only on the recommendation of the IESG. That is, it takes action by
598 the IESG to either start a protocol on the track or to move it along.
599
600 Generally, as the protocol enters the standards track a decision is
601 made as to the eventual STATUS, requirement level or applicability
602 (elective, recommended, or required) the protocol will have, although
603 a somewhat less stringent current status may be assigned, and it then
604 is placed in the the proposed standard STATE with that status. So
605 the initial placement of a protocol is into state 1. At any time the
606 STATUS decision may be revisited.
607
608
609
610
611
612 <span class="grey">Internet Architecture Board Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
615
616
617 |
618 +&lt;----------------------------------------------+
619 | ^
620 V 0 | 4
621 +-----------+ +===========+
622 | enter |--&gt;----------------+--------------&gt;|experiment |
623 +-----------+ | +=====+=====+
624 | |
625 V 1 |
626 +-----------+ V
627 | proposed |--------------&gt;+
628 +---&gt;+-----+-----+ |
629 | | |
630 | V 2 |
631 +&lt;---+-----+-----+ V
632 | draft std |--------------&gt;+
633 +---&gt;+-----+-----+ |
634 | | |
635 | V 3 |
636 +&lt;---+=====+=====+ V
637 | standard |--------------&gt;+
638 +=====+=====+ |
639 |
640 V 5
641 +=====+=====+
642 | historic |
643 +===========+
644
645 The transition from proposed standard (1) to draft standard (2) can
646 only be by action of the IESG and only after the protocol has been
647 proposed standard (1) for at least six months.
648
649 The transition from draft standard (2) to standard (3) can only be by
650 action of the IESG and only after the protocol has been draft
651 standard (2) for at least four months.
652
653 Occasionally, the decision may be that the protocol is not ready for
654 standardization and will be assigned to the experimental state (4).
655 This is off the standards track, and the protocol may be resubmitted
656 to enter the standards track after further work. There are other
657 paths into the experimental and historic states that do not involve
658 IESG action.
659
660 Sometimes one protocol is replaced by another and thus becomes
661 historic, or it may happen that a protocol on the standards track is
662 in a sense overtaken by another protocol (or other events) and
663 becomes historic (state 5).
664
665
666
667
668 <span class="grey">Internet Architecture Board Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
671
672
673 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. The Protocols</span>
674
675 Sub<a href="#section-6.1">section 6.1</a> lists recent RFCs and other changes. Subsections <a href="#section-6.2">6.2</a>
676 - 6.10 list the standards in groups by protocol state.
677
678 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Recent Changes</span>
679
680 <span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>. New RFCs:</span>
681
682 2153 - PPP Vendor Extensions
683
684 This is an information document and does not specify any
685 level of standard.
686
687 2152 - UTF-7
688
689 This is an information document and does not specify any
690 level of standard.
691
692 2151 - Not yet issued.
693
694 2150 - Not yet issued.
695
696 2149 - Multicast Server Architectures for MARS-based ATM
697 multicasting
698
699 This is an information document and does not specify any
700 level of standard.
701
702 2148 - Not yet issued.
703
704 2147 - TCP and UDP over IPv6 Jumbograms
705
706 A Proposed Standard protocol.
707
708 2146 - U.S. Government Internet Domain Names
709
710 This is an information document and does not specify any
711 level of standard.
712
713 2145 - Use and Interpretation of HTTP Version Numbers
714
715 This is an information document and does not specify any
716 level of standard.
717
718
719
720
721
722
723
724 <span class="grey">Internet Architecture Board Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
727
728
729 2144 - The CAST-128 Encryption Algorithm
730
731 This is an information document and does not specify any
732 level of standard.
733
734 2143 - Encapsulating IP with the Small Computer System Interface
735
736 An Experimental protocol.
737
738 2142 - Mailbox Names for Common Services, Roles and Functions
739
740 A Proposed Standard protocol.
741
742 2141 - URN Syntax
743
744 A Proposed Standard protocol.
745
746 2140 - TCP Control Block Interdependence
747
748 This is an information document and does not specify any
749 level of standard.
750
751 2139 - RADIUS Accounting
752
753 This is an information document and does not specify any
754 level of standard.
755
756 2138 - Remote Authentication Dial In User Service (RADIUS)
757
758 A Proposed Standard protocol.
759
760 2137 - Secure Domain Name System Dynamic Update
761
762 A Proposed Standard protocol.
763
764 2136 - Dynamic Updates in the Domain Name System (DNS UPDATE)
765
766 A Proposed Standard protocol.
767
768 2135 - Internet Society By-Laws
769
770 This is an information document and does not specify any
771 level of standard.
772
773 2134 - Articles of Incorporation of Internet Society
774
775 This is an information document and does not specify any
776 level of standard.
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
783
784
785 2133 - Basic Socket Interface Extensions for IPv6
786
787 This is an information document and does not specify any
788 level of standard.
789
790 2132 - DHCP Options and BOOTP Vendor Extensions
791
792 A Draft Standard protocol.
793
794 2131 - Dynamic Host Configuration Protocol
795
796 A Draft Standard protocol.
797
798 2130 - The Report of the IAB Character Set Workshop held 29
799 February - 1 March, 1996
800
801 This is an information document and does not specify any
802 level of standard.
803
804 2129 - Toshiba's Flow Attribute Notification Protocol (FANP)
805 Specification
806
807 This is an information document and does not specify any
808 level of standard.
809
810 2128 - Dial Control Management Information Base using SMIv2
811
812 A Proposed Standard protocol.
813
814 2127 - ISDN Management Information Base using SMIv2
815
816 A Proposed Standard protocol.
817
818 2126 - ISO Transport Service on top of TCP (ITOT)
819
820 A Proposed Standard protocol.
821
822 2125 - The PPP Bandwidth Allocation Protocol (BAP), The PPP
823 Bandwidth Allocation Control Protocol (BACP)
824
825 A Proposed Standard protocol.
826
827 2124 - Cabletron's Light-weight Flow Admission Protocol
828 Specification
829
830 This is an information document and does not specify any
831 level of standard.
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
839
840
841 2123 - Traffic Flow Measurement: Experiences with NeTraMet
842
843 This is an information document and does not specify any
844 level of standard.
845
846 2122 - VEMMI URL Specification
847
848 A Proposed Standard protocol.
849
850 2121 - Issues affecting MARS Cluster Size
851
852 This is an information document and does not specify any
853 level of standard.
854
855 2120 - Managing the X.500 Root Naming Context
856
857 An Experimental protocol.
858
859 2119 - Key words for use in RFCs to Indicate Requirement Level
860
861 This is a Best Current Practices document and does not
862 specify any level of standard.
863
864 2118 - Microsoft Point-To-Point Compression (MPPC) Protocol
865
866 This is an information document and does not specify any
867 level of standard.
868
869 2117 - Not yet issued.
870
871 2116 - X.500 Implementations Catalog-96
872
873 This is an information document and does not specify any
874 level of standard.
875
876 2115 - Not yet issued.
877
878 2114 - Data Link Switching Client Access Protocol
879
880 This is an information document and does not specify any
881 level of standard.
882
883 2113 - IP Router Alert Option
884
885 A Proposed Standard protocol.
886
887
888
889
890
891
892 <span class="grey">Internet Architecture Board Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
895
896
897 2112 - The MIME Multipart/Related Content-type
898
899 A Proposed Standard protocol.
900
901 2111 - Content-ID and Message-ID Uniform Resource Locators
902
903 A Proposed Standard protocol.
904
905 2110 - MIME E-mail Encapsulation of Aggregate Documents, such as
906 HTML (MHTML)
907
908 A Proposed Standard protocol.
909
910 2100 - The Naming of Hosts
911
912 This is an information document and does not specify any
913 level of standard.
914
915 2099 - Request for Comments Summary - RFC Numbers 2000-2099
916
917 This is an information document and does not specify any
918 level of standard.
919
920 2094 - Not yet issued.
921
922 2093 - Not yet issued.
923
924 2076 - Common Internet Message Headers
925
926 This is an information document and does not specify any
927 level of standard.
928
929 <span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>. Other Changes:</span>
930
931 The following are changes to protocols listed in the previous
932 edition.
933
934 1542 - Clarifications and Extensions for the Bootstrap Protocol
935
936 Elevated to Draft Standard.
937
938 1534 - Interoperation Between DHCP and BOOTP
939
940 Elevated to Draft Standard.
941
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
951
952
953 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Standard Protocols</span>
954
955 Protocol Name Status RFC STD *
956 ======== ===================================== ======== ==== === =
957 -------- Internet Official Protocol Standards Req 2200 1
958 -------- Assigned Numbers Req 1700 2
959 -------- Host Requirements - Communications Req 1122 3
960 -------- Host Requirements - Applications Req 1123 3
961 IP Internet Protocol Req 791 5
962 as amended by:--------
963 -------- IP Subnet Extension Req 950 5
964 -------- IP Broadcast Datagrams Req 919 5
965 -------- IP Broadcast Datagrams with Subnets Req 922 5
966 ICMP Internet Control Message Protocol Req 792 5
967 IGMP Internet Group Multicast Protocol Rec 1112 5
968 UDP User Datagram Protocol Rec 768 6
969 TCP Transmission Control Protocol Rec 793 7
970 TELNET Telnet Protocol Rec 854,855 8
971 FTP File Transfer Protocol Rec 959 9
972 SMTP Simple Mail Transfer Protocol Rec 821 10
973 SMTP-SIZE SMTP Service Ext for Message Size Rec 1870 10
974 SMTP-EXT SMTP Service Extensions Rec 1869 10
975 MAIL Format of Electronic Mail Messages Rec 822 11
976 CONTENT Content Type Header Field Rec 1049 11
977 NTPV2 Network Time Protocol (Version 2) Rec 1119 12
978 DOMAIN Domain Name System Rec 1034,1035 13
979 DNS-MX Mail Routing and the Domain System Rec 974 14
980 SNMP Simple Network Management Protocol Rec 1157 15
981 SMI Structure of Management Information Rec 1155 16
982 Concise-MIB Concise MIB Definitions Rec 1212 16
983 MIB-II Management Information Base-II Rec 1213 17
984 NETBIOS NetBIOS Service Protocols Ele 1001,1002 19
985 ECHO Echo Protocol Rec 862 20
986 DISCARD Discard Protocol Ele 863 21
987 CHARGEN Character Generator Protocol Ele 864 22
988 QUOTE Quote of the Day Protocol Ele 865 23
989 USERS Active Users Protocol Ele 866 24
990 DAYTIME Daytime Protocol Ele 867 25
991 TIME Time Server Protocol Ele 868 26
992 TFTP Trivial File Transfer Protocol Ele 1350 33
993 TP-TCP ISO Transport Service on top of the TCP Ele 1006 35
994 ETHER-MIB Ethernet MIB Ele 1643 50
995 PPP Point-to-Point Protocol (PPP) Ele 1661 51
996 PPP-HDLC PPP in HDLC Framing Ele 1662 51
997 IP-SMDS IP Datagrams over the SMDS Service Ele 1209 52
998 POP3 Post Office Protocol, Version 3 Ele 1939 53
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1007
1008
1009 [Note: an asterisk at the end of a line indicates a change from the
1010 previous edition of this document.]
1011
1012 Applicability Statements:
1013
1014 IGMP -- The Internet Architecture Board intends to move towards
1015 general adoption of IP multicasting, as a more efficient solution
1016 than broadcasting for many applications. The host interface has been
1017 standardized in <a href="./rfc1112">RFC-1112</a>; however, multicast-routing gateways are in
1018 the experimental stage and are not widely available. An Internet
1019 host should support all of <a href="./rfc1112">RFC-1112</a>, except for the IGMP protocol
1020 itself which is optional; see <a href="./rfc1122">RFC-1122</a> for more details. Even
1021 without IGMP, implementation of <a href="./rfc1112">RFC-1112</a> will provide an important
1022 advance: IP-layer access to local network multicast addressing. It
1023 is expected that IGMP will become recommended for all hosts and
1024 gateways at some future date.
1025
1026 SMI, MIB-II SNMP -- The Internet Architecture Board recommends that
1027 all IP and TCP implementations be network manageable. At the current
1028 time, this implies implementation of the Internet MIB-II (<a href="./rfc1213">RFC-1213</a>),
1029 and at least the recommended management protocol SNMP (<a href="./rfc1157">RFC-1157</a>).
1030
1031 RIP -- The Routing Information Protocol (RIP) is widely implemented
1032 and used in the Internet. However, both implementors and users
1033 should be aware that RIP has some serious technical limitations as a
1034 routing protocol. The IETF is currently devpeloping several
1035 candidates for a new standard "open" routing protocol with better
1036 properties than RIP. The IAB urges the Internet community to track
1037 these developments, and to implement the new protocol when it is
1038 standardized; improved Internet service will result for many users.
1039
1040 TP-TCP -- As OSI protocols become more widely implemented and used,
1041 there will be an increasing need to support interoperation with the
1042 TCP/IP protocols. The Internet Engineering Task Force is formulating
1043 strategies for interoperation. <a href="./rfc1006">RFC-1006</a> provides one interoperation
1044 mode, in which TCP/IP is used to emulate TP0 in order to support OSI
1045 applications. Hosts that wish to run OSI connection-oriented
1046 applications in this mode should use the procedure described in <a href="./rfc1006">RFC-</a>
1047 <a href="./rfc1006">1006</a>. In the future, the IAB expects that a major portion of the
1048 Internet will support both TCP/IP and OSI (inter-)network protocols
1049 in parallel, and it will then be possible to run OSI applications
1050 across the Internet using full OSI protocol "stacks".
1051
1052
1053
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1063
1064
1065 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Network-Specific Standard Protocols</span>
1066
1067 All Network-Specific Standards have Elective status.
1068
1069 Protocol Name State RFC STD *
1070 ======== ===================================== ===== ===== === =
1071 IP-ATM Classical IP and ARP over ATM Prop 1577
1072 IP-FR Multiprotocol over Frame Relay Draft 1490
1073 ATM-ENCAP Multiprotocol Encapsulation over ATM Prop 1483
1074 IP-TR-MC IP Multicast over Token-Ring LANs Prop 1469
1075 IP-FDDI Transmission of IP and ARP over FDDI Net Std 1390 36
1076 IP-X.25 X.25 and ISDN in the Packet Mode Draft 1356
1077 ARP Address Resolution Protocol Std 826 37
1078 RARP A Reverse Address Resolution Protocol Std 903 38
1079 IP-ARPA Internet Protocol on ARPANET Std BBN1822 39
1080 IP-WB Internet Protocol on Wideband Network Std 907 40
1081 IP-E Internet Protocol on Ethernet Networks Std 894 41
1082 IP-EE Internet Protocol on Exp. Ethernet Nets Std 895 42
1083 IP-IEEE Internet Protocol on IEEE 802 Std 1042 43
1084 IP-DC Internet Protocol on DC Networks Std 891 44
1085 IP-HC Internet Protocol on Hyperchannel Std 1044 45
1086 IP-ARC Transmitting IP Traffic over ARCNET Nets Std 1201 46
1087 IP-SLIP Transmission of IP over Serial Lines Std 1055 47
1088 IP-NETBIOS Transmission of IP over NETBIOS Std 1088 48
1089 IP-IPX Transmission of 802.2 over IPX Networks Std 1132 49
1090 IP-HIPPI IP over HIPPI Draft 2067
1091
1092 [Note: an asterisk at the end of a line indicates a change from the
1093 previous edition of this document.]
1094
1095 Applicability Statements:
1096
1097 It is expected that a system will support one or more physical
1098 networks and for each physical network supported the appropriate
1099 protocols from the above list must be supported. That is, it is
1100 elective to support any particular type of physical network, and for
1101 the physical networks actually supported it is required that they be
1102 supported exactly according to the protocols in the above list. See
1103 also the Host and Gateway Requirements RFCs for more specific
1104 information on network-specific ("link layer") protocols.
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Internet Architecture Board Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1119
1120
1121 <span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Draft Standard Protocols</span>
1122
1123 Protocol Name Status RFC
1124 ======== ===================================== ============== =====
1125 BOOTP DHCP Options and BOOTP Extensions Recommended 2132*
1126 DHCP Dynamic Host Configuration Protocol Elective 2131*
1127 ------- Clarifications and Extensions BOOTP Elective 1542*
1128 DHCP-BOOTP Interoperation Between DHCP and BOOTP Elective 1534*
1129 MIME-CONF MIME Conformance Criteria Elective 2049
1130 MIME-MSG MIME Msg Header Ext for Non-ASCII Elective 2047
1131 MIME-MEDIA MIME Media Types Elective 2046
1132 MIME Multipurpose Internet Mail Extensions Elective 2045
1133 PPP-CHAP PPP Challenge Handshake Authentication Elective 1994
1134 PPP-MP PPP Multilink Protocol Elective 1990
1135 PPP-LINK PPP Link Quality Monitoring Elective 1989
1136 COEX-MIB Coexistence between SNMPV1 &amp; SNMPV2 Elective 1908
1137 SNMPv2-MIB MIB for SNMPv2 Elective 1907
1138 TRANS-MIB Transport Mappings for SNMPv2 Elective 1906
1139 OPS-MIB Protocol Operations for SNMPv2 Elective 1905
1140 CONF-MIB Conformance Statements for SNMPv2 Elective 1904
1141 CONV-MIB Textual Conventions for SNMPv2 Elective 1903
1142 SMIV2 SMI for SNMPv2 Elective 1902
1143 CON-MD5 Content-MD5 Header Field Elective 1864
1144 OSPF-MIB OSPF Version 2 MIB Elective 1850
1145 STR-REP String Representation ... Elective 1779
1146 X.500syn X.500 String Representation ... Elective 1778
1147 X.500lite X.500 Lightweight ... Elective 1777
1148 BGP-4-APP Application of BGP-4 Elective 1772
1149 BGP-4 Border Gateway Protocol 4 Elective 1771
1150 PPP-DNCP PPP DECnet Phase IV Control Protocol Elective 1762
1151 RMON-MIB Remote Network Monitoring MIB Elective 1757
1152 802.5-MIB IEEE 802.5 Token Ring MIB Elective 1748
1153 BGP-4-MIB BGP-4 MIB Elective 1657
1154 RIP2-MIB RIP Version 2 MIB Extension Elective 1724
1155 RIP2 RIP Version 2-Carrying Additional Info. Elective 1723
1156 RIP2-APP RIP Version 2 Protocol App. Statement Elective 1722
1157 SIP-MIB SIP Interface Type MIB Elective 1694
1158 ------- Def Man Objs Parallel-printer-like Elective 1660
1159 ------- Def Man Objs RS-232-like Elective 1659
1160 ------- Def Man Objs Character Stream Elective 1658
1161 SMTP-8BIT SMTP Service Ext or 8bit-MIMEtransport Elective 1652
1162 OSI-NSAP Guidelines for OSI NSAP Allocation Elective 1629
1163 OSPF2 Open Shortest Path First Routing V2 Elective 1583
1164 ISO-TS-ECHO Echo for ISO-8473 Elective 1575
1165 DECNET-MIB DECNET MIB Elective 1559
1166 BRIDGE-MIB BRIDGE-MIB Elective 1493
1167 NTPV3 Network Time Protocol (Version 3) Elective 1305
1168 IP-MTU Path MTU Discovery Elective 1191
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1175
1176
1177 FINGER Finger Protocol Elective 1288
1178 NICNAME WhoIs Protocol Elective 954
1179
1180 [Note: an asterisk at the end of a line indicates a change from the
1181 previous edition of this document.]
1182
1183 Applicability Statements:
1184
1185 PPP -- Point to Point Protocol is a method of sending IP over serial
1186 lines, which are a type of physical network. It is anticipated that
1187 PPP will be advanced to the network-specifics standard protocol state
1188 in the future.
1189
1190 <span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Proposed Standard Protocols</span>
1191
1192 Protocol Name Status RFC
1193 ======== ===================================== ============== =====
1194 IPv6-Jumbo TCP and UDP over IPv6 Jumbograms Elective 2147*
1195 MAIL-SERV Mailbox Names for Common Services Elective 2142*
1196 URN-SYNTAX URN Syntax Elective 2141*
1197 RADIUS Remote Authentication Dial In Service Elective 2138*
1198 SDNSDU Secure Domain Name System Dynamic Update Elective 2137*
1199 DNS-UPDATE Dynamic Updates in the DNS Elective 2136*
1200 DC-MIB Dial Control MIB using SMIv2 Elective 2128*
1201 ISDN-MIB ISDN MIB using SMIv2 Elective 2127*
1202 ITOT ISO Transport Service on top of TCP Elective 2126*
1203 BAP-BACP PPP-BAP, PPP-BACP Elective 2125*
1204 VEMMI-URL VEMMI URL Specification Elective 2122*
1205 ROUT-ALERT IP Router Alert Option Elective 2113*
1206 MIME-RELAT MIME Multipart/Related Content-type Elective 2112*
1207 CIDMID-URL Content-ID and Message-ID URLs Elective 2111*
1208 MHTML MIME E-mail Encapsulation Elective 2110*
1209 HTTP-STATE HTTP State Management Mechanism Elective 2109
1210 802.3-MIB 802.3 Repeater MIB using SMIv2 Elective 2108
1211 PPP-NBFCP PPP NetBIOS Frames Control Protocol Elective 2097
1212 TABLE-MIB IP Forwarding Table MIB Elective 2096
1213 IMAPPOPAU IMAP/POP AUTHorize Extension Elective 2095
1214 RIP-TRIG Trigger RIP Elective 2091
1215 IMAP4-LIT IMAP4 non-synchronizing literals Elective 2088
1216 IMAP4-QUO IMAP4 QUOTA extension Elective 2087
1217 IMAP4-ACL IMAP4 ACL Extension Elective 2086
1218 HMAC-MD5 HMAC-MD5 IP Auth. with Replay Prevention Elective 2085
1219 RIP2-MD5 RIP-2 MD5 Authentication Elective 2082
1220 RIPNG-IPV6 RIPng for IPv6 Elective 2080
1221 URI-ATT URI Attribute Type and Object Class Elective 2079
1222 GSSAP Generic Security Service Application Elective 2078
1223 MIME-MODEL Model Primary MIME Types Elective 2077
1224 RMON-MIB Remote Network Monitoring MIB Elective 2074
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1231
1232
1233 IPV6-UNI IPv6 Provider-Based Unicast Address Elective 2073
1234 HTML-INT HTML Internationalization Elective 2070
1235 DAA Digest Access Authentication Elective 2069
1236 HTTP-1.1 Hypertext Transfer Protocol -- HTTP/1.1 Elective 2068
1237 DNS-SEC Domain Name System Security Extensions Elective 2065
1238 IMAPV4 Internet Message Access Protocol v4rev1 Elective 2060
1239 URLZ39.50 Uniform Resource Locators for Z39.50 Elective 2056
1240 SNANAU-APP SNANAU APPC MIB using SMIv2 Elective 2051
1241 PPP-SNACP PPP SNA Control Protocol Elective 2043
1242 RTP-MPEG RTP Payload Format for MPEG1/MPEG2 Elective 2038
1243 ENTITY-MIB Entity MIB using SMIv2 Elective 2037
1244 RTP-JPEG RTP Payload Format for JPEG-compressed Elective 2035
1245 SMTP-ENH SMTP Enhanced Error Codes Elective 2034
1246 RTP-H.261 RTP Payload Format for H.261 Elective 2032
1247 RTP-CELLB RTP Payload Format of Sun's CellB Elective 2029
1248 SPKM Simple Public-Key GSS-API Mechanism Elective 2025
1249 DLSW-MIB DLSw MIB using SMIv2 Elective 2024
1250 IPV6-PPP IP Version 6 over PPP Elective 2023
1251 MULTI-UNI Multicast over UNI 3.0/3.1 based ATM Elective 2022
1252 RMON-MIB RMON MIB using SMIv2 Elective 2021
1253 802.12-MIB IEEE 802.12 Interface MIB Elective 2020
1254 IPV6-FDDI Transmission of IPv6 Packets Over FDDI Elective 2019
1255 TCP-ACK TCP Selective Acknowledgement Options Elective 2018
1256 URL-ACC URL Access-Type Elective 2017
1257 MIME-PGP MIME Security with PGP Elective 2015
1258 MIB-UDP SNMPv2 MIB for UDP Elective 2013
1259 MIB-TCP SNMPv2 MIB for TCP Elective 2012
1260 MIB-IP SNMPv2 MIB for IP Elective 2011
1261 MOBILEIPMIBMobile IP MIB Definition using SMIv2 Elective 2006
1262 MOBILEIPAPPApplicability Statement for IP Mobility Elective 2005
1263 MINI-IP Minimal Encapsulation within IP Elective 2004
1264 IPENCAPIP IP Encapsulation within IP Elective 2003
1265 MOBILEIPSUPIP Mobility Support Elective 2002
1266 TCPSLOWSRT TCP Slow Start, Congestion Avoidance... Elective 2001
1267 BGP-COMM BGP Communities Attribute Elective 1997
1268 DNS-NOTIFY Mech. for Notification of Zone Changes Elective 1996
1269 DNS-IZT Incremental Zone Transfer in DNS Elective 1995
1270 SMTP-ETRN SMTP Service Extension ETRN Elective 1985
1271 SNA Serial Number Arithmetic Elective 1982
1272 MTU-IPV6 Path MTU Discovery for IP version 6 Elective 1981
1273 PPP-FRAME PPP in Frame Relay Elective 1973
1274 IPV6-ETHER Transmission IPv6 Packets Over Ethernet Elective 1972
1275 IPV6-AUTO IPv6 Stateless Address Autoconfiguation Elective 1971
1276 IPV6-ND Neighbor Discovery for IP Version 6 Elective 1970
1277 PPP-ECP PPP Encryption Control Protocol Elective 1968
1278 GSSAPI-KER Kerberos Version 5 GSS-API Mechanism Elective 1964
1279 PPP-CCP PPP Compression Control Protocol Elective 1962
1280 GSSAPI-SOC GSS-API Auth for SOCKS Version 5 Elective 1961
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1287
1288
1289 LDAP-STR String Rep. of LDAP Search Filters Elective 1960
1290 LDAP-URL LDAP URL Format Elective 1959
1291 ONE-PASS One-Time Password System Elective 1938
1292 TRANS-IPV6 Transition Mechanisms IPv6 Hosts/Routers Elective 1933
1293 AUTH-SOCKS Username Authentication for SOCKS V5 Elective 1929
1294 SOCKSV5 SOCKS Protocol Version 5 Elective 1928
1295 WHOIS++M How to Interact with a Whois++ Mesh Elective 1914
1296 WHOIS++A Architecture of Whois++ Index Service Elective 1913
1297 DSN Delivery Status Notifications Elective 1894
1298 EMS-CODE Enhanced Mail System Status Codes Elective 1893
1299 MIME-RPT Multipart/Report Elective 1892
1300 SMTP-DSN SMTP Delivery Status Notifications Elective 1891
1301 RTP-AV RTP Audio/Video Profile Elective 1890
1302 RTP Transport Protocol for Real-Time Apps Elective 1889
1303 DNS-IPV6 DNS Extensions to support IPv6 Elective 1886
1304 ICMPv6 ICMPv6 for IPv6 Elective 1885
1305 IPV6-Addr IPv6 Addressing Architecture Elective 1884
1306 IPV6 IPv6 Specification Elective 1883
1307 HTML Hypertext Markup Language - 2.0 Elective 1866
1308 SMTP-Pipe SMTP Serv. Ext. for Command Pipelining Elective 1854
1309 MIME-Sec MIME Object Security Services Elective 1848
1310 MIME-Encyp MIME: Signed and Encrypted Elective 1847
1311 WHOIS++ Architecture of the WHOIS++ service Elective 1835
1312 -------- Binding Protocols for ONC RPC Version 2 Elective 1833
1313 XDR External Data Representation Standard Elective 1832
1314 RPC Remote Procedure Call Protocol V. 2 Elective 1831
1315 -------- ESP DES-CBC Transform Ele/Req 1829
1316 -------- IP Authentication using Keyed MD5 Ele/Req 1828
1317 ESP IP Encapsulating Security Payload Ele/Req 1827
1318 IPV6-AH IP Authentication Header Ele/Req 1826
1319 -------- Security Architecture for IP Ele/Req 1825
1320 RREQ Requirements for IP Version 4 Routers Elective 1812
1321 URL Relative Uniform Resource Locators Elective 1808
1322 CLDAP Connection-less LDAP Elective 1798
1323 OSPF-DC Ext. OSPF to Support Demand Circuits Elective 1793
1324 TMUX Transport Multiplexing Protocol Elective 1692
1325 TFTP-Opt TFTP Options Elective 1784
1326 TFTP-Blk TFTP Blocksize Option Elective 1783
1327 TFTP-Ext TFTP Option Extension Elective 1782
1328 OSI-Dir OSI User Friendly Naming ... Elective 1781
1329 MIME-EDI MIME Encapsulation of EDI Objects Elective 1767
1330 Lang-Tag Tags for Identification of Languages Elective 1766
1331 XNSCP PPP XNS IDP Control Protocol Elective 1764
1332 BVCP PPP Banyan Vines Control Protocol Elective 1763
1333 Print-MIB Printer MIB Elective 1759
1334 ATM-SIG ATM Signaling Support for IP over ATM Elective 1755
1335 IPNG Recommendation for IP Next Generation Elective 1752
1336 802.5-SSR 802.5 SSR MIB using SMIv2 Elective 1749
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1343
1344
1345 SDLCSMIv2 SNADLC SDLC MIB using SMIv2 Elective 1747
1346 BGP4/IDRP BGP4/IDRP for IP/OSPF Interaction Elective 1745
1347 AT-MIB Appletalk MIB Elective 1742
1348 MacMIME MIME Encapsulation of Macintosh files Elective 1740
1349 URL Uniform Resource Locators Elective 1738
1350 POP3-AUTH POP3 AUTHentication command Elective 1734
1351 IMAP4-AUTH IMAP4 Authentication Mechanisms Elective 1731
1352 RDBMS-MIB RDMS MIB - using SMIv2 Elective 1697
1353 MODEM-MIB Modem MIB - using SMIv2 Elective 1696
1354 ATM-MIB ATM Management Version 8.0 using SMIv2 Elective 1695
1355 SNANAU-MIB SNA NAUs MIB using SMIv2 Elective 1666
1356 PPP-TRANS PPP Reliable Transmission Elective 1663
1357 -------- Postmaster Convention X.400 Operations Elective 1648
1358 TN3270-En TN3270 Enhancements Elective 1647
1359 PPP-BCP PPP Bridging Control Protocol Elective 1638
1360 UPS-MIB UPS Management Information Base Elective 1628
1361 AAL5-MTU Default IP MTU for use over ATM AAL5 Elective 1626
1362 PPP-SONET PPP over SONET/SDH Elective 1619
1363 PPP-ISDN PPP over ISDN Elective 1618
1364 DNS-R-MIB DNS Resolver MIB Extensions Elective 1612
1365 DNS-S-MIB DNS Server MIB Extensions Elective 1611
1366 FR-MIB Frame Relay Service MIB Elective 1604
1367 PPP-X25 PPP in X.25 Elective 1598
1368 OSPF-NSSA The OSPF NSSA Option Elective 1587
1369 OSPF-Multi Multicast Extensions to OSPF Elective 1584
1370 SONET-MIB MIB SONET/SDH Interface Type Elective 1595
1371 RIP-DC Extensions to RIP to Support Demand Cir. Elective 1582
1372 -------- Evolution of the Interfaces Group of MIB-II Elective 1573
1373 PPP-LCP PPP LCP Extensions Elective 1570
1374 X500-MIB X.500 Directory Monitoring MIB Elective 1567
1375 MAIL-MIB Mail Monitoring MIB Elective 1566
1376 NSM-MIB Network Services Monitoring MIB Elective 1565
1377 CIPX Compressing IPX Headers Over WAM Media Elective 1553
1378 IPXCP PPP Internetworking Packet Exchange Control Elective 1552
1379 SRB-MIB Source Routing Bridge MIB Elective 1525
1380 CIDR-STRA CIDR Address Assignment... Elective 1519
1381 CIDR-ARCH CIDR Architecture... Elective 1518
1382 CIDR-APP CIDR Applicability Statement Elective 1517
1383 -------- 802.3 MAU MIB Elective 1515
1384 HOST-MIB Host Resources MIB Elective 1514
1385 -------- Token Ring Extensions to RMON MIB Elective 1513
1386 FDDI-MIB FDDI Management Information Base Elective 1512
1387 KERBEROS Kerberos Network Authentication Ser (V5) Elective 1510
1388 GSSAPI Generic Security Service API: C-bindings Elective 1509
1389 DASS Distributed Authentication Security... Elective 1507
1390 -------- X.400 Use of Extended Character Sets Elective 1502
1391 HARPOON Rules for Downgrading Messages... Elective 1496
1392 Mapping MHS/RFC-822 Message Body Mapping Elective 1495
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1399
1400
1401 Equiv X.400/MIME Body Equivalences Elective 1494
1402 IDPR Inter-Domain Policy Routing Protocol Elective 1479
1403 IDPR-ARCH Architecture for IDPR Elective 1478
1404 PPP/Bridge MIB Bridge PPP MIB Elective 1474
1405 PPP/IP MIB IP Network Control Protocol of PPP MIB Elective 1473
1406 PPP/SEC MIB Security Protocols of PPP MIB Elective 1472
1407 PPP/LCP MIB Link Control Protocol of PPP MIB Elective 1471
1408 X25-MIB Multiprotocol Interconnect on X.25 MIB Elective 1461
1409 SNMPv2 Introduction to SNMPv2 Elective 1441
1410 PEM-KEY PEM - Key Certification Elective 1424
1411 PEM-ALG PEM - Algorithms, Modes, and Identifiers Elective 1423
1412 PEM-CKM PEM - Certificate-Based Key Management Elective 1422
1413 PEM-ENC PEM - Message Encryption and Auth Elective 1421
1414 SNMP-IPX SNMP over IPX Elective 1420
1415 SNMP-AT SNMP over AppleTalk Elective 1419
1416 SNMP-OSI SNMP over OSI Elective 1418
1417 FTP-FTAM FTP-FTAM Gateway Specification Elective 1415
1418 IDENT-MIB Identification MIB Elective 1414
1419 IDENT Identification Protocol Elective 1413
1420 DS3/E3-MIB DS3/E3 Interface Type Elective 1407
1421 DS1/E1-MIB DS1/E1 Interface Type Elective 1406
1422 BGP-OSPF BGP OSPF Interaction Elective 1403
1423 -------- Route Advertisement In BGP2 And BGP3 Elective 1397
1424 SNMP-X.25 SNMP MIB Extension for X.25 Packet Layer Elective 1382
1425 SNMP-LAPB SNMP MIB Extension for X.25 LAPB Elective 1381
1426 PPP-ATCP PPP AppleTalk Control Protocol Elective 1378
1427 PPP-OSINLCP PPP OSI Network Layer Control Protocol Elective 1377
1428 SNMP-PARTY-MIB Administration of SNMP Elective 1353
1429 SNMP-SEC SNMP Security Protocols Elective 1352
1430 SNMP-ADMIN SNMP Administrative Model Elective 1351
1431 TOS Type of Service in the Internet Elective 1349
1432 PPP-IPCP PPP Control Protocol Elective 1332
1433 ------- X.400 1988 to 1984 downgrading Elective 1328
1434 ------- Mapping between X.400(1988) Elective 1327
1435 TCP-EXT TCP Extensions for High Performance Elective 1323
1436 FRAME-MIB Management Information Base for Frame Elective 1315
1437 NETFAX File Format for the Exchange of Images Elective 1314
1438 IARP Inverse Address Resolution Protocol Elective 1293
1439 FDDI-MIB FDDI-MIB Elective 1285
1440 ------- Encoding Network Addresses Elective 1277
1441 ------- Replication and Distributed Operations Elective 1276
1442 ------- COSINE and Internet X.500 Schema Elective 1274
1443 BGP-MIB Border Gateway Protocol MIB (Version 3) Elective 1269
1444 ICMP-ROUT ICMP Router Discovery Messages Elective 1256
1445 OSI-UDP OSI TS on UDP Elective 1240
1446 STD-MIBs Reassignment of Exp MIBs to Std MIBs Elective 1239
1447 IPX-IP Tunneling IPX Traffic through IP Nets Elective 1234
1448 IS-IS OSI IS-IS for TCP/IP Dual Environments Elective 1195
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1455
1456
1457 IP-CMPRS Compressing TCP/IP Headers Elective 1144
1458 NNTP Network News Transfer Protocol Elective 977
1459
1460 [Note: an asterisk at the end of a line indicates a change from the
1461 previous edition of this document.]
1462
1463 [Note: Ele/Req indicates elective for use with IPv4 and required for use
1464 with IPv6.]
1465
1466 Applicability Statements:
1467
1468 OSPF - <a href="./rfc1370">RFC 1370</a> is an applicability statement for OSPF.
1469
1470
1471
1472
1473
1474
1475
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</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-TN3270E TN3270 Enhancements 40 Prop Ele 1647
1560 TOPT-AUTH Telnet XAUTH 41 Exp
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1567
1568
1569 TOPT-CHARSET Telnet CHARSET 42 Exp 2066
1570 TOPT-EXTOP Extended-Options-List 255 Std Rec 861 32
1571
1572 [Note: an asterisk at the end of a line indicates a change from the
1573 previous edition of this document.]
1574
1575 <span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. Experimental Protocols</span>
1576
1577 All Experimental protocols have the Limited Use status.
1578
1579 Protocol Name RFC
1580 ======== ===================================== =====
1581 IP-SCSI Encapsulating IP with the SCSI 2143*
1582 X.500-NAME Managing the X.500 Root Naming Context 2120*
1583 TFTP-MULTI TFTP Multicast Option 2090
1584 IP-Echo IP Echo Host Service 2075
1585 METER-MIB Traffic Flow Measurement Meter MIB 2064
1586 TFM-ARCH Traffic Flow Measurement Architecture 2063
1587 DNS-SRV Location of Services in the DNS 2052
1588 URAS Uniform Resource Agents 2016
1589 GPS-AR GPS-Based Addressing and Routing 2009
1590 ETFTP Enhanced Trivial File Transfer Protocol 1986
1591 BGP-RR BGP Route Reflection 1966
1592 BGP-ASC Autonomous System Confederations for BGP 1965
1593 SMKD Scalable Multicast Key Distribution 1949
1594 HTML-TBL HTML Tables 1942
1595 MIME-VP Voice Profile for Internet Mail 1911
1596 SNMPV2SM User-based Security Model for SNMPv2 1910
1597 SNMPV2AI SNMPv2 Administrative Infrastructure 1909
1598 SNMPV2CB Introduction to Community-based SNMPv2 1901
1599 ------- IPv6 Testing Address Allocation 1897
1600 DNS-LOC Location Information in the DNS 1876
1601 SGML-MT SGML Media Types 1874
1602 CONT-MT Access Type Content-ID 1873
1603 UNARP ARP Extension - UNARP 1868
1604 ------- Form-based File Upload in HTML 1867
1605 ------- BGP/IDRP Route Server Alternative 1863
1606 ------- IP Authentication using Keyed SHA 1852
1607 ESP3DES ESP Triple DES Transform 1851
1608 ------- SMTP 521 Reply Code 1846
1609 ------- SMTP Serv. Ext. for Checkpoint/Restart 1845
1610 ------- X.500 Mapping X.400 and <a href="./rfc822">RFC 822</a> Addresses 1838
1611 ------- Tables and Subtrees in the X.500 Directory 1837
1612 ------- O/R Address hierarchy in X.500 1836
1613 ------- SMTP Serv. Ext. Large and Binary MIME Msgs. 1830
1614 ST2 Stream Protocol Version 2 1819
1615 ------- Content-Disposition Header 1806
1616 ------- Schema Publishing in X.500 Directory 1804
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1623
1624
1625 ------- X.400-MHS use X.500 to support X.400-MHS Routing 1801
1626 ------- Class A Subnet Experiment 1797
1627 TCP/IPXMIB TCP/IPX Connection Mib Specification 1792
1628 ------- TCP And UDP Over IPX Networks With Fixed Path MTU 1791
1629 ICMP-DM ICMP Domain Name Messages 1788
1630 CLNP-MULT Host Group Extensions for CLNP Multicasting 1768
1631 OSPF-OVFL OSPF Database Overflow 1765
1632 RWP Remote Write ProtocolL - Version 1.0 1756
1633 NARP NBMA Address Resolution Protocol 1735
1634 DNS-DEBUG Tools for DNS debugging 1713
1635 DNS-ENCODE DNS Encoding of Geographical Location 1712
1636 TCP-POS An Extension to TCP: Partial Order Service 1693
1637 ------- DNS to Distribute <a href="./rfc1327">RFC1327</a> Mail Address Mapping Tables 1664
1638 T/TCP TCP Extensions for Transactions 1644
1639 MIME-UNI Using Unicode with MIME 1641
1640 FOOBAR FTP Operation Over Big Address Records 1639
1641 X500-CHART Charting Networks in the X.500 Directory 1609
1642 X500-DIR Representing IP Information in the X.500 Directory 1608
1643 SNMP-DPI SNMP Distributed Protocol Interface 1592
1644 CLNP-TUBA Use of ISO CLNP in TUBA Environments 1561
1645 REM-PRINT TPC.INT Subdomain Remote Printing - Technical 1528
1646 EHF-MAIL Encoding Header Field for Internet Messages 1505
1647 RAP Internet Route Access Protocol 1476
1648 TP/IX TP/IX: The Next Internet 1475
1649 X400 Routing Coordination for X.400 Services 1465
1650 DNS Storing Arbitrary Attributes in DNS 1464
1651 IRCP Internet Relay Chat Protocol 1459
1652 TOS-LS Link Security TOS 1455
1653 SIFT/UFT Sender-Initiated/Unsolicited File Transfer 1440
1654 DIR-ARP Directed ARP 1433
1655 TEL-SPX Telnet Authentication: SPX 1412
1656 TEL-KER Telnet Authentication: Kerberos V4 1411
1657 MAP-MAIL X.400 Mapping and Mail-11 1405
1658 TRACE-IP Traceroute Using an IP Option 1393
1659 DNS-IP Experiment in DNS Based IP Routing 1383
1660 RMCP Remote Mail Checking Protocol 1339
1661 TCP-HIPER TCP Extensions for High Performance 1323
1662 MSP2 Message Send Protocol 2 1312
1663 DSLCP Dynamically Switched Link Control 1307
1664 -------- X.500 and Domains 1279
1665 IN-ENCAP Internet Encapsulation Protocol 1241
1666 CLNS-MIB CLNS-MIB 1238
1667 CFDP Coherent File Distribution Protocol 1235
1668 IP-AX.25 IP Encapsulation of AX.25 Frames 1226
1669 ALERTS Managing Asynchronously Generated Alerts 1224
1670 MPP Message Posting Protocol 1204
1671 SNMP-BULK Bulk Table Retrieval with the SNMP 1187
1672 DNS-RR New DNS RR Definitions 1183
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1679
1680
1681 IMAP2 Interactive Mail Access Protocol 1176
1682 NTP-OSI NTP over OSI Remote Operations 1165
1683 DMF-MAIL Digest Message Format for Mail 1153
1684 RDP Reliable Data Protocol 908,1151
1685 TCP-ACO TCP Alternate Checksum Option 1146
1686 IP-DVMRP IP Distance Vector Multicast Routing 1075
1687 VMTP Versatile Message Transaction Protocol 1045
1688 COOKIE-JAR Authentication Scheme 1004
1689 NETBLT Bulk Data Transfer Protocol 998
1690 IRTP Internet Reliable Transaction Protocol 938
1691 LDP Loader Debugger Protocol 909
1692 RLP Resource Location Protocol 887
1693 NVP-II Network Voice Protocol ISI-memo
1694 PVP Packet Video Protocol ISI-memo
1695
1696 [Note: an asterisk at the end of a line indicates a change from the
1697 previous edition of this document.]
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1735
1736
1737 <span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a>. Informational Protocols</span>
1738
1739 Information protocols have no status.
1740
1741 Protocol Name RFC
1742 ======= ==================================== =====
1743 PPP-EXT PPP Vendor Extensions 2153*
1744 UTF-7 UTF-7 2152*
1745 CAST-128 CAST-128 Encryption Algorithm 2144*
1746 DLSCAP Data Link Switching Client Access Protocol 2114*
1747 PNG Portable Network Graphics Version 1.0 2083
1748 RC5 RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms 2040
1749 SNTP Simple Network Time Protocol v4 for IPv4, IPv6 and OSI 2030
1750 PGP-MEF PGP Message Exchange Formats 1991
1751 PPP-DEFL PPP Deflate Protocol 1979
1752 PPP-PRED PPP Predictor Compression Protocol 1978
1753 PPP-BSD PPP BSD Compression Protocol 1977
1754 PPP-DCE PPP for Data Compression in DCE 1976
1755 PPP-MAG PPP Magnalink Variable Resource Compression 1975
1756 PPP-STAC PPP Stac LZS Compression Protocol 1974
1757 GZIP GZIP File Format Specification Version 4.3 1952
1758 DEFLATE DEFLATE Compressed Data Format Specification V. 1.3 1951
1759 ZLIB ZLIB Compressed Data Format Specification V. 3.3 1950
1760 HTTP-1.0 Hypertext Transfer Protocol -- HTTP/1.0 1945
1761 -------- text/enriched MIME Content-type 1896
1762 -------- Application/CALS-1840 Content-type 1895
1763 -------- PPP IPCP Extensions for Name Server Addresses 1877
1764 SNPP Simple Network Paging Protocol - Version 2 1861
1765 -------- ISO Transport Class 2 Non-use Explicit Flow Control 1859
1766 over TCP <a href="./rfc1006">RFC1006</a> extension
1767 -------- IP in IP Tunneling 1853
1768 -------- PPP Network Control Protocol for LAN Extension 1841
1769 TESS The Exponential Security System 1824
1770 NFSV3 NFS Version 3 Protocol Specification 1813
1771 -------- A Format for Bibliographic Records 1807
1772 ------- Data Link Switching: Switch-to-Switch Protocol 1795
1773 BGP-4 Experience with the BGP-4 Protocol 1773
1774 SDMD IPv4 Option for Sender Directed MD Delivery 1770
1775 SNOOP Snoop Version 2 Packet Capture File Format 1761
1776 BINHEX MIME Content Type for BinHex Encoded Files 1741
1777 RWHOIS Referral Whois Protocol 1714
1778 DNS-NSAP DNS NSAP Resource Records 1706
1779 RADIO-PAGE TPC.INT Subdomain: Radio Paging -- Technical Procedures 1703
1780 GRE-IPv4 Generic Routing Encapsulation over IPv4 1702
1781 GRE Generic Routing Encapsulatio 1701
1782 ADSNA-IP Advanced SNA/IP: A Simple SNA Transport Protocol 1538
1783 TACACS Terminal Access Control Protocol 1492
1784 MD4 MD4 Message Digest Algorithm 1320
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1791
1792
1793 SUN-NFS Network File System Protocol 1094
1794 SUN-RPC Remote Procedure Call Protocol Version 2 1057
1795 GOPHER The Internet Gopher Protocol 1436
1796 LISTSERV Listserv Distribute Protocol 1429
1797 ------- Replication Requirements 1275
1798 PCMAIL Pcmail Transport Protocol 1056
1799 MTP Multicast Transport Protocol 1301
1800 BSD Login BSD Login 1282
1801 DIXIE DIXIE Protocol Specification 1249
1802 IP-X.121 IP to X.121 Address Mapping for DDN 1236
1803 OSI-HYPER OSI and LLC1 on HYPERchannel 1223
1804 HAP2 Host Access Protocol 1221
1805 SUBNETASGN On the Assignment of Subnet Numbers 1219
1806 SNMP-TRAPS Defining Traps for use with SNMP 1215
1807 DAS Directory Assistance Service 1202
1808 LPDP Line Printer Daemon Protocol 1179
1809
1810 [Note: an asterisk at the end of a line indicates a change from the
1811 previous edition of this document.]
1812
1813 <span class="h3"><a class="selflink" id="section-6.9" href="#section-6.9">6.9</a>. Historic Protocols</span>
1814
1815 All Historic protocols have Not Recommended status.
1816
1817 Protocol Name RFC STD
1818 ======== ===================================== ===== ===
1819 IPSO DoD Security Options for IP Elective 1108
1820 SNMPv2 Manager-to-Manager MIB Elective 1451
1821 SNMPv2 Party MIB for SNMPv2 Elective 1447
1822 SNMPv2 Security Protocols for SNMPv2 Elective 1446
1823 SNMPv2 Administrative Model for SNMPv2 Elective 1445
1824 RIP Routing Information Protocol Ele 1058 34
1825 -------- Mapping full 822 to Restricted 822 1137
1826 BGP3 Border Gateway Protocol 3 (BGP-3) 1267,1268
1827 -------- Gateway Requirements Req 1009 4
1828 EGP Exterior Gateway Protocol Rec 904 18
1829 SNMP-MUX SNMP MUX Protocol and MIB 1227
1830 OIM-MIB-II OSI Internet Management: MIB-II 1214
1831 IMAP3 Interactive Mail Access Protocol Version 3 1203
1832 SUN-RPC Remote Procedure Call Protocol Version 1 1050
1833 802.4-MIP IEEE 802.4 Token Bus MIB 1230
1834 CMOT Common Management Information Services 1189
1835 -------- Mail Privacy: Procedures 1113
1836 -------- Mail Privacy: Key Management 1114
1837 -------- Mail Privacy: Algorithms 1115
1838 NFILE A File Access Protocol 1037
1839 HOSTNAME HOSTNAME Protocol 953
1840 SFTP Simple File Transfer Protocol 913
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1847
1848
1849 SUPDUP SUPDUP Protocol 734
1850 BGP Border Gateway Protocol 1163,1164
1851 MIB-I MIB-I 1156
1852 SGMP Simple Gateway Monitoring Protocol 1028
1853 HEMS High Level Entity Management Protocol 1021
1854 STATSRV Statistics Server 996
1855 POP2 Post Office Protocol, Version 2 937
1856 RATP Reliable Asynchronous Transfer Protocol 916
1857 HFEP Host - Front End Protocol 929
1858 THINWIRE Thinwire Protocol 914
1859 HMP Host Monitoring Protocol 869
1860 GGP Gateway Gateway Protocol 823
1861 RTELNET Remote Telnet Service 818
1862 CLOCK DCNET Time Server Protocol 778
1863 MPM Internet Message Protocol 759
1864 NETRJS Remote Job Service 740
1865 NETED Network Standard Text Editor 569
1866 RJE Remote Job Entry 407
1867 XNET Cross Net Debugger IEN-158
1868 NAMESERVER Host Name Server Protocol IEN-116
1869 MUX Multiplexing Protocol IEN-90
1870 GRAPHICS Graphics Protocol NIC-24308
1871
1872 [Note: an asterisk at the end of a line indicates a change from the
1873 previous edition of this document.]
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900 <span class="grey">Internet Architecture Board Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1903
1904
1905 <span class="h3"><a class="selflink" id="section-6.10" href="#section-6.10">6.10</a>. Obsolete Protocols</span>
1906
1907 Some of the protocols listed in this memo are described in RFCs that are
1908 obsoleted by newer RFCs. "Obsolete" or "obsoleted" is not an official
1909 state or status of protocols. This subsection is for information only.
1910
1911 While it may seem to be obviously wrong to have an obsoleted RFC in the
1912 list of standards, there may be cases when an older standard is in the
1913 process of being replaced. This process may take a year or two.
1914
1915 Many obsoleted protocols are of little interest and are dropped from
1916 this memo altogether. Some obsoleted protocols have received enough
1917 recognition that it seems appropriate to list them under their current
1918 status and with the following reference to their current replacement.
1919
1920 RFC RFC Status Title *
1921 ==== ==== ========= =================================== =
1922 <span class="h2"><a class="selflink" id="section-1305" href="#section-1305">1305</a> obsoletes 1119 Stan/Rec </span> Network Time Protocol version 2
1923
1924 Thanks to Lynn Wheeler for compiling the information in this
1925 subsection.
1926
1927 [Note: an asterisk at the end of a line indicates a change from the
1928 previous edition of this document.]
1929
1930 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Contacts</span>
1931
1932 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. IAB, IETF, and IRTF Contacts</span>
1933
1934 7.1.1. Internet Architecture Board (IAB) Contact
1935
1936 Please send your comments about this list of protocols and especially
1937 about the Draft Standard Protocols to the Internet Architecture Board
1938 care of Abel Winerib, IAB Executive Director.
1939
1940 Contacts:
1941
1942 Abel Winerib
1943 Executive Director of the IAB
1944 Intel, JF2-64
1945 2111 NE 25th Avenue
1946 Hillsboro, OR 97124
1947
1948 1-503-696-8972
1949
1950 [email protected]
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
1959
1960
1961 Brian E. Carpenter
1962 Chair of the IAB
1963 IBM United Kingdon Laboratories
1964 Hursley Park
1965 Winchester
1966 Hampshire SO21 2JN
1967
1968 +44 1962 816833
1969
1970 [email protected]
1971
1972
1973 7.1.2. Internet Engineering Task Force (IETF) Contact
1974
1975 Contacts:
1976
1977 Fred Baker
1978 Chair of the IETF
1979 cisco Systems, Inc.
1980 519 Lado Drive
1981 Santa Barbara, CA 93111
1982
1983 1-805-681-0115
1984
1985 [email protected]
1986
1987 Steve Coya
1988 IESG Secretary
1989 Corporation for National Research Initiatives
1990 1895 Preston White Drive, Suite 100
1991 Reston, VA 22091
1992
1993 1-703-620-8990
1994
1995 [email protected]
1996
1997 Steve Coya
1998 Executive Director of the IETF
1999 Corporation for National Research Initiatives
2000 1895 Preston White Drive, Suite 100
2001 Reston, VA 22091
2002
2003 1-703-620-8990
2004
2005 [email protected]
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="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
2015
2016
2017 7.1.3. Internet Research Task Force (IRTF) Contact
2018
2019 Contact:
2020
2021 Abel Winerib
2022 Chair of the IRTF
2023 Intel, JF2-64
2024 2111 NE 25th Avenue
2025 Hillsboro, OR 97124
2026
2027 1-503-696-8972
2028
2029 [email protected]
2030
2031
2032 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Internet Assigned Numbers Authority Contact</span>
2033
2034 Contact:
2035
2036 Joyce K. Reynolds
2037 Internet Assigned Numbers Authority
2038 USC/Information Sciences Institute
2039 4676 Admiralty Way
2040 Marina del Rey, CA 90292-6695
2041
2042 1-310-822-1511
2043
2044 [email protected]
2045
2046 The protocol standards are managed by the Internet Assigned Numbers
2047 Authority.
2048
2049 Please refer to the document "Assigned Numbers" (<a href="./rfc1700">RFC-1700</a>) for
2050 further information about the status of protocol documents. There
2051 are two documents that summarize the requirements for host and
2052 gateways in the Internet, "Host Requirements" (<a href="./rfc1122">RFC-1122</a> and <a href="./rfc1123">RFC-1123</a>)
2053 and "Requirements for IP Version 4 Routers" (<a href="./rfc1812">RFC-1812</a>).
2054
2055 How to obtain the most recent edition of this "Internet Official
2056 Protocol Standards" memo:
2057
2058 The file "in-notes/std/std1.txt" may be copied via FTP from the
2059 FTP.ISI.EDU computer using the FTP username "anonymous" and FTP
2060 password "guest".
2061
2062
2063
2064
2065
2066
2067
2068 <span class="grey">Internet Architecture Board Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
2071
2072
2073 <span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Request for Comments Editor Contact</span>
2074
2075 Contact:
2076
2077 Jon Postel
2078 RFC Editor
2079 USC/Information Sciences Institute
2080 4676 Admiralty Way
2081 Marina del Rey, CA 90292-6695
2082
2083 1-310-822-1511
2084
2085 [email protected]
2086
2087 Documents may be submitted via electronic mail to the RFC Editor for
2088 consideration for publication as RFC. If you are not familiar with
2089 the format or style requirements please request the "Instructions for
2090 RFC Authors". In general, the style of any recent RFC may be used as
2091 a guide.
2092
2093 <span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. The Network Information Center and</span>
2094 <span class="h3"> Requests for Comments Distribution Contact</span>
2095
2096 RFC's may be obtained from DS.INTERNIC.NET via FTP, WAIS, and
2097 electronic mail. Through FTP, RFC's are stored as rfc/rfcnnnn.txt
2098 or rfc/rfcnnnn.ps where 'nnnn' is the RFC number. Login as
2099 "anonymous" and provide your e-mail address as the password.
2100 Through WAIS, you may use either your local WAIS client or telnet
2101 to DS.INTERNIC.NET and login as "wais" (no password required) to
2102 access a WAIS client. Help information and a tutorial for using
2103 WAIS are available online. The WAIS database to search is "rfcs".
2104
2105 Directory and Database Services also provides a mail server
2106 interface. Send a mail message to [email protected] and
2107 include any of the following commands in the message body:
2108
2109 document-by-name rfcnnnn where 'nnnn' is the RFC number
2110 The text version is sent.
2111
2112 file /ftp/rfc/rfcnnnn.yyy where 'nnnn' is the RFC number.
2113 and 'yyy' is 'txt' or 'ps'.
2114
2115 help to get information on how to use
2116 the mailserver.
2117
2118 The InterNIC directory and database services collection of
2119 resource listings, internet documents such as RFCs, FYIs, STDs,
2120 and Internet Drafts, and publicly accessible databases are also
2121
2122
2123
2124 <span class="grey">Internet Architecture Board Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc2200">RFC 2200</a> Internet Standards June 1997</span>
2127
2128
2129 now available via Gopher. All our collections are WAIS indexed
2130 and can be searched from the Gopher menu.
2131
2132 To access the InterNIC Gopher Servers, please connect to
2133 "internic.net" port 70.
2134
2135 Contact: [email protected]
2136
2137 <span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Sources for Requests for Comments</span>
2138
2139 Details on many sources of RFCs via FTP or EMAIL may be obtained by
2140 sending an EMAIL message to "[email protected]" with the message body
2141 "help: ways_to_get_rfcs". For example:
2142
2143 To: [email protected]
2144 Subject: getting rfcs
2145
2146 help: ways_to_get_rfcs
2147
2148 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
2149
2150 Security issues are not addressed in this memo.
2151
2152 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Author's Address</span>
2153
2154 Jon Postel
2155 USC/Information Sciences Institute
2156 4676 Admiralty Way
2157 Marina del Rey, CA 90292
2158
2159 Phone: 310-822-1511
2160 Fax: 310-823-6714
2161
2162 Email: [email protected]
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180 Internet Architecture Board Standards Track [Page 39]
2181 </pre>