Re: [dnsoverhttp] Thinking about inlining DNS in HTTP
Patrick McManus <pmcmanus@mozilla.com> Fri, 16 September 2016 17:03 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 A52DC12B172
for <dnsoverhttp@ietfa.amsl.com>; Fri, 16 Sep 2016 10:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.001,
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 GgfIvrKYyen3 for <dnsoverhttp@ietfa.amsl.com>;
Fri, 16 Sep 2016 10:03:55 -0700 (PDT)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102])
by ietfa.amsl.com (Postfix) with ESMTP id E0CD212B1E0
for <dnsoverhttp@ietf.org>; Fri, 16 Sep 2016 10:03:55 -0700 (PDT)
Received: from mail-it0-f41.google.com (mail-it0-f41.google.com
[209.85.214.41])
by linode64.ducksong.com (Postfix) with ESMTPSA id 2296B3A080
for <dnsoverhttp@ietf.org>; Fri, 16 Sep 2016 13:03:42 -0400 (EDT)
Received: by mail-it0-f41.google.com with SMTP id 186so21749852itf.0
for <dnsoverhttp@ietf.org>; Fri, 16 Sep 2016 10:03:42 -0700 (PDT)
X-Gm-Message-State: AE9vXwNIezmpDBiuhvrmeu5k1cUQ71NWX6h3mbOBul2fqe2nfQW6fLIzfKZuHc4VAdWbxZuZ6gyXQxJFafMlGA==
X-Received: by 10.36.99.2 with SMTP id j2mr7023351itc.72.1474045421661; Fri,
16 Sep 2016 10:03:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.148.50 with HTTP; Fri, 16 Sep 2016 10:03:41 -0700 (PDT)
In-Reply-To: <CABkgnnWFj4iRszwRFbAJ9Zs-V5j=qntEiDT8YgyyFS=t8NcSPQ@mail.gmail.com>
References: <CAOdDvNqBUacK5oCs3V4sYi+F3Yhqf2e5NiNC1LuPz+jAeuQ4gw@mail.gmail.com>
<CABkgnnWFj4iRszwRFbAJ9Zs-V5j=qntEiDT8YgyyFS=t8NcSPQ@mail.gmail.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Fri, 16 Sep 2016 13:03:41 -0400
X-Gmail-Original-Message-ID: <CAOdDvNoVHQ7U2J=y_Uu1qrNt5KXR9_RWmKbSp-Pv0i=4c3qcPw@mail.gmail.com>
Message-ID: <CAOdDvNoVHQ7U2J=y_Uu1qrNt5KXR9_RWmKbSp-Pv0i=4c3qcPw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a113acda0bdb96a053ca2f14f
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsoverhttp/Z8ktafl9b0QfOwhgRhE8bUfUiDI>
Cc: dnsoverhttp@ietf.org, Patrick McManus <pmcmanus@mozilla.com>
Subject: Re: [dnsoverhttp] Thinking about inlining DNS in HTTP
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: Fri, 16 Sep 2016 17:03:57 -0000
On Fri, Sep 16, 2016 at 12:44 PM, Martin Thomson <martin.thomson@gmail.com> wrote: > > If we go with the notion that you can use RFC 4501 and GET, then > HTTP/2 server push will just work. That's a powerful notion. bingo.. that's why I wanted to raise it concretely when we were talking about more traditional http api things. We would be able to get a two-fer if things went in that direction. (or more!) to be fair there is some squishiness around scoping the data (or not) to the stream that pushed it - but that's a general area of evolution/fuzziness for push, not really dns specific.
- [dnsoverhttp] Thinking about inlining DNS in HTTP Patrick McManus
- Re: [dnsoverhttp] Thinking about inlining DNS in … Martin Thomson
- Re: [dnsoverhttp] Thinking about inlining DNS in … Patrick McManus