Re: [Doh] [Ext] Benjamin Kaduk's No Objection on draft-ietf-doh-dns-over-https-13: (with COMMENT)
"Rene 'Renne' Bartsch, B.Sc. Informatics" <ietf@bartschnet.de> Thu, 16 August 2018 07:26 UTC
Return-Path: <ietf@bartschnet.de>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0B96130EC2 for <doh@ietfa.amsl.com>; Thu, 16 Aug 2018 00:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=bartschnet.de
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 c5c2dViwKdhZ for <doh@ietfa.amsl.com>; Thu, 16 Aug 2018 00:26:08 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DC4D130E74 for <doh@ietf.org>; Thu, 16 Aug 2018 00:26:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bartschnet.de; s=2018030201; h=Content-Transfer-Encoding:MIME-Version:Date: Message-ID:From:To:Subject:content-disposition; bh=pM3Xhe7aeWV7OFxwJiH+BL7+qfA0NkMMd/rICfAepm4=; b=RJvVPrRL9tc8IS9toi9JIeGmlL KRiNg/2WC7IY2AzIUYT3pTEHQwXV6KN0SAc0D4UbIDrcewyHqC4txkuvB1igG9bk1l2RDPz8180WS ormZ50b32DgDsJN/ntWrmdDiMaJVRlf7RzW1VXHhWpBFSpYC+wyk9SMA7NS6x9A+lNnPrinw27Lt5 gIuIb0h01WS07l4SQEvhRo9rr5VvsGgela9CLzJ2HKgYCVfRs/k8MrOAppIT8OGuYW7BEJrVdVxyv Ar5NXXunuw22AbIjqosEppNBU97QwAVMmFe4Zvfa+i3PUoqTR7Jz+49ZX1noF+/NCg8RFSyEL/tg4 GTxlD+ruOc+E7dYHhlP2Wlc6sA6yTGK7p8NISXSzcszo/mSfp9gCbEwQuFHet412i6+FApuCubU2s kWSt1fNaN9NQe+x7QCFLFi6Nkadf7XOdMoe1zzcbgGWB8LptgbfMaILohRa6tVMHXsqif94MVTOW4 09BkndniqV9hJo9ZZ5jv8Ws2291s+pr/hVS5F1e047HxwMbHuG54eOEXos2YfCYLAVOIK5sjKSeVC Da9VVaqMsssikza25OTnvI2cFzPzwxtLDtHiB86uunAWe6/6E8OFlclC1SlXuajp9pwkYpse0aPJo Ldn77NgKdijxvkZMouyb/+2aU+mHNZfimp3RSOno0=;
Received: from localhost (localhost [127.0.0.1]) by mail.core-networks.de id 1fqCfV-0000l8-VM with ESMTPSA (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) for doh@ietf.org; Thu, 16 Aug 2018 09:26:07 +0200
To: doh@ietf.org
References: <153426129189.27071.38667971889611003.idtracker@ietfa.amsl.com> <F6848127-5E6C-44C6-BC91-4DCAF248D3FD@icann.org> <20180814165606.GD40887@kduck.kaduk.org> <7B076945-C58B-4FBE-B8EC-BD98DDF9015B@vpnc.org>
From: "Rene 'Renne' Bartsch, B.Sc. Informatics" <ietf@bartschnet.de>
Message-ID: <3daea335-ebdd-bea2-6f1b-aa63726b2cff@bartschnet.de>
Date: Thu, 16 Aug 2018 09:26:05 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <7B076945-C58B-4FBE-B8EC-BD98DDF9015B@vpnc.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: de-DE
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/hl7Dcax12ICfQtvjxGn3pygs8Fg>
Subject: Re: [Doh] [Ext] Benjamin Kaduk's No Objection on draft-ietf-doh-dns-over-https-13: (with COMMENT)
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2018 07:26:10 -0000
Am 14.08.2018 um 19:00 schrieb Paul Hoffman: > On 14 Aug 2018, at 9:56, Benjamin Kaduk wrote: > >>>> Section 11 >>>> >>>> The HTTPS channel used by this specification establishes secure two- >>>> party communication between the DoH client and the DoH server. >>>> >>>> What does "secure" mean? >>> >>> The same thing as the "S" in "TLS". Explaining this again at this point might not bring much understanding to the reader, however. >> >> Could you say something like "due to the confidentiality and integrity >> protection provided by TLS" at the end of the subsequent sentence? > I suggest to use "encrypted" instead of "secure" as DoH lacks reliable authentication (e.g. forged TLS certificates). Renne
- [Doh] Benjamin Kaduk's No Objection on draft-ietf… Benjamin Kaduk
- Re: [Doh] [Ext] Benjamin Kaduk's No Objection on … Paul Hoffman
- Re: [Doh] [Ext] Benjamin Kaduk's No Objection on … Benjamin Kaduk
- Re: [Doh] [Ext] Benjamin Kaduk's No Objection on … Paul Hoffman
- Re: [Doh] [Ext] Benjamin Kaduk's No Objection on … Rene 'Renne' Bartsch, B.Sc. Informatics