datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

A Simple Method for Segmenting Multicast Tunnels for Multicast VPNs
draft-rosen-l3vpn-mvpn-segments-05

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-10-12 (latest revision 2013-04-10)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-rosen-l3vpn-mvpn-segments

Abstract

To provide Multicast VPN (MVPN) Service, Service Providers (SPs) need to instantiate multicast tunnels (known as "P-tunnels") that enable the Provider Edge (PE) routers of a given VPN to transmit multicast packets to each other. Some SPs organize their networks in a hierarchical manner, with the PE routers in "edge areas", and the edge areas connected to each other via a "core area". A P-tunnel that connects PE routers in different edge areas can be thought of as having three segments: a segment through one edge area, a segment through the core area, and a segment through the second edge area. It is desirable to preserve the independence of the core area by allowing it to use a different tunneling technology than that used in the edge areas. However, it is not desirable for the core area Border Routers (BRs) to participate in the MVPN-specific signaling, or even to have any knowledge of which MVPNs are in the edge areas that attach to it. This document specifies a simple method for segmenting MVPN P-tunnels at the BRs, subject to these constraints.

Authors

Maria Napierala <mnapierala@att.com>
Eric Rosen <erosen@cisco.com>

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