[i2rs] Can I2RS focus on the "Over the Wire" data structure , not on how end point handle the "DataStore"?

Linda Dunbar <linda.dunbar@huawei.com> Tue, 31 May 2016 23:09 UTC

Return-Path: <linda.dunbar@huawei.com>
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 C6A4312D8FD for <i2rs@ietfa.amsl.com>; Tue, 31 May 2016 16:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 fxn6YCBbxCIo for <i2rs@ietfa.amsl.com>; Tue, 31 May 2016 16:09:28 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AC9C12D8F5 for <i2rs@ietf.org>; Tue, 31 May 2016 16:09:27 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CPY93567; Tue, 31 May 2016 23:09:19 +0000 (GMT)
Received: from DFWEML703-CAH.china.huawei.com (10.193.5.177) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 1 Jun 2016 00:09:17 +0100
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by DFWEML703-CAH.china.huawei.com ([10.193.5.177]) with mapi id 14.03.0235.001; Tue, 31 May 2016 16:09:10 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Andy Bierman <andy@yumaworks.com>, Jeffrey Haas <jhaas@pfrc.org>
Thread-Topic: Can I2RS focus on the "Over the Wire" data structure , not on how end point handle the "DataStore"?
Thread-Index: AQHRuwdHMrGy2rZxuUWS355zkiS+h5/TiV6AgAAGiQCAAA0BgIAAIcQAgAAY2ICAABNkgIAAFZAA//+mzqA=
Date: Tue, 31 May 2016 23:09:10 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657EACE6D@dfweml501-mbb>
References: <000601d1bad5$70523090$50f691b0$@ndzh.com> <20160531063840.GA21289@elstar.local> <00d501d1bb45$0da83500$28f89f00$@ndzh.com> <20160531142540.GA22420@elstar.local> <001401d1bb4e$cfaefd10$6f0cf730$@ndzh.com> <20160531171304.GA22857@elstar.local> <CABCOCHR2JChAg1zmKDy_qxVOGYVeTm9wGVLyxzpChb5Ht0uaww@mail.gmail.com> <20160531195123.GN17462@pfrc.org> <CABCOCHQka+BezA6pLSiyOPcTghgx-UKK5dY6y70nME_EFZxCZg@mail.gmail.com>
In-Reply-To: <CABCOCHQka+BezA6pLSiyOPcTghgx-UKK5dY6y70nME_EFZxCZg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.71]
Content-Type: multipart/related; boundary="_004_4A95BA014132FF49AE685FAB4B9F17F657EACE6Ddfweml501mbb_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.574E19A0.00F7, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 1d341fef6ca7966102422d52821189ac
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/qG7hHRxAZmxPxzzHgQXQVHKseq0>
Cc: Benoit Claise <bclaise@cisco.com>, "i2rs@ietf.org" <i2rs@ietf.org>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Susan Hares <shares@ndzh.com>, Alia Atlas <akatlas@gmail.com>
Subject: [i2rs] Can I2RS focus on the "Over the Wire" data structure , not on how end point handle the "DataStore"?
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: Tue, 31 May 2016 23:09:32 -0000

IETF has been successful for past 20 years  in focusing on “Over the Wire” data structure.  It would be so much cleaner and straight forward if the YANG modules developed by I2RS  focusing on the “Over the Wire” data structure (and with NETMOD to focus on other aspects).
The “I2RS ephemeral State” has the needed description for the desired behavior  of the data received over I2RS interface. If we follow the IETF practice,  it is good enough.
Internal implementation framework is always controversial, hard to converge, usually ending up with a document (if completed) that is too big and difficult to read.

Providing some source code to show the internal implementation would be much more useful as a reference implementation.

The draft-schoenw-netmod-revised-datastores-00 is on the architectural framework for datastores as they are used by network management protocols. IMHO, how data stores are used are internal to the end points.

[http://www.urbanblisslife.com/wp-content/uploads/2012/10/Done-is-Better-Than-Perfect.jpg]<http://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0ahUKEwj50KWat4XNAhULxGMKHRhqDPQQjRwIBw&url=http%3A%2F%2Fwww.urbanblissmedia.com%2Fentrepreneur-rules-done-is-better-than-perfect%2F&psig=AFQjCNGKEiPB2iHSqyBiF5609pd72H0L7w&ust=1464822503865777>

Linda Dunbar

From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Andy Bierman
Sent: Tuesday, May 31, 2016 4:09 PM
To: Jeffrey Haas
Cc: Benoit Claise; i2rs@ietf.org; Juergen Schoenwaelder; Susan Hares; Alia Atlas
Subject: Re: [i2rs] I2RS Interim Meeting - June 1, 2016 - 10:00am - 11:00am - Topic: Ephemeral State Requirements

Hi,

I am not convinced the IETF can be forced to function as if it were
a dev-group in some corporation.  This is a volunteer organization so
usually solution proposals come from people who have created a solution
and they want the WG to standardize it.


Andy


On Tue, May 31, 2016 at 12:51 PM, Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>> wrote:
Andy,

On Tue, May 31, 2016 at 11:41:59AM -0700, Andy Bierman wrote:
> At some point the WG needs to agree on normative text instead of iterating
> on requirements forever.

IMO, it would be in I2RS's best interests if netconf/netmod provided drafts
in appropriately normative language covering I2RS requirements.  However,
we've been in a pathological cycle of:
"We don't understand, please give us requirements"
"We don't understand your requirements"
"You provided examples with your requirements that appear to be attempts to
change our protocol - don't do that."

The most recent revised-datastore draft would be a good place to document
where netmod(/netconf) believes ephemeral datastores (if that's the
instantiation) could live, and also how ephemeral configuration state could
interact with candidate, startup and running configuration.

yang-push covers much of our desired pub-sub behavior. (Yay!)

Discussion is required for how to tag security considerations impacting
transport into the yang model, in particular for notification.

Proposals for secondary identity and priority are also needed.

-- Jeff