Re: [DNSOP] Fwd: New Version Notification for draft-ietf-dnsop-dns-wireformat-http-02.txt

Bob Harold <rharolde@umich.edu> Thu, 22 March 2018 14:41 UTC

Return-Path: <rharolde@umich.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9616112D88D for <dnsop@ietfa.amsl.com>; Thu, 22 Mar 2018 07:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 YNSOpvQs9vb5 for <dnsop@ietfa.amsl.com>; Thu, 22 Mar 2018 07:41:20 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 6CB96127337 for <dnsop@ietf.org>; Thu, 22 Mar 2018 07:41:20 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id g203-v6so13507175lfg.11 for <dnsop@ietf.org>; Thu, 22 Mar 2018 07:41:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PiQGvdl646FCYViuJbXdiN+Mj6OQZj/U89A+fEda9Nw=; b=hmdlqTpkuZb9l/BZ6iDwAO3GJ8hmrjHYducqlkqAuQE9gGVnvIUdQI4mKllDy5HTFc UIIni9K8cYHkwugmJDaLPGmnCGEA9MqUb1qM/mD3pYptHB02IqjwuTg9u7HU2p52Gkh8 LYLsI92ml25ErmZTQW8OOfmRj+yFn7VGWde83y4DOinrxSy8aOmpgtMlSwKGgnEcKxGW FpYTNtPVdIqapq4FKFlxo3G4z6hxX/uSIO7XwVSYkHZsV1U11chXP4f8Y9azLxXuP+Lr QZEouXKpCflf/w+WBj0LBVJVk/IrHlqqJ56kBL86goA5ROKAWGs34mjbDtU30Sy3Kxdp 3lXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PiQGvdl646FCYViuJbXdiN+Mj6OQZj/U89A+fEda9Nw=; b=pmidbR3QHLLDLlwXZ7juAFtpej0gs0U8SRV9yWEkSNHo0LEo6y9FMwys0XFac9CHIx 60k5psPQAD6iYpGXY96BMPQFDr8NnXO79YFiD7h6JMqWQtTNJVZJUSItXbr1KFFyLCiu VSTwX8mHhAfqYg3sZgTdhVV11sp8ziBgvLZbJh55cQlzwwaUQISETY9ijdlGTGMRJuuM mPU4mwlkWg3J9gSofhhNIFNboD3s6ob17M/BihMb7t91a3OA5fCn07V2lgUBCss6D1XB em5U7pcffirW//D4BlRMSNceA3yeusFvjumZFC7rmw6wH5ygcp7ugywMz54Gl5P3/zzN mbCA==
X-Gm-Message-State: AElRT7E5s3rYXGsZzgCBtDTFlT1wF9oZgBkl8sN3sXZv4yV04xlPVaG2 8TllqPDzFI2OvhxRKTbDlVDwYfGcW4IcuLio99j7rw==
X-Google-Smtp-Source: AG47ELsbqbTQT7+10nIoT/MNlHmmTQXqLyQ5Ol+kO1OMCrw2f/6OxKzVjpIOvELf9hK5FpLSn6pJqxxSxRkqF3vfD9w=
X-Received: by 2002:a19:2145:: with SMTP id h66-v6mr16146035lfh.63.1521729678554; Thu, 22 Mar 2018 07:41:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.155.140 with HTTP; Thu, 22 Mar 2018 07:41:17 -0700 (PDT)
In-Reply-To: <CAAObRXLm3c-p9rZkn6H6tcEoh3-UT5JW06NXQ_FMyyr2NFMmyw@mail.gmail.com>
References: <152168039295.5550.9572034766968749020.idtracker@ietfa.amsl.com> <CAAObRXLm3c-p9rZkn6H6tcEoh3-UT5JW06NXQ_FMyyr2NFMmyw@mail.gmail.com>
From: Bob Harold <rharolde@umich.edu>
Date: Thu, 22 Mar 2018 10:41:17 -0400
Message-ID: <CA+nkc8DdUkUVmyU_eSM22Kokok44CyN5biOFOD29T1-F45KrvA@mail.gmail.com>
To: Davey Song <songlinjian@gmail.com>
Cc: dnsop <dnsop@ietf.org>, doh@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ef92970568014c3b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PgNxc6mSRo8UXVQLJsATMj3hwyc>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-ietf-dnsop-dns-wireformat-http-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 14:41:24 -0000

On Wed, Mar 21, 2018 at 9:36 PM, Davey Song <songlinjian@gmail.com>; wrote:

> Hi folks,
>
> I just submit a updated version of dns wireformat over HTTP. This draft
> has been adopted as the dnsop wg document for quite a while before DOH.
> The original intention of this draft is to explore the possiblity of DNS
> over HTTP(s) use cases and demonstrate its capacity as an experimental
> draft. But the draft lacked enough specification on HTTP requirement and
> context at that time. Since DOH later was setup focusing on developing
> https as DNS transport protocol. So I updated this draft as a a special use
> case of DOH which served as DNS proxy.
>
> I would like to ask comments and advice in dnsop and doh wgs mainly two
> quesions:
> 1) (for dns people) Does this proxy use case sounds useful as a IETF
> experiment document .
> 2) (for HTTP people) Is a media type "application/dns-tcpwireformat"
> acceptable specially for this use case. We also consider to introduce an
> optional parameter to existing  "application/dns-udpwireformat" MIME in
> DOH document, because the two media type carries the identical message body (the
> udp dns wireformat)  in DOH request  in proxy use case. We need
> suggestion here.
>
> Thank to Tim and Paul Hoffman to bring this draft alive.
>
> Davey
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>;
> Date: 22 March 2018 at 08:59
> Subject: New Version Notification for draft-ietf-dnsop-dns-
> wireformat-http-02.txt
> To: Shane Kerr <shane@time-travellers.org>;, Paul Vixie <vixie@tisf.net>;,
> Linjian Song <songlinjian@gmail.com>;
>
>
>
> A new version of I-D, draft-ietf-dnsop-dns-wireformat-http-02.txt
> has been successfully submitted by Linjian Song and posted to the
> IETF repository.
>
> Name:           draft-ietf-dnsop-dns-wireformat-http
> Revision:       02
> Title:          An Proxy Use Case of DNS over HTTPS
> Document date:  2018-03-21
> Group:          dnsop
> Pages:          6
> URL:            https://www.ietf.org/internet-
> drafts/draft-ietf-dnsop-dns-wireformat-http-02.txt
> Status:         https://datatracker.ietf.org/
> doc/draft-ietf-dnsop-dns-wireformat-http/
> Htmlized:       https://tools.ietf.org/html/d
> raft-ietf-dnsop-dns-wireformat-http-02
> Htmlized:       https://datatracker.ietf.org/
> doc/html/draft-ietf-dnsop-dns-wireformat-http
> Diff:           https://www.ietf.org/rfcdiff?
> url2=draft-ietf-dnsop-dns-wireformat-http-02
>
> Abstract:
>    This memo introduces a DNS proxy use case to tunnel DNS query and
>    response over HTTPs using DOH, a newly proposed DNS transport.  This
>    is useful in some situation where DNS is not working properly and DOH
>    is not widely available for many stub-resolvers.
>


The first time "DOH" is used, it should be defined.  Either:
DOH (DNS over HTTP)
or:
DNS over HTTP (DOH)

I think the second is the preferred method.

-- 
Bob Harold