Re: [dhcwg] [Last-Call] FW: Last Call: <draft-ietf-add-dnr-09.txt> (DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)) to Proposed Standard

mohamed.boucadair@orange.com Tue, 28 June 2022 05:55 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860A8C15A73F; Mon, 27 Jun 2022 22:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5qIBDr0q53rJ; Mon, 27 Jun 2022 22:55:24 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 235EBC15A73C; Mon, 27 Jun 2022 22:55:19 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) (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 opfedar23.francetelecom.fr (ESMTP service) with ESMTPS id 4LXDMm6TGczBrW0; Tue, 28 Jun 2022 07:55:16 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1656395716; bh=YPiIv9qdGWpRMOV2FkjTGNCT7LxrVllrLGK+LZMWQOE=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=fWknaV2J9G6ebOO65VEJk9IscVXiH0oDB0Szj4GJd1DNNOKUhKs/pPYziIoJIMhHu P+YITPQRKJF1+vrr8c80NiXRDKtOqlQ6K04XcgRrZMh5gGS3OxlUtl3MBRkpvRYgMd 7bqFJV12L+kD7FQUjX3Z4M22+0nyro88t8N/emk/F+qg2RHb8QEE7od1Fr2HoE6CcO GejUViEL76a4xP96/LMGQr06XsRxxYdgOo8UwkANmhpi+isvmea7YD8U5X5uJqFkyx HRzW9el9qxqeJkUvZsoTGMEHJDrGWsqSah7tlzZ9Xj096ZNglsNuV6B4zwRFtP9Xrl 337TzSPePGEDQ==
From: <mohamed.boucadair@orange.com>
To: Martin Thomson <mt@lowentropy.net>, Bernie Volz <bevolz@gmail.com>
CC: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-add-dnr@ietf.org" <draft-ietf-add-dnr@ietf.org>, "add@ietf.Org" <add@ietf.Org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: [Last-Call] [dhcwg] FW: Last Call: <draft-ietf-add-dnr-09.txt> (DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)) to Proposed Standard
Thread-Index: AQHYioNScGW26MA1CUS25xYs1G6hDq1kSEDQ
Content-Class:
Date: Tue, 28 Jun 2022 05:55:16 +0000
Message-ID: <3045_1656395716_62BA97C4_3045_346_1_e775a6e816b24dd1b9465b6a4666ea3b@orange.com>
References: <58B43635-5F2E-4106-BDD8-C6830DEC149F@cisco.com> <0C05449E-058B-447B-87F9-19D5563C4A77@gmail.com> <12962_1656310009_62B948F9_12962_271_1_a410279b328c4ce1a87452ac143e3710@orange.com> <e63dcd41-ba17-4a8b-ad4a-b243482e4a7d@beta.fastmail.com>
In-Reply-To: <e63dcd41-ba17-4a8b-ad4a-b243482e4a7d@beta.fastmail.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=2022-06-28T05:19:40Z; 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=056523e1-19f6-4b1c-8f78-67536cfe5c36; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.52]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/XolCHuSOW8WwzE8d9lkRS9_nndw>
Subject: Re: [dhcwg] [Last-Call] FW: Last Call: <draft-ietf-add-dnr-09.txt> (DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)) to Proposed Standard
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jun 2022 05:55:28 -0000

