Index Journeys
RFC 7385 PROPOSED STANDARD BGP · MULTICAST · IANA

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

Creates an IANA registry for BGP PMSI tunnel type code points.

On rfc-editor.org ↗
PUBLISHED
October 2014
AUTHORS
L. Andersson, G. Swallow
STREAM
IETF
BUILDS ON
RFC 6514 — MVPN BGP Encodings
UPDATED BY
RFC 8317 — E-Tree in EVPN, RFC 8338 — P2MP PW with LDP
TUNNEL TYPE FIELD
One octet
INITIALLY ASSIGNED VALUES
0x00 through 0x07
EXPERIMENTAL VALUES
0xFB through 0xFE
RESERVED VALUE
0xFF
DOI
10.17487/RFC7385
LINEAGE · FROM THE RFC INDEXOpen full graph →
'12RFC 6514MVPN BGP Encodings'14RFC 7385IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗ 
Internet Engineering Task Force (IETF)                      L. Andersson
Request for Comments: 7385                           Huawei Technologies
Updates: 6514                                                 G. Swallow
Category: Standards Track                                  Cisco Systems
ISSN: 2070-1721                                             October 2014


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

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.

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 Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   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) 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

   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

   In 'BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs'
   [RFC6514], 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.  RFC 6514 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"
   [SEAMLESS-MCAST] 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 RFC 6514 [RFC6514].

2.  Security Considerations

   This document simply creates an IANA registry from a table in RFC
   6514.  Thus, there are no security concerns.

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. 0xFF is reserved, the status of 0xFF may only be changed
   through Standards Action [RFC5226].

   The initial registry should appear as:

      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]


                                 Figure 1

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
   our 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

ISO Plain Language

On this page
PROBLEMRFC 6514 defined PMSI Tunnel Type code points but did not create an IANA registry for assigning additional values.
MECHANISMRFC 7385 creates a registry in the BGP Parameters registry and sets allocation rules for the code-point ranges.
STATUS TODAYRFC 7385 updates RFC 6514 and was later updated by RFC 8317 and RFC 8338.

§1A Registry for PMSI Tunnel Types

RFC 6514 defines an octet field for the tunnel type in the P-Multicast Service Interface (PMSI) Tunnel attribute. It allocated values 0 through 7 but did not create a corresponding IANA registry.

RFC 7385 creates the registry because further code-point allocations were needed, including one for Inter-Area P2MP Segmented LSPs.

The earlier specification assigned tunnel-type values but did not provide an official registry for new assignments. This RFC creates that registry.

§3Allocation Rules and Initial Values

IANA creates the P-Multicast Service Interface Tunnel (PMSI Tunnel) Tunnel Types registry within the BGP Parameters registry. The values from 0x00 through 0xFA use IETF Review. Values 0xFB through 0xFE are experimental and are not assigned. Value 0xFF is reserved and can change status only through Standards Action.

The initial registry lists the values from RFC 6514, covering no tunnel information, RSVP-TE P2MP LSP, mLDP P2MP LSP, PIM trees, ingress replication, and mLDP MP2MP LSP. Values 0x08 through 0xFA are unassigned.

The registry records the existing tunnel types and leaves a range available for future assignments. Separate ranges are reserved for experiments and for a reserved code point.

§2Security Considerations

The RFC says it simply creates an IANA registry from a table in RFC 6514 and therefore has no security concerns.

The RFC says its registry change introduces no security concerns.

§4References

[RFC5226]RFC 5226Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.May 2008[RFC6514]RFC 6514Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs", RFC 6514, February 2012.February 2012