Pseudowire Virtual Circuit Connectivity Verification (VCCV): An Inband Control Channel using offset
draft-kini-pwe3-inband-cc-offset-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Sriganesh Kini , Dave Sinicrope | ||
Last updated | 2011-03-14 | ||
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
Pseudowires need an inband control channel (CC) to do VCCV such that OAM and data packets follow the same path. PWs without a Control Word (CW) do not have an inband CC as defined in RFC5085. This document defines a simple extension to the TTL expiry CC (Type 3) to do inband VCCV. This can be used even without a CW.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)