Re: [DNSOP] Notice to dnsop: doh @ IETF 101

Paul Vixie <paul@redbarn.org> Fri, 09 March 2018 21:57 UTC

Return-Path: <paul@redbarn.org>
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 8FF21127876 for <dnsop@ietfa.amsl.com>; Fri, 9 Mar 2018 13:57:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 0piq-hIyDyYf for <dnsop@ietfa.amsl.com>; Fri, 9 Mar 2018 13:57:57 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3776F1270A0 for <dnsop@ietf.org>; Fri, 9 Mar 2018 13:57:57 -0800 (PST)
Received: from [10.10.16.53] (fixed-187-189-130-82.totalplay.net [187.189.130.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 0DE1D7594B; Fri, 9 Mar 2018 21:57:55 +0000 (UTC)
Message-ID: <5AA30362.9080003@redbarn.org>
Date: Fri, 09 Mar 2018 13:57:54 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.24 (Windows/20180302)
MIME-Version: 1.0
To: Dave Lawrence <tale@dd.org>
CC: dnsop@ietf.org
References: <23202.63153.240123.582232@gro.dd.org>
In-Reply-To: <23202.63153.240123.582232@gro.dd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bz5Kq8egOWkfRFOuWsXaB6iFgm4>
Subject: Re: [DNSOP] Notice to dnsop: doh @ IETF 101
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: Fri, 09 Mar 2018 21:57:58 -0000

so, this leaves out the proxy case described by

https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-wireformat-http/

it would be great if one document could describe both use cases.

re:

Dave Lawrence wrote:
> Please be aware that at the doh meeting on Thursday afternoon in
> London there will be a summary discussion of the state of
> https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/
> with the expected outcome being soon moving it on to working group
> last call.
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
P Vixie