Re: Quic: the elephant in the room

Nico Williams <nico@cryptonector.com> Sun, 11 April 2021 19:59 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41E4A3A1BBD for <ietf@ietfa.amsl.com>; Sun, 11 Apr 2021 12:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
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 YghIKMk_yJ8Y for <ietf@ietfa.amsl.com>; Sun, 11 Apr 2021 12:59:01 -0700 (PDT)
Received: from bumble.maple.relay.mailchannels.net (bumble.maple.relay.mailchannels.net [23.83.214.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 853F93A1BC1 for <ietf@ietf.org>; Sun, 11 Apr 2021 12:59:01 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 905E254159D; Sun, 11 Apr 2021 19:59:00 +0000 (UTC)
Received: from pdx1-sub0-mail-a74.g.dreamhost.com (100-96-133-83.trex.outbound.svc.cluster.local [100.96.133.83]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 16470541869; Sun, 11 Apr 2021 19:59:00 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a74.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.133.83 (trex/6.1.1); Sun, 11 Apr 2021 19:59:00 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Harmony-Imminent: 036332a310001706_1618171140365_3686413056
X-MC-Loop-Signature: 1618171140364:710409260
X-MC-Ingress-Time: 1618171140364
Received: from pdx1-sub0-mail-a74.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a74.g.dreamhost.com (Postfix) with ESMTP id AF3AF7E790; Sun, 11 Apr 2021 12:58:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=Q6bUHAr0ZANSshyJ6hCLcy2CVGI=; b=Oer6E1cXe9a 3Vd3DvMv64iR8vTA9qbC8Vjuj8/9WplyfeUfQXCQcNnmwLHIEszCztlNU1M6YKAs xaOSG8cTqVN0J3pDidjz5PSD9R/nBKVq9x+oBNbHq4+GZkPOGI5msQayxxUz8kIR wcyGJKiqly+PF4HD2zOi9khC1xUe+cE4=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a74.g.dreamhost.com (Postfix) with ESMTPSA id 95F8E8306A; Sun, 11 Apr 2021 12:58:58 -0700 (PDT)
Date: Sun, 11 Apr 2021 14:58:55 -0500
X-DH-BACKEND: pdx1-sub0-mail-a74
From: Nico Williams <nico@cryptonector.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: Michael Thomas <mike@mtcc.com>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Quic: the elephant in the room
Message-ID: <20210411195854.GL9612@localhost>
References: <3b25c77d-e721-e86d-6c34-a90039aab0e2@mtcc.com> <CAMm+Lwhi8xwFgZJL7jod2g4urZt_f+dm0tNi+3y1osqOfch2mQ@mail.gmail.com> <3593a01f-73f4-7d03-a85b-dff64a8b070e@mtcc.com> <506A780B-9C0D-4F4A-B045-098F6152F4DB@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <506A780B-9C0D-4F4A-B045-098F6152F4DB@akamai.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ukYNUPVJ73lunNAR2ULiGc3XVEs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Apr 2021 19:59:05 -0000

On Sun, Apr 11, 2021 at 05:23:03PM +0000, Salz, Rich wrote:
>   *   I don't see why [DNS timeouts] it can't be long lived, but even normal TTL's would get amortized over a lot of connections. Right now with certs it is a 5 message affair which cannot get better. But that is why one of $BROWSERVENDORS doing an experiment would be helpful.
> 
> There are use-cases where a five-second DNS TTL is important.  And
> they’re not amortized over multiple connections from *one* user, but
> rather affect *many* users.  Imagine an e-commerce site connected to
> two CDN’s who needs to switch.

Not for DANE though.  If you want long-lived TLSA RRs + the ability to
quickly change keys, then use TLSA RRs to "certify" an intermediate PKIX
CA.