Skip to main content

MVPN Profiles Using PIM Control Plane
draft-rosen-l3vpn-mvpn-profiles-03

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors A Boers , Yiqun Cai , Eric C. Rosen , IJsbrand Wijnands
Last updated 2009-06-29
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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 MVPN (Multicast Virtual Private Network) architecture is divided into a number of functional "layers". At each layer, multiple options are allowed. It is necessary to allow multiple options at each layer because "one size doesn't fit all." However, it is not expected that any particular implementation will support all the possible combinations of options. To ensure multi-vendor interoperability, it is useful to specify "profiles", where each profile is a particular combination of options. The number of specified profiles will be much less than the total number of possible combination, and a given implementation can be characterized by saying which profiles it supports. This document describes two profiles that use a PIM control plane.

Authors

A Boers
Yiqun Cai
Eric C. Rosen
IJsbrand Wijnands

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