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

[Kent Watsen <[e-mail]>]

Hi Alex,

	Per Ian’s response, are you okay with this Errata being closed?

Kent



> On Sep 15, 2021, at 10:29 AM, [e-mail] wrote:
> 
> Hi,
>  
> To clarify, is the errata meant to permit the configuration of multiple, comma separated bootstrap server URIs in a single entry for uri-data?
>  
> If so, the intended function is to have one URI entry per uri-data entry (containing URI-length and the associated URI). Multiple instances of uri-data entry are permitted. I think the text describes this adequately as does the reference to RFC7227. From section 8.3:
>  
> “Both of the DHCPv4 and DHCPv6 options defined in this section encode
>    a list of bootstrap server URIs.  The "URI" structure is a DHCP option that can contain multiple URIs (see [RFC7227], Section 5.7 <https://datatracker.ietf.org/doc/html/rfc7227#section-5.7>).
>    Each URI entry in the bootstrap-server-list is structured as follows:”
>  
> They could be represented in the DHCP server’s configuration via a comma separated list, but in the DHCP option sent to the client they need to be formatted as separate uri-data entries.
>  
> I’m unsure about the relevance of Note: “Most DHCP servers can only be configured with ASCII strings for options”
>  
> The URI encoding scheme is defined by RFC3986, which only permits ASCII.
>  
> Thanks,
> Ian
>  
> From: RFC Errata System <[e-mail] <mailto:[e-mail]>>
> Date: Tuesday, 14. September 2021 at 13:25
> To: [e-mail] <mailto:[e-mail]> <[e-mail] <mailto:[e-mail]>>, Farrer, Ian <[e-mail] <mailto:[e-mail]>>, [e-mail] <mailto:[e-mail]> <[e-mail] <mailto:[e-mail]>>, [e-mail] <mailto:[e-mail]> <[e-mail] <mailto:[e-mail]>>, [e-mail] <mailto:[e-mail]><[e-mail] <mailto:[e-mail]>>, [e-mail] <mailto:[e-mail]> <[e-mail] <mailto:[e-mail]>>, [e-mail] <mailto:[e-mail]><[e-mail] <mailto:[e-mail]>>
> Cc: [e-mail] <mailto:[e-mail]> <[e-mail] <mailto:[e-mail]>>, [e-mail] <mailto:[e-mail]> <[e-mail] <mailto:[e-mail]>>, [e-mail] <mailto:[e-mail]> <[e-mail] <mailto:[e-mail]>>
> Subject: [Technical Errata Reported] RFC8572 (6685)
> 
> 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/eid6685 <https://www.rfc-editor.org/errata/eid6685>
> 
> --------------------------------------
> Type: Technical
> Reported by: Alex Krichevsky <[e-mail] <mailto:[e-mail]>>
> 
> Section: 8.3
> 
> Original Text
> -------------
>    Each URI entry in the bootstrap-server-list is structured as follows:
> 
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+-+-+-+-+-+
>     |       uri-length              |          URI                  |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+-+-+-+-+-+
> 
>     * uri-length: 2 octets long; specifies the length of the URI data.
>     * URI: URI of the SZTP bootstrap server.
> 
> Corrected Text
> --------------
> Multiple URI entries can be specified in a comma-separated list.
> 
> Notes
> -----
> Most of DHCP servers can be configured only with ASCII string for options.
> 
> 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