Hi Richard,
My secondary motivation is to ensure that, with respect to automated
population of network information into ALTO servers, I could choose
ALTO server vendors and router vendors fairly independently.
But do you need to have a RFC which mandates support of BGP-TE spec by
an ALTO server ?
How about ALTO vendors which not have BGP code at all today ?
Are they out of luck to even propose ALTO servers ? I could really
easily imagine an ALTO vendor which does not support BGP and collects
network information (both routing and non-routing related) via their own
self discovering application modules running on all or on subset of
routers of given network. Result: no need to configure and maintain
dozens if not more of BGP sessions both on the ALTO server as well as on
the routers, no need to support BGP or IGP on ALTO server side.
And on the other hand if you want to choose a particular deployment
model you can select ALTO server vendor which does support BGP-TE RFC
XYZ. Just like today when you are buying routers or other network
devices you just make sure they speak the same language as described in
the protocol RFC XYZ. No need for another API spec to mandate support of
RFC XYZ.
Cheers,
R.
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
