Wildcards in Multicast VPN Auto-Discovery Routes
draft-rosen-l3vpn-mvpn-wldcds-cmbind-00

 
Document Type Replaced Internet-Draft (individual)
Last updated 2011-11-01 (latest revision 2011-08-29)
Replaced by draft-ietf-l3vpn-mvpn-wildcards
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-wildcards
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-rosen-l3vpn-mvpn-wldcds-cmbind-00.txt

Abstract

In "Multicast Virtual Private Networks" (MVPNs), customer multicast flows are carried in "tunnels" through a service provider's network. The base specifications for MVPN define BGP multicast VPN "auto-discovery" routes", and specify how to use an auto-discovery route to advertise the fact that an individual customer multicast flow is being carried in a particular tunnel. However, those specifications do not provide a way to specify, in a single such route, that multiple customer flows are being carried in a single tunnel. Those specifications also do not provide a way to advertise that a particular tunnel is to be used by default to carry all customer flows, except in the case where that tunnel is joined by all the provider edge routers of the MVPN. This document eliminates these restrictions by specifying the use of "wildcard" elements in the customer flow identifiers. With wildcard elements, a single auto-discovery route can refer to multiple customer flows, or even to all customer flows.

Authors

Ray Qiu (rayq@huawei.com)
Eric Rosen (erosen@cisco.com)
Yakov Rekhter (yakov@juniper.net)

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