Global Table Multicast with BGP-MVPN Procedures
draft-ietf-l3vpn-mvpn-global-table-mcast-00

Document Type Replaced Internet-Draft (bess WG)
Last updated 2014-10-22 (latest revision 2014-06-24)
Replaces draft-zzhang-l3vpn-mvpn-global-table-mcast
Replaced by draft-ietf-bess-mvpn-global-table-mcast
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd Thomas Morin
IESG IESG state Replaced by draft-ietf-bess-mvpn-global-table-mcast
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-l3vpn-mvpn-global-table-mcast-00.txt

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 Zhang (zzhang@juniper.net)
Leonard Giuliano (lenny@juniper.net)
Eric Rosen (erosen@cisco.com)
Karthik Subramanian (kartsubr@cisco.com)
Dante Pacella (dante.j.pacella@verizonbusiness.com)
Jason Schiller (jschiller@google.com)

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