Re: [Driu] [Doh] [DNSOP] SRV and HTTP

Joseph Lorenzo Hall <joe@cdt.org> Wed, 11 July 2018 22:25 UTC

Return-Path: <jhall@cdt.org>
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 D5F5912872C for <driu@ietfa.amsl.com>; Wed, 11 Jul 2018 15:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 X-JDzP9lqXtw for <driu@ietfa.amsl.com>; Wed, 11 Jul 2018 15:25:55 -0700 (PDT)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED138130E73 for <driu@ietf.org>; Wed, 11 Jul 2018 15:25:51 -0700 (PDT)
Received: by mail-ua0-x229.google.com with SMTP id q12-v6so17226568ual.2 for <driu@ietf.org>; Wed, 11 Jul 2018 15:25:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Xw/jjrYq+qCbhfhCI8wuejqR6md3s7xQ7PHmneUYKWo=; b=dEeZ4/Z6cYdhqqr5vBOPHSN7LbJLnOQWTk2Pf5N8JeQbR98km1erh0AtndzZF4Exbq k7ThdK/QqOXk+koLnyYE3LxSGYIZn5sUSsbeo8J5oz1kP5xX5ymCOgFAFN2M5DQTyvsJ qMZ16flqwkXodYWoaZ9P31s8QpFBJ7DOCG4/s=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Xw/jjrYq+qCbhfhCI8wuejqR6md3s7xQ7PHmneUYKWo=; b=tXBa9b/2+s2kD/o9WurlegPL4ZOLO3kXvk1bhvBeGiR7hAhC34JX/HzEePtIUSrfoB +2j/ecR7odo4VoAGKrexf1cLb9iodABsb3kfy6gZE/daqx/dpG8KHfiknkc/Pkp8BuWL bxWDAH4pe/o5yPyuiO87fv4ZfIsxYAwDXy8aT8c5fP/w75BPUgU8FESBBNqXneNlieEP zUACI6a3O76TS5YQF1V/it1M9DcfhzWCpagH6Nz9Lz9P3Xz/4KtkbBvUNO3BW4+NqxLD 5KknORiFyRoY5W9t+o0qgqKPRlgRyFlVaay0F7WHuxDIh0qtcL/KhUgBh6iM//Byphtc RMKw==
X-Gm-Message-State: AOUpUlF6/RPssPUzWboDXsuyJu9krduKecXP2eoUYlRKC1JmUA3AS907 KptKA+Mj25MeYfGjcU2FEuMqP8pY/oJ+nNGwH0+ePQ==
X-Google-Smtp-Source: AAOMgpeK4Z0Mh1j5Tda/qfL/lcnZqk8GyR/UQsbH94dECtaKOqgMe1f5d/ACGZTeqX9vIq+U+AqdJ2l0Q9vx5jfaQP4=
X-Received: by 2002:ab0:4b17:: with SMTP id h23-v6mr360465uaf.84.1531347950636; Wed, 11 Jul 2018 15:25:50 -0700 (PDT)
MIME-Version: 1.0
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> <82099DED-CCB6-4CDC-BFE6-97B1AB3EB0A4@isc.org> <7A9000F5-0772-49FC-BDBB-862C8141BA54@mnot.net>
In-Reply-To: <7A9000F5-0772-49FC-BDBB-862C8141BA54@mnot.net>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Wed, 11 Jul 2018 18:25:38 -0400
Message-ID: <CABtrr-Wv_KHWOzTB-+xthMew6HfKpaqA09dgadX1EX97F2aK_A@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: marka@isc.org, doh@ietf.org, Adam Roach <adam@nostrum.com>, driu@ietf.org, dnsop <dnsop@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, jabley@hopcount.ca
Content-Type: multipart/alternative; boundary="000000000000a017e90570c0ba9f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/driu/LnIWcCDWsAGt8iXHg163gfJ7VKs>
Subject: Re: [Driu] [Doh] [DNSOP] 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 22:26:00 -0000

I'm in, but will need to catch up on the convo... I'll do so.

BTW, don't look at the Yelp/Foursquare reviews for the social venue... yikes

On Tue, Jul 10, 2018 at 9:32 PM Mark Nottingham <mnot@mnot.net>; wrote:

> I didn't find those, but I found many others.
>
> I'll start collecting. How about Tuesday, say 6:45-7:45pm?
>
>
>
> > On 11 Jul 2018, at 11:30 am, Mark Andrews <marka@isc.org>; wrote:
> >
> >
> >
> >> On 11 Jul 2018, at 11:22 am, 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.
> >
> > I think there are three main objections.
> >
> > 1) Wildcards don’t work with prefixes.
> > 2) Additional data isn’t always returned it may require multiple round
> trips.
> > 3) Additional data processing doesn’t support negative responses.
> >
> > All of these issues are trivially easy to fix.  It just require
> willingness to implement.
> >
> > 1) is addressed by defining a new type(s) rather than using prefixes.
> > 2) is addressed by getting recursive servers to fill in missing
> additional data before returning.  Named has code in review for this for
> SRV as proof of concept.
> > 3) is addressed by adding some signalling between the client and
> recursive server to indicate if the additional section is complete or not.
> >
> >
> >> Would people be interested in a (hopefully brief) side meeting to
> discuss and maybe come to a shared understanding of the problem space?
> >>
> >> Cheers,
> >>
> >> --
> >> Mark Nottingham   https://www.mnot.net/
> >>
> >> _______________________________________________
> >> DNSOP mailing list
> >> DNSOP@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dnsop
> >
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>
> --
> Mark Nottingham   https://www.mnot.net/
>
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>


-- 
Joseph Lorenzo Hall
Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]
1401 K ST NW STE 200, Washington DC 20005-3497
e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871