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 02:30 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 11E09C14F74D; Tue, 20 Sep 2022 19:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, 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=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 vsYxGB7IXTfG; Tue, 20 Sep 2022 19:30:15 -0700 (PDT)
Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (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 56745C14CF1F; Tue, 20 Sep 2022 19:30:15 -0700 (PDT)
Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-3450990b0aeso48396097b3.12; Tue, 20 Sep 2022 19:30:15 -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=SyF3bj8BuWM1tc4GMLdt6lO8yGyC1kWJ6wWWoL2/Ogs=; b=BpyU836U0vKAnjzaNW9MpNq6HYP/0GEalw8jbSYTMl6CNh0MDKkFAfnqlfNYMdsTG6 LjkhrcDcjwpI3zl/CoNSEw/fFHr2gSUQYYkYv8TTtod01mxzqtMYKwS2LbSb18kiaQWD kLH3T/7OZ3MZMkzX5R+jbmtO0eU1udFlVJ18gbfJp0hO9/42stpuLfIW/QaTtMoC9TRm +L9JyNOStUymTM9sxAgkiG5h0cqGh9UrHbqGp/mIGSMPlqKEZvZFCsnJ4M3+oT3FKjVo gIdq/MX+mOp8W9CbUatRDFEwsrhh6CmxB7i8MsmzdMyzjM4iyFdFYysLwCSyCQArGBmH bziQ==
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=SyF3bj8BuWM1tc4GMLdt6lO8yGyC1kWJ6wWWoL2/Ogs=; b=jaQTFh4hfTyciukCvEK+VRMaTuW1FAxIqB0GLwCBQrcgGe8q95iljAYwUUS6vdacYh NTtxDFLL8f4pL3U9cixuNSJeTqVRRrJifoErhNtJnr2P1/pjv4uLjWQ7E1MSlLMJOfQN 6rwp+n+QENaOicEJ5MXMGwxdLmpRJI57Jkpggv3yeJ84drxjOUQiIZeRdn2HTCt67TYx fStBeTbNbhpHJxdnMkc1m5b/CI4PxikB+P6oSPfpvKGJcHpOHIaegf6G01VM+oFXbgST MJWzCVkvCUkkzc63ah8uFkgxJGM3Oc5Soqq4YntsM8Sqr8V+RCZRMLc3aSaVd7McDR50 XUyg==
X-Gm-Message-State: ACrzQf3zHkI3pKOqNG7tvhaYMZ5Psqo7zEV73vn6Mx63XB/Tt63tEsMT /A+SnG7bE4+zTNiXam6RiOZQU1IRLUKFCNz2Ahc=
X-Google-Smtp-Source: AMsMyM4qYm7D6GnEAhoHHlHnZmk9LOptfXgLZ4T4UDB6DrJGoAnc8/kpYDVJv1/MqNd5XoPWpJg0KMUqzvaHnzZM6u0=
X-Received: by 2002:a81:84c6:0:b0:345:1c4e:f6f3 with SMTP id u189-20020a8184c6000000b003451c4ef6f3mr22542220ywf.163.1663727413964; Tue, 20 Sep 2022 19:30:13 -0700 (PDT)
MIME-Version: 1.0
References: <CADZyTkmd+V1Er0czfBVN4yEE74BDjA9=NZr1bkipQiZnxr=rKA@mail.gmail.com> <574EC4CA-3DD9-435A-BFE1-EDFDA2F08694@gmail.com>
In-Reply-To: <574EC4CA-3DD9-435A-BFE1-EDFDA2F08694@gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Tue, 20 Sep 2022 22:30:02 -0400
Message-ID: <CADZyTkngCJmbSSznnD-joxQkcgPQuZ-syJrdb7_rf3_gDvMe1w@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="00000000000083347305e926b975"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/C_0OiTHlYaLTRPVs2VvpNRcHOV0>
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 02:30:16 -0000

Just published version 20 with the sentence being removed.

Thanks for the feedback!
Yours,
Daniel


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

> Yes, removing entire sentence is what I had in mind.
>
> - Bernie Volz
>
> On Sep 20, 2022, at 9:51 PM, Daniel Migault <mglt.ietf@gmail.com> wrote:
>
> 
> 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
>
>

-- 
Daniel Migault
Ericsson