Re: [netmod] I-D Action: draft-ietf-netmod-module-tags-09.txt

"Rob Wilton (rwilton)" <rwilton@cisco.com> Fri, 04 October 2019 08:53 UTC

Return-Path: <rwilton@cisco.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 1A874120288 for <netmod@ietfa.amsl.com>; Fri, 4 Oct 2019 01:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=e+YedRkt; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=F9cAqk+P
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 trMRJ0T9tp7n for <netmod@ietfa.amsl.com>; Fri, 4 Oct 2019 01:53:29 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1BFC12007C for <netmod@ietf.org>; Fri, 4 Oct 2019 01:53:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=28680; q=dns/txt; s=iport; t=1570179208; x=1571388808; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=bkpGH8oXX0y/yKyPZfzQaKW6tlVq4Xqq+/bpRBCiYP8=; b=e+YedRktD/narrZ6qnNw/FxFOujQvL8/qoJrdGtifEW2hgWwCLHFJWhK Ik87nth+0ggua1Z+Cjxx5lMO+j0TRUYLja5ZhfkHEU0AIXjJAKTwuZkzc 3KxtI4kedOk9qst01K1pzCWoSTspk5T8TOPanM4rfMi9QIcm/y8yeCwC1 g=;
IronPort-PHdr: =?us-ascii?q?9a23=3AcJ8buRZqhAKXhpSENLNo/k3/LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el20gebRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn?= =?us-ascii?q?1NksAKh0olCc+BB1f8KavwcC0+AMNEfFRk5Hq8d0NSHZW2ag=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AKAAA7B5dd/4cNJK1fBhkBAQEBAQE?= =?us-ascii?q?BAQEBAQEMAQEBAQEBgVQDAQEBAQELAYEbL1ADbVYgBAsqCoQYg0cDikiCXJd?= =?us-ascii?q?5gS6BJANUCQEBAQwBARgBCgoCAQGDe0UCF4IwIzUIDgIDCQEBBAEBAQIBBQR?= =?us-ascii?q?thS0MhUsBAQEBAgEBAQwEEQoTAQEjCQsBBAcEAgEGAhEEAQEBJwMCAgIlCxQ?= =?us-ascii?q?JCAIEDgUIEQmDAYEdTQMODwECDJIakGECgTiIYXWBMoJ9AQEFgTgCDkGDAxi?= =?us-ascii?q?CFwmBNAGMDRiBQD+BEUaCTD6CYQEBAgEBFoE5ECsJCIJPMoImj2uFNYksjnA?= =?us-ascii?q?KgiOHCI4rgjpyhlyELIsMlkuREQIEAgQFAg4BAQWBPxUCNYFYcBUaIYJsCUc?= =?us-ascii?q?QFIFPg3OFFIU/dIEpjyIBgSIBAQ?=
X-IronPort-AV: E=Sophos;i="5.67,255,1566864000"; d="scan'208,217";a="638377327"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Oct 2019 08:53:27 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x948rR1G012217 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 4 Oct 2019 08:53:27 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 4 Oct 2019 03:53:26 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 4 Oct 2019 03:53:25 -0500
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 4 Oct 2019 04:53:25 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZXoujlhUaKekHADoouSw6RWQfQoNEkjALFv2D084GSS23sHSSHGkCzuU2PPTfnhDala1uX3/xQsmhIvUTQ/O6QVb+v3Vm3JCA5/zk/L4ZkLmo2YC941bPLlmp+aJLeYh8hzSt3iQ7kzMfQ4OFURO2ST4E91BBdNP6lxHaqP+Wb0XKa0C7zbZuW2jZ6rOv3uc7FeRssqsKRqYtWoA/kak4ruUwBMqVn58Gi1p0luCuwxu4PBT9/fqboc0dOykVF9Z/Wr3kGJXorRZ3a5WxBtwadpTTNwfSetHP13q939c/27SC33sgg6qAPHglcUNaIlOdw0lMBy/5NHsgaoDDpsUEQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bkpGH8oXX0y/yKyPZfzQaKW6tlVq4Xqq+/bpRBCiYP8=; b=Fno8+D3wJyyHWl7mASP5PeNSFoiPJf1KHjrCMLIzBJlNWWsL8tc9739fvzzddRsdkpDsDWmZ6tQU9Ys4re++imLnTnFhNwOGYhYQhL8vlezk5Eel9r8jvooctPUIcamWBYqHskg8qYXe4nCGY9H+sXj+AGWa/Kd8hvFRK1OHJRQjtzKbVFmnra+opEcWeh/14j5CPYywYosruAybDWLNdyGO6RTmLUkAbCx4WYk06X5yFjhCb+6vL7NasqVYI3WjkQ0kBsSrKPm8kQPfHLGxt24RQk6phSF6/nkja0KVsLUci9R19QwVALKsSVrfrft2/9/vpLk+xvHF3v7NwfHYHg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bkpGH8oXX0y/yKyPZfzQaKW6tlVq4Xqq+/bpRBCiYP8=; b=F9cAqk+PxjsLWd67CRIG2RaKBkizq0LXrFH3ZHHvwwojCtUm3hhVltvbOZ3e4r8l8Tj2N03Q6wTtVEs53gWbs0ALsQc38Xhk/HNviA83Af7RYzWrwdUQuPkRgPGQwmUnkodRtxdlpYMy5Ed/K7RMWtnEhzlpa+O1gdOj/IMOjds=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB3728.namprd11.prod.outlook.com (20.178.253.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.15; Fri, 4 Oct 2019 08:53:24 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::cca:41bd:b0bb:c549]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::cca:41bd:b0bb:c549%2]) with mapi id 15.20.2305.023; Fri, 4 Oct 2019 08:53:24 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Andy Bierman <andy@yumaworks.com>
CC: Christian Hopps <chopps@chopps.org>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] I-D Action: draft-ietf-netmod-module-tags-09.txt
Thread-Index: AQHVc7y2pV/jTrPhkEaIK8rqhQZKT6c8kmcAgAwi9zCAAF39AIAAAF1ggABzL4CAALOLgA==
Date: Fri, 4 Oct 2019 08:53:23 +0000
Message-ID: <MN2PR11MB43669B75BC562B5100C7A778B59E0@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <156942813583.28879.894232837346561087@ietfa.amsl.com> <8F9EDBC3-EB9C-452E-9091-03DBBC735CAB@chopps.org> <MN2PR11MB43662800E2F593864E130468B59F0@MN2PR11MB4366.namprd11.prod.outlook.com> <4ED3E9FA-9B58-4E9C-AA88-CFF4260A9E90@chopps.org> <MN2PR11MB43667363225E96A99C755036B59F0@MN2PR11MB4366.namprd11.prod.outlook.com> <CABCOCHQ5zGmJcrZnj-AnGh1u6aZ2G=CLP0Kn8nV11in9VHFTCw@mail.gmail.com>
In-Reply-To: <CABCOCHQ5zGmJcrZnj-AnGh1u6aZ2G=CLP0Kn8nV11in9VHFTCw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [173.38.220.46]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c68c0909-5731-4eba-d52c-08d748a850bb
x-ms-traffictypediagnostic: MN2PR11MB3728:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <MN2PR11MB37289523EBFC062B7921E161B59E0@MN2PR11MB3728.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 018093A9B5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(136003)(39860400002)(376002)(346002)(366004)(51444003)(13464003)(189003)(199004)(76116006)(99286004)(14444005)(256004)(54906003)(7696005)(52536014)(229853002)(66574012)(66446008)(66556008)(486006)(316002)(76176011)(66476007)(64756008)(6506007)(86362001)(6436002)(66066001)(53546011)(66946007)(5660300002)(25786009)(446003)(236005)(11346002)(8676002)(606006)(9686003)(4326008)(81166006)(81156014)(54896002)(3846002)(476003)(6306002)(55016002)(102836004)(33656002)(26005)(6116002)(14454004)(186003)(478600001)(71200400001)(790700001)(2906002)(966005)(6246003)(71190400001)(74316002)(6916009)(7736002)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3728; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: O3//poU2/fxPk1HouD9F+nSEb4tyWNfXM8yClQx1Jh7oMcacDecQaKNM7VmXoVS82OtQ+YBCce1WaJ6dNqJU9bKzCehV+2EdeJs1trEs+fmdCtIm175X9FSrxNvST78HwaIC1MHh/n23cLmUbHzUycW426OWAoLS1XdVjkiLhyRq/USC6EAbeg4dB1apc8RilAUXqLUzxHxZm1lLrX6eojzdKQNt8CudZsjityZzYvxwPilEOIKNtb5KxI4Bb+QJznPC+MQUrUnzannt5lP/mqVX1FD3/z2IW5rfS+tOI7HWntVIdvjtLuH+x32WYpgSDRS0cnVUoRb/YZbIkSO3pPU9FK+ZXYPv5cI65yJTb7qS0r1xsGz61hSzna8Xvlor6A2CoGBeBVhEsbJ43bjOa/XppiRJAuwMKGJUhb+hpvnnwwCpKd8b+1IdbJb+dLVl15S0aXeEwKmXgknGHK0t2Q==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB43669B75BC562B5100C7A778B59E0MN2PR11MB4366namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c68c0909-5731-4eba-d52c-08d748a850bb
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2019 08:53:24.0058 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Qd54nbYmRvz0p4nBVNlcnIIkkx6LhXSmMCdqjp0ARFWSdhI+IXy7bphfn53FKXKLC6+r3GAalo+rVlJnS/e2+Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3728
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.21, xch-rcd-011.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/xDPdE1TSRP72dLMhShqsLQSyPEQ>
Subject: Re: [netmod] I-D Action: draft-ietf-netmod-module-tags-09.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 04 Oct 2019 08:53:32 -0000


