Multicast On-path Telemetry using IOAM
draft-ietf-mboned-multicast-telemetry-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Haoyu Song , Mike McBride , Greg Mirsky , Gyan Mishra , Hitoshi Asaeda , Tianran Zhou | ||
| Last updated | 2023-02-12 (Latest revision 2022-08-11) | ||
| Replaces | draft-song-multicast-telemetry | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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
This document discusses the requirements of on-path telemetry for multicast traffic using In-situ OAM. Applying In-situ OAM for multicast telemetry presents some unique challenges. This document provides the solutions based on the In-situ OAM trace option and direct export option to support the telemetry data correlation and the multicast tree reconstruction without collecting redundant data.
Authors
Haoyu Song
Mike McBride
Greg Mirsky
Gyan Mishra
Hitoshi Asaeda
Tianran Zhou
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)