Re: [i2rs] modeling options for draft-ietf-i2rs-yang-network-topo
Kent Watsen <kwatsen@juniper.net> Mon, 20 February 2017 15:35 UTC
Return-Path: <kwatsen@juniper.net>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A48841296AE for <i2rs@ietfa.amsl.com>; Mon, 20 Feb 2017 07:35:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.789
X-Spam-Level:
X-Spam-Status: No, score=-3.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, 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 c0uZ3aejJDCz for <i2rs@ietfa.amsl.com>; Mon, 20 Feb 2017 07:35:26 -0800 (PST)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0139.outbound.protection.outlook.com [104.47.37.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B77431294B1 for <i2rs@ietf.org>; Mon, 20 Feb 2017 07:35:26 -0800 (PST)
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=j/ye+Arqk5dYBdUtpIaDv72Ch/E6x94SkGQotM5pK2k=; b=YEOn7kISfIrBAtEk89ztkHc4pzH+mqVtx+XhzRv6tLZQ0BNKRbbZsRPnXWAjjCf6rRwi525LmUjZWupftgj5RqsMokOfBSedGSe3IXEBec4wOYiDV2R01xFe19i1+udnTIk+WD6v6r2MzCFtaOnyBbawFzZ/tGwrZWr/ZsFfH3o=
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com (10.160.117.151) by BN3PR0501MB1441.namprd05.prod.outlook.com (10.160.117.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Mon, 20 Feb 2017 15:35:25 +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.0919.015; Mon, 20 Feb 2017 15:35:25 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Martin Bjorklund <mbj@tail-f.com>, "xufeng.liu.ietf@gmail.com" <xufeng.liu.ietf@gmail.com>
Thread-Topic: [i2rs] modeling options for draft-ietf-i2rs-yang-network-topo
Thread-Index: AQHShm7DGX1TjHFotkqv+yitC/fU9qFoWKoA///awYCAAIH9AIADEzSAgABfVYD//9IJAIAFwz4A
Date: Mon, 20 Feb 2017 15:35:25 +0000
Message-ID: <36B6098C-84A9-480C-AF83-1EF04E18E50F@juniper.net>
References: <447B5293-75CE-4CE2-ADA4-D9E55EC7EA35@juniper.net> <20170214.174106.332845199336010868.mbj@tail-f.com> <007601d2886a$bf085170$3d18f450$@gmail.com> <20170216.221949.1797970554181706414.mbj@tail-f.com> <9B5F937A-346D-429A-9E9C-1D453BED83B3@juniper.net>
In-Reply-To: <9B5F937A-346D-429A-9E9C-1D453BED83B3@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1f.0.170216
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kwatsen@juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.13]
x-ms-office365-filtering-correlation-id: 699a2505-06a0-4046-8d3a-08d459a61749
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:BN3PR0501MB1441;
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1441; 7:A7NKpLuI/00P+ZF3dlGDdQQ9DFsYokfCZMeweoNnTih7q4YJ96F3TSuFQFn6kdyANH34igruEpOkxltdETzcQF09NJ4QvdLBPlvn53jg1RbTnhQi3bCKsMssA/0eaKA5KpdmSBSDp0V+zPnfz+076RG67ggF9GGlberAFa8S7QPFEjBlct/TkQ32CJSVyyZdbfw3u1mW7UfPI6oxLRDkyu1Yl6nJJxYffTb8IJr0fKcuBOhZBiRaFTIjQfvKBARBNxSf1Q5OfmLvj19j5NT6gbMEJfUalRbqnY+tr2gj8I7NuMDTBZbHL+GImOKR4k5+XddFBcAqJzZf1EExcRP5yA==
x-microsoft-antispam-prvs: <BN3PR0501MB1441F74F957F6496C2D4A06EA55E0@BN3PR0501MB1441.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123564025)(20161123555025)(20161123560025)(20161123562025)(6072148); SRVR:BN3PR0501MB1441; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0501MB1441;
x-forefront-prvs: 02243C58C6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39410400002)(39840400002)(39850400002)(39450400003)(39860400002)(189002)(199003)(105586002)(101416001)(39060400002)(122556002)(2950100002)(38730400002)(106356001)(66066001)(561944003)(36756003)(83716003)(83506001)(33656002)(92566002)(82746002)(6306002)(50986999)(76176999)(54356999)(230783001)(93886004)(53936002)(6512007)(99286003)(5660300001)(2900100001)(2906002)(86362001)(4001350100001)(6486002)(3280700002)(6436002)(106116001)(6506006)(3660700001)(97736004)(229853002)(25786008)(6246003)(77096006)(189998001)(7736002)(305945005)(81166006)(4326007)(2501003)(81156014)(8676002)(8936002)(6116002)(3846002)(102836003)(68736007)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1441; H:BN3PR0501MB1442.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: text/plain; charset="utf-8"
Content-ID: <4A50DBCBEE02C445A82C2543DB09A8E0@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2017 15:35:25.4320 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1441
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/cj8n5NmmZiXRSvrh8e83txPwqsE>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
Subject: Re: [i2rs] modeling options for draft-ietf-i2rs-yang-network-topo
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 15:35:28 -0000
Hi Martin, Speaking with the authors offline late last week, this discussion regarding OPTION-2 came up, and I mentioned again my concerns for CON 'c': c) unable to return the opstate value for any configured node ...to which the Xufeng suggested we take your idea to heart. Specifically, rather than augment <get-config>, let's look-ahead and use the opstate <get-data> RPC (including the 'origin' attribute) now. This way, <get-config> would return the configured value, while <get-data> could return the applied value, as well as the system generated/learned topology. So, as in previous fashion, I formally submit OPTION 3: OPTION 3: use new RPC <get-topo-data>, which is just like <get-data> -------------------------------------------------------------------- This option defines a new RPC called <get-topo-data> that is fashioned directly after the <get-data> RPC from the revised-datastores draft. The RPC is renamed for fear of conflicting with any possible future changes that may occur to the planned <get-data> RPC. The <get-topo-data> RPC would take an optional 'with-origin-data' selector to return the 'origin' attribute. PROS: a) does NOT break legacy clients (how we got here). b) ability to return the opstate value for any configured node. c) minimal rewrite of the module for revised-datastores solution. CONS: a) seems like a shady thing for an IETF module to do. b) would need to resolve other issues (e.g., how to support with RESTCONF), which makes the draft quite a bit more than just a module draft. c) requires server to support metadata, which is a relatively new concept and maybe not well supported by servers. Thanks, Kent -------ORIGINAL MESSAGE------- >>>> 2) It doesn't say anything about how the opstate data is stored on the >>>> server. The opstate data is not modeled at all. This approach >>>> only defines a presentation-layer format for how opstate data can >>>> be returned via an RPC. The server is free to persist the opstate >>>> data anyway it wants, perhaps in an internal datastore called >>>> 'operational-state' or in an uber-datastore with the opstate data >>>> flagged with a datastore='oper-state' attribute. Regardless, it's >>>> an implementation detail, and the conceptual datastore model is >>>> preserved. >>> >>> You are essentially defining a new operation, but do it by modifying the >>> semantics of an existing one. I don't think this is a good idea; it is >>> better to define a new rpc. >> >> [Xufeng] Is using a new rpc is acceptable? If so, this could be a viable >> option. > >The draft-ietf-netmod-revised-datastores proposes a new rpc (maybe ><get-data>) to return data from the new operational-state datastore. >This is IMO better than adding opstate nodes to the reply to a ><get-config> request. Martin, Going back your earlier "better to define a new rpc" comment, I fail to see how this proposal is significantly different than RFC 6243. If not this, then the new RPC would be something like <get-config-ex> more than the planned <get-data>, as the goal is to return 'running' + "some opstate" (not just opstate). Still, in looking the the pros/cons, Option 1 appears stronger - only the authors don't like the idea of having to rewrite their models later... Kent _______________________________________________ i2rs mailing list i2rs@ietf.org https://www.ietf.org/mailman/listinfo/i2rs
- [i2rs] modeling options for draft-ietf-i2rs-yang-… Kent Watsen
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Martin Bjorklund
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Kent Watsen
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Robert Wilton
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Martin Bjorklund
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Alexander Clemm
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Martin Bjorklund
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Alexander Clemm
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Martin Bjorklund
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Alexander Clemm
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Kent Watsen
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Martin Bjorklund
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Xufeng Liu
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Xufeng Liu
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Susan Hares
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Susan Hares
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Xufeng Liu
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Susan Hares
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Martin Bjorklund
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Xufeng Liu
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Xufeng Liu
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Martin Bjorklund
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Kent Watsen
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Susan Hares
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Kent Watsen
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Andy Bierman
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Martin Bjorklund
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Susan Hares
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Martin Bjorklund
- Re: [i2rs] modeling options for draft-ietf-i2rs-y… Susan Hares