Re: [netconf] [Technical Errata Reported] RFC8040 (7866)

[Andy Bierman <[e-mail]>]

On Thu, Mar 28, 2024 at 12:25 PM Mahesh Jethanandani <
[e-mail]> wrote:

> Apparently, I can edit the Errata. Please confirm that this is all the
> corrections we are making:
>
> Original Text:
> -----------------
>
> Text occurs in three places
>
>
Now there are 2 sections to identify:

1) sec. 3.5.3 (para 4)
2) sec. 3.5.3 (para 5)
3) sec. 5.1 (para 3)

Andy

1)
>
>      The leaf-list value is specified as a string, using the canonical
>       representation for the YANG data type.  Any reserved characters
>       MUST be percent-encoded, according to Sections 2.1 and 2.5 of
>       [RFC3986].
>
>
> 2)
>
>      The key value is specified as a string, using the canonical
>       representation for the YANG data type.  Any reserved characters
>       MUST be percent-encoded, according to Sections 2.1 and 2.5 of
>       [RFC3986].
>
> 3)
>
>        The contents of any query parameter value MUST be encoded according
>         to Section 3.4 of [RFC3986].  Any reserved characters MUST be
>         percent-encoded, according to Sections 2.1 and 2.5 of [RFC3986].
>
>
> Corrected Text:
> --------------------
>
> 1)
>
>       The leaf-list value is specified as a string, using the canonical
>       representation for the YANG data type.  Any reserved characters
>       MUST be percent-encoded, according to Sections 2.1, 2.2, and 2.5 of
>       [RFC3986].
>
> 2)
>
>       The key value is specified as a string, using the canonical
>       representation for the YANG data type.  Any reserved characters
>       MUST be percent-encoded, according to Sections 2.1, 2.2, and 2.5 of
>       [RFC3986].
>
> 3)
>
>      The contents of any query parameter value MUST be encoded according
>       to Section 3.4 of [RFC3986].  Any reserved characters MUST be
>       percent-encoded, according to Sections 2.1, 2.2, and 2.5 of
> [RFC3986].
>
> Notes:
> ---------
>       The reserved character list is defined in section 2.2 of RFC 3986
>
> On Mar 28, 2024, at 11:05 AM, Andy Bierman <[e-mail]> wrote:
>
>
>
> On Thu, Mar 28, 2024 at 9:25 AM Mahesh Jethanandani <
> [e-mail]> wrote:
>
>> Hi Kent/Andy,
>>
>> Should I reject the Errata so it can be filed again?
>>
>>
> I guess so -- I don't think there is any way to edit this one
>
> Andy
>
>
>> On Mar 27, 2024, at 8:54 AM, Kent Watsen <[e-mail]> wrote:
>>
>> This errata is incomplete.
>> The issue occurs three times.
>> The occurrence in Section 5.1 is missing.
>>
>> K.
>>
>>
>> On Mar 23, 2024, at 1:38 PM, RFC Errata System <[e-mail]>
>> wrote:
>>
>> The following errata report has been submitted for RFC8040,
>> "RESTCONF Protocol".
>>
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid7866
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Andy Bierman <[e-mail]>
>>
>> Section: 3.5.3
>>
>> Original Text
>> -------------
>> Text occurs in two places
>>
>> 1)
>>
>>     The leaf-list value is specified as a string, using the canonical
>>     representation for the YANG data type.  Any reserved characters
>>     MUST be percent-encoded, according to Sections 2.1 and 2.5 of
>>     [RFC3986].
>>
>>
>> 2)
>>
>>     The key value is specified as a string, using the canonical
>>     representation for the YANG data type.  Any reserved characters
>>     MUST be percent-encoded, according to Sections 2.1 and 2.5 of
>>     [RFC3986].
>>
>>
>> Corrected Text
>> --------------
>>
>> 1)
>>
>>     The leaf-list value is specified as a string, using the canonical
>>     representation for the YANG data type.  Any reserved characters
>>     MUST be percent-encoded, according to Sections 2.1, 2.2, and 2.5 of
>>     [RFC3986].
>>
>> 2)
>>
>>     The key value is specified as a string, using the canonical
>>     representation for the YANG data type.  Any reserved characters
>>     MUST be percent-encoded, according to Sections 2.1, 2.2, and 2.5 of
>>     [RFC3986].
>>
>>
>> Notes
>> -----
>> The reserved character list is defined in section 2.2 of RFC 3986
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". (If it is spam, it
>> will be removed shortly by the RFC Production Center.) Please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party
>> will log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC8040 (draft-ietf-netconf-restconf-18)
>> --------------------------------------
>> Title               : RESTCONF Protocol
>> Publication Date    : January 2017
>> Author(s)           : A. Bierman, M. Bjorklund, K. Watsen
>> Category            : PROPOSED STANDARD
>> Source              : Network Configuration
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>>
>>
>>
>> Mahesh Jethanandani
>> [e-mail]
>>
>>
>>
>>
>>
>>
>>
>
> Mahesh Jethanandani
> [e-mail]
>
>
>
>
>
>
>