A well-known URI for publishing ESNIKeys
draft-farrell-tls-wkesni-01

Document Type Active Internet-Draft (individual)
Last updated 2019-07-05
Stream (None)
Intended RFC status (None)
Formats plain text 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)
TLS                                                           S. Farrell
Internet-Draft                                    Trinity College Dublin
Intended status: Experimental                               July 5, 2019
Expires: January 6, 2020

                A well-known URI for publishing ESNIKeys
                      draft-farrell-tls-wkesni-01

Abstract

   We propose use of a well-known URI at which web servers can publish
   ESNIKeys as a way to help get those published in the DNS.

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 January 6, 2020.

Copyright Notice

   Copyright (c) 2019 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.

Farrell                  Expires January 6, 2020                [Page 1]
Internet-Draft           Well-Known URI for ESNI               July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Example use of the well-known URI for ESNI  . . . . . . . . .   3
   4.  The esni well-known URI . . . . . . . . . . . . . . . . . . .   3
   5.  The JSON structure for ESNIKeys . . . . . . . . . . . . . . .   4
   6.  Zone factory behaviour  . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Encrypted Server Name Indication (ESNI) [I-D.ietf-tls-esni] for
   TLS1.3 [RFC8446] defines a confidentiality mechanism for server names
   in TLS.  That requires publication of an ESNIKeys data structure in
   the DNS.  An ESNIKeys structure contains the public component of a
   key pair that will typically be periodically (re-)generated by a web
   server.  Many web servers will have an API that can be used to
   dynamically update ESNIKeys in the DNS.  Some implementations/
   deployments however, will not, so web server implementers could
   benefit from a mechanism to use in such cases.

   We define such a mechanism here.  Note that this is not intended for
   universal deployment, but just for cases where the zone file (or
   equivalent) that includes the ESNIKeys RR is on some machine, which
   we here call a "zone factory," to which the web server doesn't have
   write access.

   We propose use of a well-known URI [RFC8615] on the web server that
   allows the zone factory for that web server to poll for changes to
   ESNIKeys RR values.  For example, if a web server generates new
   ESNIKeys hourly and publishes those at the well-known URI, its zone
   factory server can poll that URI.  When the zone factory sees new
   values, it can check if those work, and if they do, then update the
   zone file and re-publish the zone.

   [[This idea could: a) wither on the vine, b) be published as it's own
   RFC, or c) end up as a PR for [I-D.ietf-tls-esni].  There is no
   absolute need for this to be in the RFC that defines ESNI, so (b)
   seems feasible if there's enough interest, hence this draft.  The
   source for this is in https://github.com/sftcd/wkesni/ PRs are
   welcome there too.]]

Farrell                  Expires January 6, 2020                [Page 2]
Internet-Draft           Well-Known URI for ESNI               July 2019

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Show full document text