OAM for L2 VPN Networks Using CFM and VCCV
draft-stokes-l2vpn-cfm-vccv-oam-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Olen Stokes | ||
| Last updated | 2007-11-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 IEEE has defined P802.1ag Connectivity Fault Management (CFM) for managing bridged LAN networks. The IETF has defined L2 Virtual Private Networks (VPNs) that provide an emulated LAN service for such bridged networks. These L2 VPNs are created using a collection of one or more point-to-point pseudo wires (PWs). The IETF has also defined Virtual Circuit Connectivity Verification (VCCV) for managing these PWs. This memo discusses the ability of a combination of CFM and VCCV to meet the OAM requirements of a L2 VPN.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)