Skip to main content

Path Tracing in SRv6 networks
draft-filsfils-spring-path-tracing-05

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Clarence Filsfils , Ahmed Abdelsalam , Pablo Camarillo , Mark Yufit , Thomas Graf , Yuanchao Su , Satoru Matsushima , Mike Valentine , Amit Dhamija
Last updated 2023-10-23
Replaced by draft-filsfils-ippm-path-tracing
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-filsfils-ippm-path-tracing
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

Path Tracing provides a record of the packet path as a sequence of interface ids. In addition, it provides a record of end-to-end delay, per-hop delay, and load on each egress interface along the packet delivery path. Path Tracing allows to trace 14 hops with only a 40-bytes IPv6 Hop- by-Hop extension header. Path Tracing supports fine grained timestamp. It has been designed for linerate hardware implementation in the base pipeline.

Authors

Clarence Filsfils
Ahmed Abdelsalam
Pablo Camarillo
Mark Yufit
Thomas Graf
Yuanchao Su
Satoru Matsushima
Mike Valentine
Amit Dhamija

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