Document: draft-ietf-netconf-partial-lock-08.txt Reviewer: Suresh Krishnan Review Date: 6/23/2009 IETF LC Date: 6/24/2009 Summary: This draft is almost ready for publication as Proposed Standard but I have a couple of comments. Major ===== * Section 2.4.1 page 7 paragraph 3 "Let's say ..." The following text is confusing "If someone later creates a new user, this new user will not be included in the locked-nodes list created previously, the new user will not be locked." It is unclear how this is even possible given there is a partial lock on all the users that was obtained using the following select parameter Can you please clarify what you mean here? Minor ===== * Section 2.1.1.3 The scenario described here does not really describe a deadlock as deadlock requires two competing actions waiting for each other to finish. I do not know what to call it but this is certainly not a deadlock :-) and the deadlock avoidance measures described in section 2.4.1.2 will not fix this problem. * IANA considerations - The section states that "This document registers two URIs..." but it only registers one. Either another URI is missing or this text needs to be changed. - It is also not clear where the :partial-lock capability is being allocated from. I guess it is coming from the NETCONF Capability URNs registry.