Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths
RFC 6826
| Document | Type |
RFC - Proposed Standard
(January 2013; No errata)
Updated by RFC 7438
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-wijnands-mpls-mldp-in-band-signaling | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6826 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Adrian Farrel | ||
| IESG note | Loa Andersson (loa@pi.nu) is the document shepherd. | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) IJ. Wijnands, Ed.
Request for Comments: 6826 T. Eckert
Category: Standards Track Cisco Systems, Inc.
ISSN: 2070-1721 N. Leymann
Deutsche Telekom
M. Napierala
AT&T Labs
January 2013
Multipoint LDP In-Band Signaling for
Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths
Abstract
Consider an IP multicast tree, constructed by Protocol Independent
Multicast (PIM), that needs to pass through an MPLS domain in which
Multipoint LDP (mLDP) point-to-multipoint and/or multipoint-to-
multipoint Labels Switched Paths (LSPs) can be created. The part of
the IP multicast tree that traverses the MPLS domain can be
instantiated as a multipoint LSP. When a PIM Join message is
received at the border of the MPLS domain, information from that
message is encoded into mLDP messages. When the mLDP messages reach
the border of the next IP domain, the encoded information is used to
generate PIM messages that can be sent through the IP domain. The
result is an IP multicast tree consisting of a set of IP multicast
sub-trees that are spliced together with a multipoint LSP. This
document describes procedures regarding how IP multicast trees are
spliced together with multipoint LSPs.
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/rfc6826.
Wijnands, et al. Standards Track [Page 1]
RFC 6826 In-Band Signaling with mLDP January 2013
Copyright Notice
Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. In-Band Signaling for MP LSPs . . . . . . . . . . . . . . . . 4
2.1. Transiting Unidirectional IP Multicast Shared Trees . . . 6
2.2. Transiting IP Multicast Source Trees . . . . . . . . . . . 6
2.3. Transiting IP Multicast Bidirectional Trees . . . . . . . 7
3. LSP Opaque Encodings . . . . . . . . . . . . . . . . . . . . . 8
3.1. Transit IPv4 Source TLV . . . . . . . . . . . . . . . . . 8
3.2. Transit IPv6 Source TLV . . . . . . . . . . . . . . . . . 8
3.3. Transit IPv4 Bidir TLV . . . . . . . . . . . . . . . . . . 9
3.4. Transit IPv6 Bidir TLV . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Normative References . . . . . . . . . . . . . . . . . . . 10
6.2. Informative References . . . . . . . . . . . . . . . . . . 10
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
Wijnands, et al. Standards Track [Page 2]
RFC 6826 In-Band Signaling with mLDP January 2013
1. Introduction
The mLDP (Multipoint LDP) [RFC6388] specification describes
mechanisms for creating point-to-multipoint (P2MP) and multipoint-to-
multipoint (MP2MP) LSPs (Label Switched Paths). These LSPs are
typically used for transporting end-user multicast packets. However,
the mLDP specification does not provide any rules for associating
particular end-user multicast packets with any particular LSP. Other
Show full document text