Re: [Http-srv] Alternative to SRV?

Ray Bellis <ray@bellis.me.uk> Thu, 23 August 2018 18:32 UTC

Return-Path: <ray@bellis.me.uk>
X-Original-To: http-srv@ietfa.amsl.com
Delivered-To: http-srv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3CE130EED for <http-srv@ietfa.amsl.com>; Thu, 23 Aug 2018 11:32:42 -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 3ZeAj24L5P8Q for <http-srv@ietfa.amsl.com>; Thu, 23 Aug 2018 11:32:40 -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 74DE2130EEA for <Http-srv@ietf.org>; Thu, 23 Aug 2018 11:32:40 -0700 (PDT)
Received: from 82-69-21-132.dsl.in-addr.zen.co.uk ([82.69.21.132]:54344 helo=Barbaras-MacBook-Pro.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1fsuPM-0002hi-2o (Exim 4.72) (return-path <ray@bellis.me.uk>); Thu, 23 Aug 2018 19:32:36 +0100
To: Tony Finch <dot@dotat.at>
Cc: Http-srv@ietf.org
References: <6aceab29-cf81-8644-20cd-e02281e6394c@bellis.me.uk> <alpine.DEB.2.20.1808212037370.3596@grey.csi.cam.ac.uk> <d2dc5f58-3c91-f890-2aba-fa7601636d78@bellis.me.uk> <alpine.DEB.2.20.1808231411260.3596@grey.csi.cam.ac.uk> <91657BCC-B3ED-40EE-8C7C-D8ECD85DFCB3@isc.org> <alpine.DEB.2.20.1808231509500.3596@grey.csi.cam.ac.uk>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <e96e1151-b344-0506-e9b9-7ae46dfd9f25@bellis.me.uk>
Date: Thu, 23 Aug 2018 19:32:38 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1808231509500.3596@grey.csi.cam.ac.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-srv/G5_GYeRwXQeX0jFkdpguFYC_Hnc>
Subject: Re: [Http-srv] Alternative to SRV?
X-BeenThere: http-srv@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Using DNS SRV Records with HTTP <http-srv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-srv>, <mailto:http-srv-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-srv/>
List-Post: <mailto:http-srv@ietf.org>
List-Help: <mailto:http-srv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-srv>, <mailto:http-srv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2018 18:32:43 -0000


On 23/08/2018 15:12, Tony Finch wrote:

> The reason I like ANAME is that all of this backwards compatibility and
> migration faff is automated away.

Badly, IMHO.

In the transitional phase it puts the onus on authoritative servers to 
find the targets of those ANAME records and publish them.

The corollary of that is that any CDN that's subsequently asked by the 
authoritative for the target A/AAAA addresses of an ANAME target will 
give the address relative to the authoritative server's address and not 
that of the end user's recursive server.

Not only is this poor from the CDN point of view (and after all, it's 
outsourced web hosting provision such as CDNs that are the reason for 
all this in the first place) but it puts the "intelligence" in the wrong 
layer of the DNS.

Ray