An Update to the OAM Behavior in the Network Service Header (NSH)
draft-boucadair-sfc-oam-packet-03
| Document | Type |
Replaced Internet-Draft
(candidate for sfc WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Mohamed Boucadair | ||
| Last updated | 2022-03-24 (Latest revision 2022-02-24) | ||
| Replaced by | draft-ietf-sfc-oam-packet | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sfc-oam-packet | |
| Consensus boilerplate | Yes | ||
| 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 clarifies an ambiguity in the Network Service Header (NSH) specification related to the handling of O bit. In particular, this document clarifies the meaning of "OAM packet". This document updates RFC 8300.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)