Skip to main content

Global Table Multicast with BGP-MVPN Procedures
draft-zzhang-l3vpn-mvpn-global-table-mcast-04

Document Type Replaced Internet-Draft (l3vpn WG)
Expired & archived
Authors Zhaohui (Jeffrey) Zhang , Lenny Giuliano , Eric C. Rosen , Karthik Subramanian , Dante Pacella , Jason Schiller
Last updated 2014-05-12
Replaced by draft-ietf-l3vpn-mvpn-global-table-mcast
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-l3vpn-mvpn-global-table-mcast
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

RFC6513, RFC6514, and other RFCs describe protocols and procedures which a Service Provider (SP) may deploy in order offer Multicast Virtual Private Network (Multicast VPN or MVPN) service to its customers. Some of these procedures use BGP to distribute VPN- specific multicast routing information across a backbone network. With a small number of relatively minor modifications, the very same BGP procedures can also be used to distribute multicast routing information that is not specific to any VPN. Multicast that is outside the context of a VPN is known as "Global Table Multicast", or sometimes simply as "Internet multicast". In this document, we describe the modifications that are needed to use the MVPN BGP procedures for Global Table Multicast.

Authors

Zhaohui (Jeffrey) Zhang
Lenny Giuliano
Eric C. Rosen
Karthik Subramanian
Dante Pacella
Jason Schiller

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)