Re: [Add] I-D Action: draft-ietf-add-dnr-04.txt

mohamed.boucadair@orange.com Mon, 13 December 2021 15:40 UTC

Return-Path: <mohamed.boucadair@orange.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 F23863A0788 for <add@ietfa.amsl.com>; Mon, 13 Dec 2021 07:40:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 Zopg_Skz9ELN for <add@ietfa.amsl.com>; Mon, 13 Dec 2021 07:40:16 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 411E63A0687 for <add@ietf.org>; Mon, 13 Dec 2021 07:40:16 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr20.francetelecom.fr (ESMTP service) with ESMTPS id 4JCQgf1d6Mz1yR7; Mon, 13 Dec 2021 16:40:14 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1639410014; bh=+it83akA5Hcie3YNGL7IiMbcfKwC5fwEUI1F3WjSLWg=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=FxREZkgKzpaKPU0CGeCZvw43ir+447iXdhTnvq7U6EIVLIP1EtGjGwTm1frGY0Gg0 p5gbR+avcTOE+hUGlcZJCT3udpRdwycWclV7RzkBVHiDimI28lm9cR/lqmYd/f26zP ZL+HepVJMhgMn3Lc+loWsw6XeH0Pkjs57P44Obkkt2/lmeN8owc4820s979b2f1u6g uXqCfJsLjgHavK+yads3CGud4STt5xuaLq+8ZPfkoxa/oiNL9Q7TkdncafwYgAghSL 2RYlhY2PQbNF6CooAgrsRH5HxLsCayvzsCGewqsyMUmX/aHuurKxr4dbQZLiNzbVco OzYYW/GsTZx1Q==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr01.francetelecom.fr (ESMTP service) with ESMTPS id 4JCQgf0YWQzDq7l; Mon, 13 Dec 2021 16:40:14 +0100 (CET)
From: mohamed.boucadair@orange.com
To: Ben Schwartz <bemasc@google.com>
CC: "add@ietf.org" <add@ietf.org>
Thread-Topic: [Add] I-D Action: draft-ietf-add-dnr-04.txt
Thread-Index: AQHX8DPduy1PxVPqlEyxHt3g2e2Pp6wwijpA
Content-Class:
Date: Mon, 13 Dec 2021 15:40:13 +0000
Message-ID: <5071_1639410014_61B7695E_5071_21_14_787AE7BB302AE849A7480A190F8B933035463983@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <163903270649.6465.5137287913333383312@ietfa.amsl.com> <18246_1639033141_61B1A935_18246_427_1_787AE7BB302AE849A7480A190F8B933035461678@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAHbrMsAkj28Bsm=c+VDQo71-gNZgC7EEm+Jr7Ch1F2xm9e9zcQ@mail.gmail.com> <1923_1639120108_61B2FCEC_1923_35_1_787AE7BB302AE849A7480A190F8B933035462301@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <22653_1639402453_61B74BD5_22653_443_1_787AE7BB302AE849A7480A190F8B9330354637AC@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAHbrMsCftA8hViaUhw8-Bwa-me8phca7469KTibpax9+M53XZw@mail.gmail.com>
In-Reply-To: <CAHbrMsCftA8hViaUhw8-Bwa-me8phca7469KTibpax9+M53XZw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2021-12-13T15:30:30Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=c4bbdfe4-41b3-4908-ab4d-4852b1666717; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933035463983OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/pi9HarNO1XlTqM7XGnS7LXR7Z4o>
Subject: Re: [Add] I-D Action: draft-ietf-add-dnr-04.txt
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: Mon, 13 Dec 2021 15:40:22 -0000

Ben,

We don’t introduce specific treatments based on the null label but rely on the explicit length field to identify name (like any other variable-length field in dhcp). This approach was reviewed by dhcp experts and are OK with it.

Cheers,
Med

De : Ben Schwartz <bemasc@google.com>
Envoyé : lundi 13 décembre 2021 16:12
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
Cc : add@ietf.org
Objet : Re: [Add] I-D Action: draft-ietf-add-dnr-04.txt

