IETF Logo Mail Archive

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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Wed, 04 December 2019 15:14 UTC

Return-Path: <rwilton@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 54BB612081E for <netmod-ver-dt@ietfa.amsl.com>; Wed, 4 Dec 2019 07:14:20 -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=NbTZNQqU; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=CiAWTTZ5
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 R5fiH2Yt86r1 for <netmod-ver-dt@ietfa.amsl.com>; Wed, 4 Dec 2019 07:14:18 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DA6412008C for <netmod-ver-dt@ietf.org>; Wed, 4 Dec 2019 07:14:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15335; q=dns/txt; s=iport; t=1575472458; x=1576682058; h=from:to:subject:date:message-id:mime-version; bh=NdqrwMLkpzK7D4CO0X9NIbNIsj4uAzjQPLXJ8zhnIbM=; b=NbTZNQqU2z/w+opjOBG8liWFUR3LSEmSbnV2IKIK+YQl5sWLd+Ib+qFs e8mghGp+poaja0fYSMYUzpSwXjJ7AQ6Br6QNKX4PfSA6LussQpVg2J226 qZZvasaWgVxucXlEOzUClkFESfO1Bz4bo3YE6JxvxVO4vIjUONkcqsIFO c=;
IronPort-PHdr: 9a23:L7aF0xL5WayM2rCeUtmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeBvad2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXFfkLfr2aCoSF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BsGAANzOdd/5xdJa1lHgFDDIFWgRwvUAVsWCAECyoKh2cDinpOmhWBQoEQA1QJAQEBDAEBLQIBAYRAAoIQJDcGDgIDDQEBBAEBAQIBBQRthTcBC4VrGxMBATgRAYEAJgEEGxqDAYF5TQMuAQKlZQKBOIhggieCfgEBBYUGGIIXCYE2jBcagUE/gViCHoUCARIBIYNAgiyVcCSYOgqCLgOVcpomhD+KC5ojAgQCBAUCDgEBBYFoI2dxcBWDJ1ARFJBZilN0gSiODoEiAYEPAQE
X-IronPort-AV: E=Sophos;i="5.69,277,1571702400"; d="scan'208,217";a="386917525"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Dec 2019 15:14:17 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id xB4FEHie004205 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <netmod-ver-dt@ietf.org>; Wed, 4 Dec 2019 15:14:17 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 4 Dec 2019 09:14:16 -0600
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 4 Dec 2019 10:14:12 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 4 Dec 2019 09:14:12 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jNvscABZjoQHHcs8hVtmFoS8xSuBiFPcy5+iWIfCoUVTW2hlKYBxTiZVWTjQKadQMs3CP3NiDSacZTJXfvmcsrmHoBSwyXhxBP7hN8IFXlSu592Z/IPIDLxKE1DWMdKcvd1rBlkV8i5wliQkPgMrY1wmDfdNTgMyF2VuiMZOFAzRM6HW0UGwLZRlFOY23xeXYfnjQMkb/Hn2aKSmvvYAbE+5z1iuaogmEvjVc9ppaJkRNDsPRmrPFTJA+JKi2LzWLlUxRdwwejCM9Q80ch1Z2zbV4GJ7bOcBzmmP5c6Ab2y+3a6SFWIsF9sjJ/glmcERiLrLprGNPc6j2/4tI4F80Q==
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=PJ5rOXKbxyPLWVL1mc1B6gECA3zAerDF60WP8+qp2Pg=; b=CPLH2siIAPjU6h+MZr5X1DmU5jmtE3ksZtY2bRH97wx/RsgYKbLX+/8d7NErkgrTNtYQ1+/jM9GehCBJtKzeSfdukKe/O5K4EF3FGHRc1min0I9IIupozwO2boQLVLMedOb66g6pQtjCJ0iwiHdEHL5zi8VLolGlTBlrgFTlwtUIDtqOJjbVC2hSWNZJSsQYOPToWYEDwtkLHoPb8eKGElTA21cfKmzAsqsgcP2TxxpHxESO3+vp+Y3fhpBqpPMofzFZI75OFXGIJCU2FNYQ+2/9x7FeApCQobMAOLYPsdJzshyZ4DW0+TEodkPRB5IBMcJgsMYAS/pIwK7zvNjhUA==
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=PJ5rOXKbxyPLWVL1mc1B6gECA3zAerDF60WP8+qp2Pg=; b=CiAWTTZ50KBWqhQwGTO7Xg3RvOthsEUpKmVxTuVnJyi//ipuNGwkGsarwIymApaAS0tdV4r+EmzcsBSDma27x4EAzmBGUZveIjx3woPBEvZfn3PJPC5C6cRR6vZwjjmdNysN8FJGUuVMNy84cBhnR4Rk109xtmoQcZOtBJnnkYU=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB4367.namprd11.prod.outlook.com (52.135.37.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.13; Wed, 4 Dec 2019 15:14:11 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::8106:b538:2920:a44f]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::8106:b538:2920:a44f%5]) with mapi id 15.20.2495.014; Wed, 4 Dec 2019 15:14:11 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: "netmod-ver-dt@ietf.org" <netmod-ver-dt@ietf.org>
Thread-Topic: Tomorrows meeting - I can only make first half
Thread-Index: AdWqsM8xmWJ02jV4QWSKx0EFx63KKg==
Date: Wed, 04 Dec 2019 15:14:11 +0000
Message-ID: <MN2PR11MB4366F8CDAE3126A13986C229B55D0@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.55]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fda9e5c6-9387-4eab-9db1-08d778cc9df5
x-ms-traffictypediagnostic: MN2PR11MB4367:
x-microsoft-antispam-prvs: <MN2PR11MB436766B99DF6F983C44052EEB55D0@MN2PR11MB4367.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0241D5F98C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(376002)(396003)(366004)(136003)(39860400002)(199004)(189003)(8936002)(2501003)(5640700003)(86362001)(3846002)(33656002)(478600001)(2351001)(7696005)(6436002)(26005)(6116002)(790700001)(99286004)(102836004)(25786009)(6916009)(6506007)(64756008)(54896002)(9686003)(74316002)(8676002)(55016002)(6306002)(14454004)(71200400001)(81166006)(7736002)(81156014)(2906002)(5660300002)(186003)(316002)(66446008)(66476007)(66556008)(71190400001)(76116006)(66946007)(52536014); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4367; 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: TBpKMxLXEgg1jhzlskh+UzhPLMiPR0qaPFYXCaaLNFK8hPBptsHQVCVlUMGaKjGlp0bqvWNa6X0aCNlrEAzHSLo8gRBMVdrHAf5BgLr/QCjSJ4rzSwTUaCYQn+dYCgbQt/d7d38ltJcwdCPPxVIU1AqUuU6RXCCCmqOQmbj65R3BTMkTodiV7SxDuE1n3ZfUSCWlAyeOu6fcOIY5nwk3SFcI+9CW56Kfv8C5+6opA3wiVLiLqOEGTbZhgi2PCffnW+xHvZUeSHGULoSqC5QrIz/ybFzqGXH73FeHjYCZFO2DIc4lONjP2kapw+3nTP255XqyhV6bYLaQZJI8RjFSQFs6RxTqe5yqrbJEcuQw3fTpdKMPoZiiUJmGGCjA3ktFMPRRIiJ75Dur+FrmRiEYtbx2pxpj1Dd0lPNg74p87YCkYiSQk5MlMTMwfLaUFFU9
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB4366F8CDAE3126A13986C229B55D0MN2PR11MB4366namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: fda9e5c6-9387-4eab-9db1-08d778cc9df5
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Dec 2019 15:14:11.3986 (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: DTQu3rbZhiZMoVyux//49ISfMsGbpZJ+72dMkOsgYZfyN10ErfPUW+PYK49KHWtz9DDK+/HHpvtyECu4noHZRw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4367
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod-ver-dt/Do1FX_Zzh0u5K7AHn7horDGutPw>
Subject: [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: Wed, 04 Dec 2019 15:14:20 -0000

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