Re: [Netconf] draft-ietf-netconf-rfc6536bis Query

Rohit R Ranade <rohitrranade@huawei.com> Thu, 30 November 2017 03:07 UTC

Return-Path: <rohitrranade@huawei.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 170DE127843 for <netconf@ietfa.amsl.com>; Wed, 29 Nov 2017 19:07:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 A1M_IyXbbl47 for <netconf@ietfa.amsl.com>; Wed, 29 Nov 2017 19:07:03 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 EB3F0120454 for <netconf@ietf.org>; Wed, 29 Nov 2017 19:07:02 -0800 (PST)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 9CD6C38F128A1 for <netconf@ietf.org>; Thu, 30 Nov 2017 03:06:59 +0000 (GMT)
Received: from DGGEMA422-HUB.china.huawei.com (10.1.198.155) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 30 Nov 2017 03:07:00 +0000
Received: from DGGEMA502-MBX.china.huawei.com ([169.254.2.85]) by dggema422-hub.china.huawei.com ([10.1.198.155]) with mapi id 14.03.0361.001; Thu, 30 Nov 2017 11:06:51 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] draft-ietf-netconf-rfc6536bis Query
Thread-Index: AdNdz9MehD+d0xYjTJ+ndshlR/LYrAA3pAkgArZagoA=
Date: Thu, 30 Nov 2017 03:06:50 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6B15CE6B@DGGEMA502-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.150.121]
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6B15CE6BDGGEMA502MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/UYUUYn6DrYO-x-YLezD_ui8sYjk>
Subject: Re: [Netconf] draft-ietf-netconf-rfc6536bis Query
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 30 Nov 2017 03:07:05 -0000

Hi Andy/Martin,

Can you please clarify the below query about rule-list group having "*".  Whether we need to allow a new group to be added a rule-list which already has a "*" in the leaf-list.

With Regards,
Rohit R

From: Rohit R Ranade
Sent: 16 November 2017 13:17
To: 'netconf@ietf.org' <netconf@ietf.org>
Subject: RE: [Netconf] draft-ietf-netconf-rfc6536bis Query

Hi All,

1 more point I wanted clarified was for the below point

leaf-list group {
           type union {
             type matchall-string-type;
             type group-name-type;
           }
           description
             "List of administrative groups that will be
              assigned the associated access rights
              defined by the 'rule' list.

              The string '*' indicates that all groups apply to the
              entry.";

Consider that existing configuration is like below:
<rule-list>
   <name>list1</name>
   <group>ug1</group>
</rule-list>

Consider that user will add to this group a record of '*"
<rule-list>
   <name>list1</name>
   <group>ug1</group>
<group>*</group>
</rule-list>

?  Whether this is valid configuration ? "*" can be considered as a super-set as it will apply for all group. So can this leaf-list contain * along with other UGs ?

One scenario where this is possible is when initially the user had thought of applying a rule-list to only a particular Group , but later the user wants to apply to all groups.

With Regards,
Rohit R

From: Rohit R Ranade
Sent: 15 November 2017 10:42
To: netconf@ietf.org<mailto:netconf@ietf.org>
Subject: [Netconf] draft-ietf-netconf-rfc6536bis Query

Hi All,

For the state-data in NACM like the below :

leaf denied-operations {
         type yang:zero-based-counter32;
         config false;
         mandatory true;
         description
           "Number of times since the server last restarted that a
            protocol operation request was denied.";
       }

"Number of times since the server" ==> Here the server is being referenced to NETCONF server or RESTCONF server ?
Please note that the both the NETCONF server and RESTCONF server maybe using the same NACM configurations but the state-data maintained by each protocol maybe different.

With Regards,
Rohit R