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

Davey Song <songlinjian@gmail.com> Thu, 22 March 2018 14:55 UTC

Return-Path: <songlinjian@gmail.com>
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 1733412EAC4; Thu, 22 Mar 2018 07:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 A4rcqJpLUN9L; Thu, 22 Mar 2018 07:55:50 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (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 4E94012D96B; Thu, 22 Mar 2018 07:55:50 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id r197so5395665vke.2; Thu, 22 Mar 2018 07:55:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wlm5ElUEfJk1GlJfbwyQ21P83JeQ0xdtBGv3w3+uOng=; b=VnmxgjmFxDsf6a7zxAtZGhch73HXASDpuuKOn8HY/5BAYdathZIpB/9L0xsJTfd6pF LKlzaOYb51KdqJf1ypQSJY+mHevBlhIXaLi3DRinQpnlyZyKy6kMerBguApgYnNL+DlS d3YxI8zdAoZ7WJfvc8tj98fAVOU7Isie+QbOzYmcGEn/MheZJbhW/lN+LaiscfkF8rFv ZCHg7OyVplcQxp303FrjeTIMyBBPosKpFTrlMAFG7tGrSM/IPbMEB4hZo+grmeWCdSB2 tDod9jEsfdnGxQtnEs+gchoECPr82/Pm+7pN5ohAI1gaAixpVYIxiG1pxuUL3xE8utmu xBsw==
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=Wlm5ElUEfJk1GlJfbwyQ21P83JeQ0xdtBGv3w3+uOng=; b=QoL0QcAgPai94naMLIP2vOX3CT/VFf5Zv7uAuAJKLbAH9sKzMZ3Gh8sGLSR1r5VzOj g3oZxC+6/ewR2aG0fY+EvVhluOB3ZFqxnISZjTEuV2Ttg0rwXk5WMTVZ4xfvTvYVkCh2 PrRYGTjsy8CJh5M7eK0eNPPLx4E7uQ2D4B+xafUWK7Vq9L/VcVyE+SZ8kik6XiJ2y+g+ 3mLnOypaTObKnIo1zR5PoQchIrN0bHfMY6vlKUnJjyQGshTV2s7Y8OOLDmB4gk7R/sgG s2Fl6gv444iz7VOB0TsQ/839pn65eQBZ2U4GrqKnQhhbzSkY8DxiX2Sh12cgxeVTdttq duFQ==
X-Gm-Message-State: AElRT7FLNfm7rDB50X29ct5gwk57/3aJnHZ8a1vktExDLK7VZ5bjeKPN Cdfx2Bx0fjKSOmiGHEjGCMpgJ3yA9odxVKd6l1lF9A==
X-Google-Smtp-Source: AG47ELtZ9xSO575z60AnJoypyVmSMh6ePn73pghmHOIXxtLnmdaJifwWScQVvDGF+FGwGgFvUWeSdFmX61o87w4SIUE=
X-Received: by 10.31.50.13 with SMTP id y13mr16020015vky.85.1521730549274; Thu, 22 Mar 2018 07:55:49 -0700 (PDT)
MIME-Version: 1.0
References: <152168039295.5550.9572034766968749020.idtracker@ietfa.amsl.com> <CAAObRXLm3c-p9rZkn6H6tcEoh3-UT5JW06NXQ_FMyyr2NFMmyw@mail.gmail.com> <CA+nkc8DdUkUVmyU_eSM22Kokok44CyN5biOFOD29T1-F45KrvA@mail.gmail.com>
In-Reply-To: <CA+nkc8DdUkUVmyU_eSM22Kokok44CyN5biOFOD29T1-F45KrvA@mail.gmail.com>
From: Davey Song <songlinjian@gmail.com>
Date: Thu, 22 Mar 2018 14:55:38 +0000
Message-ID: <CAAObRXLt2dU+hipLv7WUHhcLZEiq0Rhn-9HDd1eucii8oAX4Vg@mail.gmail.com>
To: Bob Harold <rharolde@umich.edu>
Cc: dnsop <dnsop@ietf.org>, doh@ietf.org
Content-Type: multipart/alternative; boundary="001a114405f0d55f4a05680180c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/J8FPMGwbCMF5eyaJ817CEmtH8WE>
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:55:57 -0000

Thanks for your advice.

Davey

Bob Harold <rharolde@umich.edu>; 于 2018年3月22日周四 22:41写道:

>
> 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/draft-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
>
>