[Netconf] Question on NACM usage

"Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com> Wed, 14 December 2016 07:49 UTC

Return-Path: <bart.bogaert@nokia.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 883A8129C99 for <netconf@ietfa.amsl.com>; Tue, 13 Dec 2016 23:49:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level:
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wDSvk6bNePM9 for <netconf@ietfa.amsl.com>; Tue, 13 Dec 2016 23:49:36 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A621129C80 for <netconf@ietf.org>; Tue, 13 Dec 2016 23:49:36 -0800 (PST)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id 7C989F791A7C7 for <netconf@ietf.org>; Wed, 14 Dec 2016 07:49:31 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id uBE7nVKs020318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <netconf@ietf.org>; Wed, 14 Dec 2016 07:49:33 GMT
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id uBE7mq3q018073 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <netconf@ietf.org>; Wed, 14 Dec 2016 07:49:29 GMT
Received: from FR712WXCHMBA09.zeu.alcatel-lucent.com ([169.254.5.164]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0301.000; Wed, 14 Dec 2016 08:49:11 +0100
From: "Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: Question on NACM usage
Thread-Index: AdJV3UXYgEg9XZFpRp2SVghevL67Og==
Date: Wed, 14 Dec 2016 07:49:11 +0000
Message-ID: <D62E05768DBAFF42A72B9F4954476D65010EB15BAB@FR712WXCHMBA09.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_00DC_01D255E6.EF6EA2D0"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/WjzqB5miGCPUJxWD3kl4tquK4Hc>
Subject: [Netconf] Question on NACM usage
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2016 07:49:39 -0000

Hi

 

I would like to continue on one of the examples given in the appendix of the
NACM RFC:

 

       <rule>

         <name>permit-dummy-interface</name>

         <path xmlns:acme="http://example.com/ns/itf">

           /acme:interfaces/acme:interface[acme:name='dummy']

         </path>

         <access-operations>read update</access-operations>

         <action>permit</action>

         <comment>

           Allow the limited and guest groups read

           and update access to the dummy interface.

         </comment>

       </rule>

 

I am assuming that this rule allows read and update access to all leaves of
the data node identified by the path, so it would allow to update a specific
leaf of that data node.  Is my understanding correct?

Another question I have is related to the XPATH itself.  In the above
example I think that the name leaf is the key of the list.  Can we use
another leaf to identify a data node and allow specific access to that data
node?

Assume that there would be a leaf called 'pool-id' which can take values
from 1 to 10, could the XPATH look like below?

 

         <path xmlns:acme="http://example.com/ns/itf">

           /acme:interfaces/acme:interface[acme:pool-id=5]

         </path>

 

We would like to allow/deny access to data nodes (and the leafs of that data
node) to groups based on the value of the pool-id.  Is the above the correct
way to express the access control?

 

Best regards - Vriendelijke groeten,

Bart Bogaert

Broadband-Access System Architect Data

Contact number +32 3 2408310 (+32 477 673952)

 

NOKIA

Copernicuslaan 50, 2018 Antwerp, Belgium