IETF Logo Mail Archive

Re: [i2rs] ephemeral RPC?

"Susan Hares" <shares@ndzh.com> Tue, 31 May 2016 20:23 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 EC71212D652 for <i2rs@ietfa.amsl.com>; Tue, 31 May 2016 13:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.738
X-Spam-Level: *
X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, RDNS_NONE=0.793] 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 cbLyZKbYg1OI for <i2rs@ietfa.amsl.com>; Tue, 31 May 2016 13:23:54 -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 9923C12D64A for <i2rs@ietf.org>; Tue, 31 May 2016 13:23:54 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.182.128;
From: Susan Hares <shares@ndzh.com>
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>, i2rs@ietf.org
References: <ac12ae3a-571d-410e-50bb-cd48d58dea82@joelhalpern.com>
In-Reply-To: <ac12ae3a-571d-410e-50bb-cd48d58dea82@joelhalpern.com>
Date: Tue, 31 May 2016 16:23:54 -0400
Message-ID: <005601d1bb7a$5aacbfd0$10063f70$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIhcry/DffX1766+S6/UC1Jb9Ue0Z80Dr3A
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/P4sJK-6dCfKQPIDc8GH89LzQAtM>
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: Tue, 31 May 2016 20:23:56 -0000

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] On Behalf Of Joel M. Halpern
Sent: Tuesday, May 31, 2016 12:34 PM
To: 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
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs

v2.23.0 | Report a Bug | By Email