Controlled Return Path for Service Function Chain (SFC) OAM
draft-ao-sfc-oam-return-path-specified-06
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Greg Mirsky , Ting Ao , Zhonghua Chen | ||
| Last updated | 2020-12-05 (Latest revision 2020-06-03) | ||
| Replaced by | draft-ietf-sfc-multi-layer-oam, draft-ietf-sfc-multi-layer-oam, RFC 9516 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 an extension to the Service Function Chain (SFC) Operation, Administration and Maintenance (OAM) that enables control of the Echo Reply return path directing it over a Reverse Service Function Path. Enforcing the specific return path can be used to verify the bidirectional connectivity of SFC and increase the robustness of SFC OAM.
Authors
Greg Mirsky
Ting Ao
Zhonghua Chen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)