Hi Martin,

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : Martin Thomson <mt@lowentropy.net>
> Envoyé : mardi 28 juin 2022 02:09
> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>om>;
> Bernie Volz <bevolz@gmail.com>
> Cc : dhcwg@ietf.org; draft-ietf-add-dnr@ietf.org; add@ietf.Org;
> last-call@ietf.org
> Objet : Re: [Last-Call] [dhcwg] FW: Last Call: <draft-ietf-add-
> dnr-09.txt> (DHCP and Router Advertisement Options for the
> Discovery of Network-designated Resolvers (DNR)) to Proposed
> Standard
> 
> How feasible is it to have multiple instances of ADN+IP+parameters
> in DHCPv4?  (I agree that the changes look good, but is this
> likely to ever allow anything more than say 2 instances?
> 

[Med] Multiple instances are possible but are likely to be split into multiple options. The main point of listing more than one instance in Figure 4 is to make it explicit how each DNR instance data can be unambiguously identified when concatenated and without making an assumption on the split boundaries. 

> Related: why is "DNR Instance Data Length" 2 bytes?

[Med] We do already allow for a single long DNR instance data to be split into multiple options. 2 bytes is used to accommodate such cases.

> 
> On Mon, Jun 27, 2022, at 16:06, mohamed.boucadair@orange.com
> wrote:
> > Hi Bernie,
> >
> > Thank you for the comment.
> >
> > Please check https://tinyurl.com/latest-dnr-changes and let me
> know if
> > any other change is needed.
> >
> > Cheers,
> > Med
> >
> >> -----Message d'origine-----
> >> De : Bernie Volz <bevolz@gmail.com>
> >> Envoyé : samedi 25 juin 2022 04:02
> >> À : Eric Vyncke (evyncke) <evyncke=40cisco.com@dmarc.ietf.org>
> >> Cc : ipv6@ietf.org; dhcwg@ietf.org; draft-ietf-add-
> dnr@ietf.org;
> >> add@ietf.Org; last-call@ietf.org Objet : Re: [dhcwg] FW: Last
> Call:
> >> <draft-ietf-add-dnr-09.txt> (DHCP and Router Advertisement
> Options
> >> for the Discovery of Network-designated Resolvers (DNR)) to
> Proposed
> >> Standard
> >>
> >> Hi:
> >>
> >> Thanks Eric for adding dhc wg. I have the following comment
> related
> >> to DHCP.
> >>
> >> For DHCPv4, you will need to reconsider the option encoding as
> >> multiple instances of options are usually concatenated as per
> RFC
> >> 3396. As an example, you may want to refer to how the Vender-
> >> Identifying Vendor-Specific Information Option (127) is handled
> - see
> >> RFC 3925. You already reference RFC 3396 to be able to encode
> long
> >> domain names. Basically RFC 3925 uses an additional “data”
> >> length field for each instance (this adds one additional octet
> per
> >> instance). You might want to consider whether that is a single
> octet
> >> or perhaps two octets given the potential size of the option?
> >>
> >> - Bernie Volz, dhc co-chair
> >>
> >> > On Jun 24, 2022, at 2:16 PM, Eric Vyncke (evyncke)
> >> <evyncke=40cisco.com@dmarc.ietf.org> wrote:
> >> >
> >> > Extending the IETF Last Call to DHC and 6MAN WG as this IETF
> >> draft contains extension to DHC and IPv6 RA.
> >> >
> >> > Please keep add@ietf.Org and last-call@ietf.org in cc in all
> >> your replies.
> >> >
> >> > Thank very much in advance for your review
> >> >
> >> > Regards
> >> >
> >> > -éric
> >> >
> >> >
> >> > On 24/06/2022, 19:31, "iesg-secretary@ietf.org on behalf of
> The
> >> IESG" <iesg-secretary@ietf.org> wrote:
> >> >
> >> >
> >> >    The IESG has received a request from the Adaptive DNS
> >> Discovery WG (add) to
> >> >    consider the following document: - 'DHCP and Router
> >> Advertisement Options for
> >> >    the Discovery of Network-
> >> >       designated Resolvers (DNR)'
> >> >      <draft-ietf-add-dnr-09.txt> as Proposed Standard
> >> >
> >> >    The IESG plans to make a decision in the next few weeks,
> and
> >> solicits final
> >> >    comments on this action. Please send substantive comments
> to
> >> the
> >> >    last-call@ietf.org mailing lists by 2022-07-08.
> >> Exceptionally, comments may
> >> >    be sent to iesg@ietf.org instead. In either case, please
> >> retain the beginning
> >> >    of the Subject line to allow automated sorting.
> >> >
> >> >    Abstract
> >> >
> >> >
> >> >       The document specifies new DHCP and IPv6 Router
> >> Advertisement options
> >> >       to discover encrypted DNS resolvers (e.g., DNS-over-
> HTTPS,
> >> DNS-over-
> >> >       TLS, DNS-over-QUIC).  Particularly, it allows a host to
> >> learn an
> >> >       authentication domain name together with a list of IP
> >> addresses and a
> >> >       set of service parameters to reach such encrypted DNS
> >> resolvers.
> >> >
> >> >
> >> >
> >> >
> >> >    The file can be obtained via
> >> >    https://datatracker.ietf.org/doc/draft-ietf-add-dnr/
> >> >
> >> >    The ADD WG has another document
> >> https://datatracker.ietf.org/doc/draft-ietf-add-ddr/, which
> should
> >> probably be reviewed at the same time.
> >> >
> >> >    No IPR declarations have been submitted directly on this
> I-D.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > dhcwg mailing list
> >> > dhcwg@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/dhcwg
> >

_________________________________________________________________________________________________________________________

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.