Re: [Add] Updated charter proposal for ADD

"Diego R. Lopez" <diego.r.lopez@telefonica.com> Wed, 15 January 2020 13:12 UTC

Return-Path: <diego.r.lopez@telefonica.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 00F3A120232 for <add@ietfa.amsl.com>; Wed, 15 Jan 2020 05:12:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telefonica.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 lpobiUxaX_M2 for <add@ietfa.amsl.com>; Wed, 15 Jan 2020 05:12:17 -0800 (PST)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on20708.outbound.protection.outlook.com [IPv6:2a01:111:f400:7d00::708]) (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 A67B612022D for <add@ietf.org>; Wed, 15 Jan 2020 05:12:16 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=H1Yv5rjL+zDDZhf70kC9zbDk7/m6hAS33RGbqarbn6CWGMWa1Y4JgmBpW+5d63GaA6IBHcV5V2QQe3a0P8gK9jSN4st8YyhGywNnSBlhbIc/wVE+j507/oj4yVt3HHifpWC8wQ4FUyeABblFKXfgiFqqK4ktun6ZgcQ5M8fufABY56K5Ms408Ywf84wGNQOyyZ/7lzQnYSXpNa1lttii5LIY0LsR9vjTNtXHYSwZSVq9lOFF1/OVbMIDGq+udiSs8Frnz2ax8Mdkp+qNgHDUHGpCbf4ahScNlPLzVAD6IyO5nQjvtVPotaASBahNPPb+qOml9U4gVEyNa/IR6qyRKA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vZC3vjZI/AZjjpuoG0ky69vnlYOHQZ3UbTliMK/Vs2Y=; b=ZmtXVVhkY9W8Vh4xVLOnEAOIQIzPW1v1iETKhe58eSI8EAJWDALAyPqOU7SZkwsNULSeFtHz8CnDeElOHnnGdpODcue4PGYNUSbFB6lxjou+7O95ku07rHl0vUG7XO5zFJz560S/55Y0k0tnFIMAX4wbwAvC56DiPTtn6ZgnTWpHiavG5r4p823YSSvM+IpW9KGyd2PzW79T1TGpOtD3simmxomQ8gPJkL6wU8FZo5m7faL0+n1k33I2wNxJBRaWmO249g8HJLls7Bj88tnn5dvXFU1pCzxZJxSCtaiNEUAuzpBaVeh7v7D4xNIpfx+GDL2Nz/POKlg4mUHDJR8RSg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telefonica.com; dmarc=pass action=none header.from=telefonica.com; dkim=pass header.d=telefonica.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telefonica.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vZC3vjZI/AZjjpuoG0ky69vnlYOHQZ3UbTliMK/Vs2Y=; b=OwdWQUgr98fmQd3a4HZdGoLxblLhrL2U680wdW9xsZnP7d8nE3Pa0SnR1F7+P6T+msqrrE2wqL6kb9m24eb463b2/XkuLgGi01ifmh8t4oY4N3qVa8YuagcYZCXYrFBNVEq/EaU0rYKJviqMaq5C3oe+x9rDsi1uuo6WQAml4H0=
Received: from AM0PR06MB6435.eurprd06.prod.outlook.com (10.186.130.150) by AM0PR06MB6260.eurprd06.prod.outlook.com (20.179.254.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2623.10; Wed, 15 Jan 2020 13:12:14 +0000
Received: from AM0PR06MB6435.eurprd06.prod.outlook.com ([fe80::7cfe:be7b:9e88:e034]) by AM0PR06MB6435.eurprd06.prod.outlook.com ([fe80::7cfe:be7b:9e88:e034%7]) with mapi id 15.20.2623.018; Wed, 15 Jan 2020 13:12:14 +0000
From: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
To: Paul Adair <padair@infoblox.com>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, ADD Mailing list <add@ietf.org>
Thread-Topic: [Add] Updated charter proposal for ADD
Thread-Index: AQHVyytd/6T3SrWRvUmCDtd6EFv9VqfrsxqAgAASHAA=
Date: Wed, 15 Jan 2020 13:12:13 +0000
Message-ID: <E91EA89C-C35C-44A9-8689-BE58248B2F50@telefonica.com>
References: <236B0A34-8C7F-49D2-8075-5AF5AC35BDFB@apple.com> <0E6BAB56-3B54-4032-BD17-30770F242BB1@infoblox.com>
In-Reply-To: <0E6BAB56-3B54-4032-BD17-30770F242BB1@infoblox.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.12.200112
authentication-results: spf=none (sender IP is ) smtp.mailfrom=diego.r.lopez@telefonica.com;
x-originating-ip: [2001:878:302:6:1d51:3f08:29c1:f59c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 12444cbb-2789-4f2f-95e1-08d799bc89d4
x-ms-traffictypediagnostic: AM0PR06MB6260:
x-microsoft-antispam-prvs: <AM0PR06MB62605DF21DE35282195CD1EADF370@AM0PR06MB6260.eurprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 02830F0362
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(376002)(136003)(39860400002)(366004)(396003)(189003)(199004)(8676002)(45080400002)(478600001)(66946007)(91956017)(71200400001)(5660300002)(76116006)(66446008)(110136005)(64756008)(66476007)(66556008)(316002)(8936002)(186003)(86362001)(53546011)(6506007)(2616005)(15650500001)(966005)(66574012)(786003)(81166006)(81156014)(33656002)(6486002)(2906002)(36756003)(6512007); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR06MB6260; H:AM0PR06MB6435.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: TkJB6dNNJfU0HGeJddNZMJwYF+2yLc0WSuhv8T2DUpuMUBCnHddf1zR7LGcf4n3sG3JC6abaWHWDh8ga5CNOMNAix7kX8PZx0Fo1bpzLWlJSfQakwo+O7ZHU7+H8oRw3mQ1FEuDOxcp3t//RCQ3wrV0ZScBMXxoSIatAbn1aWf02HqW3J+EofkITRwLccNeG0rNFp1YuKZ45fiUPBqzHaNb+XcP26jiwO9D67zy2Y+Wn4zNg1eMbcal4QbvnMFcp3Fam38DdJyu0nDnzdgdUAuYXFzhRYjMxKChVG1PN+Zf9VSj5JuxsIy1y7ycK7+CoWtmj1SxLECv45wB3NsP0/b6CpFLrztgsKlNEim1iPpY97NmXX5vf8yAQ3Mc3viO6fa+l59pmLmoDEyhmpkJdaXE7HVjrOrEcnESH1ZMB8cGLJiFEzTyRne5IxPn81O197eKPzziLBaouCjm6am7gaZVcO7iRdERUoRZ3H+pZ6IuOI7FXDmGXJDdVdYoY6ydEwdxKzL7sSdtM/4411DpCCQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <5A1F7BD7CB376E4280A0BD596ACBE2C3@eurprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 12444cbb-2789-4f2f-95e1-08d799bc89d4
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jan 2020 13:12:13.5940 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: U+35CA3XYzeHMa1tj/h40Ee8Nn0qz9QynX8jczE4F8PNWX8Y8Z8eLjNFKL3p2iVTKCRtP0i8XADiD3Ihr5lBQjdKtau6QzQxYTA6yX4yvc8=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR06MB6260
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/MMolBgnjYar83pdYLiYeYteXrcE>
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: Wed, 15 Jan 2020 13:12:22 -0000

+1

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
https://www.linkedin.com/in/dr2lopez/

e-mail: diego.r.lopez@telefonica.com
Tel:         +34 913 129 041
Mobile:  +34 682 051 091
----------------------------------

On 15/01/2020, 14:07, "Add on behalf of Paul Adair" <add-bounces@ietf.org on behalf of padair@infoblox.com> wrote:

    I support the charter as written.

    Paul Adair
    Infoblox

    On 1/14/20, 4:38 PM, "Add on behalf of Tommy Pauly" <add-bounces@ietf.org on behalf of tpauly=40apple.com@dmarc.ietf.org> wrote:

        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://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/add__;!!JYsgTRAg6ZQ!YAYWpqIz-5mnVKFP1uomaHnZqaaPeM7jg_t3b2JEb1RGKILDMtltv1eD68VDh3Y$


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



________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição