Network Time Protocol: TCP Services
draft-stenn-ntp-tcp-services-00

Document Type Expired Internet-Draft (individual)
Last updated 2019-01-03 (latest revision 2018-07-02)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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
https://www.ietf.org/archive/id/draft-stenn-ntp-tcp-services-00.txt

Abstract

NTP was assigned port number 123 in 1985, in RFC 960. Traditionally, it has only used the UDP port as while UDP is useful for time synchronization, TCP is not suitable for time synchronization. UDP packet have length limits, and there are rate limits imposed by the protocol specification. Between the UDP packet length and rate limits, some other mechanism must be provided for efficient exchange of larger data packets. A TCP connection can be used for these uses. Additionally, we can perform better authentication and authorization checks using a TCP connection.

Authors

Harlan Stenn (stenn@nwtime.org)
David Mills (mills@udel.edu)
Philip Prindeville (prindeville@ntp.org)

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