This is not what I meant.  I meant that you can now get rid of the "ADN length" field, because the authentication domain name is self-delimiting.  This makes the remainder of the payload (after the IPs) syntactically identical to SVCB RDATA.

If we keep the ADN length field, then I don't think this reordering is an improvement.

On Mon, Dec 13, 2021 at 8:34 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
Hi all,

The format was updated to list the IP addresses first: https://www.ietf.org/rfcdiff?url1=draft-ietf-add-dnr-04&url2=draft-ietf-add-dnr-05

Cheers,
Med

De : Add <add-bounces@ietf.org<mailto:add-bounces@ietf.org>> De la part de mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
Envoyé : vendredi 10 décembre 2021 08:08
À : Ben Schwartz <bemasc@google.com<mailto:bemasc@google.com>>
Cc : add@ietf.org<mailto:add@ietf.org>
Objet : Re: [Add] I-D Action: draft-ietf-add-dnr-04.txt

Hi Ben,

No problem to list the IP addresses first as both are variable-length.

For the length vs. count, this is something we considered in the past. I have reported at that time that we depend on the dhc recommendations. As a reminder, the discussion we had with Bernie (dhc wg Chair) triggered https://mailarchive.ietf.org/arch/msg/dhcwg/gZ_EbiPVOt-3tARDeQHYLHbh8R8/.

Cheers,
Med

De : Ben Schwartz <bemasc@google.com<mailto:bemasc@google.com>>
Envoyé : jeudi 9 décembre 2021 22:37
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
Cc : add@ietf.org<mailto:add@ietf.org>
Objet : Re: [Add] I-D Action: draft-ietf-add-dnr-04.txt

Now that the SvcPriority is included in the payload, I would suggest moving the IP addresses to the beginning of the payload.  That would allow the remainder to be syntactically identical to SVCB RDATA, so it can be synthesized and parsed using the exact same code used for SVCB records.  (It would also save one byte.)

As I mentioned previously I would also prefer to provide the _count_ of IP addresses, rather than the _length_ of the IP address field.  This avoids the potential for memory safety vulnerabilities when Addr Length is impossible (e.g. 13) and saves one byte for IPv6.

On Thu, Dec 9, 2021 at 1:59 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
Hi all,

This version fixes an issue about DHCP option ordering: we used to rely upon the options appearance but this is against RFC7227.

We also made some editorial changes to clean the reference to the deployment I-D.

Looking forward seeing the I-D in WGLC.

Cheers,
Med

> -----Message d'origine-----
> De : Add <add-bounces@ietf.org<mailto:add-bounces@ietf.org>> De la part de internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
> Envoyé : jeudi 9 décembre 2021 07:52
> À : i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
> Cc : add@ietf.org<mailto:add@ietf.org>
> Objet : [Add] I-D Action: draft-ietf-add-dnr-04.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Adaptive DNS Discovery WG of the IETF.
>
>         Title           : DHCP and Router Advertisement Options for the
> Discovery of Network-designated Resolvers (DNR)
>         Authors         : Mohamed Boucadair
>                           Tirumaleswar Reddy
>                           Dan Wing
>                           Neil Cook
>                           Tommy Jensen
>       Filename        : draft-ietf-add-dnr-04.txt
>       Pages           : 21
>       Date            : 2021-12-08
>
> Abstract:
>    The document specifies new DHCP and IPv6 Router Advertisement options
>    to discover encrypted DNS servers (e.g., DNS-over-HTTPS, DNS-over-
>    TLS, DNS-over-QUIC).  Particularly, it allows to learn an
>    authentication domain name together with a list of IP addresses and a
>    set of service parameters to reach such encrypted DNS servers.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-add-dnr/
>
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-add-dnr-04
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-add-dnr-04
>
>
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-
> drafts
>
>
> --
> Add mailing list
> Add@ietf.org<mailto:Add@ietf.org>
> https://www.ietf.org/mailman/listinfo/add

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

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

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.
--
Add mailing list
Add@ietf.org<mailto:Add@ietf.org>
https://www.ietf.org/mailman/listinfo/add

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.