RFC 6814
Formally Deprecating Some IPv4 Options
Formally Deprecating Some IPv4 Options 💖
okay bestie, this one is a Standards Track doc from November 2012 🍓 It's written by C. Pignataro (Cisco Systems) and F. Gont (UTN-FRH / SI6 Networks), and it's published under ISSN 2070-1721. It's the RFC 6814 cleanup crew 🧹 and it obsoletes RFC 1385, RFC 1393, RFC 1475, and RFC 1770. Lowkey iconic that it's a whole doc just to retire old stuff 💅
Abstract
okay so the vibe is that a bunch of IPv4 options have quietly become obsolete in real life 🥀 but nobody ever made it official. this doc officially deprecates them so the IANA registry gets a glow-up ✨ It also obsoletes RFCs 1385, 1393, 1475, and 1770, and asks the RFC Editor to mark those as Historic 📜
Status of This Memo
this is an Internet Standards Track document 🎀
it's a product of the Internet Engineering Task Force (IETF) 🌸 and it represents the consensus of the IETF community. it got public review and was approved for publication by the Internet Engineering Steering Group (IESG). if you want more on Internet Standards, check out Section 2 of RFC 5741.
for the current status, any errata, and how to give feedback, go to http://www.rfc-editor.org/info/rfc6814 🦋
Copyright Notice
copyright (c) 2012 IETF Trust and the people listed as document authors. all rights reserved 💜
this doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they were on the publication date. please read those carefully because they explain your rights and restrictions 🙈 Code Components pulled from this document must include the Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions. they come without warranty, same as the Simplified BSD License says 🧚
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Discussion of Deprecated Options . . . . . . . . . . . . . . . 2
2.1. Stream ID . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.2. Extended Internet Protocol . . . . . . . . . . . . . . . . 3
2.3. Traceroute . . . . . . . . . . . . . . . . . . . . . . . . 3
2.4. ENCODE . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.5. VISA . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.6. Address Extension . . . . . . . . . . . . . . . . . . . . . 3
2.7. Selective Directed Broadcast . . . . . . . . . . . . . . . 3
2.8. Dynamic Packet State . . . . . . . . . . . . . . . . . . . 3
2.9. Upstream Multicast Pkt. . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
4. Changing the Status of the Corresponding RFCs to Historic . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . . 51. Introduction 🧚
the Internet Protocol version 4 (IPv4) [RFC791] lets the protocol grow by supporting a bunch of "options" in the variable-length IPv4 header 🌈 each option is identified by a "type" value, and IANA [IANA-IP] manages those registrations. a number of these options have become obsolete in practice but were never formally deprecated 🥺 this doc deprecates them, which cleans up the IANA registry ✨
this doc also obsoletes [RFC1385], [RFC1393], [RFC1475], and [RFC1770], and asks the RFC Editor to change their status to Historic 📜
2. Discussion of Deprecated Options 💅
the subsections below talk through each option being deprecated. no other reference info has been found, so this is the tea ☕
2.1. Stream ID 🌸
the Stream ID option is obsolete 💀 it's specified in RFC 791 [RFC791], and it's deprecated in Section 3.2.1.8 of RFC 1122 [RFC1122] and Section 4.2.2.1 of RFC 1812 [RFC1812].
2.2. Extended Internet Protocol 🦋
the Extended Internet Protocol option is defined in [RFC1385] and has been superseded by [RFC2460] 👑
2.3. Traceroute 🍓
the Traceroute option is defined in [RFC1393]. it's defined as Experimental, and it was never widely deployed on the public Internet 🙈
2.4. ENCODE 🔐
this option was used for experiments with IP-layer encryption. no products are known to have ever shipped with support for it 🫥
2.5. VISA 🛂
this option was part of an experiment [VISA87] [VISA89] at USC, and it was never widely deployed 😭
2.6. Address Extension 🌙
the Address Extension option is defined in an Experimental RFC [RFC1475] and was marked as IPv7. IPv7 was never widely deployed, so no notes 🤷♀️
2.7. Selective Directed Broadcast 📡
the Selective Directed Broadcast option was originally defined in [RFC1770]. it was never widely deployed and the approach was abandoned 🪦
2.8. Dynamic Packet State ⭐
the Dynamic Packet State option was specified in [DIFFSERV-DPS]. that doc was supposed to be published as Experimental, but it never became an RFC 😩 the IP option was never widely deployed either.
2.9. Upstream Multicast Pkt. 🎀
this option was originally specified in [BIDIR-PIM]. its use was deprecated by [RFC5015], which uses a control-plane mechanism to handle upstream forwarding of multicast packets on a multi-access LAN 🧠✨
3. IANA Considerations 📋
the "IP OPTION NUMBERS" registry [IANA-IP] lists the currently assigned IP option numbers. this registry also marks a deprecated IP Option Number with a footnote 🏷️
this doc formally deprecates the options below. IANA has marked them that way in the corresponding registry [IANA-IP] 💜
Copy Class Number Value Name Reference
---- ----- ------ ----- ------------------------------- ------------
1 0 8 136 SID - Stream ID [RFC791,JBP]
1 0 14 142 VISA - Experimental Access Control [Estrin]
0 0 15 15 ENCODE - ??? [VerSteeg]
1 0 17 145 EIP - Extended Internet Protocol [RFC1385]
0 2 18 82 TR - Traceroute [RFC1393]
1 0 19 147 ADDEXT - Address Extension [Ullmann IPv7]
1 0 21 149 SDB - Selective Directed Broadcast [Graff]
1 0 23 151 DPS - Dynamic Packet State [Malis]
1 0 24 152 UMP - Upstream Multicast Pkt. [Farinacci]the IP options "MTU Probe" (MTUP, value 11) and "MTU Reply" (MTUR, value 12) were first defined in [RFC1063], and they've already been deprecated by [RFC1191] 🫶
4. Changing the Status of the Corresponding RFCs to Historic 📜
per this doc, the RFC Editor has changed the status of [RFC1385], [RFC1393], [RFC1475], and [RFC1770] to Historic 🥳
5. Security Considerations 🔒
⚠️ bestie, this one is serious. this doc does not modify the security properties of the IPv4 options being deprecated. the options are deprecated, but their security properties stay exactly as they are. don't assume that deprecating an option changes how it's secured.
6. Acknowledgments 💖
the authors would like to thank Ron Bonica for his guidance 🫶
the authors would also like to thank Ran Atkinson, Fred Baker, Deborah Estrin, Dino Farinacci, Andrew Malis, Gene Tsudik, and Bill VerSteeg for sharing insights on some of the options being formally deprecated by this doc 🌷
7. References 📚
7.1. Normative References
[RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791, September
1981.
[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989.7.2. Informative References
[BIDIR-PIM] Estrin, D. and D. Farinacci, "Bi-Directional Shared Trees
in PIM-SM", Work in Progress, May 1999.
[DIFFSERV-DPS]
Stoica, I., Zhang, H., Venkitaraman, N., and J. Mysore,
"Per Hop Behaviors Based on Dynamic Packet State", Work in
Progress, October 2002.
[IANA-IP] Internet Assigned Numbers Authority, "IP OPTION NUMBERS",
<http://www.iana.org/assignments/ip-parameters>.
[RFC1063] Mogul, J., Kent, C., Partridge, C., and K. McCloghrie, "IP
MTU discovery options", RFC 1063, July 1988.
[RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191,
November 1990.
[RFC1385] Wang, Z., "EIP: The Extended Internet Protocol", RFC 1385,
November 1992.
[RFC1393] Malkin, G., "Traceroute Using an IP Option", RFC 1393,
January 1993.
[RFC1475] Ullmann, R., "TP/IX: The Next Internet", RFC 1475, June
1993.
[RFC1770] Graff, C., "IPv4 Option for Sender Directed Multi-
Destination Delivery", RFC 1770, March 1995.
[RFC1812] Baker, F., Ed., "Requirements for IP Version 4 Routers",
RFC 1812, June 1995.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", RFC 5015, October 2007.
[VISA87] Estrin, D. and G. Tsudik, "VISA Scheme for Inter-
Organizational Network Security", IEEE Symposium on
Security and Privacy (S&P), 1987.
[VISA89] Estrin, D., Mogul, J., and G. Tsudik, "VISA Protocols for
Controlling Inter-Organizational Datagram Flow", IEEE
Journal on Selected Areas in Communications, 1989.Authors' Addresses 🧑💻
Carlos Pignataro
Cisco Systems
7200-12 Kit Creek Road
Research Triangle Park, NC 27709
United States
EMail: cpignata@cisco.com
Fernando Gont
UTN-FRH / SI6 Networks
Evaristo Carriego 2644
Haedo, Provincia de Buenos Aires 1706
Argentina
Phone: +54 11 4650 8472
EMail: fgont@si6networks.com
URI: http://www.si6networks.comthat's the whole doc, bestie 🌈✨ the big takeaway is that these old IPv4 options get officially retired, the registry gets cleaned up, and those four old RFCs go Historic 👑 iykyk 💅
📦 where this page comes from
- ietf: rfc6814 2012-11
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms