NTP Client Data Minimization
draft-ietf-ntp-data-minimization-01
Network Working Group D. Franke
Internet-Draft Akamai
Updates: 5905 (if approved) A. Malhotra
Intended status: Standards Track Boston University
Expires: January 28, 2018 July 27, 2017
NTP Client Data Minimization
draft-ietf-ntp-data-minimization-01
Abstract
This memo proposes backward-compatible updates to the Network Time
Protocol to strip unnecessary identifying information from client
requests and to improve resilience against blind spoofing of
unauthenticated server responses.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 28, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Franke & Malhotra Expires January 28, 2018 [Page 1]
Internet-Draft NTP Client Data Minimization July 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. Client Packet Format . . . . . . . . . . . . . . . . . . . . 2
4. Security and Privacy Considerations . . . . . . . . . . . . . 3
4.1. Data Minimization . . . . . . . . . . . . . . . . . . . . 3
4.2. Transmit Timestamp Randomization . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
Network Time Protocol (NTP) packets, as specified by RFC 5905
[RFC5905], carry a great deal of information about the state of the
NTP daemon which transmitted them. In the case of mode 4 packets
(responses sent from server to client), as well as in broadcast (mode
5) and symmetric peering modes (mode 1/2), most of this information
is essential for accurate and reliable time synchronizaton. However,
in mode 3 packets (requests sent from client to server), most of
these fields serve no purpose. Server implementations never need to
inspect them, and they can achieve nothing by doing so. Populating
these fields with accurate information is harmful to privacy of
clients because it allows a passive observer to fingerprint clients
and track them as they move across networks.
This memo updates RFC 5905 to redact unnecessary data from mode 3
packets. This is a fully backwards-compatible proposal. It calls
for no changes on the server side, and clients which implement these
updates will remain fully interoperable with existing servers.
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. Client Packet Format
In every client-mode packet sent by a Network Time Protocol [RFC5905]
Show full document text