Re: [Dcrouting] DC Routing requirements draft

[Tony Przygienda <[e-mail]>]

>
> some would note the lack of is-is and mpls, both known to be used in
> data centers.  hence this is describing needs of a future protocol.  but
> it reads like a laundry list meant to match a protocol product set which
> is yet to be revealed.
>
>
In this case IMO you're too suspicious Randy ;-)

The requirements doc leaves room for many solutions and e'one on the
discussion was mature enough to understand that we won't achieve much if we
go into the ISIS vs. OSPF vs. BGP vs. SDN positional warfare so we focused
on doing first pass of a laundry list as to what is necessary, relevant,
desirable or needed ...  Were people influenced by their experiences,
resulting preferences and scar-tissue from operating different solutions?
You bet they were. This ain't a fear-not-dream-on document by any means ;-)

So I think the doc' is pretty balanced BTW and yes, I think that there are
multiple subsets of the requirements each possibly justiying a different
engineering trade-off appealing to a customer base sae big enough to be
relevant

The BoF should be lively and then the market will tell ...

--- tony


>
>