Partial Lock Remote Procedure Call (RPC) for NETCONF
Note: This ballot was opened for revision 11 and is now closed.
(Dan Romascanu) (was Discuss, Yes) Yes
(Jari Arkko) No Objection
(Ron Bonica) No Objection
Comment (2009-08-12 for -** No value found for 'p.get_dochistory.rev' **)
Please check to see if the YANG snippets require licensing text. I think that they do.
(Ross Callon) No Objection
(Ralph Droms) No Objection
Comment (2009-08-08 for -** No value found for 'p.get_dochistory.rev' **)
2.4.2. <partial-unlock> Positive Response: If the device was able to satisfy the request, an <rpc-reply> is sent that contains an <ok> element. A positive response MUST be sent even if all of the locked parts of the datastore(s) have already been deleted. Negative Response: If the <lock-id> parameter does not identify a lock which is owned by the session, an ’invalid-value’ error is returned. Are there other ways in which the <partial-unlock> can fail? 2.5. Modifications to Existing Operations A successful partial lock will cause a subsequent operation to fail if that attempts [...] s/that/that operation/ ?
(Lisa Dusseault) No Objection
(Pasi Eronen) (was Discuss) No Objection
(Adrian Farrel) (was Discuss) No Objection
(Russ Housley) No Objection
Alexey Melnikov (was Discuss) No Objection
(Tim Polk) (was Discuss) No Objection
Steve's review included a number of editorial comments the authors may wish to consider.