Considerations about Multicast for BGP/MPLS VPN Standardization

Document Type Replaced Internet-Draft (individual)
Authors Thomas Morin  , Ben Niven-Jenkins  , Yuji Kamite  , Raymond Zhang  , Nicolai Leymann  , Nabil Bitar 
Last updated 2010-01-15 (latest revision 2008-07-11)
Replaced by RFC 6517
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-l3vpn-mvpn-considerations
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


The current proposal for multicast in BGP/MPLS includes multiple alternative mechanisms for some of the required building blocks of the solution. The aim of this document is to leverage previously documented requirements to identify the key elements and help move forward solution design, toward the definition of a standard having a well defined set of mandatory procedures. The different proposed alternative mechanisms are examined in the light of requirements identified for multicast in L3VPNs, and suggestions are made about which of these mechanisms standardization should favor. Issues related to existing deployments of early implementations are also addressed.


Thomas Morin (
Ben Niven-Jenkins (
Yuji Kamite (
Raymond Zhang (
Nicolai Leymann (
Nabil Bitar (

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