draft-ietf-netconf-partial-lock-10.txt   draft-ietf-netconf-partial-lock-11.txt 
NETCONF B. Lengyel NETCONF B. Lengyel
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track M. Bjorklund Intended status: Standards Track M. Bjorklund
Expires: April 22, 2010 Tail-f Systems Expires: April 23, 2010 Tail-f Systems
October 19, 2009 October 20, 2009
Partial Lock RPC for NETCONF Partial Lock RPC for NETCONF
draft-ietf-netconf-partial-lock-10 draft-ietf-netconf-partial-lock-11
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 43 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 22, 2010. This Internet-Draft will expire on April 23, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 30 skipping to change at page 3, line 30
2.6.2. Confirmed Commit Capability . . . . . . . . . . . . . 12 2.6.2. Confirmed Commit Capability . . . . . . . . . . . . . 12
2.6.3. Distinct Startup Capability . . . . . . . . . . . . . 12 2.6.3. Distinct Startup Capability . . . . . . . . . . . . . 12
3. Security Considerations . . . . . . . . . . . . . . . . . . . 12 3. Security Considerations . . . . . . . . . . . . . . . . . . . 12
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5. Appendix A - XML Schema for Partial Locking (normative) . . 15 5. Appendix A - XML Schema for Partial Locking (normative) . . 15
6. Appendix B - YANG Module for Partial Locking 6. Appendix B - YANG Module for Partial Locking
(non-normative) . . . . . . . . . . . . . . . . . . . . . . . 18 (non-normative) . . . . . . . . . . . . . . . . . . . . . . . 18
7. Appendix C - Usage Example - Reserving nodes for future 7. Appendix C - Usage Example - Reserving nodes for future
editing (non-normative) . . . . . . . . . . . . . . . . . . . 20 editing (non-normative) . . . . . . . . . . . . . . . . . . . 20
8. Appendix D - Change Log . . . . . . . . . . . . . . . . . . 24 8. Appendix D - Change Log . . . . . . . . . . . . . . . . . . 24
8.1. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8.1. 10-11 . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.2. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8.2. 09-10 . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.3. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8.3. 08-09 . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.4. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8.4. 07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.5. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8.5. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.6. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8.6. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.7. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8.7. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.8. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8.8. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.9. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8.9. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.10. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8.10. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.11. -00 . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8.11. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 25
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 26 8.12. -00 . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27
10.1. Normative References . . . . . . . . . . . . . . . . . . . 27 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28
10.2. Informative References . . . . . . . . . . . . . . . . . . 27 10.1. Normative References . . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28 10.2. Informative References . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
The [NETCONF] protocol describes the lock and unlock operations that The [NETCONF] protocol describes the lock and unlock operations that
operate on entire configuration datastores. Often, multiple operate on entire configuration datastores. Often, multiple
management sessions need to be able to modify the configuration of a management sessions need to be able to modify the configuration of a
managed device in parallel. In these cases, locking only parts of a managed device in parallel. In these cases, locking only parts of a
configuration datastore is needed. This document defines a configuration datastore is needed. This document defines a
capability based extension to the NETCONF protocol to support partial capability based extension to the NETCONF protocol to support partial
locking of the NETCONF running datastore using a mechanism based on locking of the NETCONF running datastore using a mechanism based on
skipping to change at page 5, line 15 skipping to change at page 5, line 15
operations such as SNMP and the CLI. operations such as SNMP and the CLI.
The duration of the partial lock begins when the partial lock is The duration of the partial lock begins when the partial lock is
granted and lasts until (1) either the corresponding <partial-unlock> granted and lasts until (1) either the corresponding <partial-unlock>
operation succeeds or (2) the NETCONF session terminates. operation succeeds or (2) the NETCONF session terminates.
A NETCONF session MAY have multiple parts of the running datastore A NETCONF session MAY have multiple parts of the running datastore
locked using partial lock operations. locked using partial lock operations.
The <partial-lock> operation returns a lock-id to identify each The <partial-lock> operation returns a lock-id to identify each
successfully acquired lock. The lock-id is unique for a NETCONF successfully acquired lock. The lock-id is unique at any given time
server for all partial-locks granted to any NETCONF or non-NETCONF for a NETCONF server for all partial-locks granted to any NETCONF or
sessions. non-NETCONF sessions.
2.1.1. Usage Scenarios 2.1.1. Usage Scenarios
In the following we describe a few scenarios for partial locking. In the following we describe a few scenarios for partial locking.
Besides the two described here, there are many other usage scenarios Besides the two described here, there are many other usage scenarios
possible. possible.
2.1.1.1. Multiple managers handling the writable running datastore with 2.1.1.1. Multiple managers handling the writable running datastore with
overlapping sections overlapping sections
skipping to change at page 24, line 7 skipping to change at page 24, line 7
<nc:rpc xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0" <nc:rpc xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0"
xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="105"> message-id="105">
<partial-unlock> <partial-unlock>
<lock-id>1</lock-id> <lock-id>1</lock-id>
</partial-unlock> </partial-unlock>
</nc:rpc> </nc:rpc>
8. Appendix D - Change Log 8. Appendix D - Change Log
8.1. 09-10 8.1. 10-11
Minor clarifications
8.2. 09-10
Clarifications Clarifications
Only the running datastore can be locked Only the running datastore can be locked
8.2. 08-09 8.3. 08-09
Clarifications Clarifications
8.3. 07-08 8.4. 07-08
Clarifications Clarifications
8.4. 06-07 8.5. 06-07
Changed XSD and YANG to allow additional proprietary datastores to be Changed XSD and YANG to allow additional proprietary datastores to be
locked. locked.
8.5. 05-06 8.6. 05-06
Added usage example Added usage example
Clarified error messages Clarified error messages
Clarified interaction with edit-config continue-on-error Clarified interaction with edit-config continue-on-error
Improved YANG: indentation, canonical order, contact info Improved YANG: indentation, canonical order, contact info
Added usage example in appendix C Added usage example in appendix C
Synchronized YANG and XSD Synchronized YANG and XSD
8.6. 04-05 8.7. 04-05
Language and editorial updates Language and editorial updates
all app-tags are with dashes without spaces all app-tags are with dashes without spaces
Added usage scenarios Added usage scenarios
Changed encoding Changed encoding
Clarified definitions, separated scope of lock and protected area Clarified definitions, separated scope of lock and protected area
8.7. 03-04 8.8. 03-04
Minor clarifications Minor clarifications
Added list of locked-nodes to the output of partial-lock. Added list of locked-nodes to the output of partial-lock.
Added <target> wrapper around datastore names. Added <target> wrapper around datastore names.
Allowed atomic/one operation locking of datastore parts in multiple Allowed atomic/one operation locking of datastore parts in multiple
datastores. datastores.
Improved English (hopefully) Improved English (hopefully)
Removed the <data> element from rpc-reply following the text of Removed the <data> element from rpc-reply following the text of
rfc4741. rfc4741.
8.8. 02-03 8.9. 02-03
Minor clarifications Minor clarifications
Same descriptions in XSD and YANG. Same descriptions in XSD and YANG.
8.9. 01-02 8.10. 01-02
Made XSD normative Made XSD normative
Clarified that no specific access control is assumed. Clarified that no specific access control is assumed.
Clarified that non-existing nodes are NOT covered by the lock, even Clarified that non-existing nodes are NOT covered by the lock, even
if they where existing and covered by the lock when it was originally if they where existing and covered by the lock when it was originally
granted. granted.
Some rewording Some rewording
Added app-tags for two of the error cases. Added app-tags for two of the error cases.
Made YANG an informative reference Made YANG an informative reference
Enhanced security considerations. Enhanced security considerations.
8.10. 00-01 8.11. 00-01
Added YANG module. Added YANG module.
8.11. -00 8.12. -00
Created from draft-lengyel-ngo-partial-lock-01.txt Created from draft-lengyel-ngo-partial-lock-01.txt
9. Acknowledgements 9. Acknowledgements
Thanks to Andy Bierman, Sharon Chisholm, Phil Shafer , David Thanks to Andy Bierman, Sharon Chisholm, Phil Shafer , David
Harrington, Mehmet Ersue, Wes Hardaker, Juergen Schoenwaelder, Washam Harrington, Mehmet Ersue, Wes Hardaker, Juergen Schoenwaelder, Washam
Fan and many other members of the NETCONF WG for providing important Fan and many other members of the NETCONF WG for providing important
input to this document. input to this document.
 End of changes. 17 change blocks. 
35 lines changed or deleted 39 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/