RFC 1600
Internet Official Protocol Standards
RFC 1600: INTERNET OFFICIAL PROTOCOL STANDARDS 🎀
okay bestie, let's get into it 💖 this is RFC 1600, published in March 1994 by the Internet Architecture Board and edited by J. Postel 🦋. It's from the Network Working Group, it's on the Standards Track 🛤️, and it's STD 1 👑. It also obsoletes a whole pile of older RFCs: RFCs 1540, 1500, 1410, 1360, 1280, 1250, 1100, 1083, 1130, 1140, and 1200. Main character energy, no cap 💅
Status of this Memo 🧾
so this memo basically tells you where each protocol stands in the standardization process, as decided by the Internet Architecture Board (IAB) 🗺️. It is an Internet Standard ✨, and distribution of it is unlimited 🌈
Table of Contents 📚
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1. The Standardization Process . . . . . . . . . . . . . . . . 3
2. The Request for Comments Documents . . . . . . . . . . . . . 5
3. Other Reference Documents . . . . . . . . . . . . . . . . . 6
3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6
3.2. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6
3.3. Host Requirements . . . . . . . . . . . . . . . . . . . . 6
3.4. The MIL-STD Documents . . . . . . . . . . . . . . . . . . 6
4. Explanation of Terms . . . . . . . . . . . . . . . . . . . . 7
4.1. Definitions of Protocol State (Maturity Level) . . . . . . 8
4.1.1. Standard Protocol . . . . . . . . . . . . . . . . . . . 8
4.1.2. Draft Standard Protocol . . . . . . . . . . . . . . . . 9
4.1.3. Proposed Standard Protocol . . . . . . . . . . . . . . . 9
4.1.4. Experimental Protocol . . . . . . . . . . . . . . . . . 9
4.1.5. Informational Protocol . . . . . . . . . . . . . . . . . 9
4.1.6. Historic Protocol . . . . . . . . . . . . . . . . . . . 9
4.2. Definitions of Protocol Status (Requirement Level) . . . 9
4.2.1. Required Protocol . . . . . . . . . . . . . . . . . . 10
4.2.2. Recommended Protocol . . . . . . . . . . . . . . . . . 10
4.2.3. Elective Protocol . . . . . . . . . . . . . . . . . . 10
4.2.4. Limited Use Protocol . . . . . . . . . . . . . . . . . 10
4.2.5. Not Recommended Protocol . . . . . . . . . . . . . . . 10
5. The Standards Track . . . . . . . . . . . . . . . . . . . 10
5.1. The RFC Processing Decision Table . . . . . . . . . . . 10
5.2. The Standards Track Diagram . . . . . . . . . . . . . . 12
6. The Protocols . . . . . . . . . . . . . . . . . . . . . . 14
6.1. Recent Changes . . . . . . . . . . . . . . . . . . . . . 14
6.1.1. New RFCs . . . . . . . . . . . . . . . . . . . . . . . 14
6.1.2. Other Changes . . . . . . . . . . . . . . . . . . . . 19
6.2. Standard Protocols . . . . . . . . . . . . . . . . . . . 20
6.3. Network-Specific Standard Protocols . . . . . . . . . . 22
6.4. Draft Standard Protocols . . . . . . . . . . . . . . . . 23
6.5. Proposed Standard Protocols . . . . . . . . . . . . . . 24
6.6. Telnet Options . . . . . . . . . . . . . . . . . . . . . 27
6.7. Experimental Protocols . . . . . . . . . . . . . . . . . 28
6.8. Informational Protocols . . . . . . . . . . . . . . . . 29
6.9. Historic Protocols . . . . . . . . . . . . . . . . . . . 30
6.10 Obsolete Protocols . . . . . . . . . . . . . . . . . . . 31
7. Contacts . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.1. IAB, IETF, and IRTF Contacts . . . . . . . . . . . . . . 32
7.1.1. Internet Architecture Board (IAB) Contact . . . . . . 32
7.1.2. Internet Engineering Task Force (IETF) Contact . . . . 32
7.1.3. Internet Research Task Force (IRTF) Contact . . . . . 33
7.2. Internet Assigned Numbers Authority (IANA) Contact . . . 34
7.3. Request for Comments Editor Contact . . . . . . . . . . 35
7.4. Network Information Center Contact . . . . . . . . . . . 35
7.5. Sources for Requests for Comments . . . . . . . . . . . 36
8. Security Considerations . . . . . . . . . . . . . . . . . 36
9. Author's Address . . . . . . . . . . . . . . . . . . . . . 36Introduction 🌸
okay so the intro is basically a map 🗺️ First we talk about the standardization process and the RFC document series, then we explain the terms. Sections 6.2 - 6.10 hold the lists of protocols at each stage of standardization, and at the very end there are pointers to references and contacts if you want more info 💜
this memo is meant to come out about once a quarter, so make sure the copy you're reading is current 📅 You can get current copies from the Network Information Center (INTERNIC) or from the Internet Assigned Numbers Authority (IANA) (check the contact info at the end of this memo).
Do not use this edition after 31-May-94. 🚫
see Section 6.1 for recent changes 🆕 In the official lists in Sections 6.2 - 6.10, an asterisk (*) next to a protocol means it's new to this document, got moved from one protocol level to another, or differs from the previous edition of this document ⭐
1. The Standardization Process ✨
the Internet Architecture Board keeps this list of documents that define standards for the Internet protocol suite 📜 For the IAB's charter, check RFC-1358, and for how the IAB and its subsidiary groups are organized, check RFC-1160 🗂️ Those subsidiaries are the Internet Engineering Task Force (IETF) and the Internet Research Task Force (IRTF). Each of those groups has a steering group, called the IESG and IRSG respectively 🧑🤝🧑 The IETF works on these standards with the goal of coordinating how the Internet protocols evolve, and that coordination matters so much now that the protocols are increasingly in general commercial use 💼 The definitive description of the Internet standards process is in RFC-1310 📖
most of the Internet protocol development and standardization action happens in the working groups of the IETF 🛠️
protocols that are going to become Internet standards go through a series of states, or maturity levels (proposed standard, draft standard, and standard), with more scrutiny and testing at each one 🔍 When a protocol finishes this process, it gets a STD number (see RFC-1311) 🏅 At each step, the Internet Engineering Steering Group (IESG) of the IETF must make a recommendation for advancing the protocol 🫡
to give the Internet community time to think about and react to standardization proposals, there's a minimum delay of 6 months before a proposed standard can be advanced to a draft standard, and 4 months before a draft standard can be promoted to standard ⏳
it's general practice that no proposed standard gets promoted to draft standard without at least two independent implementations (and the recommendation of the IESG) 🛠️🛠️ Promotion from draft standard to standard generally requires operational experience and demonstrated interoperability of two or more implementations (and the recommendation of the IESG) 🤝
if it's unclear what the right decision is about a protocol, a special review committee may be appointed, made up of experts from the IETF, IRTF and the IAB, whose job is to recommend an explicit action 🕵️♀️
advancing a protocol to proposed standard is a big deal, because it marks the protocol as a candidate for eventual standardization (it puts the protocol "on the standards track") 🛤️ Advancing to draft standard is a major step that warns the community that, unless major objections are raised or flaws are discovered, the protocol is likely to be advanced to standard in six months 🚨
some protocols have been superseded by better ones or are otherwise unused. Those still get documented in this memo, marked "historic" 🕰️
because it's useful to document the results of early protocol research and development, some RFCs describe protocols that are still experimental. Those are designated "experimental" in this memo. They show up here as a convenience to the community, not as evidence of their standardization 🧪
other protocols, like ones developed by other standards organizations or by particular vendors, may be of interest or may be recommended for use on the Internet. Their specifications may be published as RFCs for the convenience of the community, and they're labeled "informational" in this memo 📘
protocol development and experimentation can also come from the research groups of the Internet Research Task Force, or from other individuals interested in Internet protocol development 🧠 Documenting that experimental work in the RFC series is encouraged, but none of it is considered to be on the track for standardization until the IESG has made a recommendation to advance the protocol to the proposed standard state 🚦
a few protocols have achieved widespread implementation without the approval of the IESG. For example, some vendor protocols have become very important to the Internet community even though they haven't been recommended by the IESG 😬 Still, the IAB strongly recommends using the standards process to evolve the protocol suite, to maximize interoperability and to prevent incompatible protocol requirements from arising 🤝 The terms "standard", "draft standard", and "proposed standard" are reserved, in any RFC or other publication of Internet protocols, for only those protocols the IESG has approved 🔒
in addition to a state (like "Proposed Standard"), a protocol is also assigned a status, or requirement level, in this document 🏷️ The possible requirement levels are "Required", "Recommended", "Elective", "Limited Use", and "Not Recommended", and they're defined in Section 4.2. When a protocol is on the standards track (that is, in the proposed standard, draft standard, or standard state, see Section 5), the status shown in Section 6 is the current status ✅
few protocols are required to be implemented in all systems, because there's such a variety of possible systems, like gateways, routers, terminal servers, workstations, and multi-user hosts 🖥️ The requirement level shown in this document is only a one word label, which may not be sufficient to characterize the implementation requirements for a protocol in all situations 🫠 For some protocols, this document contains an additional status paragraph (an applicability statement) 📝 In addition, more detailed status information may be contained in separate requirements documents (see Section 3) 📚
2. The Request for Comments Documents ✨
okay so RFCs are literally the working notes of the "Network Working Group," which is the Internet research and development community 🧚. An RFC can be about pretty much any computer communication topic, from a meeting report all the way up to a full spec for a standard 💅.
Notice: All standards are published as RFCs, but not all RFCs specify standards. 🫶
Anyone can submit a document for publication as an RFC 💖. Submissions must be made by electronic mail to the RFC Editor (see the contact information at the end of this memo, and see RFC 1543).
ngl RFCs aren't refereed publications, but they do get technical review from the task forces, individual technical experts, or the RFC Editor, as appropriate 🦋.
The RFC series is super varied, with everything from informational docs of general interest to specs for standard Internet protocols 🌈. When a submission is meant to document a proposed standard, draft standard, or standard protocol, the RFC Editor will only publish it with the approval of the IESG. For documents describing experimental work, the RFC Editor will notify the IESG before publication. That gives the IETF working group or IRTF research group a chance to review it, and the RFC Editor passes those comments along to the author. See Section 5.1 for more detail 🎀.
Once a document gets an RFC number and is published, that RFC is never revised or re-issued with the same number. So there's never a question about which version of a particular RFC is the newest 🙈. Still, a protocol (like File Transfer Protocol (FTP)) can get improved and re-documented many times across different RFCs, so it's important to check that you have the most recent RFC on a particular protocol 👑. This "Internet Official Protocol Standards" memo is where you look to find the correct RFC for the current specification of each protocol 💅.
The RFCs are available from the INTERNIC and a bunch of other sites. For more on getting RFCs, see Sections 7.4 and 7.5 🍓.
3. Other Reference Documents
There are three other reference documents you'll want to check when you're figuring out the current status of protocol specs and standardization 🧚. They are the Assigned Numbers, the Gateway Requirements, and the Host Requirements. These get revised at different times, so if they ever disagree, the most recent one must prevail 🔥.
Also, you should know about the MIL-STD publications on IP, TCP, Telnet, FTP, and SMTP. They're described in Section 3.4 ✨.
3.1. Assigned Numbers
The "Assigned Numbers" document lists the assigned values of the parameters used in the various protocols 🎀. Think IP protocol codes, TCP port numbers, Telnet Option Codes, ARP hardware types, and Terminal Type names. The most recent issue is RFC-1340 🦋.
3.2. Gateway Requirements
This document reviews the specs that apply to gateways and gives guidance and clarification wherever things are ambiguous 🌸. Gateway Requirements is RFC-1009, and an IETF working group is actively preparing a revision 💜.
3.3. Host Requirements
This pair of documents reviews and updates the specs that apply to hosts, and it gives guidance and clarification for any ambiguities 🫶. Host Requirements was issued as RFC-1122 and RFC-1123 ⭐.
3.4. The MIL-STD Documents
Okay, this is a fun one. The Internet community specs for IP (RFC-791) and TCP (RFC-793) and the DoD MIL-STD specs are meant to describe exactly the same protocols 🧚. If the protocols specified by these sets of documents ever differ, that should be reported to DISA and to the IESG 🚨. The RFCs and the MIL-STDs for IP and TCP differ in style and level of detail, so it's strongly advised that you use both sets together, along with RFC-1122 and RFC-1123 💅.
The Internet and DoD MIL-STD specs for FTP, SMTP, and Telnet are basically the same documents (RFCs 765, 821, 854) 🍓. The MIL-STD versions got edited slightly. Also, the current Internet spec for FTP is RFC-959, as modified by RFC-1123 🌈.
Honestly, these MIL-STDs are kinda out of date now 💀. The Gateway Requirements (RFC-1009) and Host Requirements (RFC-1122, RFC-1123) take precedence over both the earlier RFCs and the MIL-STDs 👑.
Internet Protocol (IP) MIL-STD-1777
Transmission Control Protocol (TCP) MIL-STD-1778
File Transfer Protocol (FTP) MIL-STD-1780
Simple Mail Transfer Protocol (SMTP) MIL-STD-1781
Telnet Protocol and Options (TELNET) MIL-STD-1782These documents are available from the Naval Publications and Forms Center. You can request them by phone, telegraph, or mail, but private industry is asked to use form DD1425 if possible 📬.
Naval Publications and Forms Center, Code 3015
5801 Tabor Ave
Philadelphia, PA 19120
Phone: 1-215-697-3321 (order tape)
1-215-697-4834 (conversation)4. Explanation of Terms ✨
There are two independent ways to categorize protocols 🦋. The first is the "maturity level," or STATE of standardization, which is one of "standard," "draft standard," "proposed standard," "experimental," "informational," or "historic" 🌸. The second is the "requirement level," or STATUS of the protocol, which is one of "required," "recommended," "elective," "limited use," or "not recommended" 💜.
The status or requirement level is hard to capture in a one-word label 🙈. These status labels should only be considered an indication, and you should consult a further description or applicability statement for the details 🫶.
When a protocol advances to proposed standard or draft standard, it gets labeled with a current status 🌈.
At any given time, a protocol sits in one cell of the matrix below. Protocols tend to land in cells in roughly the proportions shown by the relative number of Xs 📊. A new protocol is most likely to start in the (proposed standard, elective) cell, or the (experimental, not recommended) cell 🧚.
S T A T U S
Req Rec Ele Lim Not
+-----+-----+-----+-----+-----+
Std | X | XXX | XXX | | |
S +-----+-----+-----+-----+-----+
Draft | X | X | XXX | | |
T +-----+-----+-----+-----+-----+
Prop | | X | XXX | | |
A +-----+-----+-----+-----+-----+
Info | | | | | |
T +-----+-----+-----+-----+-----+
Expr | | | | XXX | |
E +-----+-----+-----+-----+-----+
Hist | | | | | XXX |
+-----+-----+-----+-----+-----+What is a "system"?
Some protocols are particular to hosts, some are particular to gateways, and a few are used in both 🖥️. The definitions below refer to a "system," which is either a host or a gateway (or both). The context of the particular protocol should make it clear which types of systems are intended 💖.
4.1. Definitions of Protocol State
Every protocol listed in this document is assigned to a "maturity level," or STATE of standardization: "standard," "draft standard," "proposed standard," "experimental," or "historic" 🎀.
4.1.1. Standard Protocol
The IESG has made this an official standard protocol for the Internet 👑. These protocols get STD numbers (see RFC-1311) and fall into two groups: (1) the IP protocol and above, which apply to the whole Internet, and (2) network-specific protocols, which are generally specs for how to do IP on particular types of networks ✨.
4.1.2. Draft Standard Protocol
The IESG is actively considering this protocol as a possible Standard Protocol 🔥. Substantial and widespread testing and comment are wanted 🦋. Comments and test results should be submitted to the IESG 💌. Changes may still be made to a Draft Standard Protocol before it becomes a Standard Protocol 🌸.
4.1.3. Proposed Standard Protocol
These are protocol proposals that the IESG may consider for standardization in the future 🌈. Implementation and testing by several groups is desirable, and revision of the protocol spec is likely 🧚.
4.1.4. Experimental Protocol
A system should not implement an experimental protocol unless it is participating in the experiment and has coordinated its use of the protocol with the protocol's developer 🙈.
Experimental protocols are typically the ones developed as part of an ongoing research project that isn't tied to an operational service offering 🧪. They might be proposed as a service protocol later on and move through proposed standard and draft standard before becoming a standard protocol 💜. Still, calling a protocol experimental can sometimes be a way of saying that, even if it's pretty mature, it isn't intended for operational use ⚠️.
4.1.5. Informational Protocol
Protocols developed by other standards organizations or by vendors, or protocols that are outside the purview of the IESG for other reasons, may be published as RFCs for the convenience of the Internet community 🎀. Those are informational protocols 💖.
4.1.6. Historic Protocol
These are protocols that are unlikely to ever become Internet standards, either because later developments have superseded them or because nobody's interested anymore 🥀.
4.2. Definitions of Protocol Status
This document lists a "requirement level," or STATUS, for each protocol 💅. The status is one of "required," "recommended," "elective," "limited use," or "not recommended" 🌈.
4.2.1. Required Protocol
A system must implement the required protocols 👑.
4.2.2. Recommended Protocol
A system should implement the recommended protocols 🫶.
4.2.3. Elective Protocol
A system may or may not implement an elective protocol 🦋. The general idea is that if you're going to do something like this, you must do exactly this 💅. There may be several elective protocols in one general area. For example, there are several electronic mail protocols and several routing protocols 📬.
4.2.4. Limited Use Protocol
These protocols are for use in limited circumstances 🔒. That might be because of their experimental state, specialized nature, limited functionality, or historic state 🌸.
4.2.5. Not Recommended Protocol
These protocols are not recommended for general use 🚫. That might be because of their limited functionality, specialized nature, or experimental or historic state 🙈.
5. The Standards Track 🚀
This section goes deeper into the procedures that the RFC Editor and the IESG use when they decide how protocols get labeled and published as standards 🎀.
5.1. The RFC Processing Decision Table 🎀
Okay so here's the current decision table the RFC Editor uses to process submissions 💅 It depends on two things: who sent it in, and what status they want it to have 👀
+==========================================================+
|**************| S O U R C E |
+==========================================================+
| Desired | IAB | IESG | IRSG | Other |
| Status | | | | |
+==========================================================+
| | | | | |
| Standard | Bogus | Publish | Bogus | Bogus |
| or | (2) | (1) | (2) | (2) |
| Draft | | | | |
| Standard | | | | |
+--------------+----------+----------+----------+----------+
| | | | | |
| | Refer | Publish | Refer | Refer |
| Proposed | (3) | (1) | (3) | (3) |
| Standard | | | | |
| | | | | |
+--------------+----------+----------+----------+----------+
| | | | | |
| | Notify | Publish | Notify | Notify |
| Experimental | (4) | (1) | (4) | (4) |
| Protocol | | | | |
| | | | | |
+--------------+----------+----------+----------+----------+
| | | | | |
| Information | Publish | Publish |Discretion|Discretion|
| or Opinion | (1) | (1) | (5) | (5) |
| Paper | | | | |
| | | | | |
+==========================================================+Here's what the footnotes mean, bestie 🫶
- (1) Publish.
- (2) Bogus 🙅 Let the source know what the rules are. RFCs specifying Standard or Draft Standard MUST come from the IESG, only.
- (3) Send it to an Area Director so a WG can review it. You'll only see the doc again once the IESG approves it 🌸
- (4) Notify both the IESG and the IRSG. If nobody raises concerns within two weeks, go with Discretion (5). If they do, the RFC Editor sorts it out or goes with Refer (3) 💜
- (5) RFC Editor's discretion. The RFC Editor decides whether a review is needed and, if so, who does it. The RFC Editor also decides whether to publish 👑
Obvi, in every case the RFC Editor can ask for or make minor tweaks for style, format, and presentation 💅
The IESG has picked the IESG Secretary as its go-between 🧚 for forwarding documents that already have IESG approval, and for logging the concerns raised in response to notifications (4) with the RFC Editor. Documents from Area Directors or Working Group Chairs MAY be handled the same way as documents from "other" ✨
5.2. The Standards Track Diagram 🦋
There's a part of the STATUS and STATE categorization called the standards track, and this is the vibe check on it 🔥 Only the changes of state actually matter for moving along the track, though the status assignments MAY change as well.
Single line boxes are temporary states, and double line boxes are long term states. A protocol will normally stay in a temporary state for several months (minimum six months for proposed standard, minimum four months for draft standard). A protocol MAY be in a long term state for many years 🌈
A protocol MAY enter the standards track only on the recommendation of the IESG, and MAY move from one state to another along the track only on the recommendation of the IESG. So the IESG has to take action to either start a protocol on the track or move it along 👑
Generally, when a protocol enters the standards track, a decision gets made about its eventual STATUS and its requirement level or applicability (elective, RECOMMENDED, or REQUIRED). It can get a slightly less strict current status for now, and then it lands in the proposed standard STATE with that status. So the first stop is always state 1. The STATUS decision MAY be revisited at any time 💖
|
+<----------------------------------------------+
| ^
V 0 | 4
+-----------+ +===========+
| enter |-->----------------+-------------->|experiment |
+-----------+ | +=====+=====+
| |
V 1 |
+-----------+ V
| proposed |-------------->+
+--->+-----+-----+ |
| | |
| V 2 |
+<---+-----+-----+ V
| draft std |-------------->+
+--->+-----+-----+ |
| | |
| V 3 |
+<---+=====+=====+ V
| standard |-------------->+
+=====+=====+ |
|
V 5
+=====+=====+
| historic |
+===========+Moving from proposed standard (1) to draft standard (2) can only happen through action by the IESG, and only after the protocol has been a proposed standard (1) for at least six months 📅
Moving from draft standard (2) to standard (3) can only happen through action by the IESG, and only after the protocol has been a draft standard (2) for at least four months 📅
Sometimes the call is that a protocol isn't ready for standardization yet, so it gets assigned to the experimental state (4). That's off the standards track, but the protocol MAY be resubmitted to enter the standards track after more work 🧪 There are other paths into the experimental and historic states that don't involve any IESG action 🙈
Sometimes one protocol gets replaced by another and becomes historic. Or a protocol on the standards track gets kind of overtaken by another protocol (or other events) and becomes historic (state 5). Either way, it MAY happen that the protocol is retired 🥀
6. The Protocols ✨
Subsection 6.1 is the "what's new" tea 🍵 It lists recent RFCs and other changes. Subsections 6.2 - 6.10 group the standards by protocol state 🎀
6.1. Recent Changes 🌸
6.1.1. New RFCs ✨
okay bestie, here's the new arrivals list 💖 some numbers are still empty, lol 🙈
- 1600 - This memo. 🎀
- 1595 - Definitions of Managed Objects for the SONET/SDH Interface Type
- A Proposed Standard protocol. 🦋
- 1594 - FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions
- This is an information document and does not specify any level of standard. 🫶
- 1593 - SNA APPN Node MIB
- This is an information document and does not specify any level of standard. 🫶
- 1592 - Simple Network Management Protocol Distributed Protocol Interface Version 2.0
- An Experimental protocol. 🧪
- 1591 - Domain Name System Structure and Delegation
- This is an information document and does not specify any level of standard. 🫶
- 1590 - Media Type Registration Procedure
- This is an information document and does not specify any level of standard. 🫶
- 1589 - A Kernel Model for Precision Timekeeping
- This is an information document and does not specify any level of standard. 🫶
- 1588 - White Pages Meeting Report
- This is an information document and does not specify any level of standard. 🫶
- 1587 - Not yet issued. 🙈
- 1586 - Not yet issued. 🙈
- 1585 - Not yet issued. 🙈
- 1584 - not yet issued. 🙈
- 1583 - Not yet issued. 🙈
- 1582 - Extensions to RIP to Support Demand Circuits
- A Proposed Standard protocol. 🦋
- 1581 - Protocol Analysis for Extensions to RIP to Support Demand Circuits
- This is an information document and does not specify any level of standard. 🫶
- 1580 - Not yet issued. 🙈
- 1579 - Firewall-Friendly FTP
- This is an information document and does not specify any level of standard. 🫶
- 1578 - FYI on Questions and Answers - Answers to Commonly Asked "Primary and Secondary School Internet User" Questions
- This is an information document and does not specify any level of standard. 🫶
- 1577 - Classical IP and ARP over ATM
- A Proposed Standard protocol. 🦋
- 1576 - TN3270 Current Practices
- This is an information document and does not specify any level of standard. 🫶
- 1575 - An Echo Function for CLNP (ISO 8473)
- A Draft Standard protocol. 🔥
- 1574 - Essential Tools for the OSI Internet
- This is an information document and does not specify any level of standard. 🫶
- 1573 - Evolution of the Interfaces Group of MIB-II
- A Proposed Standard protocol. 🦋
- 1572 - Telnet Environment Option
- A Proposed Standard protocol. 🦋
- 1571 - Telnet Environment Option Interoperability Issues
- This is an information document and does not specify any level of standard. 🫶
- 1570 - PPP LCP Extensions
- A Proposed Standard protocol. 🦋
- 1569 - Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures
- This is an information document and does not specify any level of standard. 🫶
- 1568 - Simple Network Paging Protocol - Version 1(b)
- This is an information document and does not specify any level of standard. 🫶
- 1567 - X.500 Directory Monitoring MIB
- A Proposed Standard protocol. 🦋
- 1566 - Mail Monitoring MIB
- A Proposed Standard protocol. 🦋
- 1565 - Network Services Monitoring MIB
- A Proposed Standard protocol. 🦋
- 1564 - DSA Metrics (OSI-DS 34 (v3))
- This is an information document and does not specify any level of standard. 🫶
- 1563 - The text/enriched MIME Content-type
- This is an information document and does not specify any level of standard. 🫶
- 1562 - Naming Guidelines for the AARNet X.500 Directory Service
- This is an information document and does not specify any level of standard. 🫶
- 1561 - Use of ISO CLNP in TUBA Environments
- An Experimental protocol. 🧪
- 1560 - The MultiProtocol Internet
- This is an information document and does not specify any level of standard. 🫶
- 1559 - DECnet Phase IV MIB Extensions
- A Draft Standard protocol. 🔥
- 1558 - A String Representation of LDAP Search Filters
- This is an information document and does not specify any level of standard. 🫶
- 1557 - Korean Character Encoding for Internet Messages
- This is an information document and does not specify any level of standard. 🫶
- 1556 - Handling of Bi-directional Texts in MIME
- This is an information document and does not specify any level of standard. 🫶
- 1555 - Hebrew Character Encoding for Internet Messages
- This is an information document and does not specify any level of standard. 🫶
- 1554 - ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP
- This is an information document and does not specify any level of standard. 🫶
- 1553 - Compressing IPX Headers Over WAM Media (CIPX)
- A Proposed Standard protocol. 🦋
- 1552 - The PPP Internetworking Packet Exchange Control Protocol (IPXCP)
- A Proposed Standard protocol. 🦋
- 1551 - Novell IPX Over Various WAN Media (IPXWAN)
- This is an information document and does not specify any level of standard. 🫶
- 1550 - IP: Next Generation (IPng) White Paper Solicitation
- This is an information document and does not specify any level of standard. 🫶
- 1549 - PPP in HDLC Framing
- A Draft Standard protocol. 🔥
- 1548 - The Point-to-Point Protocol (PPP)
- A Draft Standard protocol. 🔥
- 1547 - Requirements for an Internet Standard Point-to-Point Protocol
- This is an information document and does not specify any level of standard. 🫶
- 1546 - Host Anycasting Service
- This is an information document and does not specify any level of standard. 🫶
- 1545 - FTP Operation Over Big Address Records (FOOBAR)
- An Experimental protocol. 🧪
- 1544 - The Content-MD5 Header Field
- A Proposed Standard protocol. 🦋
- 1543 - Instructions to RFC Authors
- This is an information document and does not specify any level of standard. 🫶
- 1542 - Clarifications and Extensions for the Bootstrap Protocol
- A Proposed Standard protocol. 🦋
- 1541 - Dynamic Host Configuration Protocol
- A Proposed Standard protocol. 🦋
6.1.2. Other Changes 🌸
these ones are changes to protocols that were already in the previous edition, so you can compare the old and new 👀
- 1356 - Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode
- Moved to Draft Standard. 🔥
- 1408 - Telnet Environment Option
- Moved to Historic. 🫠
6.2. Standard Protocols 👑
the big table of standard protocols is next, and it's giving very important energy 💅
Protocol Name Status RFC STD *
======== ===================================== ======== ==== === =
-------- Internet Official Protocol Standards Req 1600 1
-------- Assigned Numbers Req 1340 2
-------- Host Requirements - Communications Req 1122 3
-------- Host Requirements - Applications Req 1123 3
-------- Gateway Requirements Req 1009 4
IP Internet Protocol Req 791 5
as amended by:--------
-------- IP Subnet Extension Req 950 5
-------- IP Broadcast Datagrams Req 919 5
-------- IP Broadcast Datagrams with Subnets Req 922 5
ICMP Internet Control Message Protocol Req 792 5
IGMP Internet Group Multicast Protocol Rec 1112 5
UDP User Datagram Protocol Rec 768 6
TCP Transmission Control Protocol Rec 793 7
TELNET Telnet Protocol Rec 854,855 8
FTP File Transfer Protocol Rec 959 9
SMTP Simple Mail Transfer Protocol Rec 821 10
MAIL Format of Electronic Mail Messages Rec 822 11
CONTENT Content Type Header Field Rec 1049 11
NTPV2 Network Time Protocol (Version 2) Rec 1119 12
DOMAIN Domain Name System Rec 1034,1035 13
DNS-MX Mail Routing and the Domain System Rec 974 14
SNMP Simple Network Management Protocol Rec 1157 15
SMI Structure of Management Information Rec 1155 16
Concise-MIB Concise MIB Definitions Rec 1212 16
MIB-II Management Information Base-II Rec 1213 17
EGP Exterior Gateway Protocol Rec 904 18
NETBIOS NetBIOS Service Protocols Ele 1001,1002 19
ECHO Echo Protocol Rec 862 20
DISCARD Discard Protocol Ele 863 21
CHARGEN Character Generator Protocol Ele 864 22
QUOTE Quote of the Day Protocol Ele 865 23
USERS Active Users Protocol Ele 866 24
DAYTIME Daytime Protocol Ele 867 25
TIME Time Server Protocol Ele 868 26
TFTP Trivial File Transfer Protocol Ele 1350 33
RIP Routing Information Protocol Ele 1058 34
TP-TCP ISO Transport Service on top of the TCP Ele 1006 35[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] 🍓
Applicability Statements: okay so, IGMP first 🦋 The Internet Architecture Board is trying to move toward general adoption of IP multicasting, bc it's a more efficient move than broadcasting for lots of apps ✨ The host interface got standardized in RFC-1112, but multicast-routing gateways are still experimental and not widely available, so not everything is ready yet 💀 An Internet host SHOULD support all of RFC-1112, except the IGMP protocol itself, which is OPTIONAL (see RFC-1122 for more details) 🫶 Even without IGMP, implementing RFC-1112 is still a huge win, because you get IP-layer access to local network multicast addressing 🌸 It's expected that IGMP will become RECOMMENDED for all hosts and gateways at some future date 👑
SMI, MIB-II SNMP 🧚 The IAB recommends that all IP and TCP implementations be network manageable. Right now that means implementing the Internet MIB-II (RFC-1213) and at least the RECOMMENDED management protocol SNMP (RFC-1157) 💜
RIP 🍓 The Routing Information Protocol is widely implemented and used across the Internet, but ngl, implementors and users both SHOULD be aware that it has some serious technical limitations as a routing protocol 😭 The IETF is currently developing several candidates for a new standard "open" routing protocol with better properties than RIP ✨ The IAB urges the Internet community to track these developments and to implement the new protocol when it is standardized, bc improved Internet service will result for many users 🌈
TP-TCP 🎀 As OSI protocols get more widely implemented and used, there's gonna be an increasing need to support interoperation with the TCP/IP protocols. The IETF is formulating strategies for interoperation. RFC-1006 provides one interoperation mode, where TCP/IP is used to emulate TP0 in order to support OSI applications. Hosts that wish to run OSI connection-oriented applications in this mode SHOULD use the procedure described in RFC-1006 💅 In the future, the IAB expects that a major portion of the Internet will support both TCP/IP and OSI (inter-)network protocols in parallel, and then it'll be possible to run OSI applications across the Internet using full OSI protocol "stacks" 🔥
6.3. Network-Specific Standard Protocols ✨
All Network-Specific Standards have Elective status 🎀
Protocol Name State RFC STD *
======== ===================================== ===== ===== === =
IP-ATM Classical IP and ARP over ATM Prop 1577 *
IP-FR Multiprotocol over Frame Relay Draft 1490
ATM-ENCAP Multiprotocol Encapsulation over ATM Prop 1483
IP-TR-MC IP Multicast over Token-Ring LANs Prop 1469
IP-FDDI Transmission of IP and ARP over FDDI Net Std 1390 36
IP-HIPPI IP and ARP on HIPPI Prop 1374
IP-X.25 X.25 and ISDN in the Packet Mode Draft 1356 *
IP-SMDS IP Datagrams over the SMDS Service Prop 1209
IP-FDDI Internet Protocol on FDDI Networks Draft 1188
ARP Address Resolution Protocol Std 826 37
RARP A Reverse Address Resolution Protocol Std 903 38
IP-ARPA Internet Protocol on ARPANET Std BBN1822 39
IP-WB Internet Protocol on Wideband Network Std 907 40
IP-E Internet Protocol on Ethernet Networks Std 894 41
IP-EE Internet Protocol on Exp. Ethernet Nets Std 895 42
IP-IEEE Internet Protocol on IEEE 802 Std 1042 43
IP-DC Internet Protocol on DC Networks Std 891 44
IP-HC Internet Protocol on Hyperchannel Std 1044 45
IP-ARC Transmitting IP Traffic over ARCNET Nets Std 1201 46
IP-SLIP Transmission of IP over Serial Lines Std 1055 47
IP-NETBIOS Transmission of IP over NETBIOS Std 1088 48
IP-IPX Transmission of 802.2 over IPX Networks Std 1132 49[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.]
Applicability Statements: okay so, a system is expected to support one or more physical networks, and for each physical network it supports, the appropriate protocols from the above list MUST be supported 💅 That means supporting any particular type of physical network is elective, but for the physical networks you actually support, they are REQUIRED to be supported exactly according to the protocols in the above list 🫶 See also the Host and Gateway Requirements RFCs for more specific information on network-specific ("link layer") protocols 💜
6.4. Draft Standard Protocols 🌸
Protocol Name Status RFC
======== ===================================== ============== =====
ISO-TS-ECHO Echo for ISO-8473 Elective 1575*
DECNET-MIB DECNET MIB Elective 1559*
PPP_HDLC PPP in HDLC Framing Elective 1549*
PPP Point-to-Point Protocol (PPP) Elective 1548*
------- Message Header Ext. of Non-ASCII Text Elective 1522
MIME Multipurpose Internet Mail Extensions Elective 1521
802.3-MIB IEEE 802.3 Repeater MIB Elective 1516
BRIDGE-MIB BRIDGE-MIB Elective 1493
ETHER-MIB Ethernet MIB Elective 1398
NTPV3 Network Time Protocol (Version 3) Elective 1305
IP-MTU Path MTU Discovery Elective 1191
FINGER Finger Protocol Elective 1288
BGP3 Border Gateway Protocol 3 (BGP-3) Elective 1267,1268
OSPF2 Open Shortest Path First Routing V2 Elective 1247
POP3 Post Office Protocol, Version 3 Elective 1460
BOOTP Bootstrap Protocol Recommended 951,1497
NICNAME WhoIs Protocol Elective 954[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.]
Applicability Statements: PPP 🦋 Point to Point Protocol is a method of sending IP over serial lines, which are a type of physical network. It's anticipated that PPP will be advanced to the network-specifics standard protocol state in the future 🌟
6.5. Proposed Standard Protocols 💖
Okay so this is the Proposed Standard lineup, and every single one is sitting at Elective status 🧚 Main character energy for sure. The table is in a code block so nothing gets scrambled.
Protocol Name Status RFC
======== ===================================== ============== =====
SONET-MIB MIB SONET/SDH Interface Type Elective 1595*
RIP-DC Extensions to RIP to Support Demand Cir. Elective 1582*
-------- Evolution of the Interfaces Group of MIB-II Elective 1573*
PPP-LCP PPP LCP Extensions Elective 1570*
X500-MIB X.500 Directory Monitoring MIB Elective 1567*
MAIL-MIB Mail Monitoring MIB Elective 1566*
NSM-MIB Network Services Monitoring MIB Elective 1565*
CIPX Compressing IPX Headers Over WAM Media Elective 1553*
IPXCP PPP Internetworking Packet Exchange Control Elective 1552*
CON-MD5 Content-MD5 Header Field Elective 1544*
DHCP-BOOTP Interoperation Between DHCP and BOOTP Elective 1534
DHCP-BOOTP DHCP Options and BOOTP Vendor Extensions Elective 1533
BOOTP Clarifications and Extensions BOOTP Elective 1532
DHCP Dynamic Host Configuration Protocol Elective 1531
SRB-MIB Source Routing Bridge MIB Elective 1525
CIDR-STRA CIDR Address Assignment... Elective 1519
CIDR-ARCH CIDR Architecture... Elective 1518
CIDR-APP CIDR Applicability Statement Elective 1517
-------- 802.3 MAU MIB Elective 1515
HOST-MIB Host Resources MIB Elective 1514
-------- Token Ring Extensions to RMON MIB Elective 1513
FDDI-MIB FDDI Management Information Base Elective 1512
KERBEROS Kerberos Network Authentication Ser (V5) Elective 1510
GSSAPI Generic Security Service API: C-bindings Elective 1509
GSSAPI Generic Security Service Application... Elective 1508
DASS Distributed Authentication Security... Elective 1507
-------- X.400 Use of Extended Character Sets Elective 1502
HARPOON Rules for Downgrading Messages... Elective 1496
Mapping MHS/RFC-822 Message Body Mapping Elective 1495
Equiv X.400/MIME Body Equivalences Elective 1494
X.500syn X.500 String Representation ... Elective 1488
X.500lite X.500 Lightweight ... Elective 1487
STR-REP String Representation ... Elective 1485
OSI-Dir OSI User Friendly Naming ... Elective 1484
IDPR Inter-Domain Policy Routing Protocol Elective 1479
IDPR-ARCH Architecture for IDPR Elective 1478
PPP/Bridge MIB Bridge PPP MIB Elective 1474
PPP/IP MIB IP Network Control Protocol of PPP MIB Elective 1473
PPP/SEC MIB Security Protocols of PPP MIB Elective 1472
PPP/LCP MIB Link Control Protocol of PPP MIB Elective 1471
X25-MIB Multiprotocol Interconnect on X.25 MIB Elective 1461
SNMPv2 Coexistence between SNMPv1 and SNMPv2 Elective 1452
SNMPv2 Manager-to-Manager MIB Elective 1451
SNMPv2 Management Information Base for SNMPv2 Elective 1450
SNMPv2 Transport Mappings for SNMPv2 Elective 1449
SNMPv2 Protocol Operations for SNMPv2 Elective 1448
SNMPv2 Party MIB for SNMPv2 Elective 1447
SNMPv2 Security Protocols for SNMPv2 Elective 1446
SNMPv2 Administrative Model for SNMPv2 Elective 1445
SNMPv2 Conformance Statements for SNMPv2 Elective 1444
SNMPv2 Textual Conventions for SNMPv2 Elective 1443
SNMPv2 SMI for SNMPv2 Elective 1442
SNMPv2 Introduction to SNMPv2 Elective 1441
SMTP-SIZE SMTP Service Ext for Message Size Elective 1427
SMTP-8BIT SMTP Service Ext or 8bit-MIMEtransport Elective 1426
SMTP-EXT SMTP Service Extensions Elective 1425
PEM-KEY PEM - Key Certification Elective 1424
PEM-ALG PEM - Algorithms, Modes, and Identifiers Elective 1423
PEM-CKM PEM - Certificate-Based Key Management Elective 1422
PEM-ENC PEM - Message Encryption and Auth Elective 1421
SNMP-IPX SNMP over IPX Elective 1420
SNMP-AT SNMP over AppleTalk Elective 1419
SNMP-OSI SNMP over OSI Elective 1418
FTP-FTAM FTP-FTAM Gateway Specification Elective 1415
IDENT-MIB Identification MIB Elective 1414
IDENT Identification Protocol Elective 1413
DS3/E3-MIB DS3/E3 Interface Type Elective 1407
DS1/E1-MIB DS1/E1 Interface Type Elective 1406
BGP-OSPF BGP OSPF Interaction Elective 1403
-------- Route Advertisement In BGP2 And BGP3 Elective 1397
RIP2-MIB RIP Version 2 MIB Extension Elective 1389
RIP2 RIP Version 2-Carrying Additional Info. Elective 1388
SNMP-X.25 SNMP MIB Extension for X.25 Packet Layer Elective 1382
SNMP-LAPB SNMP MIB Extension for X.25 LAPB Elective 1381
PPP-ATCP PPP AppleTalk Control Protocol Elective 1378
PPP-OSINLCP PPP OSI Network Layer Control Protocol Elective 1377
PPP-DNCP PPP DECnet Phase IV Control Protocol Elective 1376
TABLE-MIB IP Forwarding Table MIB Elective 1354
SNMP-PARTY-MIB Administration of SNMP Elective 1353
SNMP-SEC SNMP Security Protocols Elective 1352
SNMP-ADMIN SNMP Administrative Model Elective 1351
TOS Type of Service in the Internet Elective 1349
PPP-AUTH PPP Authentication Elective 1334
PPP-LINK PPP Link Quality Monitoring Elective 1333
PPP-IPCP PPP Control Protocol Elective 1332
------- X.400 1988 to 1984 downgrading Elective 1328
------- Mapping between X.400(1988) Elective 1327
TCP-EXT TCP Extensions for High Performance Elective 1323
------- Def. Man. Objs Parallel-printer-like Elective 1318
------- Def. Man Objs RS-232-like Elective 1317
------- Def. Man. Objs. Character Stream Elective 1316
FRAME-MIB Management Information Base for Frame Elective 1315
NETFAX File Format for the Exchange of Images Elective 1314
SIP-MIB SIP Interface Type MIB Elective 1304
IARP Inverse Address Resolution Protocol Elective 1293
FDDI-MIB FDDI-MIB Elective 1285
------- Encoding Network Addresses Elective 1277
------- Replication and Distributed Operations Elective 1276
------- COSINE and Internet X.500 Schema Elective 1274
RMON-MIB Remote Network Monitoring MIB Elective 1271
BGP-MIB Border Gateway Protocol MIB (Version 3) Elective 1269
ICMP-ROUT ICMP Router Discovery Messages Elective 1256
OSPF-MIB OSPF Version 2 MIB Elective 1253
IPSO DoD Security Options for IP Elective 1108
AT-MIB Appletalk MIB Elective 1243
OSI-UDP OSI TS on UDP Elective 1240
STD-MIBs Reassignment of Exp MIBs to Std MIBs Elective 1239
OSI-NSAP Guidelines for OSI NSAP Allocation Elective 1237
IPX-IP Tunneling IPX Traffic through IP Nets Elective 1234
802.5-MIB IEEE 802.5 Token Ring MIB Elective 1231
GINT-MIB Extensions to the Generic-Interface MIB Elective 1229
PPP-EXT PPP Extensions for Bridging Elective 1220
IS-IS OSI IS-IS for TCP/IP Dual Environments Elective 1195
IP-CMPRS Compressing TCP/IP Headers Elective 1144
NNTP Network News Transfer Protocol Elective 977[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.]
Applicability Statements: 🦋
OSPF - RFC 1370 is an applicability statement for OSPF.
6.6. Telnet Options 🌸
Okay so for convenience, every Telnet Option is collected right here, with both their state and their status. Scroll and slay 💅
Protocol Name Number State Status RFC STD
======== ===================================== ===== ====== ==== ===
TOPT-BIN Binary Transmission 0 Std Rec 856 27
TOPT-ECHO Echo 1 Std Rec 857 28
TOPT-RECN Reconnection 2 Prop Ele ...
TOPT-SUPP Suppress Go Ahead 3 Std Rec 858 29
TOPT-APRX Approx Message Size Negotiation 4 Prop Ele ...
TOPT-STAT Status 5 Std Rec 859 30
TOPT-TIM Timing Mark 6 Std Rec 860 31
TOPT-REM Remote Controlled Trans and Echo 7 Prop Ele 726
TOPT-OLW Output Line Width 8 Prop Ele ...
TOPT-OPS Output Page Size 9 Prop Ele ...
TOPT-OCRD Output Carriage-Return Disposition 10 Prop Ele 652
TOPT-OHT Output Horizontal Tabstops 11 Prop Ele 653
TOPT-OHTD Output Horizontal Tab Disposition 12 Prop Ele 654
TOPT-OFD Output Formfeed Disposition 13 Prop Ele 655
TOPT-OVT Output Vertical Tabstops 14 Prop Ele 656
TOPT-OVTD Output Vertical Tab Disposition 15 Prop Ele 657
TOPT-OLD Output Linefeed Disposition 16 Prop Ele 658
TOPT-EXT Extended ASCII 17 Prop Ele 698
TOPT-LOGO Logout 18 Prop Ele 727
TOPT-BYTE Byte Macro 19 Prop Ele 735
TOPT-DATA Data Entry Terminal 20 Prop Ele 1043
TOPT-SUP SUPDUP 21 Prop Ele 736
TOPT-SUPO SUPDUP Output 22 Prop Ele 749
TOPT-SNDL Send Location 23 Prop Ele 779
TOPT-TERM Terminal Type 24 Prop Ele 1091
TOPT-EOR End of Record 25 Prop Ele 885
TOPT-TACACS TACACS User Identification 26 Prop Ele 927
TOPT-OM Output Marking 27 Prop Ele 933
TOPT-TLN Terminal Location Number 28 Prop Ele 946
TOPT-3270 Telnet 3270 Regime 29 Prop Ele 1041
TOPT-X.3 X.3 PAD 30 Prop Ele 1053
TOPT-NAWS Negotiate About Window Size 31 Prop Ele 1073
TOPT-TS Terminal Speed 32 Prop Ele 1079
TOPT-RFC Remote Flow Control 33 Prop Ele 1372
TOPT-LINE Linemode 34 Draft Ele 1184
TOPT-XDL X Display Location 35 Prop Ele 1096
TOPT-ENVIR Telnet Environment Option 36 Hist Not 1408 *
TOPT-AUTH Telnet Authentication Option 37 Exp Ele 1416
TOPT-ENVIR Telnet Environment Option 39 Prop Ele 1572 *
TOPT-EXTOP Extended-Options-List 255 Std Rec 861 32[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.]
6.7. Experimental Protocols ✨
All Experimental protocols have the Limited Use status 🧪✨ So these are the ones still in the lab, bestie, and they're not ready for the main stage yet 💅
Protocol Name RFC
======== ===================================== =====
SNMP-DPI SNMP Distributed Protocol Interface 1592*
CLNP-TUBA Use of ISO CLNP in TUBA Environments 1561*
FOOBAR FTP Operation Over Big Address Records 1545*
REM-PRINT TPC.INT Subdomain Remote Printing - Technical 1528
EHF-MAIL Encoding Header Field for Internet Messages 1505
REM-PRT An Experiment in Remote Printing 1486
RAP Internet Route Access Protocol 1476
TP/IX TP/IX: The Next Internet 1475
X400 Routing Coordination for X.400 Services 1465
DNS Storing Arbitrary Attributes in DNS 1464
IRCP Internet Relay Chat Protocol 1459
TOS-LS Link Security TOS 1455
SIFT/UFT Sender-Initiated/Unsolicited File Transfer 1440
DIR-ARP Directed ARP 1433
TEL-SPX Telnet Authentication: SPX 1412
TEL-KER Telnet Authentication: Kerberos V4 1411
MAP-MAIL X.400 Mapping and Mail-11 1405
TRACE-IP Traceroute Using an IP Option 1393
DNS-IP Experiment in DNS Based IP Routing 1383
DNS NSAP DNS NSAP RRs 1348
RMCP Remote Mail Checking Protocol 1339
TCP-HIPER TCP Extensions for High Performance 1323
MSP2 Message Send Protocol 2 1312
DSLCP Dynamically Switched Link Control 1307
-------- X.500 and Domains 1279
IN-ENCAP Internet Encapsulation Protocol 1241
CLNS-MIB CLNS-MIB 1238
CFDP Coherent File Distribution Protocol 1235
SNMP-DPI SNMP Distributed Program Interface 1228
IP-AX.25 IP Encapsulation of AX.25 Frames 1226
ALERTS Managing Asynchronously Generated Alerts 1224
MPP Message Posting Protocol 1204
ST-II Stream Protocol 1190
SNMP-BULK Bulk Table Retrieval with the SNMP 1187
DNS-RR New DNS RR Definitions 1183
IMAP2 Interactive Mail Access Protocol 1176
NTP-OSI NTP over OSI Remote Operations 1165
DMF-MAIL Digest Message Format for Mail 1153
RDP Reliable Data Protocol 908,1151
TCP-ACO TCP Alternate Checksum Option 1146
-------- Mapping full 822 to Restricted 822 1137
IP-DVMRP IP Distance Vector Multicast Routing 1075
VMTP Versatile Message Transaction Protocol 1045
COOKIE-JAR Authentication Scheme 1004
NETBLT Bulk Data Transfer Protocol 998
IRTP Internet Reliable Transaction Protocol 938
LDP Loader Debugger Protocol 909
RLP Resource Location Protocol 887
NVP-II Network Voice Protocol ISI-memo
PVP Packet Video Protocol ISI-memo[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] 🫶
6.8. Informational Protocols 🧚
Information protocols have no status 🤷♀️ They're just out here existing, which is honestly a vibe too 🌸
Protocol Name RFC
======= ==================================== =====
SNPP Simple Network Paging Protocol - Version 1(b) 1568*
IPXWAN Novell IPX Over Various WAN Media 1551*
ADSNA-IP Advanced SNA/IP: A Simple SNA Transport Protocol 1538
AUBR Appletalk Update-Based Routing Protocol... 1504
TACACS Terminal Access Control Protocol 1492
SUN-NFS Network File System Protocol 1094
SUN-RPC Remote Procedure Call Protocol Version 2 1057
GOPHER The Internet Gopher Protocol 1436
------- Data Link Switching: Switch-to-Switch Protocol 1434
LISTSERV Listserv Distribute Protocol 1429
------- Replication Requirements 1275
PCMAIL Pcmail Transport Protocol 1056
MTP Multicast Transport Protocol 1301
BSD Login BSD Login 1282
DIXIE DIXIE Protocol Specification 1249
IP-X.121 IP to X.121 Address Mapping for DDN 1236
OSI-HYPER OSI and LLC1 on HYPERchannel 1223
HAP2 Host Access Protocol 1221
SUBNETASGN On the Assignment of Subnet Numbers 1219
SNMP-TRAPS Defining Traps for use with SNMP 1215
DAS Directory Assistance Service 1202
MD4 MD4 Message Digest Algorithm 1186
LPDP Line Printer Daemon Protocol 1179[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] 🎀
6.9. Historic Protocols 🕰️
All Historic protocols have Not Recommended status 💀 They're retired, bestie, so please don't go building new stuff on them 🙈
Protocol Name RFC
======= ===================================== =====
SNMP-MUX SNMP MUX Protocol and MIB 1227
OIM-MIB-II OSI Internet Management: MIB-II 1214
IMAP3 Interactive Mail Access Protocol Version 3 1203
SUN-RPC Remote Procedure Call Protocol Version 1 1050
802.4-MIP IEEE 802.4 Token Bus MIB 1230
CMOT Common Management Information Services 1189
-------- Mail Privacy: Procedures 1113
-------- Mail Privacy: Key Management 1114
-------- Mail Privacy: Algorithms 1115
NFILE A File Access Protocol 1037
HOSTNAME HOSTNAME Protocol 953
SFTP Simple File Transfer Protocol 913
SUPDUP SUPDUP Protocol 734
BGP Border Gateway Protocol 1163,1164
MIB-I MIB-I 1156
SGMP Simple Gateway Monitoring Protocol 1028
HEMS High Level Entity Management Protocol 1021
STATSRV Statistics Server 996
POP2 Post Office Protocol, Version 2 937
RATP Reliable Asynchronous Transfer Protocol 916
HFEP Host - Front End Protocol 929
THINWIRE Thinwire Protocol 914
HMP Host Monitoring Protocol 869
GGP Gateway Gateway Protocol 823
RTELNET Remote Telnet Service 818
CLOCK DCNET Time Server Protocol 778
MPM Internet Message Protocol 759
NETRJS Remote Job Service 740
NETED Network Standard Text Editor 569
RJE Remote Job Entry 407
XNET Cross Net Debugger IEN-158
NAMESERVER Host Name Server Protocol IEN-116
MUX Multiplexing Protocol IEN-90
GRAPHICS Graphics Protocol NIC-24308[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] 🌈
6.10. Obsolete Protocols 🔄
Okay so some of the protocols in this memo are described in RFCs that have been obsoleted by newer RFCs 📜 "Obsolete" or "obsoleted" is not an official state or status of protocols, so this subsection is just here for information 💖
Obviously it might look wrong to have an obsoleted RFC sitting in the list of standards, but sometimes an older standard is in the middle of being replaced, and that process may take a year or two ⏳
For example, the Network Time Protocol (NTP) [RFC 1119] is a full Standard in its version 2, and in its version 3 it's a Draft Standard [RFC 1305]. Once version 3 is a full Standard, version 2 will be made Historic 🕰️
Plenty of obsoleted protocols are of little interest, so they get dropped from this memo altogether 🗑️ But some have gotten enough recognition that it makes sense to list them under their current status, along with a reference to their current replacement 🔥
RFC RFC Status Title *
==== ==== ========= =================================== =
1305 obsoletes 1119 Std /Rec Network Time Protocol (Version 2) *
1533 obsoletes 1497 Draft/Rec Bootstrap Protocol *
1331 obsoletes 1171 Draft/Ele Point to Point Protocol *
1574 obsoletes 1139 Prop /Ele Echo for ISO-8473 *
1573 obsoletes 1229 Prop /Ele Extensions to the Generic-IF MIB *
1559 obsoletes 1289 Prop /Ele DECNET MIB *
1548 obsoletes 1331 Prop /Ele Point-to-Point Protocol (PPP) *
1541 obsoletes 1531 Prop /Ele Dynamic Host Configuration Protocol *
1592 obsoletes 1228 Exper/Lim SNMP Distributed Program Interface *
1528 obsoletes 1486 Exper/Lim An Experiment in Remote Printing *
1320 obsoletes 1186 Info / MD4 Message Digest Algorithm *
1057 obsoletes 1050 Hist /Not Remote Procedure Call Version 1 *
1421 obsoletes 1113 Hist /Not Mail Privacy: Procedures *
1422 obsoletes 1114 Hist /Not Mail Privacy: Key Management *
1423 obsoletes 1115 Hist /Not Mail Privacy: Algorithms *
1267 obsoletes 1163 Hist /Not Border Gateway Protocol *
1268 obsoletes 1164 Hist /Not Border Gateway Protocol *Big thanks to Lynn Wheeler of Britton Lee for compiling the information in this subsection 🫶
[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] ✨
7. Contacts 💖
7.1. IAB, IETF, and IRTF Contacts 📬
okay so this is where you get the actual humans 🫶
7.1.1. Internet Architecture Board (IAB) Contact
bestie, if you have comments about this list of protocols (and especially about the Draft Standard Protocols 👀), send them to the Internet Architecture Board, care of Bob Braden, IAB Executive Director 💌
Contacts:
Bob Braden
Executive Director of the IAB
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
1-310-822-1511
Braden@ISI.EDU
Christian Huitema
Chair of the IAB
INRIA, Sophia-Antipolis
2004 Route des Lucioles
BP 109
F-06561 Valbonne Cedex
France
+33 93 65 77 15
Christian.Huitema@MIRSA.INRIA.FR7.1.2. Internet Engineering Task Force (IETF) Contact
the IETF crew 🎀
Contacts:
Phill Gross
Chair of the IETF
Advanced Network and Services
100 Clearbrook Road
Elmsford, NY 10523
1-914-789-5300
PGross@ANS.NET
John Stewart
IESG Secretary
Corporation for National Research Initiatives
1895 Preston White Drive, Suite 100
Reston, VA 22091
1-703-620-8990
jstewart@CNRI.RESTON.VA.US
Steve Coya
Executive Director of the IETF
Corporation for National Research Initiatives
1895 Preston White Drive, Suite 100
Reston, VA 22091
1-703-620-8990
scoya@CNRI.RESTON.VA.US7.1.3. Internet Research Task Force (IRTF) Contact
the research side of things 🧚
Contact:
Jon Postel
Chair of the IRTF
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
1-310-822-1511
Postel@ISI.EDU7.2. Internet Assigned Numbers Authority Contact 🦋
Contact:
Joyce K. Reynolds
Internet Assigned Numbers Authority
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
1-310-822-1511
IANA@ISI.EDUThe protocol standards are managed by the Internet Assigned Numbers Authority. ✨
Please refer to the document "Assigned Numbers" (RFC-1340) for further information about the status of protocol documents. Okay so there are two documents that sum up the requirements for hosts and gateways on the Internet: "Host Requirements" (RFC-1122 and RFC-1123) and "Gateway Requirements" (RFC-1009). Iconic reading list 📚
How to obtain the most recent edition of this "Internet Official Protocol Standards" memo: 🌈
The file in-notes/std/std1.txt may be copied via FTP from the FTP.ISI.EDU computer using the FTP username anonymous and FTP password guest.
7.3. Request for Comments Editor Contact 🖊️
Contact:
Jon Postel
RFC Editor
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
1-310-822-1511
RFC-Editor@ISI.EDUDocuments may be submitted via electronic mail to the RFC Editor for consideration for publication as RFC. If you're not familiar with the format or style requirements, request the "Instructions for RFC Authors". In general, the style of any recent RFC may be used as a guide. Literally the best template you could ask for 💅
7.4. The Network Information Center and Requests for Comments Distribution Contact 🌸
RFCs may be obtained from DS.INTERNIC.NET via FTP, WAIS, and electronic mail. Through FTP, RFCs are stored as rfc/rfcnnnn.txt or rfc/rfcnnnn.ps, where nnnn is the RFC number. Log in as anonymous and provide your e-mail address as the password. Through WAIS, you may use either your local WAIS client or telnet to DS.INTERNIC.NET and log in as wais (no password required) to access a WAIS client. Help information and a tutorial for using WAIS are available online. The WAIS database to search is rfcs.
Directory and Database Services also has a mail server interface. Send a mail message to mailserv@ds.internic.net and include any of the following commands in the message body:
document-by-name rfcnnnn where 'nnnn' is the RFC number
The text version is sent.
file /ftp/rfc/rfcnnnn.yyy where 'nnnn' is the RFC number.
and 'yyy' is 'txt' or 'ps'.
help to get information on how to use
the mailserver.The InterNIC directory and database services collection of resource listings, internet documents such as RFCs, FYIs, STDs, and Internet Drafts, and publicly accessible databases are also now available via Gopher. All of their collections are WAIS indexed and can be searched from the Gopher menu 🔍
To access the InterNIC Gopher Servers, please connect to "internic.net" port 70.
Contact: admin@ds.internic.net
7.5. Sources for Requests for Comments 🎁
Details on many sources of RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to "rfc-info@ISI.EDU" with the message body "help: ways_to_get_rfcs". For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs8. Security Considerations 🔐
okay bestie, this is the one section where the RFC just goes "not me" 💀 Security issues are not addressed in this memo. Yes, that's the whole section. It deserves your full seriousness anyway 🫠
9. Author's Address 💌
Jon Postel
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: 310-822-1511
Fax: 310-823-6714
Email: Postel@ISI.EDU📦 where this page comes from
- ietf: rfc1600 1994-03
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms