Re: [Rtg-yang-coord] Routing YANG Design Team Scope

[Lou Berger <[e-mail]>]

Hi Andy,


On 07/30/2015 11:53 AM, Andy Bierman wrote:
> Hi,
> 
> Is there a design team report published yet?

The work is still underway.
see https://www.ietf.org/proceedings/93/slides/slides-93-rtgwg-3.pdf
and draft-rtgyangdt-rtgwg-device-model-00.txt


> I agree with Juergen that existing YANG data
> such as /interfaces, system, netconf-state MUST NOT
> be moved to a different place in the data tree.
> 

This is part of the discussion that was and will be subject to the
Netmod interims.  We'd like to find a solution to our use case /
requirements that coexists with existing models/RFCs.

> You should restrict your activities to new routing modules.

The objective is to reuse and augment what's there to the maximum extent
possible and to work with the groups that own the respective mechanisms
when we hit limitations/restrictions to come up with a consensus-based
solution.

Lou

> 
> 
> Andy
> 
> 
> On Tue, Jul 28, 2015 at 12:16 PM, Lou Berger <[e-mail]
> <mailto:[e-mail]>> wrote:
> 
>     On 07/28/2015 02:29 PM, Acee Lindem (acee) wrote:
>     > However, the design team is
>     > certainly open to suggestions if you have a better representation.
> 
>     Going a step further, we'd love to hear more from you on this  --
>     although perhaps  we should do this off list (and on a call).  I'll send
>     mail...
> 
>     Thanks,
>     Lou
> 
> 
>     _______________________________________________
>     Rtg-yang-coord mailing list
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/rtg-yang-coord
> 
> 
> 
> 
> _______________________________________________
> Rtg-yang-coord mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtg-yang-coord
>