From: Andy Bierman <andy@yumaworks.com>
Sent: 03 October 2019 23:09
To: Rob Wilton (rwilton) <rwilton@cisco.com>
Cc: Christian Hopps <chopps@chopps.org>rg>; netmod@ietf.org
Subject: Re: [netmod] I-D Action: draft-ietf-netmod-module-tags-09.txt



On Thu, Oct 3, 2019 at 8:31 AM Rob Wilton (rwilton) <rwilton@cisco.com<mailto:rwilton@cisco.com>> wrote:
Hi Chris,

> -----Original Message-----
> From: Christian Hopps <chopps@chopps.org<mailto:chopps@chopps.org>>
> Sent: 03 October 2019 16:16
> To: Rob Wilton (rwilton) <rwilton@cisco.com<mailto:rwilton@cisco.com>>
> Cc: Christian Hopps <chopps@chopps.org<mailto:chopps@chopps.org>>; netmod@ietf.org<mailto:netmod@ietf.org>
> Subject: Re: [netmod] I-D Action: draft-ietf-netmod-module-tags-09.txt
>
> [resending to include list cc]
>
> > On Oct 3, 2019, at 5:45 AM, Rob Wilton (rwilton) <rwilton@cisco.com<mailto:rwilton@cisco.com>>
> wrote:
> >
> > Hi Chris,
> >
> > As discussed offline, you have left out the "masked-tag" container in
> the "modules-tags-state" module.
>
> One might read this as an objection that was discussed offline, but I
> don't think you are objecting, you're just stating what happened, correct?

