Subject: RE: netconf roadmap?

From: "Romascanu, Dan \(Dan\)" <[email-masked]>
Date: Sun, 24 Sep 2006 12:01:27 +0300

> -----Original Message-----
> From: [email-masked] 
> [mailto:[email-masked]] On Behalf Of Andy Bierman
> Sent: Saturday, September 23, 2006 12:25 AM
> To: [email-masked]
> Cc: [email-masked]
> Subject: Re: netconf roadmap?
> 
> [email-masked] wrote:
> > Hello
> >
> > Has there been any discussion about the steps after current 
> tasks have 
> > been finished? Or is this to be defined and is defined all the time?
> >   
> 
> Short answer:
> 
> After notifications, then NETCONF data modeling.
> 
> Long answer:
> 
> There has been a lot of discussion on this topic, although no formal
> roadmap exists.  The ADs and co-Chairs want to see some deployment
> of the base protocol, and use that experience to address NETCONF data 
> modeling
> (also called NETMOD).
> 
> There are no milestones for data modeling, and therefore no road map.
> 
> IMO, the community has not shown enough deployment or base-level 
> interoperability
> to plan very far into the future.  For example, experience is 
> suggesting 
> that specialized
> methods need to be part of the data modeling work, using a procedural 
> framework instead
> of the "static + dynamic data" framework from SMI/SNMP.   
> There are probably
> several problem areas currently unexposed in the base protocol, that 
> will likely
> surface in the next year.
> 
> 
> > Regards,
> > Antti-Jussi Korjonen
> >   
> 
> 
> Andy
> 

Just to add to what Andy wrote - in the meantime discussions,
experimentation, and sharing results and experience on items of future
work including but necessarily restricted to data modeling are supported
and encouraged. The more we have a shared experience of what is
achievable and needed, the easier will be the task to define precise
next steps if and when time arrives. 

Dan

--
to unsubscribe send a message to [email-masked] with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>