Controlled Return Path for Service Function Chain (SFC) OAM
draft-ao-sfc-oam-return-path-specified-01
| 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-04-30 (Latest revision 2017-10-27) | ||
| 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
This document defines extensions to the Service Function Chain (SFC) Operation, Administration and Maintenance (OAM) that enable control of the Echo Reply return path by specifying it as Reverse Service Function Path. Enforcing the specific return path can be used to verify bidirectional connectivity of SFC and increase robustness of SFC OAM.
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.)