On Scalability of In-situ OAM

Document Type Expired Internet-Draft (individual)
Authors Haoyu Song  , Tianran Zhou 
Last updated 2017-12-29 (latest revision 2017-06-27)
Stream (None)
Intended RFC status (None)
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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document describes several potential scalability issues when implementing in-situ OAM based on the current in-situ OAM documents and proposes the corresponding solutions and modifications to the current in-situ OAM specification. Specifically, we extend in-situ OAM to support more standard tracing data than is currently defined and add new features to avoid limitations on MTU, bandwidth, forwarding path length, and node processing capability. We provide use cases to motivate our proposal and base the changes on the current in-situ OAM header format specification.


Haoyu Song (haoyu.song@huawei.com)
Tianran Zhou (zhoutianran@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)