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

Kent Watsen <kent+ietf@watsen.net> Wed, 02 September 2020 20:07 UTC

Return-Path: <01000174506ec41e-13dd2b0c-1591-4937-be1d-d58475f4a9b0-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ECCE3A0E06 for <netconf@ietfa.amsl.com>; Wed, 2 Sep 2020 13:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id prGkD2KrxFKT for <netconf@ietfa.amsl.com>; Wed, 2 Sep 2020 13:07:52 -0700 (PDT)
Received: from a8-33.smtp-out.amazonses.com (a8-33.smtp-out.amazonses.com [54.240.8.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBA4A3A0E05 for <netconf@ietf.org>; Wed, 2 Sep 2020 13:07:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1599077270; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=VjRXWiRS4S8YxsON2sQODh/0m67S287guS/zMrfSJH4=; b=FxgyvAUB1DasTX6GD3zcrTrpNnaQu4bx5YXjXU3fG0dFkQZ0MjIA65mcogv2fuwU NusYsQsjnCk67jKMPSF15M0iC3wJG3HV/HUnXF4aWgaTtDGQvBjSornTXQe6n3eeRFZ rMWnNSoUHfgFZkbdl1oXAZ/X+ipo1PDXDG2nHuoo=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <20200902.215651.2161361777301988365.id@4668.se>
Date: Wed, 2 Sep 2020 20:07:50 +0000
Cc: Andy Bierman <andy@yumaworks.com>, Warren Kumari <warren@kumari.net>, Robert Wilton <rwilton@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "netconf@ietf.org" <netconf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <01000174506ec41e-13dd2b0c-1591-4937-be1d-d58475f4a9b0-000000@email.amazonses.com>
References: <20200902.082718.1225293218517439729.id@4668.se> <CABCOCHRTsyju+3e1jUSTzFswpvG5KzARWyQXM_M8AukxJqPkZw@mail.gmail.com> <010001744fa1d4f9-c6c34f02-e5c6-4078-9244-c0bd567ae2a2-000000@email.amazonses.com> <20200902.215651.2161361777301988365.id@4668.se>
To: =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-SES-Outgoing: 2020.09.02-54.240.8.33
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/0MlQ_R7h1l_6hl2kwdulnRXmgHE>
Subject: Re: [netconf] [Technical Errata Reported] RFC8040 (6271)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2020 20:07:53 -0000

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.