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

"Susan Hares" <shares@ndzh.com> Wed, 01 June 2016 11:09 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 E180612D0A0 for <i2rs@ietfa.amsl.com>; Wed, 1 Jun 2016 04:09:21 -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 xj1amoyYMn9s for <i2rs@ietfa.amsl.com>; Wed, 1 Jun 2016 04:09:20 -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 3FBD512B027 for <i2rs@ietf.org>; Wed, 1 Jun 2016 04:09:20 -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: "'Joel M. Halpern'" <jmh@joelhalpern.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> <7026105d-6695-c001-ab91-a566bcf8405e@joelhalpern.com>
In-Reply-To: <7026105d-6695-c001-ab91-a566bcf8405e@joelhalpern.com>
Date: Wed, 01 Jun 2016 07:09:02 -0400
Message-ID: <009101d1bbf6$08548200$18fd8600$@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: AQJdaenpM7ljbP1C/TwjkI20GPnldwI0uYM8AiAGwTkCHPlBSwI0/t9yATo5ZLkC16jwLwJ+ZFiQnkNdtnA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/JAlrCnFA_D-jwdypVj3cc6vuTu4>
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: Wed, 01 Jun 2016 11:09:22 -0000

Joel: 

I am surprised you asked this question as you have followed the I2RS data
modules.  Is this question rhetorical? 
Ephemeral operational state have three types: 

1) results of rpc operations stored to respond to rpc actions 

I2RS-RIB-Data 
Rpcs: 
      +---x rib-add
      |  +---w input
      |  |  +---w rib-name        string
      |  |  +---w rib-family      rib-family-def
      |  |  +---w ip-rpf-check?   boolean
      |  +--ro output
      |     +--ro result uint32
      |     +--ro reason? string

2) notification data stored 


I2RS-RIB-Data
   notifications:
      +---n nexthop-resolution-status-change
      |  +--ro nexthop
..... 
      +---n route-change
         +--ro rib-name                 string
         +--ro rib-family               rib-family-def
         +--ro route-index              uint64

3) read-only status information 

See my presentation where the bgp-global-config - can be used by config or
state.  It is ephemeral state augmenting these features.   Or see the L2
topology module below. 

augment /nw:networks/nw:network/nw:node/nt:termination-point:
   +--rw l2-termination-point-attributes
      +--rw description?          string
      +--rw maximum-frame-size?   uint32
      +--rw (l2-termination-point-type)?
      |  +--:(ethernet)
      |  |  +--rw mac-address?          yang:mac-address
      |  |  +--rw eth-encapsulation?    identityref
      |  |  +--rw port-vlan-id?         vlan {VLAN}?
      |  |  +--rw vlan-id-name* [vlan-id] {VLAN}?
      |  |     +--rw vlan-id      vlan
      |  |     +--rw vlan-name?   string
      |  +--:(legacy)
      |     +--rw encapsulation?        identityref
      +--ro tp-state?             Enumeration


Sue Hares 

-----Original Message-----
From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
Sent: Tuesday, May 31, 2016 4:10 PM
To: Susan Hares
Cc: i2rs@ietf.org
Subject: Re: [i2rs] I2RS Interim Meeting - June 1, 2016 - 10:00am - 11:00am
- Topic: Ephemeral State Requirements

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