Correct, not objecting, although I might be about to šŸ˜‰

Generally, I think that is what is available in "module-tags-state" should be directly equivalent to what is available in the operational datastore for servers that support NMDA.

So, my previous comments were trying to align these two together.  I.e. if you think that "masked-tag" isn't needed in "module-tags-state" then I think that there is the equivalent question of whether it should be reported in <operational>.

What is unusual in this case, is that you have some configuration that removes items from another list.


>
> > For consistently, I wonder, whether there shouldn't also be a comment in
> the "masked-tag" leaf-list in the main NMDA compatible module to indicate
> that "masked-tag" isn't reported in the operational state datastore
> because the information is combined into the "tag" leaf-list.
>
> Ok, color me confused. For NMDA, why wouldn't masked-tag show up in
> operational datastore?

By default it would.


IMO the non-NMDA state module should have the same structure as the NMDA version.
Any configured masked-tag entries that are applied will appear in <operational> and also
the non-NMDA version.

Please don't start making all kinds of special cases in NMDA.
If a configured value has an applied value, it is expected in both <operational>
and the non-NMDA module for the <operational> contents.

[RW]
I agree.

Keeping things consistent is likely to make life easier for both clients and servers because it means fewer special cases.

Thanks,
Rob




Andy



> Isn't the operational datastore the union of the
> applied intended config (config true nodes) plus the config false nodes?

