Re: [Netconf] Alexey Melnikov's Discuss on draft-ietf-netconf-zerotouch-25: (with DISCUSS and COMMENT)

[[e-mail]]

Hi Alexey,

Thanks for the review. Please see my response for you comment on the Common Field Encoding below.

Thanks,
Ian

> 
> 
>> 8.3.  Common Field Encoding
>> 
>>  Both of the DHCPv4 and DHCPv6 options defined in this section encode
>>  a list of bootstrap server URIs.  The "URI" structure is an option
>>  that can contain multiple URIs (see [RFC7227], Section 5.7).
>> 
>>    bootstrap-server-list:
>> 
>> This is confusing, because I believe the following is a single entry
>> in the list, not the whole list syntax:
>> 
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+-+-+-+-+-+
>>    |       uri-length              |          URI                  |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+-+-+-+-+-+
>> 
>>    o uri-length: 2 octets long, specifies the length of the URI data.
>> 
>>    o URI: URI of zerotouch bootstrap server, using the HTTPS URI
>>      scheme defined in Section 2.7.2 of RFC7230.  URI MUST be in
>>      form "https://<ip-address-or-hostname>[:<port>]".
>> 
>> So if I am correct above, please clarify this by changing
>> "bootstrap-server-list:" to "bootstrap-server-list is a list of 1 or more
>> items, each with the following syntax:" (Or something like this.)
>> 
>> Also, "URI" deserve to be a Normative Reference, as it defines the
>> generic syntax you are referring to.
> 

[if  Propose removing the ‘bootstrap-server-list:’ line and extending
the intro paragraph to read:

 "Both of the DHCPv4 and DHCPv6 options defined in this section encode
 a list of bootstrap server URIs.  The "URI" structure is an option
 that can contain multiple URIs (see [RFC7227], Section 5.7). Each URI
 entry in the bootstrap-server-list is structured as follows:”

Also, I’ve added RFC7230 to the normative references.]