UDP Checksum Trailer in Timing Protocols
draft-mizrahi-tictoc-checksum-trailer-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tal Mizrahi | ||
| Last updated | 2011-07-04 | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
Various time synchronization and delay measurement protocols are transported over UDP, e.g., PTP, NTP, and OWAMP/TWAMP. These protocols use timestamped packets that often have to be modified by intermediate nodes in the network. In such cases the UDP checksum field must be updated to reflect these modifications. The IEEE 1588 standard suggests to append 2 octets to every protocol message, allowing intermediate nodes to reflect the checksum modification in the last 2 octets rather than in the UDP checksum field. This document generalizes this concept, and defines a UDP Checksum Trailer for NTP and for OWAMP/TWAMP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)