Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context
RFC 7246
| Document | Type |
RFC - Proposed Standard
(June 2014; No errata)
Updated by RFC 7438
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-wijnands-l3vpn-mldp-vrf-in-band-signaling | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication (wg milestone: Jan 2014 - Submit specification... ) | |
| Document shepherd | Martin Vigoureux | ||
| Shepherd write-up | Show (last changed 2014-01-17) | ||
| IESG | IESG state | RFC 7246 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Adrian Farrel | ||
| Send notices to | (None) | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) IJ. Wijnands, Ed.
Request for Comments: 7246 Cisco Systems
Category: Standards Track P. Hitchen
ISSN: 2070-1721 BT
N. Leymann
Deutsche Telekom
W. Henderickx
Alcatel-Lucent
A. Gulko
Thomson Reuters
J. Tantsura
Ericsson
June 2014
Multipoint Label Distribution Protocol In-Band Signaling in
a Virtual Routing and Forwarding (VRF) Table Context
Abstract
An IP Multicast Distribution Tree (MDT) may traverse both label
switching (i.e., Multiprotocol Label Switching, or MPLS) and non-
label switching regions of a network. Typically, the MDT begins and
ends in non-MPLS regions, but travels through an MPLS region. In
such cases, it can be useful to begin building the MDT as a pure IP
MDT, then convert it to an MPLS Multipoint Label Switched Path
(MP-LSP) when it enters an MPLS-enabled region, and then convert it
back to a pure IP MDT when it enters a non-MPLS-enabled region.
Other documents specify the procedures for building such a hybrid
MDT, using Protocol Independent Multicast (PIM) in the non-MPLS
region of the network, and using Multipoint Label Distribution
Protocol (mLDP) in the MPLS region. This document extends those
procedures to handle the case where the link connecting the two
regions is a Virtual Routing and Forwarding (VRF) table link, as
defined in the "BGP IP/MPLS VPN" specification. However, this
document is primarily aimed at particular use cases where VRFs are
used to support multicast applications other than multicast VPN.
Wijnands, et al. Standards Track [Page 1]
RFC 7246 mLDP In-Band Signaling in VRF Context June 2014
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/rfc7246.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
2. VRF In-Band Signaling for MP LSPs . . . . . . . . . . . . . . 5
3. Encoding the Opaque Value of an LDP MP FEC . . . . . . . . . . 7
3.1. Transit VPNv4 Source TLV . . . . . . . . . . . . . . . . . 7
3.2. Transit VPNv6 Source TLV . . . . . . . . . . . . . . . . . 8
3.3. Transit VPNv4 Bidir TLV . . . . . . . . . . . . . . . . . 9
3.4. Transit VPNv6 Bidir TLV . . . . . . . . . . . . . . . . . 10
4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . . 12
Wijnands, et al. Standards Track [Page 2]
Show full document text