Extended OAM to Carry In-situ OAM Configuration Data
draft-xiao-ippm-ioam-conf-state-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Xiao Min , Greg Mirsky | ||
| Last updated | 2018-05-01 (Latest revision 2017-10-28) | ||
| Replaced by | draft-ietf-ippm-ioam-conf-state, RFC 9359 | ||
| 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 describes an extension for OAM packet such as IP Ping (ICMP [RFC0792] or ICMPv6 [RFC4443]) and MPLS LSP Ping [RFC8029], which can be used within an IOAM domain, allowing the IOAM encapsulating node to acquire IOAM configuration data of each IOAM transit node and/or IOAM decapsulating node easily and dynamically.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)