Re: [DNSOP] status of the aname and svcb/httpsvc drafts

Vladimír Čunát <vladimir.cunat+ietf@nic.cz> Wed, 26 February 2020 14:35 UTC

Return-Path: <vladimir.cunat+ietf@nic.cz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 076113A07EB for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2020 06:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_NONE=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=nic.cz
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 n6k3QVfXVWcq for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2020 06:35:00 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 D47733A07E7 for <dnsop@ietf.org>; Wed, 26 Feb 2020 06:34:57 -0800 (PST)
Received: from [IPv6:2001:1488:fffe:6:d16b:3402:41fd:8ffb] (unknown [IPv6:2001:1488:fffe:6:d16b:3402:41fd:8ffb]) by mail.nic.cz (Postfix) with ESMTPSA id 3343113F9B3; Wed, 26 Feb 2020 15:34:55 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1582727695; bh=/5iY/emObdHpnrzaK9IUPYWTIAcoUXmupwfnTHmUnWk=; h=To:From:Date; b=oFu9raR6v/Ygqty77A95qv4ITaPFZg3tWwpfPpK9tM4uTca0H++AOjbsTc55vmCIk x/p/mNq20IejqaYNlK4S3/90vVk1y/sNca97hdW5d4Mqt2crL5uZ0O6BAJquBeDPr0 BaBH9PQ/ly+mtkCEdx4gwgfBx+L7eBRt13A5Ku5o=
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Cc: "Andrew M. Hettinger" <AHettinger@Prominic.NET>
References: <b34f1b0d-fa65-23d4-1b2b-761b965a2aae@knipp.de> <CAG8jCEzO7zrfL5G5CzdJ=c5wipJgqqHfyeA-a3-QjquoyPYgvg@mail.gmail.com> <3ead518d-f166-1c36-c3e9-18aeb355d160@pletterpet.nl> <20200220221517.GA16177@isc.org> <alpine.DEB.2.20.2002222349530.27562@grey.csi.cam.ac.uk> <CAH1iCiq+rOxs9c8zoJhAWbB6-0SP_WC5onF-DrbekwX=8iR49Q@mail.gmail.com> <CA+nkc8Coe8D1ECfrRwRUnzJ3azyJfXXUq3HMy63AL-4SOvmaaw@mail.gmail.com> <OF4062C1E9.B42128F1-ON86258519.006893C9-86258519.00690F29@prominic.net>
From: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>
Message-ID: <f5f17c26-e673-119e-e7aa-bc88f8ef46a3@nic.cz>
Date: Wed, 26 Feb 2020 15:34:55 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <OF4062C1E9.B42128F1-ON86258519.006893C9-86258519.00690F29@prominic.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Virus-Scanned: clamav-milter 0.101.4 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/QWci9j6Y6K1pDIuAfLN-70Nddw4>
Subject: Re: [DNSOP] status of the aname and svcb/httpsvc drafts
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2020 14:35:04 -0000

On 2/25/20 8:07 PM, Andrew M. Hettinger wrote:
> Frankly, you've got it exactly the wrong way around: even with httpsvc
> speced out completely, it will take time for it to be deployed to
> browsers. That's assuming you can get enough buying from (mostly)
> google to even make it happen at all.

I don't think it's so simple.  The current ANAME draft specifies new
behavior for resolvers, and there I'd expect even slower overall
upgrades/deployment than in browsers.  Also I'm unsure how big a part of
authoritative implementations will want to do ANAME expansion.  (It
seems unlikely for "our" Knot DNS, for example.)

Of course, none of this will really prevent anyone from deploying it,
even though it won't be ideal, e.g. often without more precise answers
due to non-supporting resolvers.  Clearly we do have deployments even
now :-)

--Vladimir