Re: [i2rs] Comments on I2RS and YANG suggestions (aka, finally woke up)

[Joe Clarke <[e-mail]>]

On 3/30/17 13:25, Susan Hares wrote:
>  
> 
> Joe:
> 
>  
> 
> Excellent questions.  The intent was to spin down the **hares** drafts. 
> I wished you’d asked the question in the meeting.   In my experience,
> you questions are always timely.  Please start a YANG module draft for
> I2RS.    

At least the comments are recorded more for posterity here :-).  I'd be
happy to work with people to define this model.

> *Open issues for these people: *

I have some thoughts on the first two.

> 
> ·        Precedence:  (yang/protocols) – must determine how to
> prioritize between datastores during installation of configuration

I'd like to see a general precedence model followed as you know from my
previous comments.  That is, I'd like to have a mechanism at the
datastore level that isn't just specific to I2RS.

> 
> ·        Validation (yang/protocols) - does it need to be identified in
> YANG or is it an implementation specific?

MY thinking is this might be implementation specific, but should likely
be reported from the device as to what method will be done.  This still
requires some YANG, but I'm not sure how client-requestable this will be.

>  
> 
> *Now -- to your specific comments: *
> 
> ·        *Draft:* This draft was intended to be a chair's kick start
> document on open issus.
> 
> ·        *Why Kickstart:*   I started it when the revised datastores
> people did not open their github archive or publish drafts to make sure
> we covered this work at IETF.
> 
> o   *Fortunately –* they did release -01.txt revised datastores.
> 
> ·        *Content errors: *
> 
> o   For edit-config, see the comments by Phil Schafer. 

Yep, makes a lot of sense.


> 
> o   The ephemeral logic is backward =  (red face)

Cool.  Thought so.

> 
> o   Revised datastores revisions-01 – did the following
> old/control-plane datastores/dynamic datastores/ (my draft worked off
> -00.txt)

Understood.  Thanks for the clarifications.

Joe