Internet DRAFT - draft-ietf-l3vpn-pmsi-registry
draft-ietf-l3vpn-pmsi-registry
Network Working Group L. Andersson
Internet-Draft Huawei Technologies
Updates: 6514 (if approved) G. Swallow
Intended status: Standards Track Cisco Systems
Expires: February 27, 2015 August 26, 2014
IANA registry for PMSI Tunnel Type code points
draft-ietf-l3vpn-pmsi-registry-07
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 an IANA registry
for these.
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 Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 27, 2015.
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
Andersson & Swallow Expires February 27, 2015 [Page 1]
Internet-Draft PMSI IANA registry August 2014
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 . . . . . . . . . . . . . . . . . . . 2
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.1. Normative References . . . . . . . . . . . . . . . . . . 3
5.2. Informative References . . . . . . . . . . . . . . . . . 3
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
In RFC 6514 '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 now is need to make further code point allocations from this
name space. In particular, draft-ietf-mpls-seamless-mcast
[I-D.ietf-mpls-seamless-mcast] needs to make such an allocation.
However the RFC did not create an IANA registry for these codepoints.
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 is requested to create a new registry called "P-Multicast
Service Interface Tunnel (PMSI Tunnel) Tunnel Types" in the "Border
Gateway Protocol (BGP) Parameters" registry.
Andersson & Swallow Expires February 27, 2015 [Page 2]
Internet-Draft PMSI IANA registry August 2014
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 [RFC 6514]
0x01 RSVP-TE P2MP LSP [RFC 6514]
0x02 mLDP P2MP LSP [RFC 6514]
0x03 PIM-SSM Tree [RFC 6514]
0x04 PIM-SM Tree [RFC 6514]
0x05 BIDIR-PIM Tree [RFC 6514]
0x06 Ingress Replication [RFC 6514]
0x07 mLDP MP2MP LSP [RFC 6514]
0x08 - 0xFA Unassigned
0xFB - 0xFE Experimental [RFC-to-be]
0xFF Reserved [RFC-to-be]
Figure 1
4. 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.
5. References
5.1. Normative References
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[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.
5.2. Informative References
[I-D.ietf-mpls-seamless-mcast]
Rekhter, Y. and R. Aggarwal, "Inter-Area P2MP Segmented
LSPs", draft-ietf-mpls-seamless-mcast-14 (work in
progress), July 2014.
Andersson & Swallow Expires February 27, 2015 [Page 3]
Internet-Draft PMSI IANA registry August 2014
Authors' Addresses
Loa Andersson
Huawei Technologies
Email: loa@mail01.huawei.com
George Swallow
Cisco Systems
Email: swallow@cisco.com
Andersson & Swallow Expires February 27, 2015 [Page 4]
