Active OAM for Service Function Chains in Networks
draft-wang-sfc-multi-layer-oam-12
| Document | Type | Replaced Internet-Draft (sfc WG) | |
|---|---|---|---|
| Last updated | 2018-10-26 (latest revision 2018-10-08) | ||
| Replaced by | draft-ietf-sfc-multi-layer-oam | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-sfc-multi-layer-oam | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-wang-sfc-multi-layer-oam-12.txt
Abstract
A set of requirements for active Operation, Administration and Maintenance (OAM) of Service Function Chains (SFCs) in networks is presented. Based on these requirements an encapsulation of active OAM message in SFC and a mechanism to detect and localize defects described. Also, this document updates RFC 8300 in the definition of O (OAM) bit in the Network Service Header (NSH) and defines how the active OAM message identified in SFC NSH.
Authors
Gregory Mirsky
(gregimirsky@gmail.com)
Wei Meng
(unknown-email-Wei-Meng)
Bhumip Khasnabish
(bhumip.khasnabish@ztetx.com)
Cui(Linda) Wang
(lindawangjoy@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)