RFC 7441 on Encoding Multipoint LDP (mLDP) Forwarding Equivalence Classes (FECs) in the NLRI of BGP MCAST-VPN Routes

rfc-editor@rfc-editor.org Fri, 23 January 2015 04:28 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C2E71A01A5; Thu, 22 Jan 2015 20:28:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h8oB9iZbc3hT; Thu, 22 Jan 2015 20:28:42 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 139CF1A1A6B; Thu, 22 Jan 2015 20:28:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5D89F187E26; Thu, 22 Jan 2015 20:28:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7441 on Encoding Multipoint LDP (mLDP) Forwarding Equivalence Classes (FECs) in the NLRI of BGP MCAST-VPN Routes
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150123042813.5D89F187E26@rfc-editor.org>
Date: Thu, 22 Jan 2015 20:28:13 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/_4YUFW67UPtTNAKwVX83CBwtaWU>
Cc: drafts-update-ref@iana.org, bess@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 04:28:47 -0000

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