RFC 7385

RFC 7385: IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points 🎀

okay bestie, the title block first! 💅

Internet Engineering Task Force (IETF) ✨ Request for Comments: 7385 Updates: 6514 (RFC 6514, that's the one we're fixing up 🔧) Category: Standards Track 🔥 ISSN: 2070-1721 October 2014

Authors: L. Andersson (Huawei Technologies) and G. Swallow (Cisco Systems) 👑

Abstract

okay so RFC 6514 made a whole space of Tunnel Type code points for a new BGP attribute called the "P-Multicast Service Interface Tunnel (PMSI Tunnel) attribute" 🦋 but the RFC never made an IANA registry for them 😭

now people need to add more code points to that space, so this doc creates the IANA registry for that purpose. it updates RFC 6514 🫶

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). more info on Internet Standards is in Section 2 of RFC 5741 📚

for the current status, any errata, and how to give feedback, check http://www.rfc-editor.org/info/rfc7385 💜

Copyright Notice

Copyright (c) 2014 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) as in effect on the date of publication. please actually read these, they spell out your rights and restrictions for this document 🙈

Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they're provided without warranty as described in the Simplified BSD License ⚖️

Table of Contents

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
2.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
  4.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
  4.2.  Informative References  . . . . . . . . . . . . . . . . .   4
Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   4
Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

---

1. Introduction ✨

okay so in 'BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs' [RFC6514], there's an optional transitive BGP attribute called the "P-Multicast Service Interface Tunnel (PMSI Tunnel) attribute" 🦋 this attribute uses an octet field to say which PMSI tunnel type it is, and RFC 6514 only allocates the values 0-7 🌸

more allocations are needed now 🫶 "Inter-Area P2MP Segmented LSPs" [SEAMLESS-MCAST] is one that needs to grab a code point. the problem is the RFC never made an IANA registry for these, so that's the gap this doc fills 💅

this document creates a new IANA registry called "P-Multicast Service Interface Tunnel (PMSI Tunnel) Tunnel Types" for these code points. it lives in the "Border Gateway Protocol (BGP) Parameters" registry 🎀

and yes, creating this registry is an update of RFC 6514 [RFC6514] ⭐

2. Security Considerations 🔒

this doc just turns a table from RFC 6514 into an IANA registry 🙈 so, no security concerns. none. zero. nada. 💀

3. IANA Considerations 📋

IANA has created a new registry called "P-Multicast Service Interface Tunnel (PMSI Tunnel) Tunnel Types" in the "Border Gateway Protocol (BGP) Parameters" registry 🧚

the allocation policy for values 0x00 to 0xFA is IETF Review [RFC5226] 👑 values 0xFB to 0xFE are experimental and are not to be assigned 🧪 and 0xFF is reserved. the status of 0xFF may only be changed through Standards Action [RFC5226] 🔐

the initial registry looks like this 🍓

   Value        Meaning                        Reference

   0x00         no tunnel information present  [RFC6514]
   0x01         RSVP-TE P2MP LSP               [RFC6514]
   0x02         mLDP P2MP LSP                  [RFC6514]
   0x03         PIM-SSM Tree                   [RFC6514]
   0x04         PIM-SM Tree                    [RFC6514]
   0x05         BIDIR-PIM Tree                 [RFC6514]
   0x06         Ingress Replication            [RFC6514]
   0x07         mLDP MP2MP LSP                 [RFC6514]
   0x08 - 0xFA  Unassigned
   0xFB - 0xFE  Experimental                   [RFC7385]
   0xFF         Reserved                       [RFC7385]

(that's Figure 1 btw 🎨)

4. References 📚

4.1. Normative References

[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008, http://www.rfc-editor.org/info/rfc5226. 🌈

[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs", RFC 6514, February 2012, http://www.rfc-editor.org/info/rfc6514. 💖

4.2. Informative References

[SEAMLESS-MCAST] Rekhter, Y. and R. Aggarwal, "Inter-Area P2MP Segmented LSPs", Work in Progress, draft-ietf-mpls-seamless-mcast-14, July 2014. 🦋

Acknowledgements 🫶

the authors want to thank Adrian Farrel for unwavering support, and their L3VPN, MPLS, and IDR co-chairs for swift processing of this document 👑✨

Authors' Addresses 💌

Loa Andersson Huawei Technologies EMail: loa@mail01.huawei.com

George Swallow Cisco Systems EMail: swallow@cisco.com

and that's a wrap, bestie!! 🌈💖✨ this registry is literally iconic 💅