Use of Wildcard in S-PMSI Auto-Discovery Routes
draft-rekhter-mvpn-wildcard-spmsi-04

Document Type Replaced Internet-Draft (individual)
Last updated 2011-11-01 (latest revision 2011-02-14)
Replaced by draft-ietf-l3vpn-mvpn-wildcards
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
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-rekhter-mvpn-wildcard-spmsi-04.txt

Abstract

The current MVPN specifications do not define encoding and procedures for advertising in a single route binding of multiple multicast streams of a given MVPN customer to a single provider's tunnel. This document defines such encoding and procedures. These procedures allow in certain situations to reduce MVPN control plane load (note though that these procedures have no impact on the data plane load). The procedures specified in this document assume that BGP is used for transmission of MVPN customers' routing information within the service provider(s) infrastructure.

Authors

Rahul Aggarwal (raggarwa_1@yahoo.com)
Wim Henderickx (wim.henderickx@alcatel-lucent.be)
Praveen Muley (Praveen.muley@alcatel-lucent.com)
Ray Qiu (rayq@huawei.com)
Yakov Rekhter (yakov@juniper.net)

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