Roughtime
draft-ietf-ntp-roughtime-00
Internet Engineering Task Force A. Malhotra
Internet-Draft Boston University
Intended status: Informational A. Langley
Expires: July 30, 2020 Google
W. Ladd
Cloudflare
January 27, 2020
Roughtime
draft-ietf-ntp-roughtime-00
Abstract
This document specifies Roughtime - a protocol that aims to achieve
rough time synchronization while detecting servers that provide
inaccurate time and providing cryptographic proof of their
malfeasance.
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 https://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 July 30, 2020.
Copyright Notice
Copyright (c) 2020 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
(https://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
Malhotra, et al. Expires July 30, 2020 [Page 1]
Internet-Draft Roughtime January 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 4
4. The guarantee . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Message Format . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Data Types . . . . . . . . . . . . . . . . . . . . . . . 6
5.1.1. uint32 . . . . . . . . . . . . . . . . . . . . . . . 6
5.1.2. uint64 . . . . . . . . . . . . . . . . . . . . . . . 6
5.1.3. Tag . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1.4. Timestamp . . . . . . . . . . . . . . . . . . . . . . 7
5.2. Header . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Requests . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2. Responses . . . . . . . . . . . . . . . . . . . . . . . . 8
6.3. The Merkle Tree . . . . . . . . . . . . . . . . . . . . . 9
6.3.1. Root value validity check algorithm . . . . . . . . . 10
6.4. Validity of response . . . . . . . . . . . . . . . . . . 10
7. Integration into ntp . . . . . . . . . . . . . . . . . . . . 10
8. Cheater Detection . . . . . . . . . . . . . . . . . . . . . . 11
9. Grease . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
10. Roughtime Servers . . . . . . . . . . . . . . . . . . . . . . 12
11. Trust anchors and policies . . . . . . . . . . . . . . . . . 12
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
13.1. Service Name and Transport Protocol Port Number Registry 13
13.2. Roughtime Tag Registry . . . . . . . . . . . . . . . . . 13
14. Security Considerations . . . . . . . . . . . . . . . . . . . 14
15. Privacy Considerations . . . . . . . . . . . . . . . . . . . 15
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
16.1. Normative References . . . . . . . . . . . . . . . . . . 15
16.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Terms and Abbreviations . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
Time synchronization is essential to Internet security as many
security protocols and other applications require synchronization
[RFC7384] [MCBG]. Unfortunately widely deployed protocols such as
Show full document text