Network Configuration Protocol (NETCONF) Access Control Model
RFC 6536

Internet Engineering Task Force (IETF)                        A. Bierman
Request for Comments: 6536                                     YumaWorks
Category: Standards Track                                   M. Bjorklund
ISSN: 2070-1721                                           Tail-f Systems
                                                              March 2012

     Network Configuration Protocol (NETCONF) Access Control Model

Abstract

   The standardization of network configuration interfaces for use with
   the Network Configuration Protocol (NETCONF) 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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6536.

Copyright Notice

   Copyright (c) 2012 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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Bierman & Bjorklund          Standards Track                    [Page 1]
RFC 6536                          NACM                        March 2012

Table of Contents

   1. Introduction ....................................................3
      1.1. Terminology ................................................3
   2. Access Control Design Objectives ................................4
      2.1. Access Control Points ......................................5
      2.2. Simplicity .................................................5
      2.3. Procedural Interface .......................................6
      2.4. Datastore Access ...........................................6
      2.5. Users and Groups ...........................................6
      2.6. Maintenance ................................................6
      2.7. Configuration Capabilities .................................7
      2.8. Identifying Security-Sensitive Content .....................7
   3. NETCONF Access Control Model (NACM) .............................8
      3.1. Introduction ...............................................8
           3.1.1. Features ............................................8
           3.1.2. External Dependencies ...............................9
           3.1.3. Message Processing Model ............................9
      3.2. Datastore Access ..........................................11
           3.2.1. Access Rights ......................................11
           3.2.2. <get> and <get-config> Operations ..................12
           3.2.3. <edit-config> Operation ............................12
           3.2.4. <copy-config> Operation ............................13
           3.2.5. <delete-config> Operation ..........................14
           3.2.6. <commit> Operation .................................14
           3.2.7. <discard-changes> Operation ........................14
           3.2.8. <kill-session> Operation ...........................14
      3.3. Model Components ..........................................15
           3.3.1. Users ..............................................15
           3.3.2. Groups .............................................15
           3.3.3. Emergency Recovery Session .........................15
           3.3.4. Global Enforcement Controls ........................15
                  3.3.4.1. enable-nacm Switch ........................15
                  3.3.4.2. read-default Switch .......................16
                  3.3.4.3. write-default Switch ......................16