Re: [Add] Updated charter proposal for ADD

<nigel.tedeschi@bt.com> Thu, 16 January 2020 12:40 UTC

Return-Path: <nigel.tedeschi@bt.com>
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 C153212002E for <add@ietfa.amsl.com>; Thu, 16 Jan 2020 04:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 8pqT5dbQ1S1G for <add@ietfa.amsl.com>; Thu, 16 Jan 2020 04:40:18 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30AAD12002F for <add@ietf.org>; Thu, 16 Jan 2020 04:40:18 -0800 (PST)
Received: from tpw09926dag07e.domain1.systemhost.net (10.9.202.34) by BWP09926078.bt.com (10.36.82.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Thu, 16 Jan 2020 12:40:06 +0000
Received: from tpw09926dag07f.domain1.systemhost.net (10.9.202.38) by tpw09926dag07e.domain1.systemhost.net (10.9.202.34) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 16 Jan 2020 12:40:15 +0000
Received: from tpw09926dag07f.domain1.systemhost.net ([fe80::39eb:b031:eb4f:b2c9]) by tpw09926dag07f.domain1.systemhost.net ([fe80::39eb:b031:eb4f:b2c9%12]) with mapi id 15.00.1395.000; Thu, 16 Jan 2020 12:40:15 +0000
From: nigel.tedeschi@bt.com
To: add@ietf.org
Thread-Topic: [Add] Updated charter proposal for ADD
Thread-Index: AQHVyytcRtHa+WPLBEiaNmcxCCaIX6ftPU7Q
Date: Thu, 16 Jan 2020 12:40:15 +0000
Message-ID: <aafb074aa3a641489cd1d6bd8d46a2fb@tpw09926dag07f.domain1.systemhost.net>
References: <236B0A34-8C7F-49D2-8075-5AF5AC35BDFB@apple.com>
In-Reply-To: <236B0A34-8C7F-49D2-8075-5AF5AC35BDFB@apple.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.9.202.243]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/PdDao_t6JUInzGIRQLMFrbCfKHM>
Subject: Re: [Add] Updated charter proposal for ADD
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: Thu, 16 Jan 2020 12:40:24 -0000

Agree

+1

-----Original Message-----
From: Add [mailto:add-bounces@ietf.org] On Behalf Of Tommy Pauly
Sent: 14 January 2020 22:38
To: ADD Mailing list <add@ietf.org>
Subject: [Add] Updated charter proposal for ADD

Hi all,

I wanted to share an updated proposal for an ADD charter, based on the feedback and discussion on the list in the past several weeks.

This is based on the original proposal that was sent in December, taking into account various comments and suggestions. Glenn Deen, Andrew Campling, and I worked on this revision together and came to consensus on its contents.

Thoughts and comments are welcome as always!

(Note that the proposed name of the group was not changed, and is entirely open to bikeshedding. Naming is hard!)

Best,
Tommy



Adaptive DNS Discovery (ADD)
====================================
Proposed Working Group Charter

Sending DNS messages over encrypted transports, as defined in DNS over TLS (DoT) [RFC 7858] and DNS over HTTPS (DoH) [RFC 8484], provides benefits to the security and privacy of DNS data. Clients, such as applications and host operating systems, have started adopting these protocols to provide these user benefits.

This working group will focus on discovery and selection of DNS resolvers by DNS clients in a variety of networking environments, including public networks, private networks, and VPNs; supporting both encrypted and unencrypted resolvers.

Clients adopting encrypted DNS protocols need to determine which DNS servers support encrypted transports, and which server to use for specific queries if multiple servers are available. These decisions can vary based on the network environment, and also based on the content and purpose of the client queries.

Network operators that start offering DNS encryption on their servers also need a way to indicate this support to clients. Communicating information about resolver configuration and behavior allows clients to make more informed decisions about which DNS servers to use. For example, a resolver may be able to resolve private or local names as a split DNS server.

The Adaptive DNS Discovery (ADD) working group will work on the following
deliverables:

- define a mechanism that allows clients to discover DNS resolvers, including encrypted DNS servers, that are available to the client either on the public Internet or on private or local networks;

- define a mechanism that allows communication of DNS resolver information to clients for use in selection decisions;

- develop an informational document that describes how client applications and systems can manage selection of DNS resolvers in various network environments and use cases.

Any mechanisms that specify interactions between clients and servers must provide the security properties expected of IETF protocols, e.g., confidentiality protection, integrity protection, and authentication with strong work factor.

This working group will coordinate with dnsop, doh, and dprive for any changes required in DNS protocols. It will also work with capport to ensure that solutions are applicable to captive networks.

--
Add mailing list
Add@ietf.org
https://www.ietf.org/mailman/listinfo/add