7385
PROPOSED STANDARD

IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points

Authors: L. Andersson, G. Swallow
Date: October 2014
Area: rtg
Working Group: l3vpn
Stream: IETF
Updates: RFC 6514
Updated by: RFC 8317

Abstract

RFC 6514 created a space of Tunnel Type code points for a new BGP attribute called the "P-Multicast Service Interface Tunnel (PMSI Tunnel) attribute". However, the RFC did not create a corresponding IANA registry.

There now is need to make further code point allocations from this name space. This document serves to update RFC 6514 in that it creates an IANA registry for that purpose.

RFC 7385: IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points [RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]

PROPOSED STANDARD
Updated by: 8317, 8338
Internet Engineering Task Force (IETF)                      L. Andersson
Request for Comments: 7385                           Huawei Technologies
Updates: <a href="./rfc6514">6514</a>                                                 G. Swallow
Category: Standards Track                                  Cisco Systems
ISSN: 2070-1721                                             October 2014


         <span class="h1">IANA Registry for P-Multicast Service Interface (PMSI)</span>
                        <span class="h1">Tunnel Type Code Points</span>

Abstract

   <a href="./rfc6514">RFC 6514</a> created a space of Tunnel Type code points for a new BGP
   attribute called the "P-Multicast Service Interface Tunnel (PMSI
   Tunnel) attribute".  However, the RFC did not create a corresponding
   IANA registry.

   There now is need to make further code point allocations from this
   name space.  This document serves to update <a href="./rfc6514">RFC 6514</a> in that it
   creates an IANA registry for that purpose.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc7385">http://www.rfc-editor.org/info/rfc7385</a>.

















<span class="grey">Andersson & Swallow          Standards Track                    [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc7385">RFC 7385</a>                   PMSI IANA registry               October 2014</span>


Copyright Notice

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

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to 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 are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-2">2</a>
   <a href="#section-2">2</a>.  Security Considerations . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-3">3</a>.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-4">4</a>.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
     <a href="#section-4.1">4.1</a>.  Normative References  . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
     <a href="#section-4.2">4.2</a>.  Informative References  . . . . . . . . . . . . . . . . .   <a href="#page-4">4</a>
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-4">4</a>
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-4">4</a>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   In 'BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs'
   [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>], an optional transitive BGP attribute called the
   "P-Multicast Service Interface Tunnel (PMSI Tunnel) attribute" is
   specified.  This BGP attribute uses an octet field to specify the
   PMSI tunnel type.  <a href="./rfc6514">RFC 6514</a> allocates the values 0-7.

   There is now a need to make further code point allocations from this
   name space.  In particular, "Inter-Area P2MP Segmented LSPs"
   [<a href="#ref-SEAMLESS-MCAST">SEAMLESS-MCAST</a>] needs to make such an allocation.  However, the RFC
   did not create an IANA registry for these code points.

   This document creates a new IANA registry called "P-Multicast Service
   Interface Tunnel (PMSI Tunnel) Tunnel Types" for these code points.
   The registry is created in the "Border Gateway Protocol (BGP)
   Parameters" registry.

   Creating this registry is an update of <a href="./rfc6514">RFC 6514</a> [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>].





<span class="grey">Andersson & Swallow          Standards Track                    [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc7385">RFC 7385</a>                   PMSI IANA registry               October 2014</span>


<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Security Considerations</span>

   This document simply creates an IANA registry from a table in <a href="./rfc6514">RFC</a>
   <a href="./rfc6514">6514</a>.  Thus, there are no security concerns.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  IANA Considerations</span>

   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
   [<a href="./rfc5226" title="">RFC5226</a>].  Values 0xFB to 0xFE are experimental and are not to be
   assigned. 0xFF is reserved, the status of 0xFF may only be changed
   through Standards Action [<a href="./rfc5226" title="">RFC5226</a>].

   The initial registry should appear as:

      Value        Meaning                        Reference

      0x00         no tunnel information present  [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>]
      0x01         RSVP-TE P2MP LSP               [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>]
      0x02         mLDP P2MP LSP                  [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>]
      0x03         PIM-SSM Tree                   [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>]
      0x04         PIM-SM Tree                    [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>]
      0x05         BIDIR-PIM Tree                 [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>]
      0x06         Ingress Replication            [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>]
      0x07         mLDP MP2MP LSP                 [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>]
      0x08 - 0xFA  Unassigned
      0xFB - 0xFE  Experimental                   [<a href="./rfc7385">RFC7385</a>]
      0xFF         Reserved                       [<a href="./rfc7385">RFC7385</a>]


                                 Figure 1

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  References</span>

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Normative References</span>

   [<a id="ref-RFC5226">RFC5226</a>]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
              May 2008, <<a href="https://www.rfc-editor.org/info/rfc5226">http://www.rfc-editor.org/info/rfc5226</a>>.

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




<span class="grey">Andersson & Swallow          Standards Track                    [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc7385">RFC 7385</a>                   PMSI IANA registry               October 2014</span>


<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Informative References</span>

   [<a id="ref-SEAMLESS-MCAST">SEAMLESS-MCAST</a>]
              Rekhter, Y. and R. Aggarwal, "Inter-Area P2MP Segmented
              LSPs", Work in Progress, <a href="./draft-ietf-mpls-seamless-mcast-14">draft-ietf-mpls-seamless-</a>
              <a href="./draft-ietf-mpls-seamless-mcast-14">mcast-14</a>, July 2014.

Acknowledgements

   The authors want to thank Adrian Farrel for unwavering support and
   our L3VPN, MPLS, and IDR co-chairs for swift processing of this
   document.

Authors' Addresses

   Loa Andersson
   Huawei Technologies

   EMail: [email protected]


   George Swallow
   Cisco Systems

   EMail: [email protected]


























Andersson & Swallow          Standards Track                    [Page 4]

Additional Resources