I2RS interim June 1, 2016 

Agenda: 

The agenda is simply a discussion of I2RS Ephemeral State requirements.  
The presentation is online, and it is expected people will view the presentation
before the meeting. 

Description: Ephemeral State Update Review 

Streaming recording link:
https://ietf.webex.com/ietf/ldr.php?RCID=47311823b09d78f541a6276705b18795
Download recording link:
https://ietf.webex.com/ietf/lsr.php?RCID=d57e5e4c6ba68521d21dd33971d3b58d

Blue Sheets: 
http://etherpad.tools.ietf.org:9000/p/i2rs-interim-Jun1-2016-bluesheets
Minutes: 
http://etherpad.tools.ietf.org:9000/p/i2rs-interim-Jun1-2016-minutes


presentation: 
https://www.ietf.org/proceedings/interim/2016/06/01/i2rs/slides/slides-interim-2016-i2rs-9-0.pdf

Discussion of I2RS Ephemeral State 


1.  Do you think Ephemeral-REQ-05 covers the resource constraint
issue discussed on the list and at IETF-95? 

2.  Does Ephemeral-REQ-07 provide the Yang requirements in 
a clear fashion?  Do you have any suggestions for alternative text? 


   Ephemeral-REQ-07: Yang MUST have a way to indicate in a data model
   that nodes have the following properties: ephemeral, writable/not-
   writable, and status/configuration.  Yang must also have a way to
   specify on a module or submodule level whether the data MAY
   optionally flow across an non-secure transport.


3. Do you think any of the Ephemeral-REQ-08 NETCONF Changes 
   are not necessary?   If so, what changes would you leave out?
   Do the "policy-knobs" seem useful to you? 
      
4. Do you think any of the Ephemeral-REQ-09 RESTCONF changes 
   are not necessary?  If so, what changes would you leave out? 
   Do we need all the features (yang module library, call-home, 
   server)? 
   
   
5. Do you think the pub/sub requirements are sufficient? 
    (PUB-SUB-REQ-01, PUB-SUB-REQ-02)
	
6.  Do you think we should remove or keep the second sentence
    from Ephemeral-REQ-04?
	
	 Ephemeral-REQ-04: Ephemeral state MAY refer to non-ephemeral state
   for purposes of implementing constraints.  The designer of ephemeral
   state modules are advised that such constraints may impact the speed
   of processing ephemeral state commits and should avoid them when
   speed is essential.
	
7. Do you have any concerns about Ephemeral-REQ-01?  

   Ephemeral-REQ-01: I2RS requires ephemeral state; i.e. state that does
   not persist across reboots.  If state must be restored, it should be
   done solely by replay actions from the I2RS client via the I2RS
   agent.  Ephemeral state may consist of ephemeral configuration or
   ephemeral operational state, or both.
   
8. Do you have an concern about Ephemeral-REQ-02: 
    Ephemeral-REQ-02: Non-ephemeral state MUST NOT refer to ephemeral
   state for constraint purposes; it SHALL be considered a validation
   error if it does.

9.  Do you have any concerns about Ephemeral-REQ-03 or Ephemeral-REQ-04? 

   Ephemeral-REQ-03: Ephemeral state must be able to utilized temporary
   operational state (e.g.  MPLS LSP-ID or a BGP IN-RIB) as a
   constraints.

   Ephemeral-REQ-04: Ephemeral state MAY refer to non-ephemeral state
   for purposes of implementing constraints.  The designer of ephemeral
   state modules are advised that such constraints may impact the speed
   of processing ephemeral state commits and should avoid them when
   speed is essential.
   
   
https://ietf.webex.com/ietf/j.php?MTID=m163079dec821ba49f3eec1f97b52006f

Join by phone
1-877-668-4493 Call-in toll free number (US/Canada)
1-650-479-3208 Call-in toll number (US/Canada)