Re: Quic: the elephant in the room

Viktor Dukhovni <ietf-dane@dukhovni.org> Mon, 12 April 2021 15:54 UTC

Return-Path: <ietf-dane@dukhovni.org>
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 86B143A23A2 for <ietf@ietfa.amsl.com>; Mon, 12 Apr 2021 08:54:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 BE6YxqMSqXUj for <ietf@ietfa.amsl.com>; Mon, 12 Apr 2021 08:54:11 -0700 (PDT)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (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 B0D8B3A2392 for <ietf@ietf.org>; Mon, 12 Apr 2021 08:54:11 -0700 (PDT)
Received: by straasha.imrryr.org (Postfix, from userid 1001) id 28240B99F8; Mon, 12 Apr 2021 11:54:10 -0400 (EDT)
Date: Mon, 12 Apr 2021 11:54:10 -0400
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Quic: the elephant in the room
Message-ID: <YHRtIgMvBtpA2Dmi@straasha.imrryr.org>
Reply-To: ietf@ietf.org
References: <20210412021224.GP9612@localhost> <31A7A397-747D-4099-A3A3-F845137022BD@akamai.com> <20210412002634.GO9612@localhost> <94707E61-D7D2-4494-B88C-E229C8D8F3E4@akamai.com> <YHPAoW8D7K1ew4mQ@straasha.imrryr.org> <3658907C-200F-4E11-8DAE-160D5C8CE429@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3658907C-200F-4E11-8DAE-160D5C8CE429@akamai.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ib8d8Xd8cxEBbJpO2fHLVvHv1MY>
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: Mon, 12 Apr 2021 15:54:15 -0000

On Mon, Apr 12, 2021 at 12:57:21PM +0000, Salz, Rich wrote:

> >    one may as well delegate the TLSA record management to the CDN:
> 
> Sure, if you're never going to switch CDN's.

No, to *each* CDN.  Each one can publish the appropriate TLSA RRs for
its service.

> There is a whole industry and providers around switching CDN's in real
> time.  Web-search "Cdn switch" will find them, for example.

What do you mean by "in real-time"?

> >    But any sort of TLSA RR on the customer side, while the cert rollover
>     are managed by the CDN is too fragile.  The TLSA RRs should properly
>     be published by the CDN as above.
> 
> Sure, if there's one CDN.

It also works for multiple CDNs, provided they don't keep switching back
and forth, or proving some modest set of trust-anchors is known to cover
them all.

> >    If indeed sub-minute migration from one CDN to another is required, then
>     the TTL for the _443._tcp.[...] CNAME would need to be sub-minute.  Is
>     such a short cutover time really a requirement?
> 
> If millions of dollars of commerce are happening per minute, then yes.
> Or the head of state dies and the official news source is overloaded.

And do they keep switching back and forth, or is a one time switch
stable for some days or longer?

-- 
    Viktor.