Re: [Netconf] Netconf-partial-lock comment/discuss
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Netconf] Netconf-partial-lock comment/discuss



This looks fine. I have cleared my DISCUSS and changed my vote to a
'Yes'. 

Thank you for addressing my concerns. 

Regards,

Dan
 

> -----Original Message-----
> From: Balazs Lengyel [mailto:balazs.lengyel at ericsson.com] 
> Sent: Monday, October 19, 2009 2:53 PM
> To: netconf-chairs at tools.ietf.org; Romascanu, Dan (Dan)
> Cc: netconf mailing list; iesg at ietf.org
> Subject: Netconf-partial-lock comment/discuss
> 
> Hello Dan,
> In the tracker 
> https://datatracker.ietf.org/idtracker/ballot/3035 about the
> draft-ietf-netconf-partial-lock-09 you have the comment:
> 
> Discuss [2009-08-12]:
> Late discussions among the editors and implementers of the 
> NETCONF standard raised the issue of possibly removing 
> partial-lock for startup, since it was clarified in 4741bis 
> that startup cannot be modified with edit-config. I am 
> holding a DISCUSS until the WG reaches the consensus on this issue.
> 
> ANSWER: startup and candidate datastores removed from the 
> scope in the already stored -10 draft. They can not be locked 
> with partial-lock. Startup was removed due to the argument 
> you raised, candidate because:
> - partial-locking was always aimed predominantly towards the 
> running database. 
> Partially-Locking the candidate was always seen as a lesser 
> use-case included for completeness.
> - a number of people objected that having partial locking 
> with a global commit operation will lead to problems
> - the workgroup consensus was not broad enough
> 
> 
> 
> Please indicate if you can accept these answers!
> 
> regards Balazs
> 
> 
> -- 
> Balazs Lengyel                       Ericsson Hungary Ltd.
> System Manager
> ECN: 831 7320                        Fax: +36 1 4377792
> Tel: +36-1-437-7320                  email: 
> Balazs.Lengyel at ericsson.com
> 

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.