Re: [DNSOP] [Ext] Root reasons (aka "why") - HTTP vs SRV vs ANAME vs CNAME

Paul Vixie <paul@redbarn.org> Thu, 08 November 2018 03:57 UTC

Return-Path: <paul@redbarn.org>
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 5780712958B for <dnsop@ietfa.amsl.com>; Wed, 7 Nov 2018 19:57:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ZoQWPu_FESzK for <dnsop@ietfa.amsl.com>; Wed, 7 Nov 2018 19:57:50 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35DEC1293FB for <dnsop@ietf.org>; Wed, 7 Nov 2018 19:57:50 -0800 (PST)
Received: from [IPv6:2001:559:8000:c9:ec89:6a65:e867:265a] (unknown [IPv6:2001:559:8000:c9:ec89:6a65:e867:265a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id D6173892C6 for <dnsop@ietf.org>; Thu, 8 Nov 2018 03:57:49 +0000 (UTC)
Message-ID: <5BE3B43C.50904@redbarn.org>
Date: Wed, 07 Nov 2018 19:57:48 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.25 (Windows/20180328)
MIME-Version: 1.0
To: "dnsop@ietf.org" <dnsop@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2rXFpyt_bCXorXk744yHLY0TaHs>
Subject: Re: [DNSOP] [Ext] Root reasons (aka "why") - HTTP vs SRV vs ANAME vs CNAME
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: Thu, 08 Nov 2018 03:57:51 -0000

> On Nov 8, 2018, at 9:38 AM, p vixie <paul@redbarn.org>rg>; wrote:
>>
>> If additional data is optional, so most resolvers can just pass it
>> through, the DNS techs will say yes but the HTTP techs will say
>> no.
>
> We have a bad track record of predicting what other groups will want
> from the DNS or use it for. Specifying what "HTTP techs" will say
> seems premature before a fully-fleshed proposal is taken to them.

are you thinking i made that part up?

did you not notice when they rejected SRV for two decades, or what 
reason they gave?

(hint: "i solved the wildcard problem you weren't worried about, but the 
browser will still have to ask two questions on first reference, to get 
the cache populated, and additional data will only be included if the 
resolver has been upgraded to recognize this type code"... will not 
change the answer they gave to SRV.)

feels a bit like ground-hog day in here.

-- 
P Vixie