Re: [Netconf] [netmod] development plan

[Juergen Schoenwaelder <[e-mail]>]

On Tue, Aug 06, 2013 at 12:55:37PM +0200, Ladislav Lhotka wrote:
> Juergen Schoenwaelder <[e-mail]> writes:
> 
> > On Mon, Aug 05, 2013 at 10:04:38PM +0200, Martin Bjorklund wrote:
> >> 
> >> FWIW, this is not how I understand I2RS - I think they explicitly
> >> mention the configuration data as being one thing, and that they want
> >> another "direct" method to modify the operational state.
> >> 
> >
> > Yes, this is also my reading of draft-atlas-i2rs-architecture-01.txt,
> > which is likely going to become the I2RS architecture document soon.
> 
> That document clearly states (Sec. 5.3): "... local device configuration is considered to be separate from the I2RS data store." So if Fig. 1 indicates that I2RS agents interact with Local Config, I assume it has to do so as a compliant NETCONF client. So "config true" data stay fully in the NETCONF realm.
> 

My reading of the I-D is that the want to read config, not write it.
Nothing seems to persists in I2RS.

   The I2RS Agent will not attempt to retain or reapply state across
   routing element reboot.

Anyway, we may have to check this document to make sure it really
clearly says this when it gets final using a terminology we do
understand.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
Fax:   [phone]         <http://www.jacobs-university.de/>