Use of Wildcard in S-PMSI Auto-Discovery Routes
draft-rekhter-mvpn-wildcard-spmsi-04
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Rahul Aggarwal , Wim Henderickx , Praveen Muley , Ray Qiu , Yakov Rekhter | ||
Last updated | 2011-11-01 (Latest revision 2011-02-14) | ||
Replaced by | draft-ietf-l3vpn-mvpn-wildcards | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
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 | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Wim Henderickx
Praveen Muley
Ray Qiu
Yakov Rekhter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)