SFC OAM for path consistency
draft-ao-sfc-oam-path-consistency-03
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | None Internet-Draft (individual) | |
Last updated | 2018-10-19 | ||
Stream | (None) | ||
Intended RFC status | (None) | ||
Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
Additional URLs |
|
||
Stream | Stream state | (No stream defined) | |
Consensus Boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Unknown state | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ao-sfc-oam-path-consistency-03.txt
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
(ao.ting@zte.com.cn)
Gregory Mirsky
(gregimirsky@gmail.com)
Zhonghua Chen
(18918588897@189.cn)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)