IETF Logo Mail Archive

Re: [Http-srv] Alternative to SRV?

Mark Andrews <marka@isc.org> Thu, 23 August 2018 13:25 UTC

Return-Path: <marka@isc.org>
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 51B75130E0E for <http-srv@ietfa.amsl.com>; Thu, 23 Aug 2018 06:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 q34p5vqTjOyH for <http-srv@ietfa.amsl.com>; Thu, 23 Aug 2018 06:25:03 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 57A1D130EBE for <Http-srv@ietf.org>; Thu, 23 Aug 2018 06:25:03 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 168FA3AB03B; Thu, 23 Aug 2018 13:25:03 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id D42CA160042; Thu, 23 Aug 2018 13:25:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id C2A24160073; Thu, 23 Aug 2018 13:25:02 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id qhRi-jW9m2TK; Thu, 23 Aug 2018 13:25:02 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id EA117160042; Thu, 23 Aug 2018 13:25:01 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <alpine.DEB.2.20.1808231411260.3596@grey.csi.cam.ac.uk>
Date: Thu, 23 Aug 2018 23:24:59 +1000
Cc: Ray Bellis <ray@bellis.me.uk>, Http-srv@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <91657BCC-B3ED-40EE-8C7C-D8ECD85DFCB3@isc.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>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-srv/XClmN9nohM0pGEvTLI9M71p8mCo>
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 13:25:06 -0000


> On 23 Aug 2018, at 11:15 pm, Tony Finch <dot@dotat.at> wrote:
> 
> Ray Bellis <ray@bellis.me.uk> wrote:
>> On 21/08/2018 20:40, Tony Finch wrote:
>> 
>>> What will the backwards compatibility story be?
>> 
>> A / AAAA lookup, in parallel.
> 
> Sorry, I meant on the publisher side.
> 
>>> In the early days, what advantages will there be for DNS operators that
>>> will make them want to use this record?
>> 
>> The primary one is the ability to put them at the zone apex (or indeed
>> alongside any other record that would currently be precluded by CNAME rules).
> 
> So the plan is that I'll have to get the target names as well as the
> target addresses, instead of just the target name (aname / cname) or just
> the target addresses. This is not very enticing.

The plan is to get to the stage when you are outsourcing the HTTP servers
to just have to publish new records with the names of those servers.  You
only *need* to publish A and AAAA’s for legacy clients.  You are also not
forced to publish the new record as the clients will continue to work with
just A and AAAA records.

This matches MX record behaviour but the recommendation is to do all lookups
in parallel rather than doing it serially.

> Tony.
> -- 
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> North Fitzroy: Northwesterly 4 or 5. Slight or moderate. Showers. Good,
> occasionally moderate at first.
> 
> -- 
> Http-srv mailing list
> Http-srv@ietf.org
> https://www.ietf.org/mailman/listinfo/http-srv

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org

v2.23.0 | Report a Bug | By Email