Deployment Considerations for In-situ OAM with IPv6 Options
draft-ioametal-ippm-6man-ioam-ipv6-deployment-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shwetha Bhandari , Frank Brockners , Tal Mizrahi , Aviv Kfir , Barak Gafni , Mickey Spiegel , Suresh Krishnan , Mark Smith | ||
| Last updated | 2020-09-30 (Latest revision 2020-03-29) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
In-situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document outlines how IOAM can be enabled in an IPv6 network.
Authors
Shwetha Bhandari
Frank Brockners
Tal Mizrahi
Aviv Kfir
Barak Gafni
Mickey Spiegel
Suresh Krishnan
Mark Smith
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)