BIER Encapsulation for IOAM Data
draft-xzlnp-bier-ioam-06
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Xiao Min , Zheng Zhang , Yisong Liu , Nagendra Kumar Nainar , Carlos Pignataro | ||
| Last updated | 2024-02-01 (Latest revision 2023-07-31) | ||
| RFC stream | (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) collects operational and telemetry information in the packet while the packet traverses a path between two points in the network. Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "multicast domain", without requiring intermediate routers to maintain any per-flow state or to engage in an explicit tree-building protocol. The BIER header contains a bit- string in which each bit represents exactly one egress router to forward the packet to. This document outlines the requirements to carry IOAM data in BIER header and specifies how IOAM data is encapsulated in BIER header.
Authors
Xiao Min
Zheng Zhang
Yisong Liu
Nagendra Kumar Nainar
Carlos Pignataro
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)