Re: [DNSOP] Minimum viable ANAME

Ray Bellis <ray@bellis.me.uk> Sun, 04 November 2018 01:05 UTC

Return-Path: <ray@bellis.me.uk>
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 75154128BCC for <dnsop@ietfa.amsl.com>; Sat, 3 Nov 2018 18:05:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 3kQLObH-xTy2 for <dnsop@ietfa.amsl.com>; Sat, 3 Nov 2018 18:05:25 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27B36127333 for <dnsop@ietf.org>; Sat, 3 Nov 2018 18:05:24 -0700 (PDT)
Received: from cm-114-109-178-6.revip13.asianet.co.th ([114.109.178.6]:64366 helo=Rays-MacBook-Pro.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:RSA_AES_128_CBC_SHA1:16) id 1gJ6qs-0005Cs-DC (Exim 4.72) (return-path <ray@bellis.me.uk>); Sun, 04 Nov 2018 01:05:18 +0000
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop@ietf.org
References: <20180919201401.8E0C220051382A@ary.qy> <08C8A740-D09B-4577-AF2A-79225EDB526B@dotat.at> <20180920061343.GA754@jurassic> <E944887D-51ED-41A0-AC5A-3076743620D8@isoc.org> <acef1f69-8e4f-52cc-dca5-3ada9446e0ee@bellis.me.uk> <5BDE34E3.5030602@redbarn.org>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <a149f8ba-7350-327f-ab13-8c6eeb76f2f5@bellis.me.uk>
Date: Sun, 4 Nov 2018 08:05:17 +0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <5BDE34E3.5030602@redbarn.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/A0oVgE76DqCZF62HXUFrcq6XECg>
Subject: Re: [DNSOP] Minimum viable ANAME
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: Sun, 04 Nov 2018 01:05:27 -0000

On 04/11/2018 06:53, Paul Vixie wrote:

> the arguments against SRV in that document are unsupported and wrong.

They are something of a straw man, yes.

We did hear unequivocally at the side meeting in Montreal that SRV is 
not acceptable to the HTTP folks, though, for the broad reasons 
mentioned in my draft.

> SRV responses include additional data.

AFAIK, BIND does not currently do this.  That said, MarkA has a patch 
that supports it, so we do know it's possible.

> i think that makes HTTP as fast in terms of round trips as SRV is.

The intent is to make it as fast as CNAME, and faster than SRV currently is.

> so use "0" for the port number, and don't include more than one SRV RR.

If the record supports it, people will want to use it, and complain when 
they can't.

> so just keep using non-DNS solutions.

No argument from me, I've always strongly believed that if 
load-balancing and/or failover are the question then DNS is not the answer.

> there's no benefit to accompany the cost of this proposal compared to 
> re-use of existing code points which are already broadly implemented.

There appear to be political benefits, though.   Code points are cheap 
these days, and the point of this document is to try to introduce 
something where the DNS folk and the HTTP folks can "meet in the middle" 
with a mutually acceptable solution.

> the HTTP folks are obviously not interested in round trips, anyway:

Sometimes the content folk appear less interested in this than the UI folk.

Ray