End-to-end Response Time Needed for IPv6 Diagnostics

Document Type Expired Internet-Draft (individual)
Authors Nalini Elkins  , Michael Ackermann  , William Jouris  , Keven Haining , Sigfrido Perdomo
Last updated 2014-04-06 (latest revision 2013-10-03)
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


To diagnose performance and connectivity problems, metrics on real (non-synthetic) transmission are critical for timely end-to-end problem resolution. Such diagnostics may be real-time or after the fact, but must not impact an operational production network. The base metrics are: packet sequence number and packet timestamp. Metrics derived from these will be described separately. This document provides the background and rationale for the requirement for end-to- end response time.


Nalini Elkins (nalini.elkins@insidethestack.com)
Michael Ackermann (mackermann@bcbsmi.com)
William Jouris (bill.jouris@insidethestack.com)
Keven Haining (keven.haining@usbank.com)
Sigfrido Perdomo (s.perdomo@dtcc.com)

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