[netmod] A mean to match many entries would ease the writing of rules

otilibil@eurecom.fr Wed, 14 February 2018 14:42 UTC

Return-Path: <otilibil@eurecom.fr>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 931FE12741D; Wed, 14 Feb 2018 06:42:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 vxo4MKaissSr; Wed, 14 Feb 2018 06:42:05 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp2.eurecom.fr [193.55.113.211]) by ietfa.amsl.com (Postfix) with ESMTP id 1D6AE126BFD; Wed, 14 Feb 2018 06:42:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.46,512,1511823600"; d="scan'208";a="7652973"
Received: from thorgal.eurecom.fr ([10.3.2.220]) by drago2i.eurecom.fr with ESMTP; 14 Feb 2018 15:42:02 +0100
Received: (from apache@localhost) by thorgal.eurecom.fr (8.14.4+Sun/8.14.4/Submit) id w1EEg2E4020499; Wed, 14 Feb 2018 15:42:02 +0100 (CET)
X-Authentication-Warning: thorgal.eurecom.fr: apache set sender to otilibil@eurecom.fr using -f
Received: from reverse.completel.net (reverse.completel.net [92.103.89.82]) by webmail.eurecom.fr (Horde MIME library) with HTTP; Wed, 14 Feb 2018 15:42:02 +0100
Message-ID: <20180214154202.v15kguz5cs80ok44@webmail.eurecom.fr>
Date: Wed, 14 Feb 2018 15:42:02 +0100
From: otilibil@eurecom.fr
To: draft-ietf-netconf-rfc6536bis@ietf.org
Cc: netmod@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.1.4)
X-Originating-IP: 92.103.89.82
X-Remote-Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/zsUihuokPYhvidvkyd1Mr1J7unU>
Subject: [netmod] A mean to match many entries would ease the writing of rules
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Feb 2018 14:42:08 -0000

Hello all,
I reviewed draft-ietf-netconf-rfc6536bis-09; it seems the draft misses  
a way to match many entries under the same rule. For example, instead  
of,

       <rule>
         <name>permit-get-config</name>
         <module-name>ietf-netconf</module-name>
         <rpc-name>get-config</rpc-name>
         <access-operations>exec</access-operations>
         <action>permit</action>
         <comment>
	  Permits invocation of the NETCONF 'get-config'.
	</comment>
       </rule>
       <rule>
         <name>permit-get</name>
         <module-name>ietf-netconf</module-name>
         <rpc-name>get</rpc-name>
         <access-operations>exec</access-operations>
         <action>permit</action>
         <comment>
	  Permits invocation of the NETCONF 'get'.
	</comment>
       </rule>

It would ease the writing to have a keyword (or a white space, as for  
'access-operations') to match many entries at the same time:

       <rule>
         <name>permit-get</name>
         <module-name>ietf-netconf</module-name>
         <rpc-name>get get-config</rpc-name>
         <access-operations>exec</access-operations>
         <action>permit</action>
         <comment>
	  Permits invocation of the NETCONF 'get' & 'get-config'.
	</comment>
       </rule>

So, the valid values will become (for 'rpc-name', 'notification-name',  
and 'path'):

  * A string for one entry
  * A string for more than one entry (a white space separates entries)
  * Or, the catch-all '*'.

How do you see my proposal?

Regards,
Ariel



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr