Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000240330D
Original Publication Date: 2015-Jan-01
Included in the Prior Art Database: 2015-Jan-24
Document File: 20 page(s) / 23K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

IJ. Wijnands: AUTHOR [+3]

Abstract

Many service providers (SPs) offer BGP/MPLS IP VPN service to their customers. When a customer has IP multicast traffic in its VPN, the service provider needs to signal the customer multicast states across the backbone. A customer with IP multicast traffic is typically using PIM (Protocol Independent Multicast) [PIM] and/or IGMP (Internet Group Management Protocol) [IGMP] as the multicast control protocol in its VPN. The IP multicast states of these protocols are commonly denoted as "(S,G)" and/or "(*,G)" states, where "S" is a multicast source address and "G" is a multicast group address. [MVPN-BGP] specifies the way an SP may use BGP to signal a customer's IP multicast states across the SP backbone. This is done by using Multiprotocol BGP Updates whose Subsequent Address Family Identifier (SAFI) values contain the codepoint for MCAST-VPN (as defined in [MVPN-BGP]). The NLRI (Network Layer Reachability Information) field of these BGP Updates includes a customer Multicast Source field and a customer Multicast Group field, thus enabling the customer's (S,G) or (*,G) states to be encoded in the NLRI.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Internet Engineering Task Force (IETF)                      IJ. Wijnands Request for Comments: 7441                           Cisco Systems, Inc. Updates: 6514                                                   E. Rosen Category: Standards Track                         Juniper Networks, Inc. ISSN: 2070-1721                                                U. Joorde                                                         Deutsche Telekom                                                             January 2015

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

Abstract

   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.

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/rfc7441.

 Wijnands, et al.            Standards Track                     [Page 1]
 RFC 7441        mLDP FECs in NLRI of BGP MCAST-VPN Routes   January 2015

 Copyright Notice

   Copyright (c) 2015 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   ...