Re: [Netconf] Confirmed commit

["Bert Wijnen (IETF)" <[e-mail]>]

See at bottom

On 9/20/13 7:13 AM, Juergen Schoenwaelder wrote:
> On Thu, Sep 19, 2013 at 01:39:28PM -0700, Andy Bierman wrote:
>> Hi,
>>
>> I always found section 8.4.1, para 2 confusing.
>>
>> T0: /int8.1 does not exist
>>
>>     > merge /int8.1 value=20
>>     > commit confirmed confirm-timeout=60
>>
>> T1: /int8.1 = 20
>>
>>     merge /int8.1 value=30
>>     commit confirmed confirm-timeout=60
>>
>> T2: /int8.1 = 30
>>
>> T3: timeout occurs:
>>
>> para 6 says:
>>
>>     If a confirming commit is not issued, the device will revert its
>>     configuration to the state prior to the issuance of the confirmed
>>     commit.
>>
>>
>> The problem is that there are 2 confirmed commit operations.
>> At time T3 does the server go back to state T1 or T0?
>> (Our server goes back to T0).
>>
>> The 2nd commit contains a confirmed parameter, and para 2
>> sentence 2 clearly says this is not a confirming commit.
>> The text does not actually define a "confirmed commit",
>> but I assume it is a commit with a confirmed parameter.
>> Therefore, paragraphs 5 - 7 are wrong where they refer
>> to "the confirmed commit", because there are 2 of them.
>>
>
> Yes, this corner case where multiple confirmed commits are issued is
> not described well. Your interpretation that subsequent confirmed
> commits effectively extend the first one makes sense to me.
>


Can wee keep this somewhere so we clarify it if we ever have to
open up and update the document?

Bert
> /js
>