Integrity of In-situ OAM Data Fields
draft-brockners-ippm-ioam-data-integrity-03
Document | Type |
Replaced Internet-Draft
(ippm WG)
Expired & archived
|
|
---|---|---|---|
Authors | Frank Brockners , Shwetha Bhandari , Tal Mizrahi | ||
Last updated | 2021-08-18 (Latest revision 2021-07-31) | ||
Replaced by | draft-ietf-ippm-ioam-data-integrity | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-ippm-ioam-data-integrity | |
Consensus boilerplate | Unknown | ||
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. IOAM deployments could require ensuring the integrity of IOAM data fields. This document specifies methods to ensure the integrity of IOAM data fields.
Authors
Frank Brockners
Shwetha Bhandari
Tal Mizrahi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)