Considerations about Multicast for BGP/MPLS VPN Standardization
draft-morin-l3vpn-mvpn-considerations-03

 
Document Type Replaced Internet-Draft (individual)
Last updated 2010-01-15 (latest revision 2008-07-11)
Replaced by draft-ietf-l3vpn-mvpn-considerations
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
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
https://www.ietf.org/archive/id/draft-morin-l3vpn-mvpn-considerations-03.txt

Abstract

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.

Authors

Thomas Morin (thomas.morin@orange-ftgroup.com)
Ben Niven-Jenkins (benjamin.niven-jenkins@bt.com)
Yuji Kamite (y.kamite@ntt.com)
Raymond Zhang (raymond.zhang@bt.com)
Nicolai Leymann (nicolai.leymann@t-systems.com)
Nabil Bitar (nabil.n.bitar@verizon.com)

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