Network Time Protocol: TCP Services
draft-stenn-ntp-tcp-services-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Harlan Stenn , Professor David L. Mills , Philip Prindeville | ||
| Last updated | 2019-01-03 (Latest revision 2018-07-02) | ||
| 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
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
Professor David L. Mills
Philip Prindeville
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)