IETF Logo Mail Archive

Re: [Netmod-ver-dt] Tomorrows meeting - I can only make first half

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Thu, 05 December 2019 03:03 UTC

Return-Path: <rrahman@cisco.com>
X-Original-To: netmod-ver-dt@ietfa.amsl.com
Delivered-To: netmod-ver-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC33F12022D for <netmod-ver-dt@ietfa.amsl.com>; Wed, 4 Dec 2019 19:03:44 -0800 (PST)
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=VcBjlJ1B; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=E/oL5tWo
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 Ntl_EZgQZo1S for <netmod-ver-dt@ietfa.amsl.com>; Wed, 4 Dec 2019 19:03:42 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 789A9120133 for <netmod-ver-dt@ietf.org>; Wed, 4 Dec 2019 19:03:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15075; q=dns/txt; s=iport; t=1575515022; x=1576724622; h=from:to:subject:date:message-id:mime-version; bh=zC/W1e6vDecZOeDGwl028x5oFhDO2MlpKse2n4vUshw=; b=VcBjlJ1BYJJCpyFIbJraJAh/SgQaAWT9BFE6aiN2Ay8t02JuQlQF9n4l 4xhmD1+I1JOTm5CxEEZWbD51KSY5C0mZQKlNjVdb5ksUoK+KrJJwV8xG7 PsqLwW48LEss6uL3QOIs+Bl0RV0zJFtJDadJKdo5X/i9mnjwCHXF+2m6t c=;
X-IPAS-Result: A0BXFgCpcuhd/5JdJa1lHgELHIFzC4EcL1AFbFggBAsqhCuDRgOKe06CEZMihGKBLhSBEANUCQEBAQwBAS0CAQGEQBmBeSQ2Bw4CAwEBAQMCAwIBAQQBAQECAQUEbYU3DIVSAQMDEhEdAQE4EQEIEQMBAh4NAgQwHQoEARIigwABgXlNAy4BpUMCgTiIYHWBMoJ+AQEFgkqCPhiCFwmBNowXGoFBP4E4IIIeLj6EFgESAT+CcDKCLJAhhU8kiSePEwqCLpVaG5omhD+KC5ojAgQCBAUCDgEBBYFZBytncXAVZQGCQVARFIxmg3OKU3SBKI4OgjIBAQ
IronPort-PHdr: 9a23:nT6bkxzBNiMqEjbXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhSN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZufE0T7KffsRyc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.69,164,1571702400"; d="scan'208,217";a="395607278"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Dec 2019 03:03:41 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id xB533evk009133 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <netmod-ver-dt@ietf.org>; Thu, 5 Dec 2019 03:03:41 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 4 Dec 2019 21:03:40 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 4 Dec 2019 21:03:39 -0600
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 4 Dec 2019 22:03:39 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Zt/UamRaCWGXdInIDqjNVLt7H7kftDMejsS7VD/wkcKM+2rQ/za9pXx1Y27Ik7csK+NxYuMgE99sZwaq1BxJzmU2SrfXhp8Ws7o/iRBOA0xibZugmkhLpkeX7h6Iqo8aUchnMzGrRTaUH/gjX3YKUrzEkDHJ0cLygFU06wLWVsCMpgL0W0Y58VuBTFhdQA9pLq4MhyDVEq3qDxaIdW3q2ez+lOpTB16xbGemJlK+QL0VgLiRiejVzcIfGnhhWalwufTW/6Jbem+M6oBHaQuxAISGOpD5Xp5yMpib3kDRqKLAYcGsR1oZPOGQEmhll01de7pVwb4vGz6uEb80yark2g==
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=zC/W1e6vDecZOeDGwl028x5oFhDO2MlpKse2n4vUshw=; b=PEWZAlVXIraOSb82UUOxgtfg8SjGKB1fPJamadIrsrF0Jme3bWEZ+rXU1ehw0CjIzy+zBuYTLdEwmlqHIllvJ7/PgiPqelCrsm6qC4btT+vmv13KMswgLTldz8U2tYYlCpLGobMZGNlXKCstcEiCMexENlzomTFfwK8pxtajdr7Aky+eV+ysyPHnZJS852F+RvnhmchTRy4CSDdCO68tsPNvabd4QrEpikK/OZwxipPdsQp19uVeummHaYAXGjl5kNNVz8t8n28YbtlnzpALg3sVpFVb16PGGxfusm+edMtza+kA5FYzlAwnSaQMwHUrfA8CuuyLHi4Hrr6hXVkl6A==
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=zC/W1e6vDecZOeDGwl028x5oFhDO2MlpKse2n4vUshw=; b=E/oL5tWovPLFXcQzzpE3WKQDzlJHvs73PrMysi5thL8b6A+ZCB6ISUpOkqO80z36eHv0Rr+G+W5aVzDAz6cpBX3HfOqIyOEzOjHJalWTM7BnBcvntkzzP52RMC8JPVPpeJBDGjMWXcnaNPaQG9s+lRHusBGY5ftr5KoPsMWwD+k=
Received: from MN2PR11MB4157.namprd11.prod.outlook.com (10.255.181.213) by MN2PR11MB3662.namprd11.prod.outlook.com (20.178.251.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.22; Thu, 5 Dec 2019 03:03:39 +0000
Received: from MN2PR11MB4157.namprd11.prod.outlook.com ([fe80::f030:6ed6:391f:e3eb]) by MN2PR11MB4157.namprd11.prod.outlook.com ([fe80::f030:6ed6:391f:e3eb%5]) with mapi id 15.20.2516.014; Thu, 5 Dec 2019 03:03:39 +0000
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>, "netmod-ver-dt@ietf.org" <netmod-ver-dt@ietf.org>
Thread-Topic: [Netmod-ver-dt] Tomorrows meeting - I can only make first half
Thread-Index: AQHVqxiXUFR/fnOlgUusAdurhw6izw==
Date: Thu, 05 Dec 2019 03:03:39 +0000
Message-ID: <FBBABA60-3FC9-44AF-B37F-3F5D4465EA56@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rrahman@cisco.com;
x-originating-ip: [2001:420:c0cc:1006::6b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ebc43a16-2790-4b52-0361-08d7792fba51
x-ms-traffictypediagnostic: MN2PR11MB3662:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <MN2PR11MB3662BF51010E54F6E6DFDDB1AB5C0@MN2PR11MB3662.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 02426D11FE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(366004)(136003)(396003)(346002)(39860400002)(199004)(189003)(71200400001)(71190400001)(6246003)(229853002)(6486002)(54896002)(6306002)(53546011)(6506007)(186003)(5660300002)(91956017)(99286004)(76116006)(8936002)(2616005)(6512007)(7736002)(66556008)(66946007)(81166006)(81156014)(8676002)(102836004)(6436002)(66476007)(64756008)(66446008)(316002)(6116002)(2501003)(110136005)(58126008)(2906002)(25786009)(478600001)(36756003)(14454004)(33656002)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3662; H:MN2PR11MB4157.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: DfJYWuOd4WDjDBdbNijSThNzP8rS2+F2MBdXZfC7ZDdr8AA95VVgVxIYjURwWihCofz38e5110Lf5MtpcusZuBwSH6ctnrBVuokTTRUKik5iM9lkSpdQZDmy6SsjFqb0jPOy6+MzbE3MlFxKY7/W4RMbeX+LeVLXZGHxFolUbisHO81o8X5f9HB6IfWGMX+Y05CDZ4y2y9u51uboWGKnAneDpG8QUr5uU69CuMpRMQ35Myc3kD8xs0asZh5Lx8TrdcLN6XwFx2VjJezu8hqdPL0+iH7yhEt/42hk57LWOfFyGdmaPcnCEKBTtA0smXNWz4GDgB7g/7AMcmHADI5wuLWmSYpiVKcz4ClFvSdbuGbtGBo2HsT1Wtm98OlA+HbLW6OX3p+Vo5YexZYXYeOlKTK3HolcIj7BL0NCMioOE0Mu5T4DqMq3XZDOLKUDEJfl
Content-Type: multipart/alternative; boundary="_000_FBBABA603FC944AFB37F3F5D4465EA56ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ebc43a16-2790-4b52-0361-08d7792fba51
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Dec 2019 03:03:39.0960 (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: NZliY3x0P8nnYMGXkqUMUi9FwT77KW+3uesTSpaVD2Hw2kVP9PxW0DGjxdcgL5oFmU+4tuA5L8nWoLY12aCC7g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3662
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.24, xch-rcd-014.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod-ver-dt/YdRv8xUuKomA8nP7sWYMyj-uGT4>
Subject: Re: [Netmod-ver-dt] Tomorrows meeting - I can only make first half
X-BeenThere: netmod-ver-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NetMod WG YANG Model Versioning Design Team <netmod-ver-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod-ver-dt/>
List-Post: <mailto:netmod-ver-dt@ietf.org>
List-Help: <mailto:netmod-ver-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Dec 2019 03:03:45 -0000

I’m also squeezed for time this Thursday. Ok with a plan, we’ll probably have time just for the YANG version selection discussion.

Regards,
Reshad.

From: Netmod-ver-dt <netmod-ver-dt-bounces@ietf.org> on behalf of "Rob Wilton (rwilton)" <rwilton@cisco.com>
Date: Wednesday, December 4, 2019 at 10:14 AM
To: "netmod-ver-dt@ietf.org" <netmod-ver-dt@ietf.org>
Subject: [Netmod-ver-dt] Tomorrows meeting - I can only make first half

Regarding tomorrows YANG versioning meeting, I can only make the first half an hour, but happy for folks to continue discussions afterwards.

I would suggest that we focus the discussion primarily on the email that I sent out yesterday.  Hopefully looking for progress on the following questions:

A) Yang Version Selection:

  1.  Does the YANG that I proposed for version selection look along the right lines?  Do we think that it is simpler?
  2.  For custom packages, what fields should we allow to be configured (e.g. just a minimal subset, or everything that could be valid)?  Should clients be allowed to select features?
  3.  What allowed modes of version selection do we want to sanction?  Does the current use of capabilities give too much flexibility?
  4.  Is using <pkg-name@version> okay as a schema identifier in RESTCONF?  Would the name need to be encoded beforehand?  Or do we want to force the client to configure a simpler name?

B) For YANG packages:

  1.  Is a revision date a valid version identifier for a package?
  2.  Is having a pkg-identifier (i.e. pkg-name@version) better than separate name and version leaves?  Is it right to have different naming conventions for packages within a file vs on the device?  How far do we go - do we try and apply this convention to identifying modules as well?

C) Discussion on whether features should be allowed to remove nodes when they are enabled - YANG 1.1 does currently allow this - but I’m suggesting that this is bad practice.

Thanks,
Rob

v2.23.0 | Report a Bug | By Email