--- 1/draft-ietf-netconf-access-control-06.txt 2011-12-23 14:13:58.095171026 +0100 +++ 2/draft-ietf-netconf-access-control-07.txt 2011-12-23 14:13:58.171170576 +0100 @@ -1,19 +1,19 @@ Internet Engineering Task Force A. Bierman Internet-Draft Brocade Intended status: Standards Track M. Bjorklund -Expires: May 3, 2012 Tail-f Systems - October 31, 2011 +Expires: June 25, 2012 Tail-f Systems + December 23, 2011 Network Configuration Protocol (NETCONF) Access Control Model - draft-ietf-netconf-access-control-06 + draft-ietf-netconf-access-control-07 Abstract The standardization of network configuration interfaces for use with the NETCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF protocol access for particular users to a pre- configured subset of all available NETCONF protocol operations and content. This document defines such an access control model. @@ -26,21 +26,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on May 3, 2012. + This Internet-Draft will expire on June 25, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -73,59 +73,61 @@ 3.2.2. and Operations . . . . . . . . . . 14 3.2.3. Operation . . . . . . . . . . . . . . . 14 3.2.4. Operation . . . . . . . . . . . . . . . 15 3.2.5. Operation . . . . . . . . . . . . . . 16 3.2.6. Operation . . . . . . . . . . . . . . . . . . 16 3.2.7. Operation . . . . . . . . . . . . . 16 3.2.8. Operation . . . . . . . . . . . . . . . 16 3.3. Model Components . . . . . . . . . . . . . . . . . . . . . 16 3.3.1. Users . . . . . . . . . . . . . . . . . . . . . . . . 17 3.3.2. Groups . . . . . . . . . . . . . . . . . . . . . . . . 17 - 3.3.3. Global Enforcement Controls . . . . . . . . . . . . . 17 - 3.3.3.1. enable-nacm Switch . . . . . . . . . . . . . . . . 17 - 3.3.3.2. read-default Switch . . . . . . . . . . . . . . . 17 - 3.3.3.3. write-default Switch . . . . . . . . . . . . . . . 18 - 3.3.3.4. exec-default Switch . . . . . . . . . . . . . . . 18 - 3.3.4. Access Control Rules . . . . . . . . . . . . . . . . . 18 + 3.3.3. Emergency Recovery Session . . . . . . . . . . . . . . 17 + 3.3.4. Global Enforcement Controls . . . . . . . . . . . . . 17 + 3.3.4.1. enable-nacm Switch . . . . . . . . . . . . . . . . 17 + 3.3.4.2. read-default Switch . . . . . . . . . . . . . . . 17 + 3.3.4.3. write-default Switch . . . . . . . . . . . . . . . 18 + 3.3.4.4. exec-default Switch . . . . . . . . . . . . . . . 18 + 3.3.4.5. enable-external-groups Switch . . . . . . . . . . 18 + 3.3.5. Access Control Rules . . . . . . . . . . . . . . . . . 19 3.4. Access Control Enforcement Procedures . . . . . . . . . . 19 3.4.1. Initial Operation . . . . . . . . . . . . . . . . . . 19 - 3.4.2. Session Establishment . . . . . . . . . . . . . . . . 19 + 3.4.2. Session Establishment . . . . . . . . . . . . . . . . 20 3.4.3. "access-denied" Error Handling . . . . . . . . . . . . 20 3.4.4. Incoming RPC Message Validation . . . . . . . . . . . 20 3.4.5. Data Node Access Validation . . . . . . . . . . . . . 23 3.4.6. Outgoing Authorization . . . . . . . . 25 - 3.5. Data Model Definitions . . . . . . . . . . . . . . . . . . 27 - 3.5.1. Data Organization . . . . . . . . . . . . . . . . . . 28 + 3.5.1. Data Organization . . . . . . . . . . . . . . . . . . 27 3.5.2. YANG Module . . . . . . . . . . . . . . . . . . . . . 28 3.6. IANA Considerations . . . . . . . . . . . . . . . . . . . 38 - 3.7. Security Considerations . . . . . . . . . . . . . . . . . 38 - 3.7.1. NACM Configuration and Monitoring Considerations . . . 38 + 3.7. Security Considerations . . . . . . . . . . . . . . . . . 39 + 3.7.1. NACM Configuration and Monitoring Considerations . . . 39 3.7.2. General Configuration Issues . . . . . . . . . . . . . 40 - 3.7.3. Data Model Design Considerations . . . . . . . . . . . 41 + 3.7.3. Data Model Design Considerations . . . . . . . . . . . 42 4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43 4.1. Normative References . . . . . . . . . . . . . . . . . . . 43 4.2. Informative References . . . . . . . . . . . . . . . . . . 43 Appendix A. Usage Examples . . . . . . . . . . . . . . . . . . . 44 A.1. Example . . . . . . . . . . . . . . . . . . . . . 44 A.2. Module Rule Example . . . . . . . . . . . . . . . . . . . 45 A.3. RPC Rule Example . . . . . . . . . . . . . . . . . . . . . 46 A.4. Data Rule Example . . . . . . . . . . . . . . . . . . . . 48 A.5. Notification Rule Example . . . . . . . . . . . . . . . . 50 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 52 - B.1. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 52 - B.2. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 52 - B.3. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 52 - B.4. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 53 - B.5. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 53 - B.6. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 53 - B.7. 00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 + B.1. 06-07 . . . . . . . . . . . . . . . . . . . . . . . . . . 52 + B.2. 05-06 . . . . . . . . . . . . . . . . . . . . . . . . . . 52 + B.3. 04-05 . . . . . . . . . . . . . . . . . . . . . . . . . . 52 + B.4. 03-04 . . . . . . . . . . . . . . . . . . . . . . . . . . 52 + B.5. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 53 + B.6. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 53 + B.7. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 53 + B.8. 00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 54 1. Introduction The NETCONF protocol does not provide any standard mechanisms to restrict the protocol operations and content that each user is authorized to access. There is a need for inter-operable management of the controlled access to administrator selected portions of the available NETCONF @@ -269,43 +271,46 @@ standard or proprietary, was used to access the datastore. 2.5. Users and Groups It is necessary that access control rules for a single user or a configurable group of users can be configured. The ACM needs to support the concept of administrative groups, to support the well-established distinction between a root account and other types of less-privileged conceptual user accounts. These - groups needs to be configurable by the administrator. + groups need to be configurable by the administrator. It is necessary that the user-to-group mapping can be delegated to a central server, such as a RADIUS server [RFC2865] [RFC5607]. Since authentication is performed by the NETCONF transport layer, and RADIUS performs authentication and service authorization at the same time, the underlying NETCONF transport needs to be able to report a - set of group names associated with the user to the server. + set of group names associated with the user to the server. It is + necessary that the administrator can disable the usage of these group + names within the ACM. 2.6. Maintenance It ought to be possible to disable part or all of the access control - model without deleting any access control rules. + model enforcement procedures without deleting any access control + rules. 2.7. Configuration Capabilities Suitable configuration and monitoring mechanisms are needed to allow an administrator to easily manage all aspects of the ACM behavior. A standard data model, suitable for use with the protocol operation needs to be available for this purpose. Access control rules to restrict access operations on specific - subtrees within the configuration datastore needs to be supported. + subtrees within the configuration datastore need to be supported. 2.8. Identifying Security-Sensitive Content One of the most important aspects of the data model documentation, and biggest concerns during deployment, is the identification of security-sensitive content. This applies to protocol operations in NETCONF, not just data and notifications. It is mandatory for security-sensitive objects to be documented in the Security Considerations section of an RFC. This is nice, but it @@ -368,38 +373,36 @@ o Support for YANG security tagging (e.g., "nacm:default-deny-write" statement) allows default security modes to automatically exclude sensitive data. o Separate default access modes for read, write, and execute permissions. o Access control rules are applied to configurable groups of users. - o The entire ACM can be disabled during operation, in order to debug - operational problems. + o The access control enforcement procedures can be disabled during + operation, without deleting any access control rules, in order to + debug operational problems. o Access control rules are simple to configure. o The number of denied protocol operation requests and denied datastore write requests can be monitored by the client. o Simple unconstrained YANG instance identifiers are used to configure access control rules for specific data nodes. 3.1.2. External Dependencies The NETCONF [RFC6241] protocol is used for all management purposes - within this document. It is expected that the mandatory transport - mapping NETCONF Over SSH [RFC6242] is also supported by the server, - and that the server has access to the user name associated with each - session. + within this document. The YANG Data Modeling Language [RFC6020] is used to define the NETCONF data models specified in this document. 3.1.3. Message Processing Model The following diagram shows the conceptual message flow model, including the points at which access control is applied, during NETCONF message processing. @@ -644,101 +647,113 @@ 3.3.1. Users A "user" is the conceptual entity that is associated with the access permissions granted to a particular session. A user is identified by a string which is unique within the server. As described in [RFC6241], the user name string is derived from the transport layer during session establishment. If the transport layer cannot authenticate the user, the session is terminated. - The server MAY support a "recovery session" mechanism, which will - bypass all access control enforcement. This is useful for - restricting initial access and repairing a broken access control - configuration. - 3.3.2. Groups Access to a specific NETCONF protocol operation is granted to a session, associated with a group, not a user. A group is identified by its name. All group names are unique within the server. A group member is identified by a user name string. The same user can be a member of multiple groups. -3.3.3. Global Enforcement Controls +3.3.3. Emergency Recovery Session - There are four global controls that are used to help control how + The server MAY support a "recovery session" mechanism, which will + bypass all access control enforcement. This is useful for + restricting initial access and repairing a broken access control + configuration. + +3.3.4. Global Enforcement Controls + + There are five global controls that are used to help control how access control is enforced. -3.3.3.1. enable-nacm Switch +3.3.4.1. enable-nacm Switch A global "enable-nacm" on/off switch is provided to enable or disable all access control enforcement. When this global switch is set to "true", then all requests are checked against the access control rules, and only permitted if configured to allow the specific access request. When this global switch is set to "false", then all access requested are permitted. -3.3.3.2. read-default Switch +3.3.4.2. read-default Switch An on/off "read-default" switch is provided to enable or disable default access to receive data in replies and notifications. When the "enable-nacm" global switch is set to "true", then this global switch is relevant, if no matching access control rule is found to explicitly permit or deny read access to the requested NETCONF datastore data or notification event type. When this global switch is set to "permit", and no matching access control rule is found for the NETCONF datastore read or notification event requested, then access is permitted. When this global switch is set to "deny", and no matching access control rule is found for the NETCONF datastore read or notification event requested, then access is denied. -3.3.3.3. write-default Switch +3.3.4.3. write-default Switch An on/off "write-default" switch is provided to enable or disable default access to alter configuration data. When the "enable-nacm" global switch is set to "true", then this global switch is relevant, if no matching access control rule is found to explicitly permit or deny write access to the requested NETCONF datastore data. When this global switch is set to "permit", and no matching access control rule is found for the NETCONF datastore write requested, then access is permitted. When this global switch is set to "deny", and no matching access control rule is found for the NETCONF datastore write requested, then access is denied. -3.3.3.4. exec-default Switch +3.3.4.4. exec-default Switch An on/off "exec-default" switch is provided to enable or disable default access to execute protocol operations. When the "enable- nacm" global switch is set to "true", then this global switch is relevant, if no matching access control rule is found to explicitly permit or deny access to the requested NETCONF protocol operation. When this global switch is set to "permit", and no matching access control rule is found for the NETCONF protocol operation requested, then access is permitted. When this global switch is set to "deny", and no matching access control rule is found for the NETCONF protocol operation requested, then access is denied. -3.3.4. Access Control Rules +3.3.4.5. enable-external-groups Switch + + When this global switch is set to "true", the group names reported by + the NETCONF transport layer for a session are used together with the + locally configured group names, to determine the access control rules + for the session. + + When this switch is set to "false", the group names reported by the + NETCONF transport layer are ignored by NACM. + +3.3.5. Access Control Rules There are 4 types of rules available in NACM: module rule: Controls access for definitions in a specific YANG module, identified by its name. protocol operation rule: Controls access for a specific protocol operation, identified by its YANG module and name. data node rule: Controls access for a specific data node, identified @@ -786,22 +801,22 @@ rules, based on the supplied user name, group names, and the configuration data stored on the server. 3.4.3. "access-denied" Error Handling The "access-denied" error-tag is generated when the access control system denies access to either a request to invoke a protocol operation or a request to perform a particular access operation on the configuration datastore. - A server MUST NOT include any sensitive information in any elements within the response. + A server MUST NOT include any information the client is not allowed + to read in any elements within the response. 3.4.4. Incoming RPC Message Validation The diagram below shows the basic conceptual structure of the access control processing model for incoming NETCONF messages, within a server. NETCONF server +------------+ | XML | @@ -848,22 +863,22 @@ operation is permitted. 2. If the requesting session is identified as a "recovery session", then the protocol operation is permitted. 3. If the requested operation is the NETCONF protocol operation, then the protocol operation is permitted. 4. Check all the "group" entries for ones that contain a "user- name" entry that equals the user name for the session making the - request. Add to these groups the set of groups provided by the - transport layer. + request. If the "enable-external-groups" leaf is "true", add to + these groups the set of groups provided by the transport layer. 5. If no groups are found, continue with step 10. 6. Process all rule-list entries, in the order they appear in the configuration. If a rule-list's "group" leaf-list does not match any of the user's groups, proceed to the next rule-list entry. 7. For each rule-list entry found, process all rules, in order, until a rule that matches the requested access operation is @@ -929,22 +944,23 @@ The data node access request is authorized by following these steps: 1. If the "enable-nacm" leaf is set to "false", then the access operation is permitted. 2. If the requesting session is identified as a "recovery session", then the access operation is permitted. 3. Check all the "group" entries for ones that contain a "user- name" entry that equals the user name for the session making the - request. Add to these groups the set of groups provided by the - transport layer. + request. If the the "enable-external-groups" leaf is "true", + add to these groups the set of groups provided by the transport + layer. 4. If no groups are found, continue with step 9. 5. Process all rule-list entries, in the order they appear in the configuration. If a rule-list's "group" leaf-list does not match any of the user's groups, proceed to the next rule-list entry. 6. For each rule-list entry found, process all rules, in order, until a rule that matches the requested access operation is @@ -1050,22 +1066,22 @@ 2. If the session is identified as a "recovery session", then the notification is permitted. 3. If the notification is the NETCONF or event type [RFC5277], then the notification is permitted. 4. Check all the "group" entries for ones that contain a "user- name" entry that equals the user name for the session making the - request. Add to these groups the set of groups provided by the - transport layer. + request. If the "enable-external-groups" leaf is "true", add to + these groups the set of groups provided by the transport layer. 5. If no groups are found, continue with step 10. 6. Process all rule-list entries, in the order they appear in the configuration. If a rule-list's "group" leaf-list does not match any of the user's groups, proceed to the next rule-list entry. 7. For each rule-list entry found, process all rules, in order, until a rule that matches the requested access operation is @@ -1091,33 +1107,31 @@ advertised in the server capabilities, and the "notification" statement contains a "nacm:default-deny-all" statement, then the notification is dropped for the associated subscription. 11. If the "read-default" leaf is set to "permit", then permit the notification, otherwise drop the notification for the associated subscription. 3.5. Data Model Definitions - This section defines the semantics of the conceptual data structures - found in the data model in Section 3.5. - 3.5.1. Data Organization The following diagram highlights the contents and structure of the NACM YANG module. +--rw nacm +--rw enable-nacm? boolean +--rw read-default? action-type +--rw write-default? action-type +--rw exec-default? action-type + +--rw enable-external-groups? boolean +--ro denied-operations yang:zero-based-counter32 +--ro denied-data-writes yang:zero-based-counter32 +--ro denied-notifications yang:zero-based-counter32 +--rw groups | +--rw group [name] | +--rw name group-name-type | +--rw user-name* user-name-type +--rw rule-list [name] +--rw name string +--rw group* union @@ -1136,25 +1150,26 @@ +--rw comment? string 3.5.2. YANG Module The following YANG module specifies the normative NETCONF content that MUST by supported by the server. The "ietf-netconf-acm" YANG module imports typedefs from [RFC6021]. // RFC Ed.: please update the date to the date of publication - file="ietf-netconf-acm@2011-10-31.yang" + file="ietf-netconf-acm@2011-12-23.yang" module ietf-netconf-acm { namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-acm"; + prefix "nacm"; import ietf-yang-types { prefix yang; } organization "IETF NETCONF (Network Configuration) Working Group"; contact @@ -1161,21 +1176,21 @@ "WG Web: WG List: WG Chair: Mehmet Ersue WG Chair: Bert Wijnen Editor: Andy Bierman - + Editor: Martin Bjorklund "; description "NETCONF Access Control Model. Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. @@ -1185,26 +1200,27 @@ License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and // remove this note // RFC Ed.: remove this note - // Note: extracted from draft-ietf-netconf-access-control-06.txt + // Note: extracted from draft-ietf-netconf-access-control-07.txt // RFC Ed.: please update the date to the date of publication - revision "2011-10-31" { + revision "2011-12-23" { description "Initial version"; + reference "RFC XXXX: Network Configuration Protocol Access Control Model"; } /* * Extension statements */ extension default-deny-write { @@ -1338,20 +1355,24 @@ 'USER', which contains the name of user of the current session. o The function library is the core function library, but note that due to the syntax restrictions of an instance-identifier, no functions are allowed. o The context node is the root node in the data tree."; } + /* + * Data definition statements + */ + container nacm { nacm:default-deny-all; description "Parameters for NETCONF Access Control Model."; leaf enable-nacm { type boolean; default true; description @@ -1379,20 +1400,31 @@ particular write request."; } leaf exec-default { type action-type; default "permit"; description "Controls whether exec access is granted if no appropriate rule is found for a particular protocol operation request."; } + leaf enable-external-groups { + type boolean; + default true; + description + "Controls whether the server uses the groups reported by the + NETCONF transport layer when it assigns the user to a set of + NACM groups. If this leaf has the value 'false', any group + names reported by the transport layer are ignored by the + server."; + } + leaf denied-operations { type yang:zero-based-counter32; config false; mandatory true; description "Number of times a protocol operation request was denied since the server last restarted."; } leaf denied-data-writes { @@ -1415,23 +1447,24 @@ the event type was denied, since the server last restarted."; } container groups { description "NETCONF Access Control Groups."; list group { key name; - description - "One NACM Group Entry."; + "One NACM Group Entry. This list will only contain + configured entries, not any entries learned from + any transport protocols."; leaf name { type group-name-type; description "Group name associated with this entry."; } leaf-list user-name { type user-name-type; description @@ -1619,25 +1651,25 @@ when configuring a NETCONF server with NACM. 3.7.1. NACM Configuration and Monitoring Considerations Configuration of the access control system is highly sensitive to system security. A server may choose not to allow any user configuration to some portions of it, such as the global security level, or the groups which allowed access to system resources. By default, NACM enforcement is enabled. By default, "read" access - to all datastore contents enabled, (unless "nacm:default-deny-all" is - specified for the data definition) and "exec" access is enabled for - safe protocol operations. An administrator needs to ensure that NACM - is enabled, and also decide if the default access parameters are set - appropriately. Make sure the following data nodes are properly + to all datastore contents is enabled, (unless "nacm:default-deny-all" + is specified for the data definition) and "exec" access is enabled + for safe protocol operations. An administrator needs to ensure that + NACM is enabled, and also decide if the default access parameters are + set appropriately. Make sure the following data nodes are properly configured: o /nacm/enable-nacm (default "true") o /nacm/read-default (default "permit") o /nacm/write-default (default "deny") o /nacm/exec-default (default "permit") @@ -1661,32 +1693,43 @@ representing access control rules (/nacm/rule-list and /nacm/ rule-list/rule) are ordered by the client. The server will evaluate the access control rules according to their relative conceptual order within the running datastore configuration. Note that the /nacm/groups data structure contains the administrative group names used by the server. These group names may be configured locally and/or provided through an external protocol, such as RADIUS [RFC2865] [RFC5607]. + An administrator needs to be aware of the security properties of any + external protocol used by the NETCONF transport layer to determine + group names. For example, if this protocol does not protect against + man-in-the-middle attacks, an attacker might be able to inject group + names that are configured in NACM, so that a user gets more + permissions than it should. In such cases, the administrator may + wish to disable the usage of such group names, by setting /nacm/ + enable-external-groups to "false". + An administrator needs to restrict read access to the following objects within this data model, which reveal access control configuration which could be considered sensitive. o /nacm/enable-nacm o /nacm/read-default o /nacm/write-default o /nacm/exec-default + o /nacm/enable-external-groups + o /nacm/groups o /nacm/rule-list 3.7.2. General Configuration Issues There is a risk that invocation of non-standard protocol operations will have undocumented side effects. An administrator needs to construct access control rules such that the configuration datastore is protected from such side effects. @@ -1756,21 +1799,21 @@ o o 3.7.3. Data Model Design Considerations Designers need to clearly identify any sensitive data, notifications, or protocol operations defined within a YANG module. For such definitions, a "nacm:default-deny-write" or "nacm:default-deny-all" - statement SHOULD be present, in addition to a clear description of + statement ought to be present, in addition to a clear description of the security risks. Protocol operations need to be properly documented by the data model designer, so it is clear to administrators what data nodes (if any) are affected by the protocol operation, and what information (if any) is returned in the message. Data models ought to be designed so that different access levels for input parameters to protocol operations is not required. Use of generic protocol operations should be avoided, and separate protocol @@ -1793,23 +1836,20 @@ Network Configuration Protocol (NETCONF)", RFC 6020, October 2010. [RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, October 2010. [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman, "Network Configuration Protocol (NETCONF)", RFC 6241, June 2011. - [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure - Shell (SSH)", RFC 6242, June 2011. - 4.2. Informative References [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. [RFC5607] Nelson, D. and G. Weber, "Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management", RFC 5607, July 2009. @@ -2131,104 +2171,112 @@ This example shows 1 notification rule: deny-config-change: This rule prevents the "limited" or "guest" groups from receiving the acme event type. Appendix B. Change Log -- RFC Ed.: remove this section before publication. -B.1. 05-06 +B.1. 06-07 + + Added the leaf "enable-external-groups". + + Removed dependency to RFC 6242. + + Some editorial changes after IESG review. + +B.2. 05-06 Added clarification to Security Considerations section about ordered-by user lists (/nacm/rule-list and /nacm/rule-list/rule). Added clarifications to security considerations wrt/ user names and NETCONF capability changes. Fixed typos found in review. -B.2. 04-05 +B.3. 04-05 Updated Security Considerations section. Changed term 'operator' to 'administrator'. Used the terms "access operation" and "protocol operation" consistently. Moved some normative text from section 2 to section 3. Also made it more clear that section 2 is not a requirements section, but documentation of the objectives for NACM. Renamed "nacm:secure" to "nacm:default-deny-write", and "nacm:very- secure" to "nacm:default-deny-all". Explained that "nacm:default- deny-write" is ignored on rpc statements. Described that and behave as if specified with "nacm:default-deny-all". -B.3. 03-04 +B.4. 03-04 Introduced rule-lists to group related rules together. Moved "module-rule", "rpc-rule", "notification-rule", and "data-rule" into one common "rule", with a choice to select between the four variants. Changed "superuser" to "recovery session", and adjusted text throughout document for this change. Clarified behavior of global default NACM parameters, enable-nacm, read-default, write-default, exec-default. Clarified when access control is applied during system initialization. -B.4. 02-03 +B.5. 02-03 Fixed improper usage of RFC 2119 keywords. Changed term usage of "database" to "datastore". Clarified that "secure" and "very-secure" extensions only apply if the /nacm/enable-nacm object is "true". -B.5. 01-02 +B.6. 01-02 Removed authentication text and objects. Changed module name from ietf-nacm to ietf-netconf-acm. Updated NETCONF and YANG terminology. Removed open issues section. Changed some must to MUST in requirements section. -B.6. 00-01 +B.7. 00-01 Updated YANG anf YANG Types references. Updated module namespace URI to standard format. Updated module header meta-data to standard format. Filled in IANA section. -B.7. 00 +B.8. 00 Initial version cloned from draft-bierman-netconf-access-control-02.txt. Authors' Addresses Andy Bierman Brocade - Email: andy.bierman@brocade.com + Email: andy@netconfcentral.org Martin Bjorklund Tail-f Systems Email: mbj@tail-f.com