summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc7385.txt
diff options
context:
space:
mode:
authorThomas Voss <mail@thomasvoss.com> 2024-11-27 20:54:24 +0100
committerThomas Voss <mail@thomasvoss.com> 2024-11-27 20:54:24 +0100
commit4bfd864f10b68b71482b35c818559068ef8d5797 (patch)
treee3989f47a7994642eb325063d46e8f08ffa681dc /doc/rfc/rfc7385.txt
parentea76e11061bda059ae9f9ad130a9895cc85607db (diff)
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc7385.txt')
-rw-r--r--doc/rfc/rfc7385.txt227
1 files changed, 227 insertions, 0 deletions
diff --git a/doc/rfc/rfc7385.txt b/doc/rfc/rfc7385.txt
new file mode 100644
index 0000000..5768b7f
--- /dev/null
+++ b/doc/rfc/rfc7385.txt
@@ -0,0 +1,227 @@
+
+
+
+
+
+
+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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Andersson & Swallow Standards Track [Page 1]
+
+RFC 7385 PMSI IANA registry October 2014
+
+
+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].
+
+
+
+
+
+Andersson & Swallow Standards Track [Page 2]
+
+RFC 7385 PMSI IANA registry October 2014
+
+
+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>.
+
+
+
+
+Andersson & Swallow Standards Track [Page 3]
+
+RFC 7385 PMSI IANA registry October 2014
+
+
+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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Andersson & Swallow Standards Track [Page 4]
+