draft-ietf-i2rs-ephemeral-state-04.txt   draft-ietf-i2rs-ephemeral-state-05.txt 
I2RS working group J. Haas I2RS working group J. Haas
Internet-Draft Juniper Internet-Draft Juniper
Intended status: Standards Track S. Hares Intended status: Standards Track S. Hares
Expires: September 10, 2016 Huawei Expires: September 22, 2016 Huawei
March 9, 2016 March 21, 2016
I2RS Ephemeral State Requirements I2RS Ephemeral State Requirements
draft-ietf-i2rs-ephemeral-state-04 draft-ietf-i2rs-ephemeral-state-05
Abstract Abstract
This document covers requests to the netmod and netconf Working This document covers requests to the netmod and netconf Working
Groups for functionality to support the ephemeral state requirements Groups for functionality to support the ephemeral state requirements
to implement the I2RS architecture. to implement the I2RS architecture.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on September 10, 2016. This Internet-Draft will expire on September 22, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 14 skipping to change at page 2, line 14
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Review of Requirements from I2RS architecture document . . . 3 2. Review of Requirements from I2RS architecture document . . . 3
3. Ephemeral State Requirements . . . . . . . . . . . . . . . . 4 3. Ephemeral State Requirements . . . . . . . . . . . . . . . . 4
3.1. Persistence . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Persistence . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Constraints . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Constraints . . . . . . . . . . . . . . . . . . . . . . . 4
3.3. Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . 5 3.3. Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . 5
3.4. changes to YANG . . . . . . . . . . . . . . . . . . . . . 5 3.4. changes to YANG . . . . . . . . . . . . . . . . . . . . . 5
3.5. Minimal sub-set of Changes to NETCONF . . . . . . . . . . 5 3.4.1. Suggested Yang changes . . . . . . . . . . . . . . . 5
3.6. Requirements regarding Identity, Secondary-Identity and 3.4.2. Changes to Yang Under debate . . . . . . . . . . . . 5
Priority . . . . . . . . . . . . . . . . . . . . . . . . 5 3.5. Minimal Changes to NETCONF for I2RS Protocol (v1) . . . . 6
3.6.1. Identity Requirements . . . . . . . . . . . . . . . . 5 3.5.1. dependencies . . . . . . . . . . . . . . . . . . . . 6
3.6.2. Priority Requirements . . . . . . . . . . . . . . . . 5 3.5.2. New operations (under debate) . . . . . . . . . . . . 6
3.6.3. Transactions . . . . . . . . . . . . . . . . . . . . 6 3.5.3. modified operations . . . . . . . . . . . . . . . . . 6
3.6.4. Subscriptions to Changed State Requirements . . . . . 7 3.5.4. no supported operations . . . . . . . . . . . . . . . 6
4. Previously Considered Ideas . . . . . . . . . . . . . . . . . 8 3.5.5. interactions with capabilities (Some Debate) . . . . 7
4.1. A Separate Ephemeral Datastore . . . . . . . . . . . . . 8 3.6. Changes to RESTCONF for I2RS Protocol (v1) . . . . . . . 7
4.2. Panes of Glass/Overlay . . . . . . . . . . . . . . . . . 9 3.6.1. dependencies for RESTCONF . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 3.6.2. modification to context . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 3.6.3. modification to existing operations . . . . . . . . . 8
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 3.7. Requirements regarding Identity, Secondary-Identity and
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 Priority . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References: . . . . . . . . . . . . . . . . . . 10 3.7.1. Identity Requirements . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 11 3.7.2. Priority Requirements . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 3.7.3. Transactions . . . . . . . . . . . . . . . . . . . . 10
3.7.4. Subscriptions to Changed State Requirements . . . . . 10
4. Previously Considered Ideas . . . . . . . . . . . . . . . . . 11
4.1. A Separate Ephemeral Datastore . . . . . . . . . . . . . 11
4.2. Panes of Glass/Overlay . . . . . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References: . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
The Interface to the Routing System (I2RS) Working Group is chartered The Interface to the Routing System (I2RS) Working Group is chartered
with providing architecture and mechanisms to inject into and with providing architecture and mechanisms to inject into and
retrieve information from the routing system. The I2RS Architecture retrieve information from the routing system. The I2RS Architecture
document [I-D.ietf-i2rs-architecture] abstractly documents a number document [I-D.ietf-i2rs-architecture] abstractly documents a number
of requirements for implementing the I2RS requirements. of requirements for implementing the I2RS requirements.
The I2RS Working Group has chosen to use the YANG data modeling The I2RS Working Group has chosen to use the YANG data modeling
skipping to change at page 5, line 18 skipping to change at page 5, line 24
objects) that have the property of being ephemeral. An object needs objects) that have the property of being ephemeral. An object needs
to be able to have (both) the property of being writable and the to be able to have (both) the property of being writable and the
property of the data being ephemeral (or non-ephemeral). property of the data being ephemeral (or non-ephemeral).
3.4. changes to YANG 3.4. changes to YANG
Ephemeral-REQ-06: Yang MUST have a way to indicate in a data model Ephemeral-REQ-06: Yang MUST have a way to indicate in a data model
that nodes have the following properties: ephemeral, writable/not- that nodes have the following properties: ephemeral, writable/not-
writable, status/configuration, and secure/non-secure transport. writable, status/configuration, and secure/non-secure transport.
3.5. Minimal sub-set of Changes to NETCONF 3.4.1. Suggested Yang changes
Ephemeral-REQ-07: The minimal set of changes are: (TBD). The minimal changes to Yang are:
Potential set: TBD 1. protocol version support - "version 1",
Note: I2RS protocol design team is working to complete this set of 2. ephemeral true; (key word)
minimal changes.
3.6. Requirements regarding Identity, Secondary-Identity and Priority 3. data models indicate which supported - "NETCONF", "RESTCONF",
"NETCONF pub-sub push",
3.6.1. Identity Requirements 4. encoding support - XML or JSON
Ephemeral-REQ-08:Clients shall have identifiers, and secondary 5. data models indicate which transports protocol supported: "TCP",
"SSH", "TLS", non-secure, and othrs.
6. configuration for non-secure transport
1. i2rs:nonsecure-ok;
3.4.2. Changes to Yang Under debate
(under debate) "ephemeral-validation syntax, no-reference, full" -
for modules or rpc allowing flexible validation.
3.5. Minimal Changes to NETCONF for I2RS Protocol (v1)
Ephemeral-REQ-07: The conceptual changes to NETCONF/RESTCONF are:
o protocol version support - "version 1",
o ephemeral model scope - ephemeral modules, mixed config module
(ephemeral and config), mixed derived state (ephemeral and
config).
o multiple message support - "all or nothing",
o pane of glass support - "single only".
o protocol supported - "NETCONF", "RESTCONF", "NETCONF pub-sub
push",
o encoding support - XML or JSON
o transports protocol supported: "TCP", "SSH", "TLS", non-secure,
and others.
o ability to select transports data model is available for.
Insecure portions must be able to select a insecure transport.
3.5.1. dependencies
The dependencies for ephemeral support are: yang changes (see below),
yang modules support notificatino of write-conflicts, and pub/sub
push support.
3.5.2. New operations (under debate)
The new operations were a bulk-write. This feature along with the
flexible validation is under debate.
3.5.3. modified operations
<get-config>, <edit-config> <copy-config>, <delete-config> <get>
<close-session>, <kill-session> are altered to abide by ephemeral
data store rules.
3.5.4. no supported operations
<lock> and <unlock> are not supported for a target of ephemeral.
3.5.5. interactions with capabilities (Some Debate)
Ephemeral data stores do not support inteaction with writable-
running, candidate datastore, confirmed commit, distinct start-up
capbility,
Ephemeral data stores only support a "roll-back-on error" (I2RS all-
or-nothing), URL capability and XPATH capbility in source or target.
(Debate) Validate function - is either full (NETCONF/RESTCONF) or
optionally (syntax, no-referential, full)
3.6. Changes to RESTCONF for I2RS Protocol (v1)
Ephemeral-REQ-08: The conceptual changes to NETCONF/RESTCONF are:
o protocol version support - "version 1",
o ephemeral model scope - ephemeral modules, mixed config module
(ephemeral and config), mixed derived state (ephemeral and
config).
o multiple message support - "all or nothing",
o pane of glass support - "single only".
o protocol supported - "NETCONF", "RESTCONF", "NETCONF pub-sub
push",
o encoding support - XML or JSON
o transports protocol supported: "TCP", "SSH", "TLS", non-secure,
and others.
o ability to select transports data model is available for.
Insecure portions must be able to select a insecure transport.
3.6.1. dependencies for RESTCONF
1. Yang data models, sub-modules, or modules must be flaged with
ephemeral data store flag,
2. Yang modules must suport notification of write conflicts.
3. Yang modules must suport the following:
1. the yang-patch features as specified in
[I-D.ietf-netconf-yang-patch].
2. The yang module library feature
[I-D.ietf-netconf-yang-library],
3. the equivalent of the netconf pub/subscription push service
found in [I-D.ietf-netconf-yang-push]
3.6.2. modification to context
RESTCONF must be able to support ephemeral data with an ephemeral
context that supports "edit-collision" features that include
timestamp, Entity tag, and the ability to compare I2RS client-
priorities.
3.6.3. modification to existing operations
The following modification to the existing operations are required:
1. OPTIONS - provide indication of ephemeral in modules,
2. HEAD - able to get HEAD of ephemeral or config module or the head
of groups of ephemeral or configuratinon nodes in a module.
3. GET,Post,PUt, Patch, Delete, Query Parmeters - must be able to
handle a context="Ephemeral".
4. Ephemeral database must support publication notifications or
errors as event stream, and subscribing to portions of that event
stream. (see [I-D.ietf-netconf-yang-push]
3.7. Requirements regarding Identity, Secondary-Identity and Priority
3.7.1. Identity Requirements
Ephemeral-REQ-09:Clients shall have identifiers, and secondary
identifiers. identifiers.
Explanation: Explanation:
I2RS requires clients to have an identifier. This identifier will be I2RS requires clients to have an identifier. This identifier will be
used by the Agent authentication mechanism over the appropriate used by the Agent authentication mechanism over the appropriate
protocol. protocol.
The Secondary identities can be carried as part of RPC or meta-data. The Secondary identities can be carried as part of RPC or meta-data.
The primary purpose of the secondary identity is for traceability The primary purpose of the secondary identity is for traceability
information which logs (who modifies certain nodes). This secondary information which logs (who modifies certain nodes). This secondary
identity is an opaque value. [I-D.ietf-i2rs-traceability] provides identity is an opaque value. [I-D.ietf-i2rs-traceability] provides
an example of how the secondary identity can be used for an example of how the secondary identity can be used for
traceability. traceability.
3.6.2. Priority Requirements 3.7.2. Priority Requirements
To support Multi-Headed Control, I2RS requires that there be a To support Multi-Headed Control, I2RS requires that there be a
decidable means of arbitrating the correct state of data when decidable means of arbitrating the correct state of data when
multiple clients attempt to manipulate the same piece of data. This multiple clients attempt to manipulate the same piece of data. This
is done via a priority mechanism with the highest priority winning. is done via a priority mechanism with the highest priority winning.
This priority is per-client. This priority is per-client.
Ephemeral-REQ-09: The data nodes MAY store I2RS client identity and Ephemeral-REQ-09: The data nodes MAY store I2RS client identity and
not the effective priority at the time the data node is stored. The not the effective priority at the time the data node is stored. The
I2RS Client MUST have one priority at a time. The priority MAY be I2RS Client MUST have one priority at a time. The priority MAY be
skipping to change at page 6, line 45 skipping to change at page 10, line 5
Ephemeral configuration state nodes that are created or altered by Ephemeral configuration state nodes that are created or altered by
users that match a rule carrying i2rs-priority will have those nodes users that match a rule carrying i2rs-priority will have those nodes
annotated with metadata. Additionally, during commit processing, if annotated with metadata. Additionally, during commit processing, if
nodes are found where i2rs-priority is already present, and the nodes are found where i2rs-priority is already present, and the
priority is better than the transaction's user's priority for that priority is better than the transaction's user's priority for that
node, the commit should fail. An appropriate error should be node, the commit should fail. An appropriate error should be
returned to the user stating the nodes where the user had returned to the user stating the nodes where the user had
insufficient priority to override the state. insufficient priority to override the state.
3.6.3. Transactions 3.7.3. Transactions
Ephemeral-REQ-13: Section 7.9 of the [I-D.ietf-i2rs-architecture] Ephemeral-REQ-13: Section 7.9 of the [I-D.ietf-i2rs-architecture]
states the I2RS architecture does not include multi-message atomicity states the I2RS architecture does not include multi-message atomicity
and roll-back mechanisms. I2RS notes multiple operations in one or and roll-back mechanisms. I2RS notes multiple operations in one or
more messages handling can handle errors within the set of operations more messages handling can handle errors within the set of operations
in many ways. No multi-message commands SHOULD cause errors to be in many ways. No multi-message commands SHOULD cause errors to be
inserted into the I2RS ephemeral data-store. inserted into the I2RS ephemeral data-store.
Explanation: Explanation:
skipping to change at page 7, line 39 skipping to change at page 10, line 46
Discussion of Current NETCONF/RESTCONF versus Discussion of Current NETCONF/RESTCONF versus
RESTCONF does an atomic action within a http session, and NETCONF has RESTCONF does an atomic action within a http session, and NETCONF has
atomic actions within a commit. These features may be used to atomic actions within a commit. These features may be used to
perform these features. perform these features.
I2RS processing is dependent on the I2RS model. The I2RS model must I2RS processing is dependent on the I2RS model. The I2RS model must
consider the dependencies within multiple operations work within a consider the dependencies within multiple operations work within a
model. model.
3.6.4. Subscriptions to Changed State Requirements 3.7.4. Subscriptions to Changed State Requirements
I2RS clients require the ability to monitor changes to ephemeral I2RS clients require the ability to monitor changes to ephemeral
state. While subscriptions are well defined for receiving state. While subscriptions are well defined for receiving
notifications, the need to create a notification set for all notifications, the need to create a notification set for all
ephemeral configuration state may be overly burdensome to the user. ephemeral configuration state may be overly burdensome to the user.
There is thus a need for a general subscription mechanism that can There is thus a need for a general subscription mechanism that can
provide notification of changed state, with sufficient information to provide notification of changed state, with sufficient information to
permit the client to retrieve the impacted nodes. This should be permit the client to retrieve the impacted nodes. This should be
doable without requiring the notifications to be created as part of doable without requiring the notifications to be created as part of
skipping to change at page 9, line 37 skipping to change at page 12, line 42
lost, perhaps on reboot. In such a case, the previously shadowed lost, perhaps on reboot. In such a case, the previously shadowed
persistent state may no longer validate. persistent state may no longer validate.
5. IANA Considerations 5. IANA Considerations
There are no IANA requirements for this document. There are no IANA requirements for this document.
6. Security Considerations 6. Security Considerations
The security requirements for the I2RS protocol are covered in The security requirements for the I2RS protocol are covered in
[I-D.hares-i2rs-auth-trans] document. [I-D.ietf-i2rs-protocol-security-requirements] document.
7. Acknowledgements 7. Acknowledgements
This document is an attempt to distill lengthy conversations on the This document is an attempt to distill lengthy conversations on the
I2RS mailing list for an architecture that was for a long period of I2RS mailing list for an architecture that was for a long period of
time a moving target. Some individuals in particular warrant time a moving target. Some individuals in particular warrant
specific mention for their extensive help in providing the basis for specific mention for their extensive help in providing the basis for
this document: this document:
o Alia Atlas o Alia Atlas
skipping to change at page 10, line 20 skipping to change at page 13, line 27
o Thomas Nadeau o Thomas Nadeau
o Juergen Schoenwaelder o Juergen Schoenwaelder
o Kent Watsen o Kent Watsen
8. References 8. References
8.1. Normative References: 8.1. Normative References:
[I-D.hares-i2rs-auth-trans]
Hares, S., Migault, D., and J. Halpern, "I2RS Security
Related Requirements", draft-hares-i2rs-auth-trans-05
(work in progress), August 2015.
[I-D.ietf-i2rs-architecture] [I-D.ietf-i2rs-architecture]
Atlas, A., Halpern, J., Hares, S., Ward, D., and T. Atlas, A., Halpern, J., Hares, S., Ward, D., and T.
Nadeau, "An Architecture for the Interface to the Routing Nadeau, "An Architecture for the Interface to the Routing
System", draft-ietf-i2rs-architecture-13 (work in System", draft-ietf-i2rs-architecture-13 (work in
progress), February 2016. progress), February 2016.
[I-D.ietf-i2rs-protocol-security-requirements]
Hares, S., Migault, D., and J. Halpern, "I2RS Security
Related Requirements", draft-ietf-i2rs-protocol-security-
requirements-03 (work in progress), March 2016.
[I-D.ietf-i2rs-pub-sub-requirements] [I-D.ietf-i2rs-pub-sub-requirements]
Voit, E., Clemm, A., and A. Prieto, "Requirements for Voit, E., Clemm, A., and A. Prieto, "Requirements for
Subscription to YANG Datastores", draft-ietf-i2rs-pub-sub- Subscription to YANG Datastores", draft-ietf-i2rs-pub-sub-
requirements-05 (work in progress), February 2016. requirements-05 (work in progress), February 2016.
[I-D.ietf-i2rs-rib-info-model] [I-D.ietf-i2rs-rib-info-model]
Bahadur, N., Kini, S., and J. Medved, "Routing Information Bahadur, N., Kini, S., and J. Medved, "Routing Information
Base Info Model", draft-ietf-i2rs-rib-info-model-08 (work Base Info Model", draft-ietf-i2rs-rib-info-model-08 (work
in progress), October 2015. in progress), October 2015.
[I-D.ietf-i2rs-traceability] [I-D.ietf-i2rs-traceability]
Clarke, J., Salgueiro, G., and C. Pignataro, "Interface to Clarke, J., Salgueiro, G., and C. Pignataro, "Interface to
the Routing System (I2RS) Traceability: Framework and the Routing System (I2RS) Traceability: Framework and
Information Model", draft-ietf-i2rs-traceability-07 (work Information Model", draft-ietf-i2rs-traceability-07 (work
in progress), February 2016. in progress), February 2016.
[I-D.ietf-netconf-restconf]
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", draft-ietf-netconf-restconf-10 (work in
progress), March 2016.
[I-D.ietf-netconf-yang-library]
Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module
Library", draft-ietf-netconf-yang-library-04 (work in
progress), February 2016.
[I-D.ietf-netconf-yang-patch]
Bierman, A., Bjorklund, M., and K. Watsen, "YANG Patch
Media Type", draft-ietf-netconf-yang-patch-08 (work in
progress), March 2016.
[I-D.ietf-netconf-yang-push]
Clemm, A., Prieto, A., Voit, E., Tripathy, A., and E.
Einar, "Subscribing to YANG datastore push updates",
draft-ietf-netconf-yang-push-01 (work in progress),
February 2016.
[I-D.ietf-netmod-yang-metadata] [I-D.ietf-netmod-yang-metadata]
Lhotka, L., "Defining and Using Metadata with YANG", Lhotka, L., "Defining and Using Metadata with YANG",
draft-ietf-netmod-yang-metadata-04 (work in progress), draft-ietf-netmod-yang-metadata-06 (work in progress),
February 2016. March 2016.
8.2. Informative References [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>.
[I-D.ietf-netconf-restconf] 8.2. Informative References
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", draft-ietf-netconf-restconf-09 (work in
progress), December 2015.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>. <http://www.rfc-editor.org/info/rfc6536>.
Authors' Addresses Authors' Addresses
Jeff Haas Jeff Haas
Juniper Juniper
 End of changes. 22 change blocks. 
50 lines changed or deleted 217 lines changed or added

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