IETF Logo Mail Archive

[netmod] regarding yang-next

Kent Watsen <kwatsen@juniper.net> Wed, 19 April 2017 19:43 UTC

Return-Path: <kwatsen@juniper.net>
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 D7BB3129526 for <netmod@ietfa.amsl.com>; Wed, 19 Apr 2017 12:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level:
X-Spam-Status: No, score=-2.021 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_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 Sz-daDeq3Abs for <netmod@ietfa.amsl.com>; Wed, 19 Apr 2017 12:43:27 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0109.outbound.protection.outlook.com [104.47.41.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0D9C129C40 for <netmod@ietf.org>; Wed, 19 Apr 2017 12:43:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=MZbQXelm6qfuBF0bW2hTIzgRZd5cZVWNWLi5Wvpmmz0=; b=HNzk67XVBs3RHKoyy9spiBKAlU+j/wRajbPEDkMZ6cT/d84dv/dZyZCYfzGXw+zXHKl8zz6+XWLttPQBFnWNJAODGc04KXCyl6tv5j/cK3Oy/ZJX04ketuVHeVPmGAyWIsPHLXt3lkHG6f+WQBPPXX1xUQo1bNbcIJ85/GxLpKs=
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com (10.160.117.151) by BN3PR0501MB1444.namprd05.prod.outlook.com (10.160.117.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.6; Wed, 19 Apr 2017 19:43:26 +0000
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) by BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) with mapi id 15.01.1047.006; Wed, 19 Apr 2017 19:43:25 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: regarding yang-next
Thread-Index: AQHSuUU1r9YWPr1F8UiDeRS+con7uQ==
Date: Wed, 19 Apr 2017 19:43:25 +0000
Message-ID: <EF629DD3-C94C-4FC4-918A-C950AEADA625@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1444; 7:aAdmzKk+dtBRElSsMjEwHg/L02CX7OwCNDvgRaShWFZTsdMb/ksAFwTLfeJVUOMncC02qq9BU5TfdnW8H+x0BjMrGDdZKKU9bPRCwW98Mmmng9hwDjewGTeEByISld5Da/1u9b94otXxdw3tYYV46vX8Ci+IJJTkspGf+aDjReUiPV/PFhR2vmmYoCtJj9EtH8nbrfwzNeOLmh4W7DRie10LKOQj1wE+QP+pRklwTry6KaEE5KuyXYGw6O14OEnn6VAblZcREyLbh+s5yL4n7Y4zVt8JwrcD+oy3B8REgJbi6o2w/WtZIToP5ChyVCSrFHK+42wTsDbHM4a1K91ymQ==
x-ms-office365-filtering-correlation-id: d488ae5a-cd0b-43f3-6d8c-08d4875c5881
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:BN3PR0501MB1444;
x-microsoft-antispam-prvs: <BN3PR0501MB1444981EFE6DBFBE70937B07A5180@BN3PR0501MB1444.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(6055026)(6041248)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(20161123555025)(20161123564025)(20161123562025)(6072148); SRVR:BN3PR0501MB1444; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0501MB1444;
x-forefront-prvs: 028256169F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39850400002)(39450400003)(39410400002)(39860400002)(39840400002)(39400400002)(4001350100001)(2351001)(83506001)(82746002)(5640700003)(99286003)(6306002)(6512007)(83716003)(66066001)(6436002)(2501003)(6916009)(38730400002)(5660300001)(110136004)(6506006)(77096006)(86362001)(3660700001)(25786009)(53936002)(189998001)(2900100001)(6486002)(50986999)(54356999)(305945005)(33656002)(8676002)(2906002)(1730700003)(81166006)(3280700002)(122556002)(8936002)(6116002)(102836003)(3846002)(7736002)(36756003); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1444; H:BN3PR0501MB1442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <356A55B41B989D4E94E3D72CED1403BD@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Apr 2017 19:43:25.4918 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1444
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/3DQydAf3RufQ1_kEIGVLh7KbpX8>
Subject: [netmod] regarding yang-next
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 19 Apr 2017 19:43:35 -0000

The YANG Next discussion from the Chicago meeting was interesting.  
What I took away from it is that it would be good to find a way 
to update YANG more rapidly, somewhat like code with patches and
branches.

In the end, I viewed this more of an RFC-publishing thing than a
NETMOD thing.  For instance, imagine we have:

  7950 - YANG 1.1
  8xxx - The 'map' statement       (updates 7950)
  8yyy - The 'template' statement  (updates 7950)
  8zzz - The 'inactive' attribute  (updates 7950)
  9999 - YANG 1.2 = Y1.1 + 8xxx + 8yyy + 8zzz

I doubt that the RFC Editor would ever do something as callous as 
that but, still, the takeaway for us, for now at least, is to work
on simple drafts that update 7950 rather than work on a 7950bis.

So that settles the YANG Next discussion for a while.  Please still
use the Yang Next issue tracker when you have ideas for YANG can be
improved:  https://github.com/netmod-wg/yang-next/issues.

Thanks,
Kent // co-chair

v2.23.0 | Report a Bug | By Email