Re: [Last-Call] [dhcwg] Last Call: <draft-ietf-homenet-naming-architecture-dhc-options-19.txt> (DHCPv6 Options for Home Network Naming Authority) to Proposed Standard

Daniel Migault <mglt.ietf@gmail.com> Wed, 21 September 2022 01:51 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3A16C14CF0B; Tue, 20 Sep 2022 18:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 NcfGxeZaBA4n; Tue, 20 Sep 2022 18:51:24 -0700 (PDT)
Received: from mail-yw1-x1129.google.com (mail-yw1-x1129.google.com [IPv6:2607:f8b0:4864:20::1129]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 0F9ABC14CE26; Tue, 20 Sep 2022 18:51:24 -0700 (PDT)
Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-3457bc84d53so48760887b3.0; Tue, 20 Sep 2022 18:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=C0zjSVb8bOnV40Ilh2/FJxjs2UtT9Z9tn8elYokXRAg=; b=nfUtnwlaMW0XEBBV9HJcqeiXuZdF75S8iJPTwNb5RyRyC3nR5DZVF1sUG2OBTvKNpJ RPjo3VBi5N1W/yVgFv8kTPbQufWLkof3zPqyix4VGplf9s+UI7PVOAx1tcwt2vgjX0ET IFMjih71k1J6pykki+J3XtaobqilAt7KGN4wJioXk8lU8n7eFYV46J4XAQKbS4qZJ321 kJMvH7x4gX4fRdZN+18mPa9g/XdjKAS8QPzYWwozBYyVtEdVSM3WhKe1y2s2/APTe0lY suQjQ0SysTEc+Joc3p1XSpG39yE1IHLe5r90NrQLbwtV/x2cclWVNeeM4lqLe8PWdsni toRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=C0zjSVb8bOnV40Ilh2/FJxjs2UtT9Z9tn8elYokXRAg=; b=6eZBdXzIszHY2NHtgvmB3Sxqp3e2hQbaqWralr64vofWkmv1bp7H0X8ikOgrIo/ZVm MsXZBF9z59pnTjKgBSHmwURTgH5Mw299nv0aNIG0acVe7RR0tqtfby1hnaqV+hx50tGM GuzJuwHkcp98t3J+tiu7s6UEwD51MbKRo+P6/w1cJ4ycTeScgp/NUR6UCp3xiIi/Pz7R bMatL8Bqjhj/xMh3shG7ymB6MRPAsDFWELqWs8xvDYR3WyGgh0cvgMkqvhe9viJIpYqj V13cuGkLksMGLiBBVmM/KV9k2op3RAH+EzUJHk3ruav+WLWlsren9XwVKcZbSKpRc9qg VStw==
X-Gm-Message-State: ACrzQf0v/eniszA+o8qrqK7fMgA0iCchkszU+51gyBakBLV+yOcUqXaC luL9XgcI3XbnU68mGLFQ0qgzHX7PByRbJxtiwxsyZ83LQXE=
X-Google-Smtp-Source: AMsMyM5d5DYUExVt+60P1CALo7LA3KHUMAUyEHy1tEm14uXdpF1C6fH0AvU+tt6spHr3Kp7rVuXOHQK0oGB+OkofJkA=
X-Received: by 2002:a81:7986:0:b0:349:853d:d165 with SMTP id u128-20020a817986000000b00349853dd165mr22518897ywc.467.1663725082698; Tue, 20 Sep 2022 18:51:22 -0700 (PDT)
MIME-Version: 1.0
References: <DE7004BC-22A0-4A97-9460-86DA081805A5@cisco.com> <B91A04F8-E7B5-4AF0-9181-A70CDF0F62A1@gmail.com>
In-Reply-To: <B91A04F8-E7B5-4AF0-9181-A70CDF0F62A1@gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Tue, 20 Sep 2022 21:51:11 -0400
Message-ID: <CADZyTkmd+V1Er0czfBVN4yEE74BDjA9=NZr1bkipQiZnxr=rKA@mail.gmail.com>
To: Bernie Volz <bevolz@gmail.com>
Cc: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, dhcwg@ietf.org, last-call@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008ee6ae05e9262e5d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/VawRrGrfE_FB4MhE4ju4ibYERQQ>
Subject: Re: [Last-Call] [dhcwg] Last Call: <draft-ietf-homenet-naming-architecture-dhc-options-19.txt> (DHCPv6 Options for Home Network Naming Authority) to Proposed Standard
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Sep 2022 01:51:27 -0000

Hi,

Thanks for the feedback Bernie, the sentence mentioning the reference is
the one below in the security consideration.

The link between the HNA and the DHCPv6 server may benefit from additional
security for example by using {{?I-D.ietf-dhc-sedhcpv6}}.

I think the example was illustrative on how the link security can be
improved. Now I also agree that referring a dead idea is not so ideal. My
questions are: do we have more valuable examples to cite and if not 2)
don't you think we should remove the sentence completely ? - I suspect
simply removing the reference creates a sort of Lapalissade.

Yours,
Daniel

On Tue, Sep 20, 2022 at 2:50 PM Bernie Volz <bevolz@gmail.com> wrote:

> Hi:
>
> I would highly recommend dropping the text/reference to:
>
> [I-D.ietf-dhc-sedhcpv6]
>               Li, L., Jiang, S., Cui, Y., Jinmei, T., Lemon, T., and D.
>               Zhang, "Secure DHCPv6", Work in Progress, Internet-Draft,
>               draft-ietf-dhc-sedhcpv6-21, 21 February 2017,
>               <https://www.ietf.org/archive/id/draft-ietf-dhc-
>               sedhcpv6-21.txt>.
>
>
> As that work was long ago abandoned by the DHC wg and it serves no purpose
> to reference dead work.
>
> Thanks.
>
> - Bernie Volz
>
> On 20/09/2022, 17:43, "iesg-secretary@ietf.org on behalf of The IESG" <
> iesg-secretary@ietf.org> wrote:
>
>
>
>    The IESG has received a request from the Home Networking WG (homenet) to
>    consider the following document: - 'DHCPv6 Options for Home Network
> Naming
>    Authority'
>      <draft-ietf-homenet-naming-architecture-dhc-options-19.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-10-04. 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
>
>
>       This document defines DHCPv6 options so an Homenet Naming Authority
>       (HNA) can automatically proceed to the appropriate configuration and
>       outsource the authoritative naming service for the home network.  In
>       most cases, the outsourcing mechanism is transparent for the end
>       user.
>
>
>
>
>    The file can be obtained via
>
> https://datatracker.ietf.org/doc/draft-ietf-homenet-naming-architecture-dhc-options/
>
>
>
>    No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>


-- 
Daniel Migault
Ericsson