IETF Logo Mail Archive

Re: [Add] Thoughts on a DoH (and DoT) BCP?

Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 24 July 2019 20:41 UTC

Return-Path: <stephane@laperouse.bortzmeyer.org>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A103E1206CB for <add@ietfa.amsl.com>; Wed, 24 Jul 2019 13:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 xktRVCIEFTkc for <add@ietfa.amsl.com>; Wed, 24 Jul 2019 13:41:45 -0700 (PDT)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fe27:3d3f]) (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 DBE861206A3 for <add@ietf.org>; Wed, 24 Jul 2019 13:41:44 -0700 (PDT)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 9030AA052F; Wed, 24 Jul 2019 22:41:43 +0200 (CEST)
Received: by godin (Postfix, from userid 1000) id 76CDDEC0AFD; Wed, 24 Jul 2019 22:38:35 +0200 (CEST)
Date: Wed, 24 Jul 2019 16:38:35 -0400
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: philippe.fouquart@orange.com
Cc: "andrew.fidler@bt.com" <andrew.fidler@bt.com>, "chris.box@bt.com" <chris.box@bt.com>, "add@ietf.org" <add@ietf.org>
Message-ID: <20190724203835.GB5078@laperouse.bortzmeyer.org>
References: <LO2P123MB2462DEB5330C313055D62CC396FB0@LO2P123MB2462.GBRP123.PROD.OUTLOOK.COM> <30950_1563958271_5D381BFF_30950_9_1_B5939C6860701C49AA39C5DA5189448B939E9268@OPEXCAUBMA1.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <30950_1563958271_5D381BFF_30950_9_1_B5939C6860701C49AA39C5DA5189448B939E9268@OPEXCAUBMA1.corporate.adroot.infra.ftgroup>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 18.04 (bionic)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/veiMtxLLBD8VrblRYxB1lG75lTo>
Subject: Re: [Add] Thoughts on a DoH (and DoT) BCP?
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jul 2019 20:41:49 -0000

On Wed, Jul 24, 2019 at 08:51:11AM +0000,
 philippe.fouquart@orange.com <philippe.fouquart@orange.com> wrote 
 a message of 88 lines which said:

> regarding your call for call for inputs yesterday, we would support
> this work and be happy to contribute on some of these items.

Part of it is already done. For instance, the message you quote
mentions "authentication requirements for DoH and DoT resolvers" which
are already covered in the RFCs standardizing DoTH.

v2.23.0 | Report a Bug | By Email