Subject: [Netconf] RESTCONF and confirmed-commit

From: Andy Bierman <[email-masked]>
Date: Mon, 28 Dec 2015 22:02:12 -0800

Hi,

Sec. 1.3 in RESTCONF-09 does not mention confirmed-commit at all.
I just finished implementing confirmed-commit for RESTCONF
and some details should be mentioned in this section.

1) persist-id

A normal NETCONF commit will fail if a confirmed-commit is running
with a 'persist-id' lock, and the session does not provide the correct
value.
Since standard RESTCONF has no way of passing a 'persist-id'
parameter to the edit or commit, any RESTCONF edit must fail
if this parameter is expected by the server.

If no 'persist-id' is expected, then the RESTCONF edit will
be processed by the server, and it will act as the confirming commit.

2) shared candidate

This section does not mention that any edits in the candidate at
the time of the RESTCONF edit will also be part of the commit.

I propose that new text be added to sec. 1.3 similar to the text above.

Andy