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

Bernie Volz <> Sat, 25 June 2022 02:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 37650C15AD4F; Fri, 24 Jun 2022 19:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Status: No, score=-2.105 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, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AiAJG0DiCZjE; Fri, 24 Jun 2022 19:02:30 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::f29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id 9EA2FC15AD3F; Fri, 24 Jun 2022 19:02:27 -0700 (PDT)
Received: by with SMTP id cs6so7115514qvb.6; Fri, 24 Jun 2022 19:02:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=yVGLXoARL5t02vbu8xuckt517wgIZ73rfPTcMYs2zhg=; b=eV+G+W1TRh4B23s2VluAlz5dmuhIHAk0/Tawh5b0MGivigxUhuG4sA8/I66dT2kQCz GWSae7G0ZyNEJd71jFbslDFb/5wLDyDoYiQ3RNuO6H7pSGS7WDeM88KTlwgAwLG9XRPe uwHQvS0ed5lhBdj64d73BI5S8PFLvojPdOr85RkkUpGcFpIw5PY5ISrGfq0/gXqNfHQn RoR9j3304PX8BA4qRnZAWLEQTJgcpdpfQLuRbCawMjxl2p7eOPvTyXyndXuE5X9i2X7v DeAuCc3n4v77QltwcSBha8NHIbeuc5fuqCUwOa/to1TWGn8zOatAixZP46J7YoBZ/Alm sUkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=yVGLXoARL5t02vbu8xuckt517wgIZ73rfPTcMYs2zhg=; b=mBxEE6wP/DyoLRKWSDb47Tv+DaLsB+c+eJlxwfqpVQuEqY1FQVeusKNR1IN8I7Ybb2 KDwUi8gdY55mgDtrbHnTQqkCnOXgaSPhuPfDSkyH9rc0egh92SUX66o16HvXEQ3Iym/T bNG3+PcjOAh0kxnx1eSLxZmkAFbrnRr9A5qypkbZY5seGAPZYqKbakwbkFZ+4TYgKQ/b kGMzEw/8u0BjhH1kbOvCrs+lKhUGBmicwsgd6J4WH6p9zmqaXfu/PZ+3zs6atDrISngR 6wAQCoIwEd8yVxQsGcfstgxOmh46k7zsLAucr/HDnXhz4WBsMSWMNju8wyi7fk1zCe1N ySdA==
X-Gm-Message-State: AJIora/qkW0lyjFg7s5nmbJ3xOUAVhqBoTJIrTjRmPCK/KN+frXb6YK1 VbABuua+RCeOcK/PvssI0SKs4S/ydw==
X-Google-Smtp-Source: AGRyM1uR9gC28RtQIF5W8GmU9JBc4nTEemzzW/AO0ldRayaObbc+ou55cUU7EeqLxCxXOspofupTNA==
X-Received: by 2002:a05:6214:240d:b0:470:46a1:fc74 with SMTP id fv13-20020a056214240d00b0047046a1fc74mr1626180qvb.30.1656122546143; Fri, 24 Jun 2022 19:02:26 -0700 (PDT)
Received: from ( []) by with ESMTPSA id d15-20020a05620a240f00b006a6278a2b31sm3564112qkn.75.2022. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Jun 2022 19:02:25 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Bernie Volz <>
Mime-Version: 1.0 (1.0)
Date: Fri, 24 Jun 2022 22:02:24 -0400
Message-Id: <>
References: <>
Cc:,,, add@ietf.Org,
In-Reply-To: <>
To: "Eric Vyncke (evyncke)" <>
X-Mailer: iPad Mail (19F77)
Archived-At: <>
Subject: 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
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 25 Jun 2022 02:02:31 -0000


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) <> 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 in cc in all your replies.
> Thank very much in advance for your review
> Regards
> -éric
> On 24/06/2022, 19:31, " on behalf of The IESG" <> 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
> mailing lists by 2022-07-08. Exceptionally, comments may
>    be sent to 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
>    The ADD WG has another document, which should probably be reviewed at the same time.
>    No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> dhcwg mailing list