Segment Routing Header encapsulation for In-situ OAM Data
draft-ali-spring-ioam-srv6-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2020-05-06 (latest revision 2019-11-03) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ali-spring-ioam-srv6-02.txt
Abstract
OAM and PM information from the SR endpoints can be piggybacked in the data packet. The OAM and PM information piggybacking in the data packets is also known as In-situ OAM (IOAM). IOAM records operational and telemetry information in the data packet while the packet traverses a path between two points in the network. This document defines how IOAM data fields are transported as part of the Segment Routing with IPv6 data plane (SRv6) header.
Authors
Zafar Ali
(zali@cisco.com)
Rakesh Gandhi
(rgandhi@cisco.com)
Clarence Filsfils
(cf@cisco.com)
Frank Brockners
(fbrockne@cisco.com)
Nagendra Nainar
(naikumar@cisco.com)
Carlos Pignataro
(cpignata@cisco.com)
Cheng Li
(chengli13@huawei.com)
Mach Chen
(mach.chen@huawei.com)
Gaurav Dawra
(gdawra.ietf@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)