On Thu, Mar 26, 2015 at 03:54:14PM -0500, Jeffrey Haas wrote:
> 
> On Mar 26, 2015, at 3:51 PM, Juergen Schoenwaelder 
> <[email protected]> wrote:
> 
> > On Tue, Mar 10, 2015 at 07:46:47PM +0100, Juergen Schoenwaelder wrote:
> >> Hi,
> >> 
> >> can someone explain how the model described here relates to the
> >> routing model described in the core routing configuration data model?
> >> 
> >> https://tools.ietf.org/html/draft-ietf-netmod-routing-cfg-17
> >> 
> >> Any major differences or conflicts one should be aware of?
> >> 
> > 
> > I am still waiting for a response to this question.
> 
> There is strong overlap.  
> 
> I2RS requires ephemeral state.  Until we know what ephemeral state 
> implementation looks like, we have some difficulty in fully analyzing 
> overlap.  At best, we may be able to refactor common schema into a shared 
> grouping.
>

Even if you believe you need to reinvent the wheel, at least key
abstractions better be the same. Are they?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to