Re: [netmod] YANG next

"Rob Wilton (rwilton)" <rwilton@cisco.com> Tue, 23 July 2019 21:51 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 B536F1209BF for <netmod@ietfa.amsl.com>; Tue, 23 Jul 2019 14:51:00 -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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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=EA1rumKg; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ORkv6sTp
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 3toDvb0guusm for <netmod@ietfa.amsl.com>; Tue, 23 Jul 2019 14:50:58 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B2571209C0 for <netmod@ietf.org>; Tue, 23 Jul 2019 14:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1791; q=dns/txt; s=iport; t=1563918658; x=1565128258; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=2C0V33HDYgpsyFNnBmxDSsn8FVFqIHHBicpxvYGPrfY=; b=EA1rumKghwLFtjFbq5AqqrLULBJO/RLNt47UcjOlubModkuidYPaV65b 2NsW7Ec3GouysNgIZzDSEd7BYonS0vrB40lZ6yxQJJK03u48BqBNo+1d5 oaFggxw7YsHsGJoVVzvTtpsyJHm3vFT2alOU1TOQpekVmWC7ITZT/npZf Q=;
IronPort-PHdr: 9a23:H2bbkB80GjFBVf9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVdSaCEnnK/jCZC0hF8MEX1hgrDm2
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BzAABAgDdd/5JdJa1mHAEBAQQBAQcEAQGBVAYBAQsBgUNQA21VIAQLKodkA41/TIIPl1CBLoEkA1QJAQEBDAEBGAsKAgEBg3pGAoJOIzUIDgEDAQEEAQECAQZthR4MhUoBAQEBAwEBECgGAQEsBgYLBAIBCBEEAQEfECcLHQgCBAESCBqDAYFqAx0BAgyfdQKBOIhggiOCeQEBBYULGIITAwaBNAGLXheBQD+BEUaCTD6CYQEBgWODO4ImqmcJAoIZlCeYCo01l1ACBAIEBQIOAQEFgVEBNiqBLnAVO4JsgkKDcYUUhT9ygSmOJAEB
X-IronPort-AV: E=Sophos;i="5.64,300,1559520000"; d="scan'208";a="597981397"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Jul 2019 21:50:57 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x6NLovDD009867 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 23 Jul 2019 21:50:57 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 23 Jul 2019 16:50:56 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 23 Jul 2019 16:50:55 -0500
Received: from NAM03-DM3-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; Tue, 23 Jul 2019 16:50:55 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Czz/SlfCNwcSKQvX17z17pAVo9MsWwBsEkZ7W3UBEcH4vCT2Vv407sFivFRJl+5spscN7IjbIQoOhHzotULDVoF2kh977hX42B7nMzC1UO6FdJWA6gCNxsnnDcc0P7f7KAK2DG7fTkEE95K3vyxotPAqK83DsSJ7x0f4MUVgH8pTf9TrwmiOIGO3OmjRh1mNwQNbvIE5JdBgYPh+jvwa10Vsh0RIz5nGnDZzkqztsgtNq0eJwxFXNawOeUEzNACBfDCruTZZHVCgaXMH+O1v5QUvHx2ENya4uIBxGvKP2roTpHCu7tzWV1Z4kIC1zzWASFAwLWcBhzeT2/vWvMU6kA==
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=2C0V33HDYgpsyFNnBmxDSsn8FVFqIHHBicpxvYGPrfY=; b=gtHdYYQU2k7yeep2/svXsqlxSBpb02oh2y+xLKTejO2ov0OpxatZ4fZLFG3vA4oaDkfHDhpszUvdcuPlzpTuSSpEez+nz7v42Jr60w5Tr7wyWOYGwNLN/rN8Rz+5GjmpLpCJhnw9Z1BQemPDsy3+QsLnPeKp6XKp6QvLTE3w2M7sD+piR0RT6t5rT+q4My0g3Hc/HH7Jkr1xMZnYG9eTQsnoQeTMnSb55xiqJcQO2oENlFfcCPdypXcd/GBumFW2g+dXh/R09YPu5bam/yWKK8ca+WwrnKckOPCqXX6/NQY5M5Hzyni7G57+WOifyMvWqxkoE88Ak+eTOXmz7AxO0g==
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=2C0V33HDYgpsyFNnBmxDSsn8FVFqIHHBicpxvYGPrfY=; b=ORkv6sTp/3jk7m86zTugVNHRLPYknUlogW9C/a2I4gscfSA7AdPAq/wOn4uBC9g57tDKRMOTrXJQbMRUhnEsB9X1o7KTh+st3hMyV71RsIv+RZKqLJ5rlEkfEnbzmy4pjDte/VJg7ty1WdC5tICt9ZLYMXpXMD0pcQSfwcg52ZE=
Received: from BYAPR11MB2631.namprd11.prod.outlook.com (52.135.227.28) by BYAPR11MB2534.namprd11.prod.outlook.com (52.135.226.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.16; Tue, 23 Jul 2019 21:50:54 +0000
Received: from BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::91da:1669:aaf0:d428]) by BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::91da:1669:aaf0:d428%4]) with mapi id 15.20.2094.013; Tue, 23 Jul 2019 21:50:54 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Ladislav Lhotka <lhotka@nic.cz>, NETMOD WG <netmod@ietf.org>
Thread-Topic: [netmod] YANG next
Thread-Index: AQHVQXBQtjURL141VkWQZDrJ7b+rTKbYva+w
Date: Tue, 23 Jul 2019 21:50:54 +0000
Message-ID: <BYAPR11MB2631B637E464FDFF99A38915B5C70@BYAPR11MB2631.namprd11.prod.outlook.com>
References: <ff5d90b51872df190abb226cb10d51a635e88521.camel@nic.cz>
In-Reply-To: <ff5d90b51872df190abb226cb10d51a635e88521.camel@nic.cz>
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: [2001:420:c0c8:1002::367]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 085ba61a-f9c3-4da6-23ad-08d70fb7d65b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB2534;
x-ms-traffictypediagnostic: BYAPR11MB2534:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BYAPR11MB2534394D584C7E2761B8F6ABB5C70@BYAPR11MB2534.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0107098B6C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(366004)(396003)(346002)(39860400002)(189003)(51444003)(199004)(13464003)(86362001)(55016002)(6436002)(2906002)(81166006)(9686003)(6246003)(33656002)(6306002)(68736007)(6116002)(81156014)(53936002)(8936002)(71200400001)(71190400001)(5660300002)(14454004)(229853002)(7696005)(76116006)(110136005)(478600001)(446003)(64756008)(66556008)(66476007)(316002)(76176011)(966005)(7736002)(256004)(25786009)(476003)(66946007)(11346002)(52536014)(486006)(102836004)(46003)(305945005)(8676002)(74316002)(6506007)(53546011)(99286004)(66446008)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2534; H:BYAPR11MB2631.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-message-info: kkPBT3tzsWq5vWInR5xH2V5O99jBc+JJLPfmrSw2PfT4CyOsPGZSZE0cD42TASkMD7C0VA/Qd5ckeODV7uiOLiFAGhib7wMaAD2Fb00PYUMywLrR2XQIsB3G0ue65PiG7YNfgsiAV6RlxZeE1wvMCocbXs5Y1QEUVY/ga35e+x6Zd/7C/FWY3e+N8qNubcjjf13QIxs9meeWiyUmJ7aMIMEo6rVseAFFQd6zXX2ZXOu+n84SCssSY90MrwzkNjBpYvjXrrILm1KTdRHnLmS7KnKVQpdjLKZzYk/8/2Y9oPBQ8wqv+Mo95EnC51/vGEx0R1zDtlZy3kVCQvfADTzVIs1LX9xETVNgmXrWdRUAaHA5nkhvYA7VbZ1fyFpKQEctQbyb5XrA5/nKgF1CDeiJCHuneLekY9TpUGHmhPOYjgM=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 085ba61a-f9c3-4da6-23ad-08d70fb7d65b
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jul 2019 21:50:54.4334 (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: rwilton@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2534
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.16, xch-rcd-006.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/M1dYaXVcnp3JT29wznRtpaRl2TM>
Subject: Re: [netmod] YANG next
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: Tue, 23 Jul 2019 21:51:12 -0000

Hi Lada,

I still think that it makes sense to do YANG Next, on the assumption that it will take a couple of years to work out, maybe longer if the work doesn't properly get started until the YANG versioning work has progressed further.

When I look at the YANG Next issue list, I think that there are quite a lot of things on that list (some of which are quite small) that would be good to do, and will help modelling efforts.

Thanks,
Rob


-----Original Message-----
From: netmod <netmod-bounces@ietf.org> On Behalf Of Ladislav Lhotka
Sent: 23 July 2019 12:03
To: NETMOD WG <netmod@ietf.org>
Subject: [netmod] YANG next

Hi,

this morning I attended the side meeting "Next Step of IETF YANG". I was somewhat misled into thinking that it would be about future evolution of YANG the language, which was not the case at all. However, my personal conclusion from the meeting is that it would be a total disaster to throw in a new version of YANG within the next few years or so.

The operators and equipment vendors are busy putting together YANG modules and tools, filling the gaps, coping with NMDA, schema mount, IETF versus OpenConfig etc. A new YANG version (and modules written in it) would IMO be extremely counter-productive at this rather turbulent stage.

So, if we want to continue the yang-next discussion, I think we first have to figure out how to evolve YANG without making waves in the current YANG pond and let the operators and vendors do their work, without which YANG can never succeed.

Lada

--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

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