L2VPN Interworking
draft-sajassi-l2vpn-interworking-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ali Sajassi | ||
| Last updated | 2003-03-07 | ||
| 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 need to support L2VPN services with disparate Attachment Circuits (heterogeneous transport) is becoming as important as the support of L2VPN services with the same type of Attachment Circuits (homogenous transport). To support L2VPN services with heterogeneous transport, some means of interworking is needed. The requirement to support L2VPN interworking is stated in [PPVPN-L2FRWK]. This document describes different approaches and mechanisms that can be used to provide L2VPN interworking among disparate interfaces.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)