A new Request for Comments is now available in online RFC libraries.
RFC 7441
Title: Encoding Multipoint LDP (mLDP) Forwarding
Equivalence Classes (FECs) in the NLRI
of BGP MCAST-VPN Routes
Author: IJ. Wijnands, E. Rosen, U. Joorde
Status: Standards Track
Stream: IETF
Date: January 2015
Mailbox: ice@cisco.com,
erosen@juniper.net,
uwe.joorde@telekom.de
Pages: 10
Characters: 22839
Updates: RFC 6514
I-D Tag: draft-ietf-l3vpn-mvpn-mldp-nlri-10.txt
URL: https://www.rfc-editor.org/info/rfc7441
Many service providers offer "BGP/MPLS IP VPN" service to their
customers. Existing IETF standards specify the procedures and
protocols that a service provider uses in order to offer this service
to customers who have IP unicast and IP multicast traffic in their
VPNs. It is also desirable to be able to support customers who have
MPLS multicast traffic in their VPNs. This document specifies the
procedures and protocol extensions that are needed to support
customers who use the Multipoint LDP (mLDP) as the control protocol for
their MPLS multicast traffic. Existing standards do provide some support
for customers who use mLDP, but only under a restrictive set of
circumstances. This document generalizes the existing support to include
all cases where the customer uses mLDP, without any restrictions. This
document updates RFC 6514.
This document is a product of the BGP Enabled Services Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
