IETF Logo Mail Archive

Re: [TLS] publishing ESNIKeys under a .well-known URI...

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 26 June 2019 15:58 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80798120059 for <tls@ietfa.amsl.com>; Wed, 26 Jun 2019 08:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d-biZaIz12YI for <tls@ietfa.amsl.com>; Wed, 26 Jun 2019 08:58:10 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAE9012004F for <tls@ietf.org>; Wed, 26 Jun 2019 08:58:10 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 496FC3808A; Wed, 26 Jun 2019 11:56:26 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id CAE1DE68; Wed, 26 Jun 2019 11:58:09 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C9512E37; Wed, 26 Jun 2019 11:58:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: "tls@ietf.org" <tls@ietf.org>
In-Reply-To: <7374648a-d684-87be-0807-219bc10793ac@cs.tcd.ie>
References: <7374648a-d684-87be-0807-219bc10793ac@cs.tcd.ie>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 26 Jun 2019 11:58:09 -0400
Message-ID: <18514.1561564689@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/7VORWbW1O662n60Ov14ScaAjq1s>
Subject: Re: [TLS] publishing ESNIKeys under a .well-known URI...
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2019 15:58:13 -0000

Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
    > My web server doesn't have an API it can use to update
    > ESNIKeys in the DNS. Many implementations/deployments may
    > have such an API but in my case, the zone file that
    > includes the ESNIKeys RR is on another machine and the
    > web server doesn't have write access to that. I do
    > control both machines as it happens, but I still don't
    > want to give general write-access to the web server.

When you say, "general write-access", did you mean that you didn't want to
setup Dynamic DNS to be able to update the QNAMEs involved, because that
usually permits the web server to delete A and AAAA records, as well as
updating the ESNI ?

Or did you mean "general write-access", meaning NFS or something like that?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email