Sort of yes.

What is in <operational> is the "actual operational state in effect in the system".  For configurable items, this is often, but not necessarily, the same as "applied intended config".


>
> Non-NMDA has no concept of "applied" (operational state of config true
> nodes), that is why masked-tags don't go in the module-tags-state
> container. The user can still read the configured masked-tag value on the
> normal non-deprecated module in the non-NMDA case.

On balance, I'm not sure this was the right choice.  I think that it might be easier to include "masked-tags" in module-tags-state, and have it just report the list of tags that have been masked.  I.e. exactly the same meaning as NMDA.

Thanks,
Rob


>
> Thanks,
> Chris.
>
> >
> > Thanks,
> > Rob
> >
> >> -----Original Message-----
> >> From: netmod <netmod-bounces@ietf.org<mailto:netmod-bounces@ietf.org>> On Behalf Of Christian Hopps
> >> Sent: 25 September 2019 17:19
> >> To: netmod@ietf.org<mailto:netmod@ietf.org>
> >> Subject: Re: [netmod] I-D Action:
> >> draft-ietf-netmod-module-tags-09.txt
> >>
> >> This adds the deprecated non-NMDA state module.
> >>
> >> Thanks,
> >> Chris.
> >>
> >>> On Sep 25, 2019, at 12:15 PM, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> wrote:
> >>>
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> >> directories.
> >>> This draft is a work item of the Network Modeling WG of the IETF.
> >>>
> >>>       Title           : YANG Module Tags
> >>>       Authors         : Christian Hopps
> >>>                         Lou Berger
> >>>                         Dean Bogdanovic
> >>>   Filename        : draft-ietf-netmod-module-tags-09.txt
> >>>   Pages           : 18
> >>>   Date            : 2019-09-25
> >>>
> >>> Abstract:
> >>>  This document provides for the association of tags with YANG modules.
> >>>  The expectation is for such tags to be used to help classify and
> >>> organize modules.  A method for defining, reading and writing a
> >>> modules tags is provided.  Tags may be registered and assigned
> >>> during  module definition; assigned by implementations; or
> >>> dynamically  defined and set by users.  This document also provides
> >>> guidance to  future model writers; as such, this document updates
> RFC8407.
> >>>
> >>>
> >>> The IETF datatracker status page for this draft is:
> >>> https://datatracker.ietf.org/doc/draft-ietf-netmod-module-tags/
> >>>
> >>> There are also htmlized versions available at:
> >>> https://tools.ietf.org/html/draft-ietf-netmod-module-tags-09
> >>> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-module-tags-
> >>> 09
> >>>
> >>> A diff from the previous version is available at:
> >>> https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-module-tags-09
> >>>
> >>>
> >>> Please note that it may take a couple of minutes from the time of
> >>> submission until the htmlized version and diff are available at
> >> tools.ietf.org<http://tools.ietf.org>.
> >>>
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>
> >>> _______________________________________________
> >>> netmod mailing list
> >>> netmod@ietf.org<mailto:netmod@ietf.org>
> >>> https://www.ietf.org/mailman/listinfo/netmod
> >>>
> >

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