NTS for the NTP pool
draft-ladd-nts-for-ntp-pool-00

Document Type Active Internet-Draft (individual)
Last updated 2020-02-28
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
NTP                                                              W. Ladd
Internet-Draft                                                Cloudflare
Intended status: Informational                          28 February 2020
Expires: 31 August 2020

                          NTS for the NTP pool
                     draft-ladd-nts-for-ntp-pool-00

Abstract

   Network Time Security authenticates NTP servers.  This document
   outlines an architecture that uses ACME and SRV records for the NTP
   pool to carry out NTS.

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 31 August 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 the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Ladd                     Expires 31 August 2020                 [Page 1]
Internet-Draft            NTS for the NTP Pool             February 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   2
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Clients . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Pool Members  . . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  Pool Operators  . . . . . . . . . . . . . . . . . . . . . . .   3
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   10. Informative References  . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   NTP is commonly provided via an NTP pool: a collection of servers
   behind a DNS load balanced and/or geolocated domain name.  However
   Network Time Security requires certificates associated to the
   hostname of a server.

2.  Conventions and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   The reader may wish to note that one of the two RFC references in the
   preceding paragraph was normative; the other was informative.  These
   will be correctly identified as such in the References section below.

3.  Background

   The NTP pool uses dynamic DNS techniques to spread the load of NTP
   over a wide variety of servers.  Unfortunately this creates
   challenges to the deployment of NTS: the servers all appear to share
   the same hostname of the pool, and would all need certificates for
   that hostname.

   To avoid these problems this draft presents a technique using SRV
   records and per-server hostnames along with ACME.

Ladd                     Expires 31 August 2020                 [Page 2]
Internet-Draft            NTS for the NTP Pool             February 2020

4.  Clients

   A client interested in using NTS with nts-pool.ntp.example.org will
   look up the SRV records for NTS-KE at nts-pool.ntp.example.org.  This
   SRV record will point to Fully Qualified Domain names of the form
   servername.servers.pool.ntp.example.org, here called pool associated
   domain names.

   Clients will then execute NTS-KE against the resolved IP address for
   those names, and continue as specified in
   [I-D.ietf-ntp-using-nts-for-ntp]

   Clients SHOULD obtain multiple servers from a pool lookup and treat
   them as independent sources.  If a source is unacceptable clients
   SHOULD replace them with new ones obtained from the pool.

   Clients MAY periodically resolve the pool associated domain names to
Show full document text