Re: [Driu] Resolverless DNS Side Meeting in Montreal

Ted Lemon <mellon@fugue.com> Tue, 10 July 2018 02:55 UTC

Return-Path: <mellon@fugue.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 CFA8E130EBC for <driu@ietfa.amsl.com>; Mon, 9 Jul 2018 19:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 oCrJtXxHuzKk for <driu@ietfa.amsl.com>; Mon, 9 Jul 2018 19:55:30 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 4BC45131070 for <driu@ietf.org>; Mon, 9 Jul 2018 19:55:27 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id e13-v6so18954527iof.6 for <driu@ietf.org>; Mon, 09 Jul 2018 19:55:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hbievmt9Qg7XZ30HuxATmXkHzWVEzkLqH9rZb5dQaWY=; b=dmDee0ECsiSDTlMlZXMB3DVvrtMwOg5fTOJuRP3Tsru/mUDK2ySoKCeVRwywzIhi7g qHMqc0ccmIJSdpOTdGZgUPI5m5njuX1vkm4/MbKXrWgLjLHjoAod8DLYqLJ/uH+rL1Em epOk0jEyurphBXZFpQQcb9ZPYhcdHIe3uQS/Lq4tYLXM+Re5q7iEh06ZxAmybLjP0E6E HqyutDF6Wd6TaneB0GkUOrjpCzDUxnnfmfER7xAHe8lHO7JH+cIzcz54hBmtak4fl/W/ jcktKZFcyr7bKn0GOyNt24iJV9daa9REm/p+D6dREqhz0ZvvgMeHZ+jUSc70/bpThTWK sioQ==
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=hbievmt9Qg7XZ30HuxATmXkHzWVEzkLqH9rZb5dQaWY=; b=VKHktk/gHrA0vzX0MD/tWNym75rgdyYgsc4/ge49vr4lUJLU1aBhFQsZvkeS6kOsSo CuChS8q2YCuYjtBRdCSlfM7aCAx2Y0cT23Nie12rKrjSrYS66YsLaPqC/me7s5fW1O+2 unjMbfyBaH3qhZBnhVhi7JqFbfKK7NERKB2fkTLHe78HPDVHDBHySv+AiMH37noR/g6i AIkPAYbnPDgmQ4jpQ3TnYbds5RA534CrM/rJNUh30WBAEmGkt+SUW9PLBFFOrdgqGrwQ U2UgPaQ0yK/CsTGNluDSMIpByc5neJFt7/uaaGWjjFLyceBjuuoGiznqXpaOT4DFICpN KOGg==
X-Gm-Message-State: AOUpUlGFCayNzPIW8aKE/gEkt7jHWo5wMMiEINoX7jrmXGabnDHZN6Hw n4IdRHYCmcUecDfxCOzilSQ6bz+DV+vWa417dNruDw==
X-Google-Smtp-Source: AAOMgpfm/h7ZdeoqmxrYYxAWCOXsIvKIGk4JFbHfLfmOHCkBjLjTVygxCjcid55AXYB8biALia3Ea8UdDK1IGs9q1qk=
X-Received: by 2002:a6b:9d0b:: with SMTP id g11-v6mr20108924ioe.85.1531191326640; Mon, 09 Jul 2018 19:55:26 -0700 (PDT)
MIME-Version: 1.0
References: <CAOdDvNp0S5-aEzy4ziqVvL1Kd+V79nD49_Zuo1dLoThXYP7nFg@mail.gmail.com>
In-Reply-To: <CAOdDvNp0S5-aEzy4ziqVvL1Kd+V79nD49_Zuo1dLoThXYP7nFg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 9 Jul 2018 22:55:16 -0400
Message-ID: <CAPt1N1nKcrxXbJmYr+1p=XtpA9NhKNvJ78A7-TrHz8Op4vNCuQ@mail.gmail.com>
To: Patrick McManus <pmcmanus@mozilla.com>
Cc: Ben Schwartz <bemasc@google.com>, Daniel Kahn Gillmor <dkg@aclu.org>, DoH WG <doh@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, dnsop <dnsop@ietf.org>, driu@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001ba40005709c43ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/driu/rcDgC1PVyHWw1giABlH6RlGghgw>
Subject: Re: [Driu] Resolverless DNS Side Meeting in Montreal
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: Tue, 10 Jul 2018 02:55:32 -0000

This sounds an awful lot like an unapproved bof. The reason we don’t do
those is that they tend to make it hard for people to participate. Why
isn’t this in scope for dnsop?

On Mon, Jul 9, 2018 at 10:49 PM Patrick McManus <pmcmanus@mozilla.com>
wrote:

> Hi All,
>
> I am organizing an ad-hoc Side Meeting regarding 'Resolverless DNS' in
> Montreal.
>
> We have often talked about the benefits and concerns of DNS information
> obtained from sources that are, shall we say, less globally trusted than a
> recursive a resolver. The central use case is DoH when pushed from an
> endpoint that isn't a recursive resolver but there have been other
> proposals.
>
> For example www.example.com pushes you a AAAA record for img1.example.com.
> Should you use it? What if it is for img1.img-example.com ? Do the
> relationship between these domains matter? What kind of relationship (i.e.
> it could be a domain relationship, or in the context of a browser it might
> be a first-party tab like relationship, etc..)? What are the implications
> of poison? Trackers? Privacy of requests never made? Speed? Competitive
> shenanigans or DoS attacks?
>
> This was out of scope for DoH.
>
> *We'll do the meeting over 1 hour in the Dorchester room from 16:30 to
> 17:30 on Monday July 16th.*
>
> This is a meeting of interested folks looking to see if we can agree on
> next steps - we're not going to work out the details (nor should a side
> meeting try and do so). so we'll have a tight agenda that I suggest
> organizaing as follows:
>
> 1] What forms of transport could be in scope? HTTP/2 push is one such
> vector, but I've heard others. Spray paint for example.
>
> 2] What needs to be considered when using such data? (signatures? scope?
> etc?)
>
> 3] Who are the stakeholders for 1 + 2?
>
> 4] Is there enough interest to explore further? Next steps as output
>
> I hope you can come!
>
> -Patrick
>
> _______________________________________________
> DRIU mailing list
> DRIU@ietf.org
> https://www.ietf.org/mailman/listinfo/driu
>