Re: [Netconf] draft-ietf-netconf-rfc6536bis Query
Andy Bierman <andy@yumaworks.com> Thu, 30 November 2017 03:37 UTC
Return-Path: <andy@yumaworks.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 5DACF128AB0 for <netconf@ietfa.amsl.com>; Wed, 29 Nov 2017 19:37:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.com
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 0lAO25JUaaxv for <netconf@ietfa.amsl.com>; Wed, 29 Nov 2017 19:37:35 -0800 (PST)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F253C12896F for <netconf@ietf.org>; Wed, 29 Nov 2017 19:37:34 -0800 (PST)
Received: by mail-lf0-x235.google.com with SMTP id x20so6333948lff.1 for <netconf@ietf.org>; Wed, 29 Nov 2017 19:37:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uqTMOBTQTpTiq0kZ+/rImhRF8BSoYcIOZVxYKtzdUjI=; b=tbDK9On5pGEpW+d1HEA64GF53kAbjtKeD52cGhbyo6laqFOvm6bHsVKQBdHf1+lmv8 g+WpRUDtavOMtf2je8k7k4lW8ib0dG79otTV54pzILL3tu1YP3fTZ6xPAi9dRa3l2x3P CCVmQ8ZCjct1Tp+8908xmbxac8RHhUQ/qlmZU8u5jvcu/w0tFXqxSdZNjxdfEcsiEV1y HGfkYxyXKXpUMzzhuXXMsjWDGiKeQcBukQzSoUAVrTBlI7VnBM88+0Ixa0Y4Dxlu+Eeh RbwUoLbYgJHW/Ns//71LJPdincsIEZNYr+JxcziETLMTESyQwPeybRsfqPYTj/ZflcXJ XChQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uqTMOBTQTpTiq0kZ+/rImhRF8BSoYcIOZVxYKtzdUjI=; b=g4ybh2tMyxfYR5SOF9NbS5ESfMU18sE7oo4iY6n/Q6g+zpEnrjDnt7N94EM9Qy1kqD qw2s93S1wF9x+KiU9/upuNJAMQBKxeEulfFYe8G9beX3MhzV0EW072nx0kLkbtxTPF9d 1T7Q8Bg8/dDo0kDAAtJJTVcl+m1hkEAZgtaUhFjx8jRDOUmVWAiVpwF+HcH2/PtDhiEH WkWuOR/lJCpeR5aNitYRY+G1z04yfHax4G0qCKHvnQ9kys+n5t6oP8zef4OMb4shYFhW cNKwNhjxTSyVGSq0JvqTd15oxsn+qKjK5l6C9y8vGSC3ZMyodZQaIOgJ8C3SKOurQY4W rSsg==
X-Gm-Message-State: AJaThX4rKu2FjS5yjlA9LUvWaRAF1R2+VVDTtQKcmUSRT51LTX26W0Eh CV9CmUQsW8wU7qC5lKRGayCAF70TN7TpRqZjojLR5w==
X-Google-Smtp-Source: AGs4zMaeMmaT9ikV3vuTuktlhN1RNtA952TONxfQ4Jly+YeH525xSnt11kYaOrKhPf9s7yuyPQsRmDD2BTR6M4U3ypg=
X-Received: by 10.25.147.23 with SMTP id v23mr1946579lfd.120.1512013053170; Wed, 29 Nov 2017 19:37:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.33.81 with HTTP; Wed, 29 Nov 2017 19:37:32 -0800 (PST)
In-Reply-To: <991B70D8B4112A4699D5C00DDBBF878A6B15CE6B@DGGEMA502-MBX.china.huawei.com>
References: <991B70D8B4112A4699D5C00DDBBF878A6B15CE6B@DGGEMA502-MBX.china.huawei.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 29 Nov 2017 19:37:32 -0800
Message-ID: <CABCOCHS0EVKVb+5t2VYFGscdV4UQ0O_f5b+pNVBHxfXmGVNGbA@mail.gmail.com>
To: Rohit R Ranade <rohitrranade@huawei.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045ce2d6ee25dc055f2af84d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/f6joEbMyxHJjYXbZoEJHt2ClHsg>
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:37:37 -0000
On Wed, Nov 29, 2017 at 7:06 PM, Rohit R Ranade <rohitrranade@huawei.com> wrote: > 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. > > > Yes -- both group entries are allowed, even though 1 of them is redundant > With Regards, > > Rohit R > Andy > > > *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 > *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 > > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf > >
- [Netconf] draft-ietf-netconf-rfc6536bis Query Rohit R Ranade
- Re: [Netconf] draft-ietf-netconf-rfc6536bis Query Rohit R Ranade
- Re: [Netconf] draft-ietf-netconf-rfc6536bis Query Rohit R Ranade
- Re: [Netconf] draft-ietf-netconf-rfc6536bis Query Andy Bierman