IETF Logo Mail Archive

Re: [i2rs] I2RS Interim Meeting - June 1, 2016 - 10:00am - 11:00am - Topic: Ephemeral State Requirements

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 31 May 2016 20:10 UTC

Return-Path: <jmh@joelhalpern.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 9084512D652 for <i2rs@ietfa.amsl.com>; Tue, 31 May 2016 13:10:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level:
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=joelhalpern.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 vm5fh6kjhnKR for <i2rs@ietfa.amsl.com>; Tue, 31 May 2016 13:10:08 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5332E12D641 for <i2rs@ietf.org>; Tue, 31 May 2016 13:10:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 3FE7A9A0382; Tue, 31 May 2016 13:10:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1464725408; bh=ENJmEWcMMkZCaZoW+kZ4ZRBsQKEZ89vI+0oFi1lUuQE=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=Nj/Uz3d9aBKYWZ3poJPqmDsIRd0WS9zZsWou0QzrCNRnmi7JIWma/7y99yfrLmtId e8/ta4rf2OLGUW5a/cHky2VarR2iYLaGaVWqskMJ2TsIuq/hHKnV5Nfywd5yglPqwZ z1U7P4Njg5wB/s1Yy342VeKMvWrcQeQ7UuabZL1k=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id C71A11C0B82; Tue, 31 May 2016 13:10:07 -0700 (PDT)
To: Susan Hares <shares@ndzh.com>
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> <004801d1bb72$d0129680$7037c380$@ndzh.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <7026105d-6695-c001-ab91-a566bcf8405e@joelhalpern.com>
Date: Tue, 31 May 2016 16:10:05 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <004801d1bb72$d0129680$7037c380$@ndzh.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/KNFdX2FzoxoeD-xzmNZ9Sykr0GI>
Cc: i2rs@ietf.org
Subject: Re: [i2rs] I2RS Interim Meeting - June 1, 2016 - 10:00am - 11:00am - Topic: Ephemeral State Requirements
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:10:09 -0000

Can you clarify something for me?
What is ephemeral operational state?

The only thing I can think of is operational state like statistics 
related to ephemeral leaves or constructs?
Is that what you mean by "ephemeral operational state"?
The reason i ask is that such state does not seem to need any special 
handling or labeling.

Yours,
Joel

On 5/31/16 3:29 PM, Susan Hares wrote:
> Juergen:
>
>
>> I understand YANG validation rules and I understand YANG's notion of
> configuration datastores. I do not >think this matches your ephemeral
> configuration validation.
>
> This does not provide a technical discussion of:
> a) what you understand the ephemeral configuration validation rules to be,
> b) why you do not the model matches the configuration validation rules.
>
> 1 Data Model is a great idea for NETCONF/NETMOD.  However, it should
> encompass
>
> Ephemeral data:== ephemeral state ::== Ephemeral configuration + Ephemeral
> operational state
>
> Cheers,
>
> Sue

v2.23.0 | Report a Bug | By Email