Testing Hierarchical Virtual Private LAN Services
draft-stokes-vkompella-ppvpn-hvpls-oam-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Olen Stokes , Vach Kompella , Giles Heron , Yetik Serbest | ||
| Last updated | 2003-07-03 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-stokes-vkompella-ppvpn-hvpls-oam-02.txt
Abstract
This document describes a methodology for testing the operation, administration and maintenance (OA&M) of a general VPN service, that is applied here to Hierarchical Virtual Private LAN Services (HVPLS) as described in [VPLS]. As part of this methodology, the MPLS ping concepts described in [LSP- PING] are extended to enable HVPLS spoke-to-spoke connectivity testing. A method to provide the information necessary for this spoke-to-spoke OA&M is also proposed. These are the goals of this draft: - checking connectivity between 'service-aware' nodes of a network, - verifying data plane and control plane integrity, - verifying service membership There are two specific requirements to which we call attention because of their seemingly contradictory nature: - the checking of connectivity MUST involve the ability to use packets that look like customer packets - the OAM packets MUST not propagate beyond the boundary of the provider network
Authors
Olen Stokes
Vach Kompella
Giles Heron
Yetik Serbest
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)