IETF Logo Mail Archive

Re: [netmod] OpsState and Schema-Mount

Kent Watsen <kwatsen@juniper.net> Mon, 08 August 2016 23:24 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 6263712B030 for <netmod@ietfa.amsl.com>; Mon, 8 Aug 2016 16:24:45 -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 B_BQmNcNFRiK for <netmod@ietfa.amsl.com>; Mon, 8 Aug 2016 16:24:43 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0095.outbound.protection.outlook.com [104.47.41.95]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0E0012B012 for <netmod@ietf.org>; Mon, 8 Aug 2016 16:24:42 -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=xZEATlkKXy27QyPTJJs1WWwghDA4T5xEA6zvJHG5hK4=; b=gnAfaGeiCsMEjSDZjYfWQ84Tfill5eWR4miC/bZSJsWoPodAxe19gfzYgy7Fhaykq+lePFL1rOe0WAH38ILzf1VPYm5n1TM6yc56H8vbnejv0aF6+5hQgZ6zbgBKrifWyZ/bj/IlwpSuVB0w5YaLDkOWLhARBa+XDDdrxGtDBfU=
Received: from CY1PR0501MB1450.namprd05.prod.outlook.com (10.160.149.11) by CY1PR0501MB1452.namprd05.prod.outlook.com (10.160.149.13) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.557.8; Mon, 8 Aug 2016 23:24:39 +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, 8 Aug 2016 23:24:39 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Andy Bierman <andy@yumaworks.com>
Thread-Topic: [netmod] OpsState and Schema-Mount
Thread-Index: AQHR7Nwrg+3BeZANfEqM5r9gczFpmaA2zIQAgAAlNwCAAKDWgIABEGmAgAAzOACABnBxAIAAXauA///W/IA=
Date: Mon, 08 Aug 2016 23:24:39 +0000
Message-ID: <673D4236-7564-4B64-8088-BE6CBA3A790E@juniper.net>
References: <bed9398c-0e6a-450e-d2ac-b381b6bebf87@cisco.com> <5296754B-8178-4B1B-B4A6-FE228ABB8E7F@juniper.net> <9367f4b1-7814-e175-32e8-d518438b841d@cisco.com> <m24m79c1ja.fsf@birdie.labs.nic.cz> <D3BF8708.72620%acee@cisco.com> <552008CB-F216-4578-A709-AE0613C2EFB9@nic.cz> <12ed1a4d-44c5-9a51-b6d4-95e1620a24ee@cisco.com> <m260roedim.fsf@birdie.labs.nic.cz> <CABCOCHRF98sTa=MA1VTkZovOufL-=yQr9Gzy+ojnncjSfK1y0Q@mail.gmail.com> <e307c2fc-e621-b5c6-4fcc-67bbcdcb87b9@cisco.com> <20160729163220.GA3579@elstar.local> <68421198-703c-bb26-0fcc-f560e6fe108d@ericsson.com> <100B5D71-C23E-4C72-9EA2-2DB6574DEB87@nic.cz> <5153eab1-8d87-6e3c-3b54-441f683695e4@cisco.com> <D3C7B1A4.7482A%acee@cisco.com> <18066971-3353-b13f-04fa-e214a47ab9a7@cisco.com> <D3C8C14F.74A40%acee@cisco.com> <3175490B-E8DA-4819-B294-C64D1A7D8A40@juniper.net> <CABCOCHRuzTTBM-9OU5GaXS_fHmpNSn5Yp-3K6oXF33SeObSonA@mail.gmail.com>
In-Reply-To: <CABCOCHRuzTTBM-9OU5GaXS_fHmpNSn5Yp-3K6oXF33SeObSonA@mail.gmail.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.11]
x-ms-office365-filtering-correlation-id: 07fb29f4-81d3-4ba3-4af1-08d3bfe32b57
x-microsoft-exchange-diagnostics: 1; CY1PR0501MB1452; 6:YllsjFe2KNZCykTpEkrDXreGZBMDmrzwBnDJTzjr4fqAmKvlxIulJbv/d80P0jvSnPd0HkkgHXA8hYAEIri59gtt7opzoD5lLYEAo4Rj0NR7QwI3/dz0ndFbDDpW+EXuce+gThPuShncu7QE8AKcsJDCs22utjKoaOJMKTuV5E1OyCuKJgH6uCmugXtnqKvMZI378tf5+XRW9ylmAt7CYPsVrb3MqfSUSbqUaXKjKY1tXXv73WxmFnxtDgMvVryt8s0a4GqmfjaqbEtt0zvia11GJ6QGw1LQ30XGa0UjHJjzKxPTZNLWIiBo6douxVi/EXKHQ8sqPLSCeC83T9u0SQ==; 5:l401O9EHJqwzvp/siO7rxoHgOG4dcVbb8CVSSeoTrv9ZpBeH8u8I6kCxaYfH0L/SZLwjDIUbBPUk2rsxL6xEnyA5RHd17/Cvek/4g2kCEOvkAC9JW+hCCdeVA2JYm1EQu5GEYp5whVWWifxsKeV5bQ==; 24:DdNC5zOIFXXN0nTF1GSadHWIjZKHUpMooLELkKPVzEpF5MTaD6k5QizJ631RqhTPu2+oafzYfaktWE4IZGxVa7AZBSCyuhcLf2JbF2Y8RoY=; 7:T8fL51tcI5PJ5CJqfbwFH1q+OnXj/F6aAWmkY5ncSQMGHzDnNkBe5eYzK1DgrDR+dRedu4EAX1OO+N1qGNE2+ePqlf3rNbHqM20YTYrT1L/ZpTAqVKjQ6zqjLNiaixTNASapgIt2rQSSB6mPbkXe2lqGoBoRXDCIliz2kwKxMjbR+rjypPaPHWEKQMxDRFfqiC1v/LaIpvowFywrgMe1a2OQywuvTwc2MHFdLFlkKdHj76HonTr/85LfrYy74b7+
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0501MB1452;
x-microsoft-antispam-prvs: <CY1PR0501MB145260156B9D8EC1D5CDA4A0A51B0@CY1PR0501MB1452.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(72170088055959)(138986009662008)(95692535739014)(21748063052155)(17755550239193);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026); SRVR:CY1PR0501MB1452; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0501MB1452;
x-forefront-prvs: 00286C0CA6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(24454002)(377454003)(189002)(199003)(66066001)(99286002)(110136002)(83716003)(77096005)(82746002)(189998001)(36756003)(19625215002)(2906002)(83506001)(106116001)(106356001)(2900100001)(97736004)(8936002)(4001350100001)(16236675004)(2950100001)(101416001)(76176999)(33656002)(54356999)(15975445007)(50986999)(87936001)(561944003)(7906003)(586003)(11100500001)(105586002)(81156014)(81166006)(68736007)(7736002)(7846002)(10400500002)(6116002)(102836003)(3846002)(3280700002)(3660700001)(5002640100001)(19300405004)(19617315012)(4326007)(93886004)(92566002)(19580395003)(122556002)(19580405001)(575784001)(86362001)(8676002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0501MB1452; 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_673D423675644B648088BE6CBA3A790Ejunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Aug 2016 23:24:39.4514 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB1452
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/pUajvyqXMFVI_fZ5hbrKWGtzQVo>
Cc: netmod WG <netmod@ietf.org>
Subject: Re: [netmod] OpsState and Schema-Mount
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, 08 Aug 2016 23:24:45 -0000

For 1,2,3, realize that placing config false nodes under config true nodes has been with us from the beginning.  All the issues you mentioned (if they’re issues at all) can’t be new.   Having a duplicate -state tree is the wart here, it’s introducing an inconsistency in how models have been written for a long time.  I prefer to remove the wart than celebrate it.

For 4, right, this discussion on s5.23 of 6087bis regards how to handle state for system-generated objects (e.g., interfaces).  It is not directly related to the how to report applied configuration problem.  It is however indirectly related, in that a holistic solution can address both.

Kent


From: Andy Bierman <andy@yumaworks.com>
Date: Monday, August 8, 2016 at 5:51 PM
To: Kent Watsen <kwatsen@juniper.net>
Cc: "Acee Lindem (acee)" <acee@cisco.com>, "Robert Wilton -X (rwilton - ENSOFT LIMITED at Cisco)" <rwilton@cisco.com>, Ladislav Lhotka <lhotka@nic.cz>, Balazs Lengyel <balazs.lengyel@ericsson.com>, "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] OpsState and Schema-Mount



On Mon, Aug 8, 2016 at 1:16 PM, Kent Watsen <kwatsen@juniper.net<mailto:kwatsen@juniper.net>> wrote:
Acee writes:
>    Then I see no YANG language barriers in collapsing config and state trees
>    - the model root just needs to be “config true”.

Great, I think we’re all agreed.  Can we now discuss the text I proposed for 6087bis?  - here’s the link to my proposal:  https://mailarchive.ietf.org/arch/msg/netmod/-zbXNhw2BJYMyrBT9nnCwoLAJ0s.

IMO this effort to avoid 2 containers is not well thought out.
Some concerns:

1) modularity
    placing the monitoring objects within the configuration means the monitoring
    cannot be used on its own

2) access control
    placing the monitoring data within configuration means the monitoring-only clients
    need write permission turned on for the nodes they can access for read-only
    This relies on granular and complex NACM rules which require regular maintenance.

3) YANG conformance
    placing the monitoring data inside the configuration means the configuration
    will be required for conformance; it is not likely to be just 1 NP container.

4) pointless;
   given that new RPC operations are needed to access applied config, the only data not
   affected (and moved under the config container anyway) is stuff that does not share
   the same indexing, or counters which are not part of the opstate problem.



Andy


Hint: the first few edits are just nits...skip over the first few paragraphs until you start seeing large blocks of changed lines...

Kent // as a contributor



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

v2.23.0 | Report a Bug | By Email