Control In-situ OAM Overhead with Segment IOAM
draft-song-ippm-segment-ioam-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Haoyu Song , Tianran Zhou | ||
| Last updated | 2018-10-19 (Latest revision 2018-04-17) | ||
| 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
This document describes a proposal which partitions an in-situ OAM (iOAM) domain into multiple segments in order to control the iOAM data overhead, adapt to the path MTU limitations, and enable new applications. We discuss several use cases to motivate our proposal and base the necessary modifications on the current in-situ OAM header format specification.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)