Re: [netconf] [Technical Errata Reported] RFC8572 (6684)

Kent Watsen <kent+ietf@watsen.net> Mon, 20 September 2021 16:03 UTC

Return-Path: <0100017c03f28c54-5e7092d0-720c-45b5-8140-7cbd21a453c4-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBF7C3A15EF for <netconf@ietfa.amsl.com>; Mon, 20 Sep 2021 09:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 MAdA5ho92w5M for <netconf@ietfa.amsl.com>; Mon, 20 Sep 2021 09:03:23 -0700 (PDT)
Received: from a8-33.smtp-out.amazonses.com (a8-33.smtp-out.amazonses.com [54.240.8.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3545B3A15ED for <netconf@ietf.org>; Mon, 20 Sep 2021 09:03:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1632153800; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=U7yhql4wXXc0CqZMYA6wXRv2DgQGBz4690YM2Uphopw=; b=A3htz4j4GuPaAlOkMp4dEOnqSri8gm/VLZjHx4XzbfZjEoQeBfSqma/HsGFBcA/V KJOOqMUAle3o76uV8Az2mXb3dCUVMmTis+ln84Sg36BmZoMokjbCjIS/J506OX2ILHE Nas51Ucn7TW7Lbly1Jf6XpeGFwiTDOSyoQzGbXQo=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100017c03f28c54-5e7092d0-720c-45b5-8140-7cbd21a453c4-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CFB87B12-8729-42A8-83A5-0E45AE17C7EA"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Mon, 20 Sep 2021 16:03:19 +0000
In-Reply-To: <DB6PR10MB17999637AC019DA25CB449FFC9DF9@DB6PR10MB1799.EURPRD10.PROD.OUTLOOK.COM>
Cc: "ian.farrer@telekom.de" <ian.farrer@telekom.de>, "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, "mikael.abrahamsson@t-systems.se" <mikael.abrahamsson@t-systems.se>, "warren@kumari.net" <warren@kumari.net>, "rwilton@cisco.com" <rwilton@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "netconf@ietf.org" <netconf@ietf.org>, Ofer Rotschield <ofer@asocscloud.com>, Evgeny Lischuk <evgeny@asocscloud.com>, Michael Freidkin <michael@asocscloud.com>, Dan Berin <danb@asocscloud.com>, Moshe Sasson <moshe@asocscloud.com>
To: Alex Krichevsky <alexkri@asocscloud.com>
References: <20210914111540.33BA6F4084D@rfc-editor.org> <FR2P281MB08215F8E8433AA389DB2A566FCDC9@FR2P281MB0821.DEUP281.PROD.OUTLOOK.COM> <DB6PR10MB17999637AC019DA25CB449FFC9DF9@DB6PR10MB1799.EURPRD10.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2021.09.20-54.240.8.33
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/a1f6Cl1T8wUwyMsEMMA7WBM1PCc>
Subject: Re: [netconf] [Technical Errata Reported] RFC8572 (6684)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2021 16:03:29 -0000

Hi Alex,

	The Errata system is rather particular...
	Can you file another errata with just the corrected text?

Rob,

	As AD, can you cancel https://www.rfc-editor.org/errata/eid6684? <https://www.rfc-editor.org/errata/eid6684?>

Thanks,
Kent (all hats)


> On Sep 19, 2021, at 3:18 AM, Alex Krichevsky <alexkri@asocscloud.com> wrote:
> 
> Hi Ian,
>  
> Thank you very much for your response!
> Agreed, your version of the correction is fine too.
>  
> Thanks,
>  
> Alex Krichevsky
> Embedded Software Director
> 21 Hamelacha Street|Rosh Haayin, 48091| 
> Edan 1 Twin Building|Park Afek|P.O.Box 11459|Israel 
> Mobile: +972+506347290
> Web: www.asocscloud.com <http://www.asocscloud.com/>|  
> Follow us on LinkedIn <https://www.linkedin.com/company/54063/> 
> <image001.png>
>  
>  
>  
>  
> From: ian.farrer@telekom.de <mailto:ian.farrer@telekom.de> <ian.farrer@telekom.de <mailto:ian.farrer@telekom.de>> 
> Sent: Thursday, 16 September 2021 10:48
> To: rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>; kent+ietf@watsen.net <mailto:kent+ietf@watsen.net>; mikael.abrahamsson@t-systems.se <mailto:mikael.abrahamsson@t-systems.se>; warren@kumari.net <mailto:warren@kumari.net>; rwilton@cisco.com <mailto:rwilton@cisco.com>; mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>
> Cc: Alex Krichevsky <alexkri@asocscloud.com <mailto:alexkri@asocscloud.com>>; netconf@ietf.org <mailto:netconf@ietf.org>; rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>
> Subject: Re: [Technical Errata Reported] RFC8572 (6684)
>  
> Hi,
>  
> The intent of the text is to define how OPTION_V4_SZTP_REDIRECT when larger than 255 bytes is conveyed in the DHCP message.
>  
> RFC3396 describes how this is achieved – the >255 byte option is created, it is then split on an octet boundary into multiple instances
> of, in this case, OPTION_V4_SZTP_REDIRECT options which are placed in the DHCP message.
>  
> On receipt, the client re-assembles all of the instances of OPTION_V4_SZTP_REDIRECT into a single option and then processes the resulting
> payload.
>  
> The proposed wording change could be interpreted to permit multiple ‘self-contained’ (i.e. not split according to RFC396)  instances of the
> option in a message, which is not generally permitted  and may not work with client implementations.
>  
> I agree that the current text can be read as contradictory. I suggest the following change to resolve this:
>  
> Original
> ----
>    The DHCPv4 server MAY include a single instance of the
>    OPTION_V4_SZTP_REDIRECT option in DHCP messages it sends.  Servers
>    MUST NOT send more than one instance of the OPTION_V4_SZTP_REDIRECT
>    option.
>  
> Corrected
> -----
> The DHCPv4 server MAY include OPTION_V4_SZTP_REDIRECT in DHCP messages it sends.
>  
> As the remainder of the section explains the intended behavior referencing RFC3396, I think this removes the ambiguity.
>  
> Thanks,
> Ian
>  
>  
> From: RFC Errata System <rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>>
> Date: Tuesday, 14. September 2021 at 13:16
> To: kent+ietf@watsen.net <mailto:kent+ietf@watsen.net> <kent+ietf@watsen.net <mailto:kent+ietf@watsen.net>>, Farrer, Ian <ian.farrer@telekom.de <mailto:ian.farrer@telekom.de>>, mikael.abrahamsson@t-systems.se <mailto:mikael.abrahamsson@t-systems.se> <mikael.abrahamsson@t-systems.se <mailto:mikael.abrahamsson@t-systems.se>>, warren@kumari.net <mailto:warren@kumari.net> <warren@kumari.net <mailto:warren@kumari.net>>, rwilton@cisco.com <mailto:rwilton@cisco.com><rwilton@cisco.com <mailto:rwilton@cisco.com>>, kent+ietf@watsen.net <mailto:kent+ietf@watsen.net> <kent+ietf@watsen.net <mailto:kent+ietf@watsen.net>>, mjethanandani@gmail.com <mailto:mjethanandani@gmail.com><mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>>
> Cc: alexkri@asocscloud.com <mailto:alexkri@asocscloud.com> <alexkri@asocscloud.com <mailto:alexkri@asocscloud.com>>, netconf@ietf.org <mailto:netconf@ietf.org> <netconf@ietf.org <mailto:netconf@ietf.org>>, rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org> <rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>>
> Subject: [Technical Errata Reported] RFC8572 (6684)
> 
> The following errata report has been submitted for RFC8572,
> "Secure Zero Touch Provisioning (SZTP)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6684 <https://www.rfc-editor.org/errata/eid6684>
> 
> --------------------------------------
> Type: Technical
> Reported by: Alex Krichevsky <alexkri@asocscloud.com <mailto:alexkri@asocscloud.com>>
> 
> Section: 8.1
> 
> Original Text
> -------------
>    The DHCPv4 server MAY include a single instance of the
>    OPTION_V4_SZTP_REDIRECT option in DHCP messages it sends.  Servers
>    MUST NOT send more than one instance of the OPTION_V4_SZTP_REDIRECT
>    option.
> 
> Corrected Text
> --------------
>    The DHCPv4 server MAY include a single instance or multiple instances of the
>    OPTION_V4_SZTP_REDIRECT option in DHCP messages it sends.
> 
> Notes
> -----
> The original text contradicts the statement in the same section:
>    "If the length of the 'bootstrap-server-list' field is too large to
>    fit into a single option, then OPTION_V4_SZTP_REDIRECT MUST be split
>    into multiple instances of the option according to the process
>    described in [RFC3396]."
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC8572 (draft-ietf-netconf-zerotouch-29)
> --------------------------------------
> Title               : Secure Zero Touch Provisioning (SZTP)
> Publication Date    : April 2019
> Author(s)           : K. Watsen, I. Farrer, M. Abrahamsson
> Category            : PROPOSED STANDARD
> Source              : Network Configuration
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG