Inline: GV>
We have thought about that. The beauty of BGP SPF is that you can use it solely for the underlay and maintain the services (e.g., RFC 4364) in the overlay. Additionally, it is very easy to migrate only a portion of your data center to BGP SPF. Routers operating in both domains (BGP SPF and RFC 7938) can perform the interworking by advertising AF IPv4 unicast routes into the BGP-SPF domain as BGP-LS Prefix NLRI and reachable BGP-SPF prefixes into the normal BGP IPv4 or IPv6 unicast domain as reachable NLRI. That's not what I am talking about ... I am talking of running both in parallel not interworking at the boundary. Think outside of the box pls. Just to translate to your world is like running ISIS and OSPF together if for nothing else then for routing with OSPF and using ISIS only to compute your LFAs (if really needed and OSPF does not support it yet on your boxes) :) . Yes – the could be done and the next-hops could be resolved recursively anywhere in the BGP-SPF domain. However, what advantage would this bring over advertising attached prefixes as BGP-LS Prefix NLRI? GV> The promise is to make things easier, not more complex… so what would be a realistic use-case for such a setup? Sounds as a special corner use-case, particular in the DC. DCs fabrics tend to be decommissioned and completely rebuild in a new architecture for faster/better/larger? G/
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
