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

[Kent Watsen <[e-mail]>]

Hi Martin,


>>    NEWER:
>>        The "insert" (Section 4.8.5) and "point" (Section 4.8.6) query
>>        parameters MUST be supported by the PUT method for data resources.
>>        These parameters are only allowed if the target resource is an
>>        entry of an "ordered-by user" list or leaf-list.
> 
> This isn't quite correct (the target resource in POST is not a list
> entry), and it isn't needed IMO.  The text in4.8.5 and 4.8.6 says the
> same thing already, so we don't need to say it here as well.  Esp. not
> in an errata.

But this is in Section 4.5, which only regards PUT.

That said, I also noticed redundant text regarding where the query-parameters are allowed.  Generally, it seems such text should be in Sections 4.8.5 and 4.8.6, more so than Section 4.5...


>> 2) for the “insert” query parameter
>> 
>>    In Section 4.8.5: The "insert" Query Parameter
>> 
>>    OLD:
>> 
>>       The default value is "last".
>> 
>>       This parameter is only supported for the POST and PUT methods.  It is
>>       also only supported if the target resource is a data resource, and
>>       that data represents a YANG list or leaf-list that is
>>       "ordered-by user”.
>> 
>>    NEW:
>> 
>>       The default value is “last”, with exception to when used with PUT
>>       and the target resource already exists, in which case the default
>>       is to replace the target resource without altering its position in the
>>       "ordered-by user” list or leaf-list.
> 
> Ok, but is the grammar correct "with exception to when..."?

There’s a fork in this thread on this point.  Let’s see how that resolves first…


>>       This parameter is only supported for the POST and PUT methods.
>>       It is also only supported if the target resource is a data resource 
>>       that is an entry of an "ordered-by user" list or leaf-list.
> 
> I prefer the old text over this.

But Section 3.5 (Data Resource) clearly says that “list entry" and "leaf-leaf entry" are data resources (not “list” and “leaf-list”).


> 
>> 
>> Thoughts?
>> 
>> Separately, but related, is it possible to PUT on an "ordered-by
>> user” leaf-list?   Presumably, the operation changes the implicit
>> “key” field...
> 
> Section 4.5 says:
> 
>   If the target resource represents a YANG leaf-list, then the PUT
>   method MUST NOTchange the value of the leaf-list instance.

Ah-ha, very good.  And, interestingly, if not "changing the value of the leaf-list instance”, then it seems the only thing it could be used for it to move the entry’s position - right?


> 
> /Martin


K.