IETF Logo Mail Archive

Re: Quic: the elephant in the room

Viktor Dukhovni <ietf-dane@dukhovni.org> Mon, 12 April 2021 18:12 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 675053A107D for <ietf@ietfa.amsl.com>; Mon, 12 Apr 2021 11:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 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] 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 Fg7931yZ9VzX for <ietf@ietfa.amsl.com>; Mon, 12 Apr 2021 11:12:45 -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 33E303A1079 for <ietf@ietf.org>; Mon, 12 Apr 2021 11:12:45 -0700 (PDT)
Received: by straasha.imrryr.org (Postfix, from userid 1001) id 2FCEDB9DCE; Mon, 12 Apr 2021 14:12:44 -0400 (EDT)
Date: Mon, 12 Apr 2021 14:12:44 -0400
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Quic: the elephant in the room
Message-ID: <YHSNnEb2vOCX66zS@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> <YHRtIgMvBtpA2Dmi@straasha.imrryr.org> <7F577425-2CC9-45D4-8561-B7FBCFFD0BF9@akamai.com> <YHR3NMvak8NV4Ro7@straasha.imrryr.org> <D5795304-382A-4F26-B6F5-3533837CC54F@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <D5795304-382A-4F26-B6F5-3533837CC54F@akamai.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jBaKNpSLBqKBmDlRz7ruVVuGjY4>
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 18:12:46 -0000

On Mon, Apr 12, 2021 at 06:07:40PM +0000, Salz, Rich wrote:
> > Bottom line, if DANE/TLSA were adopted for HTTPS, it can be made to work
> > also with CDNs as described in this thread.
> 
> I am not so sanguine.  I am not a DNS expert.  I know many, some of
> whom also work at my employer and who have not commented on this.

I'm open to an off-list discussion to uncover the obstacles, we could
then summarise back to the list.  There is perhaps some work remaining
to be done, but I haven't seen any fundamental obstacles as yet.

-- 
    Viktor.

v2.23.0 | Report a Bug | By Email