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

[Kent Watsen <[e-mail]>]

Hi Mahesh,

I cannot tell from your edit, but in the original Errata, just *before* the line that says “Original Text”, there is the line "Section 3.5.3 says:”.   I think that Andy means that this line should change also.  Does your edit change this line also?

IDK if it is editable.  When filing an Errata, there is a field called “Section” separate from the Original/Corrected text sections.  This field is intended to be either a section number (presumably Andy entered “3.5.3”) or the string “GLOBAL” (which likely should be the value now, given that there is more than one section).  Are you able to change this value too?

Kent // contributor


> On Mar 28, 2024, at 4:53 PM, Mahesh Jethanandani <[e-mail]> wrote:
> 
> Ok. How about this?
> 
> Original Text:
> ------------------
> 
> Text occurs in five 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]. 
> 
> 3)    
> 
>       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].
> 
> 4)    
> 
>       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].  The comma (",") character MUST be percent-encoded if
>       it is present in the key value.
> 
> 
> 5)    
> 
>       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 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].
> 
> 4)    
> 
>       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].  The comma (",") character MUST be percent-encoded if
>       it is present in the key value.
> 
> 5)    
>       
>       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 12:39 PM, Andy Bierman <[e-mail] <mailto:[e-mail]>> wrote:
>> 
>> 
>> 
>> On Thu, Mar 28, 2024 at 12:25 PM Mahesh Jethanandani <[e-mail] <mailto:[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] <mailto:[e-mail]>> wrote:
>>>> 
>>>> 
>>>> 
>>>> On Thu, Mar 28, 2024 at 9:25 AM Mahesh Jethanandani <[e-mail] <mailto:[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] <mailto:[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] <mailto:[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] <mailto:[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] <mailto:[e-mail]>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
>>> Mahesh Jethanandani
>>> [e-mail] <mailto:[e-mail]>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
> 
> 
> Mahesh Jethanandani
> [e-mail] <mailto:[e-mail]>
> 
> 
> 
> 
> 
>