BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
RFC 6514
Document | Type | RFC - Proposed Standard (February 2012; Errata) | |
---|---|---|---|
Authors | Yakov Rekhter , Rahul Aggarwal , Eric Rosen , Thomas Morin | ||
Last updated | 2015-10-14 | ||
Replaces | draft-raggarwa-l3vpn-2547bis-mcast-bgp | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6514 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Stewart Bryant | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) R. Aggarwal Request for Comments: 6514 Juniper Networks Category: Standards Track E. Rosen ISSN: 2070-1721 Cisco Systems, Inc. T. Morin France Telecom - Orange Y. Rekhter Juniper Networks February 2012 BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs Abstract This document describes the BGP encodings and procedures for exchanging the information elements required by Multicast in MPLS/BGP IP VPNs, as specified in RFC 6513. 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/rfc6514. Copyright Notice Copyright (c) 2012 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. Aggarwal, et al. Standards Track [Page 1] RFC 6514 BGP Encodings and Procedures for MVPNs February 2012 Table of Contents 1. Introduction ....................................................4 2. Specification of Requirements ...................................4 3. Terminology .....................................................4 4. MCAST-VPN NLRI ..................................................5 4.1. Intra-AS I-PMSI A-D Route ...................................6 4.2. Inter-AS I-PMSI A-D Route ...................................7 4.3. S-PMSI A-D Route ............................................7 4.4. Leaf A-D Route ..............................................8 4.5. Source Active A-D Route .....................................9 4.6. C-Multicast Route ..........................................10 5. PMSI Tunnel Attribute ..........................................10 6. Source AS Extended Community ...................................13 7. VRF Route Import Extended Community ............................14 8. PE Distinguisher Labels Attribute ..............................15 9. MVPN Auto-Discovery/Binding ....................................16 9.1. MVPN Auto-Discovery/Binding - Intra-AS Operations ..........16 9.1.1. Originating Intra-AS I-PMSI A-D Routes .................16 9.1.2. Receiving Intra-AS I-PMSI A-D Routes ...................19 9.2. MVPN Auto-Discovery/Binding - Inter-AS Operations ..........20 9.2.1. Originating Inter-AS I-PMSI A-D Routes .................22 9.2.2. When Not to Originate Inter-AS I-PMSI A-D Routes .......23 9.2.3. Propagating Inter-AS I-PMSI A-D Routes .................23 9.2.3.1. Propagating Inter-AS I-PMSI A-D Routes - Overview ..23 9.2.3.2. Inter-AS I-PMSI A-D Route Received via EBGP ........24 9.2.3.2.1. Originating Leaf A-D Route into EBGP ...........25 9.2.3.3. Leaf A-D Route Received via EBGP ...................26 9.2.3.4. Inter-AS I-PMSI A-D Route Received via IBGP ........27 9.2.3.4.1. Originating Leaf A-D Route into IBGP ...........28 9.2.3.5. Leaf A-D Route Received via IBGP ...................29 9.2.3.6. Optimizing Bandwidth by IP Filtering on ASBRs ......30 10. Non-Congruent Unicast and Multicast Connectivity ..............30 11. Exchange of C-Multicast Routing Information among PEs .........32 11.1. Originating C-Multicast Routes by a PE ....................32 11.1.1. Originating Routes: PIM as the C-Multicast Protocol ...32 11.1.1.1. Originating Source Tree Join C-Multicast Route ....33 11.1.1.2. Originating Shared Tree Join C-Multicast Route ....33 11.1.2. Originating Routes: mLDP as the C-Multicast Protocol ..34Show full document text