SFC OAM for path consistency
draft-ao-sfc-oam-path-consistency-11

Document Type Replaced Internet-Draft (individual)
Authors Greg Mirsky  , Ting Ao  , Zhonghua Chen  , Kent Leung  , Gyan Mishra 
Last updated 2021-10-01 (latest revision 2021-03-30)
Replaced by draft-ietf-sfc-multi-layer-oam
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text html xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sfc-multi-layer-oam
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
https://www.ietf.org/archive/id/draft-ao-sfc-oam-path-consistency-11.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 due to classification. SFC Operation, Administration and Maintenance can monitor the continuity of the SFC, i.e., that all SFC elements 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 to 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.

Authors

Greg Mirsky (gregimirsky@gmail.com)
Ting Ao (18555817@qq.com)
Zhonghua Chen (18918588897@189.cn)
Kent Leung (kleung@cisco.com)
Gyan Mishra (gyan.s.mishra@verizon.com)

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