Using UDP Checksum Trailers in the Network Time Protocol (NTP)
draft-ietf-ntp-checksum-trailer-01

The information below is for an old version of the document
Document Type Expired Internet-Draft (ntp WG)
Last updated 2015-07-20 (latest revision 2015-01-15)
Replaces draft-mizrahi-ntp-checksum-trailer
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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
https://www.ietf.org/archive/id/draft-ietf-ntp-checksum-trailer-01.txt

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

Tal Mizrahi (talmi@marvell.com)

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