IETF Logo Mail Archive

Re: [Driu] SRV and HTTP

Leif Hedstrom <leif@ogre.com> Wed, 11 July 2018 16:24 UTC

Return-Path: <leif@ogre.com>
X-Original-To: driu@ietfa.amsl.com
Delivered-To: driu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3DBE130F59; Wed, 11 Jul 2018 09:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ogre.com
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 f9i0FTXmC-1o; Wed, 11 Jul 2018 09:24:47 -0700 (PDT)
Received: from cosmo.ogre.com (cosmo4.ogre.com [71.6.165.248]) (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 28D7D130F58; Wed, 11 Jul 2018 09:24:47 -0700 (PDT)
Received: by cosmo.ogre.com (8.15.2/8.15.2) with ESMTPSA id w6BGOiVN008931 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 11 Jul 2018 09:24:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ogre.com; s=03062012; t=1531326285; bh=4epcr6NZvRK6VAwstEbx4ltZJzuEdPI0QD7spVgkygU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=crrWJBjtd/ISL4gYU6NiricdESriDJW4eq5DgPoeeXCMduztOc3HH72LQ+ymoRx6f 1puQ0zyO6DxcdyR+t6qWkq7Njh1fb7wyr7z1dnk95S+M00fgxFsio9GbdRJXuz9AxI QwLjcHz3qgASTAvUOAJGjVgo9ggdkSO+cl2qG1tU=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
From: Leif Hedstrom <leif@ogre.com>
In-Reply-To: <F6C1AF50-EB1B-4E09-9A72-229AD4AC7E57@mnot.net>
Date: Wed, 11 Jul 2018 10:24:43 -0600
Cc: Joe Abley <jabley@hopcount.ca>, Adam Roach <adam@nostrum.com>, DoH WG <doh@ietf.org>, driu@ietf.org, dnsop@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C5A84AA-C599-4294-AE55-52B2CC233D40@ogre.com>
References: <m1fcoe5-0000GuC@stereo.hq.phicoh.net> <alpine.LRH.2.21.1807101056140.5219@bofh.nohats.ca> <4a845808-5348-d6e4-dda2-59aaf0e85c14@nostrum.com> <3DF5A66C-CCBF-4116-A1FC-35CF8E05808B@hopcount.ca> <e1675184-f0bc-670d-3db1-b99a9daf1657@nostrum.com> <CAJhMdTOZtOpF_aK-ZzP0DfkDMcAtTKFLdSpKkrSPvP1cOgnOjQ@mail.gmail.com> <e658445a-242b-5f94-f1fc-0bc4c850319d@nostrum.com> <CAJhMdTOPjhbOK=NQijnYZ3kCY_+f-87n7wwwuR38ifHUG5msqA@mail.gmail.com> <F6C1AF50-EB1B-4E09-9A72-229AD4AC7E57@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/driu/8lDlPbXsuxBSHi4nKRAF9lstyYY>
Subject: Re: [Driu] SRV and HTTP
X-BeenThere: driu@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "DNS Resolver Identification and Use \(DRIU\)." <driu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/driu>, <mailto:driu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/driu/>
List-Post: <mailto:driu@ietf.org>
List-Help: <mailto:driu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/driu>, <mailto:driu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 16:24:50 -0000


> On Jul 10, 2018, at 7:22 PM, Mark Nottingham <mnot@mnot.net> wrote:
> 
> 
> 
>> On 11 Jul 2018, at 3:55 am, Joe Abley <jabley@hopcount.ca> wrote:
>> 
>> On Jul 10, 2018, at 18:02, Adam Roach <adam@nostrum.com> wrote:
>> 
>>> In large part because DNS provides "a richer scheme that accommodates address families and multiple addresses with priorities".
>> 
>> *cups hand to ear*
>> 
>> Was that the sound of a distant desire to specify use of SRV for HTTP?
>> 
> 
> I recently did some digging on this topic, and can try to characterise what the issues / objections are.
> 
> Would people be interested in a (hopefully brief) side meeting to discuss and maybe come to a shared understanding of the problem space?


Definitely. We (Traffic Server) added some support for SRV a while back, but it’s mostly a hack.

Cheers,

— Leif

v2.1.22 | Report a Bug | By Email