IETF Logo Mail Archive

Re: [i2rs] Ephemeral State Requirements discussion

"Fedyk, Don" <don.fedyk@hpe.com> Mon, 06 June 2016 18:51 UTC

Return-Path: <don.fedyk@hpe.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 8559912D0B2 for <i2rs@ietfa.amsl.com>; Mon, 6 Jun 2016 11:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_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 odkVWTaXJ8QH for <i2rs@ietfa.amsl.com>; Mon, 6 Jun 2016 11:51:49 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0142.outbound.protection.outlook.com [207.46.100.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42CFC12B05A for <i2rs@ietf.org>; Mon, 6 Jun 2016 11:51:49 -0700 (PDT)
Received: from AT5PR84MB0305.NAMPRD84.PROD.OUTLOOK.COM (10.162.138.27) by AT5PR84MB0305.NAMPRD84.PROD.OUTLOOK.COM (10.162.138.27) with Microsoft SMTP Server (TLS) id 15.1.511.8; Mon, 6 Jun 2016 18:51:47 +0000
Received: from AT5PR84MB0305.NAMPRD84.PROD.OUTLOOK.COM ([10.162.138.27]) by AT5PR84MB0305.NAMPRD84.PROD.OUTLOOK.COM ([10.162.138.27]) with mapi id 15.01.0511.010; Mon, 6 Jun 2016 18:51:47 +0000
From: "Fedyk, Don" <don.fedyk@hpe.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Susan Hares <shares@ndzh.com>
Thread-Topic: [i2rs] Ephemeral State Requirements discussion
Thread-Index: AQHRu2oeCP1ke0oWUU2icYgTrkl4wZ/TY0gAgAAFHoCAAAW2gIAAEN6AgADXtICAAehLgIAGgEaAgAAJDgCAAAQeAIAABITA
Date: Mon, 06 Jun 2016 18:51:46 +0000
Message-ID: <AT5PR84MB0305B2CE55770F1A6A216ADDF65C0@AT5PR84MB0305.NAMPRD84.PROD.OUTLOOK.COM>
References: <20160531063840.GA21289@elstar.local> <026df5be-4a60-f340-60aa-d713a0e75c48@joelhalpern.com> <20160531184844.GB22928@elstar.local> <413ef504-49a8-2ba2-7fd4-582a41bd0ad0@joelhalpern.com> <20160531192729.GA23116@elstar.local> <005801d1bb7a$e7b2e440$b718acc0$@ndzh.com> <20160601091953.GD24118@elstar.local> <20160602142733.GU17462@pfrc.org> <20160606174413.GA7492@elstar.local> <01a701d1c01f$918dbf00$b4a93d00$@ndzh.com> <20160606183122.GA7624@elstar.local>
In-Reply-To: <20160606183122.GA7624@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=don.fedyk@hpe.com;
x-originating-ip: [15.219.147.13]
x-ms-office365-filtering-correlation-id: 72a42a92-4a19-4b18-4dfc-08d38e3b9c96
x-microsoft-exchange-diagnostics: 1; AT5PR84MB0305; 5:OuiVoPAM66XUus3TNEyr9ySGIWEpJ4aQ1LBOt7aWZLWoPcn5bpuoFojyzKjONGnItPpls1s6q9KDBkbnDzRsCPf+fnIJpEIMan46LXS3KDmop2qD6VIWgbBrZevgbpFpikEG9ZECZqpOFwQGbuhjDg==; 24:YOZDj4vHaL+IhmFwksts98GA2kNORfA+nzjqWYf0+MUg9pVF1rj/emnLfj+VeJszjtotIq9NAJ1ZcgEBPl8R3iEUFRcAI07/+pBlIiWFNHI=; 7:dZ88CjV8uL3Tohst9vTV906/0i1WFNbzvph7skGnKTs+T94J9DChBsMkXDWfmWvvP/f1rKRZ8t9MeBaO19t8dtSQCHFkUx7E4LKspaB/2lYj4+RwGKMNPp+5q/+Q+lyUaU1kMb4t22O9mncbXhIT6kJvpI2PMXONQvQTjFktsPJ3CKpB3Abx3rggdYSTnAYh4mH1p8gSU/piY0voQ+NnfFDfCLQ9tpkhJC3m/ziUMUI=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AT5PR84MB0305;
x-microsoft-antispam-prvs: <AT5PR84MB030559BF882666C7B03871EEF65C0@AT5PR84MB0305.NAMPRD84.PROD.OUTLOOK.COM>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AT5PR84MB0305; BCL:0; PCL:0; RULEID:; SRVR:AT5PR84MB0305;
x-forefront-prvs: 096507C068
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(13464003)(24454002)(189002)(377454003)(2900100001)(2950100001)(33656002)(93886004)(9686002)(4326007)(2906002)(99286002)(11100500001)(10400500002)(5008740100001)(5002640100001)(77096005)(68736007)(15975445007)(66066001)(5004730100002)(19580405001)(19580395003)(8936002)(105586002)(106356001)(106116001)(97736004)(8676002)(81166006)(189998001)(3660700001)(3280700002)(101416001)(87936001)(5001770100001)(3846002)(5003600100002)(586003)(122556002)(86362001)(81156014)(50986999)(54356999)(76176999)(6116002)(102836003)(92566002); DIR:OUT; SFP:1102; SCL:1; SRVR:AT5PR84MB0305; H:AT5PR84MB0305.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: hpe.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hpe.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Jun 2016 18:51:46.8648 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AT5PR84MB0305
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/AEI8vkpkrZgVAW2VOhj-SuuHahc>
Cc: 'Jeffrey Haas' <jhaas@pfrc.org>, "i2rs@ietf.org" <i2rs@ietf.org>, "'Joel M. Halpern'" <jmh@joelhalpern.com>
Subject: Re: [i2rs] Ephemeral State Requirements discussion
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, 06 Jun 2016 18:51:52 -0000

Does this imply for a minor tweak of some operational datastore (temporary link metric change or something similar) , I2RS ephemeral has to have its own complete datastore?  

Don 

> -----Original Message-----
> From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Juergen
> Schoenwaelder
> Sent: Monday, June 06, 2016 2:31 PM
> To: Susan Hares <shares@ndzh.com>
> Cc: 'Jeffrey Haas' <jhaas@pfrc.org>; i2rs@ietf.org; 'Joel M. Halpern'
> <jmh@joelhalpern.com>
> Subject: Re: [i2rs] Ephemeral State Requirements discussion
> 
> On Mon, Jun 06, 2016 at 02:16:38PM -0400, Susan Hares wrote:
> > Juergen:
> >
> > I2RS Ephemeral Configuration - is configuration which needs
> > validation, but does not survive a reboot.
> 
> Sue, 'validation' is not enough; there needs to be a clearer definition what
> 'validation' means.
> 
> > I2RS data models which are "ephemeral at top node" and have
> > operational state.  In these models, the operational state is like all
> > other operational state.
> 
> The phrase 'ephemeral at top node' just confuses me.
> 
> > I suggest we focus on the I2RS ephemeral Configuration.  On this topic
> > you stated below:
> >
> > "Again, for configuration datastores, I can obtain the config and
> > validate it pretty much anywhere, on the device or offline at a
> > controller. My understanding is that this would not be true for I2RS'
> > ephemeral stat datastores; I would need some amount of additional data
> > to do something close to YANG's configuration datastore validation."
> >
> > Why is this not true for ephemeral datastore?  I am missing any reason
> > why you think this is true.
> 
> Configuration datastore validation works because data is self-consistent
> without references to any (external) state. Are you saying that the same is
> true for I2RS' ephemeral datastores?
> 
> /js
> 
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> 
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs

v2.23.0 | Report a Bug | By Email