IETF Logo Mail Archive

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

Klaus Malorny <Klaus.Malorny@knipp.de> Fri, 21 February 2020 13:24 UTC

Return-Path: <Klaus.Malorny@knipp.de>
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 96402120106 for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2020 05:24:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 6JU0l_89rfmr for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2020 05:24:02 -0800 (PST)
Received: from kmx5a.knipp.de (kmx5a.knipp.de [195.253.6.99]) (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 C3FEC12004A for <dnsop@ietf.org>; Fri, 21 Feb 2020 05:24:02 -0800 (PST)
X-Original-Recipient: dnsop@ietf.org
X-Original-Recipient: klaus.malorny@knipp.de
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx5a.knipp.de (Postfix) with ESMTP id 48PBxY0bYkz4vwr; Fri, 21 Feb 2020 14:24:00 +0100 (CET)
Received: from [195.253.2.27] (mclane.do.knipp.de [195.253.2.27]) by hp9000.do.knipp.de (Postfix) with ESMTP id D13A672399; Fri, 21 Feb 2020 14:23:30 +0100 (MEZ)
To: dnsop@ietf.org
References: <b34f1b0d-fa65-23d4-1b2b-761b965a2aae@knipp.de> <CAG8jCEzO7zrfL5G5CzdJ=c5wipJgqqHfyeA-a3-QjquoyPYgvg@mail.gmail.com> <3ead518d-f166-1c36-c3e9-18aeb355d160@pletterpet.nl> <57323a0d-6d33-ceef-1e99-58d61eff16dd@knipp.de> <041cf7a9-be2b-18bd-7f76-edbae5cd1e4b@NLnetLabs.nl> <57505938-340A-4594-A283-EF670BD1B47E@isoc.org>
From: Klaus Malorny <Klaus.Malorny@knipp.de>
Message-ID: <48d82bb1-81ff-6e25-b060-5a2b9ac7791f@knipp.de>
Date: Fri, 21 Feb 2020 14:23:29 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Thunderbird/75.0a1
MIME-Version: 1.0
In-Reply-To: <57505938-340A-4594-A283-EF670BD1B47E@isoc.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Spamd-Bar: /
Authentication-Results: kmx5a.knipp.de; none
X-Rspamd-Server: v1117
X-Rspamd-Queue-Id: 48PBxY0bYkz4vwr
X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:8391, ipnet:195.253.0.0/16, country:DE]; LOCAL_WL_IP(0.00)[195.253.2.54]
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/an-tep6BU5H_yNrOaESGyeLwjgM>
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: Fri, 21 Feb 2020 13:24:05 -0000

On 21.02.20 13:19, Dan York wrote:
> If HTTPSVC can do that, and browser vendors will implement it [1], then that use 
> case can be satisfied.
> 
> Dan
> 

Hi all,

I have to admit that I haven't worked through the HTTPSSVC/SVCB draft in detail, 
but while it seems to provide much more functionality than the ANAME (as it 
addresses other problems, too), I see a major drawback in comparison to the 
ANAME draft, namely that there seems to be no fallback for old browsers (and 
robot software accessing websites) being defined. Of course, authoritative name 
servers could implement a similar mechanism as specified in the ANAME draft. The 
question would be whether it needs to be addressed in the HTTPSSVC/SVCB 
specification in an appropriate manner.

Regards,

Klaus

v2.23.0 | Report a Bug | By Email