RFC 5871

Internet Engineering Task Force (IETF) 🎀 J. Arkko, Ericsson ✨ — Request for Comments: 5871 💖 — Updates: 2460 🦋 — Category: Standards Track 🌸 — ISSN: 2070-1721 — May 2010 🧚

IANA Allocation Guidelines for the IPv6 Routing Header 💅

S. Bradner, Harvard University 🫶 (co-author, same vibe!)

Okay bestie, this one's the IANA rulebook for the Routing Type field in the IPv6 Routing Header. Think of it as the "how do we hand out new numbers" manual. It's a Standards Track doc, it updates RFC 2460, and it came out May 2010. Iconic. 👑

Abstract ✨

Okay so the whole point is simple: this doc sets the IANA guidelines for allocating brand-new values for the Routing Type field in the IPv6 Routing Header. That's it, that's the tea. 🍓

Status of This Memo 🌈

This is an Internet Standards Track document. 🔥

It's a product of the IETF, so 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 what Internet Standards even are, check Section 2 of RFC 5741. 📚

Want the current status, any errata, or to send feedback? Head to http://www.rfc-editor.org/info/rfc5871. 💌

Copyright Notice 💜

Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. 🔒

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication. Please review those docs carefully, bestie, because they spell out your rights and restrictions. 🙈

Code Components pulled out of this document must include Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come without warranty, as described in the Simplified BSD License. ⚠️

1. Introduction 🦋

Okay so this doc specifies the IANA guidelines [RFC5226] for allocating new values for the Routing Type field in the IPv6 Routing Header [RFC2460]. Before this, there was no IANA guidance for these allocations at all. Chaotic, honestly. 💀

2. IANA Considerations 📋

New Routing Type values get allocated through IETF Review or IESG Approval [RFC5226]. ✨

Also, two experimental values (253 and 254) are already available for use [RFC4727]. Bestie, those are the ones you can play with right now. 🧪

3. Security Considerations 🔥

This specification does not change the security properties of the Routing Header. 🛡️

BUT. Past experience shows that it's super easy to design routing headers with significant problems [RFC5095]. So be careful out there, it is not giving safe by default. 😭⚠️

4. References 📚

4.1. Normative References 💎

[RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
           (IPv6) Specification", RFC 2460, December 1998.

[RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
           IANA Considerations Section in RFCs", BCP 26, RFC 5226,
           May 2008.

4.2. Informative References 🌸

[RFC4727]  Fenner, B., "Experimental Values In IPv4, IPv6, ICMPv4,
           ICMPv6, UDP, and TCP Headers", RFC 4727, November 2006.

[RFC5095]  Abley, J., Savola, P., and G. Neville-Neil, "Deprecation
           of Type 0 Routing Headers in IPv6", RFC 5095,
           December 2007.

Appendix A. Changes from RFC 2460 🧚

This doc only specifies the IANA rules tied to the Routing Type field. That's the whole glow-up. ✨

Authors' Addresses 🎀

Jari Arkko
Ericsson
Jorvas  02420
Finland

EMail: jari.arkko@piuha.net


Scott Bradner
Harvard University
Cambridge, MA  02138
US

Phone: +1 617 495 3864
EMail: sob@harvard.edu