Subject: [netconf] Open question 4/4 "Granularity of Etags" in draft-lindblad-netconf-transaction-id-01.txt

From: "Jan Lindblad (jlindbla)" <[email-masked]>
Date: Thu, 11 Nov 2021 20:47:42 +0000

Hello NETCONF team,

This thread (4/4) is about Granularity of Etags: at the NETCONF WG session earlier this week, the chairs asked me to start a separate thread for each of the outstanding question relating to draft-lindblad-netconf-transaction-id-01. 

Should it be possible for a client to specify which Etag value the server should use for a particular transaction?

Proposed solution #1) Etags are only available at the datastore top level

Proposed solution #2) Etags are available at the datastore top level, and some containers and list elements, as decided by the server implementor

Proposed solution #3) Etags are available at the datastore top level and some elements (containers, list elements, leafs, ...), as decided by the server implementor

Proposed solution #4) Etags are available at the datastore top level and some elements (containers, list elements, leafs, ...), as decided by the client in runtime

The -01 draft specifies solution #2. Please indicate your preferences among the options. Comments or suggestions for other options are also welcome.

Comments: For some use cases, solution #1 may be enough. For others, solution #1 is counter productive, and a more comprehensive solution is required.

Best Regards,
/jan

> On 22 Oct 2021, at 13:28, [email-masked] wrote:
> 
> 
> A new version of I-D, draft-lindblad-netconf-transaction-id-01.txt
> has been successfully submitted by Jan Lindblad and posted to the
> IETF repository.
> 
> Name:		draft-lindblad-netconf-transaction-id
> Revision:	01
> Title:		Transaction ID Mechanism for NETCONF
> Document date:	2021-10-22
> Group:		Individual Submission
> Pages:		22
> URL:            https://www.ietf.org/archive/id/draft-lindblad-netconf-transaction-id-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-lindblad-netconf-transaction-id/
> Html:           https://www.ietf.org/archive/id/draft-lindblad-netconf-transaction-id-01.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-lindblad-netconf-transaction-id
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-lindblad-netconf-transaction-id-01
> 
> Abstract:
>   NETCONF clients and servers often need to have a synchronized view of
>   the server's configuration data stores.  The volume of configuration
>   data in a server may be very large, while data store changes
>   typically are small when observed at typical client resynchronization
>   intervals.
> 
>   Rereading the entire data store and analyzing the response for
>   changes is an inefficient mechanism for synchronization.  This
>   document specifies an extension to NETCONF that allows clients and
>   servers to keep synchronized with a much smaller data exchange and
>   without any need for servers to store information about the clients.
> 
> 
> 
> 
> The IETF Secretariat