Hi,
I'd like to figure out what the right architecture is to support VPN
routing. I'm not terribly interested in them myself, but it seems they're
not going away and there are various people interested in adding things in
this area.
I'd like to try pin down which VPN routing technologies are of interest,
and what the requirements and commonalities are. It'd be good to be learn
from ospfd/ospf6d and ripd/ripngd, and try do a bit better.
VPN routing, to my mind, mostly is about mapping some set of information
to a routing context, potentially in some series, to retrieve routing
information[1]. E.g. perhaps some kind of interface ID to some context
identifier to index into the final prefix-trie.
* Which VPN routing technologies are people interested in? (L3VPN)
* What kind of relations and lookups do we need, in terms of what kind of
identifiers (ifindices? VRF IDs? RDs? etc..)?
* At which places do you want to exchange routing information?
I think it'd be really good to get all these details down in one place, so
we can figure out what commonalities there are, and avoid having set after
set of "similar but different" bits of code going in here and there.
We sometimes pay a heavy cost down the road for the want of relatively
small amounts of up-front work.
1. In an ideal world, we'd just prepend these things to each other and put
them into the address label and put that information in the packet. Then
routing lookup could be a lot more straight-forward and regular. But, hey
32-bits is enough for everyone...
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
Gordon's Law:
If you think you have the solution, the question was poorly phrased.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
