SFC OAM for path consistency

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Ting Ao  , Greg Mirsky  , Zhonghua Chen  , Kent Leung 
Last updated 2020-06-03 (latest revision 2019-12-01)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 active OAM method to support SFC consistency check, i.e. verification that all elements of the given SFC are being traversed in the expected order.


Ting Ao (18555817@qq.com)
Greg Mirsky (gregimirsky@gmail.com)
Zhonghua Chen (18918588897@189.cn)
Kent Leung (kleung@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)