IETF Logo Mail Archive

Re: [Http-srv] Alternative to SRV?

Ray Bellis <ray@bellis.me.uk> Tue, 21 August 2018 20:52 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 A53F6130F00 for <http-srv@ietfa.amsl.com>; Tue, 21 Aug 2018 13:52:04 -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 RrsaQuQpky1u for <http-srv@ietfa.amsl.com>; Tue, 21 Aug 2018 13:52:03 -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 D304C130EED for <Http-srv@ietf.org>; Tue, 21 Aug 2018 13:52:02 -0700 (PDT)
Received: from 82-69-21-132.dsl.in-addr.zen.co.uk ([82.69.21.132]:64722 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 1fsDd8-00048R-CI (Exim 4.72) for Http-srv@ietf.org (return-path <ray@bellis.me.uk>); Tue, 21 Aug 2018 21:51:58 +0100
To: Http-srv@ietf.org
References: <6aceab29-cf81-8644-20cd-e02281e6394c@bellis.me.uk> <alpine.DEB.2.20.1808212037370.3596@grey.csi.cam.ac.uk>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <d2dc5f58-3c91-f890-2aba-fa7601636d78@bellis.me.uk>
Date: Tue, 21 Aug 2018 21:52:01 +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.1808212037370.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/uxrqcczSgDom2iPPS2vyFR_hfhU>
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: Tue, 21 Aug 2018 20:52:05 -0000


On 21/08/2018 20:40, Tony Finch wrote:

> What will the backwards compatibility story be?

A / AAAA lookup, in parallel.

In the short / medium term the downside would be having to wait for all 
three lookups to complete before proceeding (absent a happy eyeballs 
scenario)

> 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).

Ray

v2.23.0 | Report a Bug | By Email