Re: [dnsoverhttp] Bar BOF in Seoul and Mailing List - DNS over HTTP ideas

Patrick McManus <pmcmanus@mozilla.com> Thu, 20 October 2016 16:58 UTC

Return-Path: <pmcmanus@mozilla.com>
X-Original-To: dnsoverhttp@ietfa.amsl.com
Delivered-To: dnsoverhttp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73D701295A1; Thu, 20 Oct 2016 09:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.735
X-Spam-Level:
X-Spam-Status: No, score=-0.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 xcw30vy2ngaC; Thu, 20 Oct 2016 09:57:58 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id 70A211294BD; Thu, 20 Oct 2016 09:57:58 -0700 (PDT)
Received: from mail-it0-f54.google.com (mail-it0-f54.google.com [209.85.214.54]) by linode64.ducksong.com (Postfix) with ESMTPSA id E90D03A058; Thu, 20 Oct 2016 12:57:56 -0400 (EDT)
Received: by mail-it0-f54.google.com with SMTP id 139so171473867itm.1; Thu, 20 Oct 2016 09:57:56 -0700 (PDT)
X-Gm-Message-State: AA6/9RkSJDY7Of9qU2HUpEAzm2H5IbTNmpxXHyA3+sRXDNhbW1mypK5N5yb5i7NRYgCCRpsPQ0luq0i5SCiL7Q==
X-Received: by 10.36.107.82 with SMTP id v79mr9662117itc.52.1476982671802; Thu, 20 Oct 2016 09:57:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.110.164 with HTTP; Thu, 20 Oct 2016 09:57:51 -0700 (PDT)
In-Reply-To: <CAOdDvNpNTgEPzBe7eg2OQCrAfcUGgcQ9d2qjTzZfd0W+yxUB8Q@mail.gmail.com>
References: <CAOdDvNpNTgEPzBe7eg2OQCrAfcUGgcQ9d2qjTzZfd0W+yxUB8Q@mail.gmail.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Thu, 20 Oct 2016 12:57:51 -0400
X-Gmail-Original-Message-ID: <CAOdDvNr8EOPgeOcgpJ8vg_UVOQ2-LjFjzwYJykGWgG3-T8zqXA@mail.gmail.com>
Message-ID: <CAOdDvNr8EOPgeOcgpJ8vg_UVOQ2-LjFjzwYJykGWgG3-T8zqXA@mail.gmail.com>
To: Patrick McManus <pmcmanus@mozilla.com>
Content-Type: multipart/alternative; boundary="001a114ac8407e09b4053f4ed30c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsoverhttp/dU0zu3K_vJ50Qed1CGNbMvREVUI>
X-Mailman-Approved-At: Thu, 20 Oct 2016 10:01:44 -0700
Cc: tjw ietf <tjw.ietf@gmail.com>, dnsoverhttp@ietf.org, Joe Hildebrand <joe@cursive.net>, dnsop@ietf.org, Mark Nottingham <mnot@mnot.net>, Bence Béky <bnc@chromium.org>, Suzanne Woolf <suzworldwide@gmail.com>, Paul Hoffman <phoffman@proper.com>, HTTP Working Group <ietf-http-wg@w3.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [dnsoverhttp] Bar BOF in Seoul and Mailing List - DNS over HTTP ideas
X-BeenThere: dnsoverhttp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of DNS over HTTP <dnsoverhttp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsoverhttp>, <mailto:dnsoverhttp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsoverhttp/>
List-Post: <mailto:dnsoverhttp@ietf.org>
List-Help: <mailto:dnsoverhttp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsoverhttp>, <mailto:dnsoverhttp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2016 16:58:01 -0000

Hi All - an update on this:

We're planning an informal Bar BOF on this topic Tuesday night in Seoul.
The place is TBD - but I'll reply to this mail as we get closer with the
detail. Just hold the place on your dance-card.

If you haven't joined the list, there is some good discussion there and
even a draft (thanks Paul and Joe!) - check it out on the archives.

-Patrick


On Tue, Sep 13, 2016 at 11:22 AM, Patrick McManus <pmcmanus@mozilla.com>
wrote:

> Hi All -
>
> DNS over HTTP comes up again and again - each time the context is a bit
> different. Some efforts try and extract information from the DNS via HTTP,
> others try and modify the DNS information via HTTP, others try and use HTTP
> as a tunnel for the DNS protocol, and still others aim to integrate DNS
> information directly into the HTTP protocol stack. Along the way there are
> firewalls, caches, markup languages, content-encodings, half solutions,
> security challenges, and other dragons.
>
> Someone made the excellent suggestion that we try and get a broad set of
> expertise here - both from the folks that understand DNS, the folks that
> are more experienced with HTTP, as well as the folks well versed in
> interfaces together to build a more complete set of requirements and after
> that's done we can make a gut check on whether that's a problem we want to
> solve together.
>
> Let's hold an informal bar-bof in Seoul (time and place TBD) on the topic
> and see if we can get critical mass together for the effort - we can
> discuss forums/etc for this work along the way - but I'm most interested to
> see if we can get the attention of the diverse set of folks necessary to
> make it succeed.
>
> There is a new list as a way to prepare for that meetup.
>
> List address: dnsoverhttp@ietf.org
> Archive: https://mailarchive.ietf.org/arch/search/?email_list=dnsoverhttp
> To subscribe: https://www.ietf.org/mailman/listinfo/dnsoverhttp
>
> I know some folk are working in this space already - please join
> dnsoverhttp and share what you're working on (or have worked on in the past
> and lessons learned from it)
>
> Thanks!
> -Patrick
>
>
>
>