IETF Logo Mail Archive

Re: [i2rs] ephemeral RPC?

"Susan Hares" <shares@ndzh.com> Wed, 01 June 2016 11:41 UTC

Return-Path: <shares@ndzh.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 25A9C12D09E for <i2rs@ietfa.amsl.com>; Wed, 1 Jun 2016 04:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.749
X-Spam-Level: *
X-Spam-Status: No, score=1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RDNS_NONE=0.793, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no 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 pNgoEJeCn2hM for <i2rs@ietfa.amsl.com>; Wed, 1 Jun 2016 04:41:28 -0700 (PDT)
Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F06D112B059 for <i2rs@ietf.org>; Wed, 1 Jun 2016 04:41:27 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.63;
From: Susan Hares <shares@ndzh.com>
To: 'Jeffrey Haas' <jhaas@pfrc.org>
References: <ac12ae3a-571d-410e-50bb-cd48d58dea82@joelhalpern.com> <005601d1bb7a$5aacbfd0$10063f70$@ndzh.com> <20160531215802.GO17462@pfrc.org>
In-Reply-To: <20160531215802.GO17462@pfrc.org>
Date: Wed, 01 Jun 2016 07:41:20 -0400
Message-ID: <009e01d1bbfa$848bd630$8da38290$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_009F_01D1BBD8.FD7D4370"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIhcry/DffX1766+S6/UC1Jb9Ue0QFfwZxbAuhMHnefEs1aEA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/PmJ6sqhvYIWxPi3alWiYl-hswCw>
Cc: i2rs@ietf.org, "'Joel M. Halpern'" <jmh@joelhalpern.com>
Subject: Re: [i2rs] ephemeral RPC?
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: Wed, 01 Jun 2016 11:41:30 -0000

Jeff: 

 

I believe I have answered this elsewhere.  I2RS RIB Data Model provides an
rpc to:

.         add/delete RIBs, 

.         Add/delete Routes, 

.         Add/delete nexthops. 

 

The rpc could be augmented to simply provide a datastore. 

 

Sue  

 

-----Original Message-----
From: Jeffrey Haas [mailto:jhaas@pfrc.org] 
Sent: Tuesday, May 31, 2016 5:58 PM
To: Susan Hares
Cc: 'Joel M. Halpern'; i2rs@ietf.org
Subject: Re: [i2rs] ephemeral RPC?

 

Sue,

 

Rather than saying "ephemeral RPC", I suspect you mean an RPC that has
impact on ephemeral configuration or operational state.

 

Arguably, if the RPC in question only manifests as operational state for
that case the idea of ephemeral configuration in yang may become moot.

 

-- Jeff

 

On Tue, May 31, 2016 at 04:23:54PM -0400, Susan Hares wrote:

> Joel:

> 

> I2RS data model is a ephemeral-only data model, and uses an rpc to do 

> rib add/delete, route add/delete, nexthop add/delete.  Therefore, we 

> need ephemeral rpc support.

> 

> 

> Sue

> 

> -----Original Message-----

> From: i2rs [ <mailto:i2rs-bounces@ietf.org> mailto:i2rs-bounces@ietf.org]
On Behalf Of Joel M. Halpern

> Sent: Tuesday, May 31, 2016 12:34 PM

> To:  <mailto:i2rs@ietf.org> i2rs@ietf.org

> Subject: [i2rs] ephemeral RPC?

> 

> We have agreed that non-ephemeral data must not reference ephemeral data.

> 

> However, we have, up till now, not had the notion of ephemeral RPCs.  

> I see that the recent ephemeral requirements draft, as a side-effect 

> of improving clarity, creates the notion of an ephemeral RPC.

> 

> What is an ephemeral RPC, and why do we have it?

> We have been, up till now, assuming that we could use normal NetConf 

> RPCs to set and get the ephemeral information.

> 

> Thank you,

> Joel

> 

> _______________________________________________

> i2rs mailing list

>  <mailto:i2rs@ietf.org> i2rs@ietf.org

>  <https://www.ietf.org/mailman/listinfo/i2rs>
https://www.ietf.org/mailman/listinfo/i2rs

> 

> _______________________________________________

> i2rs mailing list

>  <mailto:i2rs@ietf.org> i2rs@ietf.org

>  <https://www.ietf.org/mailman/listinfo/i2rs>
https://www.ietf.org/mailman/listinfo/i2rs

v2.23.0 | Report a Bug | By Email