IETF Logo Mail Archive

Re: [netmod] OpsState Direction Impact on Recommended IETF YANG Model Structure

Kent Watsen <kwatsen@juniper.net> Mon, 25 July 2016 20:03 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 DE2C312D0C0 for <netmod@ietfa.amsl.com>; Mon, 25 Jul 2016 13:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.com
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 sHmsqy7f0jvi for <netmod@ietfa.amsl.com>; Mon, 25 Jul 2016 13:03:46 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0129.outbound.protection.outlook.com [104.47.41.129]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D416912D1AE for <netmod@ietf.org>; Mon, 25 Jul 2016 13:03:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Ssw/VqHb3O8+ya+NyozkuzNIej9qyse7kRhmbinemec=; b=i8WPZfCk3K3fksjYP4sq6kYWPZmjuWRZznwDHnRpaiSwoNZfK17oZiPAmcNWxm0tYxP//ccMdWwK5eh6Ui9VHxP2ofPsHFPt+XJdZ29pDMytNk2CEY/yr0I9WgWRwl8Ru9atnEgQNRj3i9uyblFeQ2DOCHEgDL2rDDZnLbny0gg=
Received: from CY1PR0501MB1450.namprd05.prod.outlook.com (10.160.149.11) by CY1PR0501MB1450.namprd05.prod.outlook.com (10.160.149.11) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.557.8; Mon, 25 Jul 2016 20:03:41 +0000
Received: from CY1PR0501MB1450.namprd05.prod.outlook.com ([10.160.149.11]) by CY1PR0501MB1450.namprd05.prod.outlook.com ([10.160.149.11]) with mapi id 15.01.0557.009; Mon, 25 Jul 2016 20:03:41 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: netmod WG <netmod@ietf.org>
Thread-Topic: [netmod] OpsState Direction Impact on Recommended IETF YANG Model Structure
Thread-Index: AQHR426Bbp8QhQYR/0+rHOW0oBTwuqAjJxmAgADv8QCABT5TAA==
Date: Mon, 25 Jul 2016 20:03:41 +0000
Message-ID: <DCB3EBBF-5EB1-4C8E-AA55-F59C4B5A8E4D@juniper.net>
References: <D3A935F0.6A4DC%acee@cisco.com> <eb15fd23-2c0a-50c4-1ebc-7c0e4867dfd8@cisco.com> <20160721174033.GB54646@elstar.local> <d18f5dd0-64d0-e223-88a9-faa4df4b7866@cisco.com>
In-Reply-To: <d18f5dd0-64d0-e223-88a9-faa4df4b7866@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.18.0.160709
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kwatsen@juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.10]
x-ms-office365-filtering-correlation-id: 2cb24ff3-b719-45a9-6b18-08d3b4c6c69c
x-microsoft-exchange-diagnostics: 1; CY1PR0501MB1450; 6:+Q+WKsoMaQ78Gj5j1Joe0OdHoBAth7+7kz4lUKesBPxuSAJebhfCthrVn/ZlocJPsrEn2qbIF5CndqDBKHzbcbb1UNbIhBu7LF/fKCnW9IL6sUoucUpPYgCTWmREtTiPVbHqVVu8zpQtuP3zdyTpOrZb3LlYXkm4l9WnFJBFr3cz7VIvqwcUupbR+i26fewCVkR3qE3pVvDGueEu8gWS+4H/wBQErJJuFav1Xl2FdotoacgJ38uPu52m0FpxTNS7GJs80eMjFNX4f4ZAnPyPN3wjRTyeLqXGMqSakxgL/t7sL/LF3OxUK+Ph40I3rwCd/+oQD3p9mq1tujv2FQsERQ==; 5:Osu66zV6IEX7do/xKOs8zPVb7URwab3/BDVvcKhVJlIU0Q7DMKHzAe+Ekyk2mbr+qcBtoNND8+QpA/0Azz37mPusktdbAyzCls6xq4UOO+XKpFT/p7Ziad9z3Qn71t8Y9aXpTP+kqwpi65EDNZngeQ==; 24:NmZ/loikuog1VZUOI1Tw5fpKXVuk4KgYTY4X7Q7O6jR2cSwCHxVDYtOEMaBZ6uJTKVs7ux3+XZKnBaAS8a9x34rMbP2rSNS0r8ye1PiBC1M=; 7:T26ULje1m5ksqs1m0xwCaIoWmlmW8CCFVc8UNMYTzxlJu9/dPZxqEX3AVt/C0UycQsBGETVixtl+4cGp3mou3NSLqe/M5ZL9Pmg3XOxrF4kUcJrXzTU6NJiwCGmzs5l24zJt+xj8CEQhyb2wd2aQ9f7G665aLHLbtg15hLpFIZcyTcPnIOZ7mIi0plnzaMsySt+ywJ+kAmL4DClpZx+sjCLEF5VRrjohDa57RPzC+QE67dpIUvwQXWq6Upue4+fB
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0501MB1450;
x-microsoft-antispam-prvs: <CY1PR0501MB14509E62CEFD82C173B00DD8A50D0@CY1PR0501MB1450.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026); SRVR:CY1PR0501MB1450; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0501MB1450;
x-forefront-prvs: 0014E2CF50
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(189002)(199003)(110136002)(189998001)(3846002)(6116002)(102836003)(86362001)(92566002)(15975445007)(77096005)(4001350100001)(97736004)(93886004)(10400500002)(2906002)(5002640100001)(8936002)(99286002)(3660700001)(66066001)(81166006)(81156014)(105586002)(3280700002)(68736007)(8676002)(106356001)(82746002)(16236675004)(83506001)(19625215002)(11100500001)(19300405004)(19580395003)(4326007)(54356999)(33656002)(76176999)(50986999)(101416001)(122556002)(7736002)(83716003)(7846002)(36756003)(106116001)(2900100001)(2950100001)(586003)(87936001)(217873001)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0501MB1450; H:CY1PR0501MB1450.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DCB3EBBF5EB14C8EAA55F59C4B5A8E4Djunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jul 2016 20:03:41.6444 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB1450
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/kVPSObUVdHZv6Xm07f-zIgMqwLg>
Subject: Re: [netmod] OpsState Direction Impact on Recommended IETF YANG Model Structure
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 25 Jul 2016 20:03:48 -0000

>> Juergen writes:
>> Bottom line: I think we should continue to follow the model used by
>> the ietf-interfaces model and the ietf-ip model until we have a better
>> solution in place (and subsequently we can deprecate objects that
>> became redundant).
>
> Rob writes:
> This is pretty much what I'm trying to say as well, but in a stronger
> way.  I.e. mandating that all IETF YANG models MUST follow this
> structure, and split config and state into two top level trees.


I agree that a revised datastore model plus matching solutions can
eliminate the need for the interfaces-state convention.  But this would
only apply to client/servers that have been updated to grok the new
approach - right?  If these nodes are subsequently deprecated, or new
modules are created assuming the new approach from the get go, are
we leaving the legacy client/servers behind with no way to get, for
instance, the operational status for system-created interfaces?

It seems that we need to make a hard cutover sooner or later...

Kent  // as a contributor

v2.23.0 | Report a Bug | By Email