Using UDP Checksum Trailers in the Network Time Protocol (NTP)
draft-mizrahi-ntp-checksum-trailer-02
| Document | Type |
Replaced Internet-Draft
(candidate for ntp WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Tal Mizrahi | ||
| Last updated | 2014-07-31 (Latest revision 2014-04-15) | ||
| Replaced by | draft-ietf-ntp-checksum-trailer, draft-ietf-ntp-checksum-trailer, RFC 7821 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ntp-checksum-trailer, draft-ietf-ntp-checksum-trailer | |
| 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
The Network Time Protocol (NTP) allows clients to synchronize to a time server using timestamped protocol messages. To faciliate accurate timestamping, some implementations use hardware-based timestamping engines that integrate the accurate transmission time into every outgoing NTP packet during transmission. Since these packets are transported over UDP, the UDP checksum field is then updated to reflect this modification. This document proposes an extension field that includes a 2-octet Checksum Trailer, allowing timestamping engines to reflect the checksum modification in the last 2 octets of the packet rather than in the UDP checksum field. The behavior defined in this document is interoperable with existing NTP implementations.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)