Re: [netmod] Netmod ACL - Can "access-lists" be set up as a "grouping"

"Jon Shallow" <supjps-ietf@jpshallow.com> Mon, 08 January 2018 15:47 UTC

Return-Path: <supjps-ietf@jpshallow.com>
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 64D90129966 for <netmod@ietfa.amsl.com>; Mon, 8 Jan 2018 07:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 vJU44eU9Z9Vr for <netmod@ietfa.amsl.com>; Mon, 8 Jan 2018 07:47:17 -0800 (PST)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (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 7E9A3126579 for <netmod@ietf.org>; Mon, 8 Jan 2018 07:47:17 -0800 (PST)
Received: from [127.0.0.1] (helo=N01332) by mail.jpshallow.com with smtps (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from <jon.shallow@jpshallow.com>) id 1eYZdn-0005df-61; Mon, 08 Jan 2018 15:47:11 +0000
From: "Jon Shallow" <supjps-ietf@jpshallow.com>
To: "'Robert Wilton'" <rwilton@cisco.com>, <netmod@ietf.org>, "'Einar Nilsen-Nygaard \(einarnn\)'" <einarnn@cisco.com>, "'Mahesh Jethanandani'" <mjethanandani@gmail.com>
References: <012301d3886e$f96f08e0$ec4d1aa0$@jpshallow.com> <B0576B62-CB61-45EA-99EF-E5B67545B85C@cisco.com> <041cd24f-858c-5e94-6bea-6d25f62b4acc@cisco.com>
In-Reply-To: <041cd24f-858c-5e94-6bea-6d25f62b4acc@cisco.com>
Date: Mon, 8 Jan 2018 15:47:11 -0000
Message-ID: <022401d38897$f2aa1b70$d7fe5250$@jpshallow.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0225_01D38897.F2ABA210"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKQyRuXL6dM12jnz185RKPboCEftgLUfB8AAmARq32hxfarIA==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/3UJFn5syUVF7UgO4c1XeYak0Z_E>
Subject: Re: [netmod] Netmod ACL - Can "access-lists" be set up as a "grouping"
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: Mon, 08 Jan 2018 15:47:19 -0000

Hi Robert,

 

A good set of points.

 

My particular use case (hence raising the question) is defining a YANG model where there are multiple appliances and where ACLs are defined for each appliance, but there is the likelihood of the different appliances using the same “acl-name”, but the contents of “acl-name” are different.  Having a grouping (using import-by-revision) would help me considerably here.

 

Regards

 

Jon

 

From: Robert Wilton [mailto: rwilton@cisco.com] 
Sent: 08 January 2018 15:31
To: Einar Nilsen-Nygaard (einarnn); Jon Shallow; Mahesh Jethanandani
Cc: netmod@ietf.org
Subject: Re: [netmod] Netmod ACL - Can "access-lists" be set up as a "grouping"

 

Hi Einar, Jon, Mahesh,

My gut instinct is that making this a grouping might not be a good idea:

1) If somebody updates the core ACL model, will then need to check that anyone using it should be similarly updated (unless they use import-by-revision).

2) Does it make sense to define ACLs in separate places.  Would like be more simple if ACLs were defined in a central place and then just referenced by other protocols as required.

3) I think that groupings are probably overused and I think that they can detract from the readability of the model.  (I regard the OpenConfig YANG models as an extreme example of this, where it is necessary to compile the modules together to figure out where everything fits together).

Having said that, I don't think that this issue is important enough to have a long discussion about ...

Thanks,
Rob



On 08/01/2018 15:02, Einar Nilsen-Nygaard (einarnn) wrote:

Since this is a 7-line change, I see no harm in it if no-one objects? Mahesh has the token for rolling in updates discussed just prior to the end of 2017. 

 

Here’s a possible diff: 

 

$ git diff -b

diff --git a/src/yang/ietf-access-control-list.yang b/src/yang/ietf-access-control-list.yang

index 4d698c9..b1a173f 100644

--- a/src/yang/ietf-access-control-list.yang

+++ b/src/yang/ietf-access-control-list.yang

@@ -402,6 +402,10 @@ module ietf-access-control-list {

   /*

    * Configuration data nodes

    */

+  grouping access-lists-top {

+    description

+      "Grouping to allow reuse of access lists container elsewhere.";

+

     container access-lists {

       description

         "This is a top level container for Access Control Lists.

@@ -576,6 +580,9 @@ module ietf-access-control-list {

         }

       }

     }

+  }

+  uses access-lists-top;

+

   augment "/if:interfaces/if:interface" {

     description

       "Augment interfaces to allow ACLs to be associated in either the

 

Cheers,

 

Einar

 





On 8 Jan 2018, at 10:53, Jon Shallow <supjps-ietf@jpshallow.com>; wrote:

 

Hi There,

 

I appreciate that this is late to the table, but is it possible to set up “access-lists” as a “grouping” in the YANG data model so that “access-lists” can be included by “uses” in a higher level YANG data model?

 

I have raised this as issue #22 at  <https://github.com/netmod-wg/acl-model/issues> https://github.com/netmod-wg/acl-model/issues

 

Regards

 

Jon

_______________________________________________
netmod mailing list
 <mailto:netmod@ietf.org> netmod@ietf.org
 <https://www.ietf.org/mailman/listinfo/netmod> https://www.ietf.org/mailman/listinfo/netmod

 






_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod