SFC OAM for path consistency
draft-ao-sfc-oam-path-consistency-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ting Ao , Greg Mirsky , Zhonghua Chen | ||
| Last updated | 2018-09-01 (Latest revision 2018-02-28) | ||
| Replaced by | draft-ietf-sfc-multi-layer-oam, draft-ietf-sfc-multi-layer-oam, RFC 9516 | ||
| RFC stream | (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
Service Function Chain (SFC) defines an ordered set of service functions (SFs) to be applied to packets and/or frames and/or flows selected as a result of classification. SFC Operation, Administration and Maintenance can monitor the continuity of the SFC, i.e., that all elements of the SFC are reachable to each other in the downstream direction. But SFC OAM must support verification that the order of traversing these SFs corresponds to the state defined by the SFC control plane or orchestrator, the metric referred in this document as the path consistency of the SFC. This document defines a new SFC OAM method to support SFC consistency, i.e. verification that all elements of the given SFC are being traversed in the expected order.
Authors
Ting Ao
Greg Mirsky
Zhonghua Chen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)