[netmod] References to the "tags" typedef

"Rob Wilton (rwilton)" <rwilton@cisco.com> Thu, 03 October 2019 09:38 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 8490F12010C for <netmod@ietfa.amsl.com>; Thu, 3 Oct 2019 02:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=SD9RNFQQ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=kxXR9wjl
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 RPDSIsuLyLHu for <netmod@ietfa.amsl.com>; Thu, 3 Oct 2019 02:38:01 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1614A1200C5 for <netmod@ietf.org>; Thu, 3 Oct 2019 02:38:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4229; q=dns/txt; s=iport; t=1570095481; x=1571305081; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=OjA8cArRYpXjPhs8VeZlWw7UuwyPwibd/J/K+JJPNHk=; b=SD9RNFQQr/Cebsexy15Dvmq3p0lKAkZGx+CX7wHanr4Rty2TOWR0TJBo wsF6upUzYTe3j1uB5TUhmsN8Vk0ylnhiCqg5qhMSdVg3LRVBTwzia1PcW f49EGTXE6RxtJ+sQGb1CuoKFpOnv/Ygf65A3/y5ht18k3qBzwrOyXZFSO c=;
IronPort-PHdr: 9a23:/+GdnxfjJhvNUfGe1LcxutFolGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGRD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/dTM7GNhFUndu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALAAAXwZVd/5RdJa1mGgEBAQEBAgEBAQEMAgEBAQGBUwUBAQEBCwGBSlADbVYgBAsqCodfA4RYhWtNgg+XeIEugSQDVAkBAQEMAQEYCwoCAQGDe0UCgkMjNAkOAgMJAQEEAQEBAgEFBG2FLQyFSwEBAQECAgEQKAYBASwGBgQHBgEWAwQBAQEeNwsdCQEEARIIGoMBgWoDDg8BAgyjVAKBOIhhgieCfQEBBYE4Ag5Bgn0YghcJgTQBjA0YgUA/gRFGgkyDHwEBAgEBFoFJgz2CJpVDl3gKgiMDhwWOK4I5coZcjzeOKogfkRECBAIEBQIOAQEFgVI5gVhwFRohgmwJRxAUgU+Dc4UUhT90gSmOTwGBIgEB
X-IronPort-AV: E=Sophos;i="5.67,251,1566864000"; d="scan'208";a="643702133"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Oct 2019 09:37:59 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x939bxmK017794 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 3 Oct 2019 09:37:59 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 3 Oct 2019 04:37:59 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 3 Oct 2019 04:37:58 -0500
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 3 Oct 2019 05:37:58 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=g3LbZA47N/qtnkPLkm3oViHaRPckeJYJ0Y9pLYVDfbxN1uGX5X4aj0j4ShkfFpiSocVLolIakJ7vMbH6vMX/eHMUhrlXVwS3tAXWhPEDnUWC24rhAXxtcw4362JB8lvClgTSwcVKrw2pM+B2a3+sGrAMQX56A+ppPvGniDeqpi/EbnmFf+Rdwj5BjFWumuyiDnL4Yk14vyEjxzP7vSaL63Z/r0hrtfVP6xobGhxSHBHXt9Sda0MAlNJB5bAR85IlEhhlO7EDbAgVxyRIcl+fjedOBAoO7Vs5VxDWcbz/4bbCj5cQ51JtAa2H2MRAVM/kkzzN0vZzd10ypc/WjNhqFA==
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=V/MGsHywwrJBVf4rhrOjFzSfNWQzLB6QwbnDxh3Aodc=; b=mbFxiLmnrY9dbMlRHE6B5UBgN/X1/G9UDNTYFakrkwQfx+8ILbYSFxuvCbDOXtG1q41AuZyCPtQgBhb2uVRkGVHhH9PmJ++cmf7WZnYR4xcrOD0GBB4qW0HasAxeQ23gytzCAre1rA/fkVBUD54NpsuEma9ZDOFJsM4uBf06SnfuPoeAZGxYSqyDcYS9wHBMZlmtLXf21s/5B8w72t+UkxFcwBZh+Y4a0Sdm1DsDpZSGuCrRJi/EdJCYZwhZXKsvduvWW9WgF75up1ZpF8SbZ9IjRscxc8ifrfpi1fBR8wpavm4dvGHK81tIE4Qd+FUcCcuSOg9a81NfLT9XYMHsSA==
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=V/MGsHywwrJBVf4rhrOjFzSfNWQzLB6QwbnDxh3Aodc=; b=kxXR9wjlUuoQTRTL1p6vTLXdXQq8krN6czANL5VL/1qZmFSAz5CcHKpP+Ua3f4uJN9ufIaWDVXaQJwuQxJ6AlOlpwqowdK2aBcHGqWA6MiotBThaMEIXijwJhq9vTJd17Ns8DRbQPB5Z4Xez2qs1mezD6YTEeAjb7AFHp0XWsPE=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB4256.namprd11.prod.outlook.com (52.135.36.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.20; Thu, 3 Oct 2019 09:37:57 +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; Thu, 3 Oct 2019 09:37:57 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Christian Hopps <chopps@chopps.org>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: References to the "tags" typedef
Thread-Index: AdV5zjrR87+ocsTFRHuyDJWUSmakTQ==
Date: Thu, 03 Oct 2019 09:37:57 +0000
Message-ID: <MN2PR11MB4366172C3044D238A5BE7C30B59F0@MN2PR11MB4366.namprd11.prod.outlook.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.43]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 294650ba-d1b1-4441-11a4-08d747e55f95
x-ms-traffictypediagnostic: MN2PR11MB4256:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <MN2PR11MB425610D748C5B0022DF26D8CB59F0@MN2PR11MB4256.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01792087B6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(376002)(346002)(396003)(39860400002)(199004)(189003)(51444003)(13464003)(486006)(305945005)(7736002)(26005)(186003)(33656002)(316002)(256004)(74316002)(5660300002)(478600001)(81156014)(81166006)(66066001)(66946007)(66476007)(66556008)(66446008)(64756008)(76116006)(8936002)(8676002)(966005)(102836004)(14454004)(99286004)(52536014)(53546011)(66574012)(3846002)(6116002)(2906002)(110136005)(7696005)(25786009)(71190400001)(71200400001)(55016002)(2501003)(9686003)(86362001)(6306002)(6436002)(476003)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4256; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: 0PmuJlsN4Tn/KqDn+vJYPvWXKDnYqsEwuEV+DNDupdcWCEM2chyELroLnulRvbGl0poba4h8o+cz2mzR7GOrV8x1MRdwDDdU3ogmkhb+zfsOzdBLZ4QgC8FVksARQBiyATRQ9B8xA7C6DnUF5l1Jo75E5qzXukH08eoxXalMRZy3/3otwIpKwKu2H96IS05IH59Mh/jr3V8TcyS0PheNOpbYi+HVhCUEVFNCHKbJoVTgvrCUAcA+PP2cufwSeMKgGmLJs89Z798uV+2+C+qUHcBu/sMROLyVMjWJaNMibRYYGvK4RTt2S5O6RSJNM68u86YuE1yB7PjbaoUB3LTutircFRJFg1F9ox0T0JbhilqJIzxqBtPKh2TQDPDYFCN7hTRvDYchElguyAUofNNuCpZpcKxE6wAEB3vai30fmpje2dViGCLLcWvFJSNFMLFWgow6GdXDAsXp8BiuuB9v2w==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 294650ba-d1b1-4441-11a4-08d747e55f95
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Oct 2019 09:37:57.0853 (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: AKMTiHQx5sqhoecJukuXwiOQmYqi7+51fd5d6TxCGzcHL1iAe+64C93QlZPc7YyUsx6ELQ5xRYMkeTklyTIesQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4256
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/VYwlvItKibZ-gHUugd-OYmdGl5E>
Subject: [netmod] References to the "tags" typedef
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: Thu, 03 Oct 2019 09:38:04 -0000

Hi Chris,

I know that this is late, but ...

The YANG packages draft (https://tools.ietf.org/html/draft-rwilton-netmod-yang-packages-01, but an updated version will be posted soon), is currently using the module-tags typedef to allow a package definition to contain a list of tags.

E.g. 
module: ietf-yang-package
       +--ro yang-package
          +--ro name                      yang:yang-identifier
          +--ro version                   yang-sem-ver
          +--ro revision-date?            yanglib:revision-identifier
          +--ro location*                 inet:uri
          +--ro description?              string
          +--ro reference?                string
          +--ro previous-version?         yang-sem-ver
          +--ro tag*                      tags:tag
          +--ro referentially-complete?   Boolean
          ...

This package definition goes into an instance data document, for which the schema should just be ietf-yang-package, but by it importing ietf-module-tags.yang, it effectively also pulls in the "container module-tags" into the schema for the package definition, that I don't think should be there.

If we keep package tags, then I think that there are two ways to fix this:

(1) Split ietf-module-tags into an ietf-module-tags-types.yang and a ietf-module-tags.yang.  But it would be very late to do this, and the packages draft isn't even a workgroup document at this stage.

(2) Have the package draft define its own "package tag" typedef, and not have an import reference on module-tags at all.  Probably if we do keep package tags, then we should also consider a mechanism by which they can be updated on a device equivalently to module tags.

I'm currently thinking that the second choice might be a better approach at this time, but wanted to check whether you or the WG had an opinion.

Thanks,
Rob



> -----Original Message-----
> From: netmod <netmod-bounces@ietf.org> On Behalf Of Christian Hopps
> Sent: 25 September 2019 17:19
> To: 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 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.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> >