On Tue, 15 Dec 2015, Lou Berger wrote:
Hi Paul,
Do you have any thoughts on how you'd like to have this discussion?
I'd like to get a catalogue of the specific mappings and lookups people
want/need for various kinds and aspect of VPN routings. If there's a few,
we can put them side by side, and use them as a rosetta stone to see what
they have in common.
I stopped trying to follow all the iterations of VPN stuff at IETF, so I
really don't know the details of what's hot now. I presume those
interested can supply the details. :)
I/we think both routing and NVO3/NVA overlay control are of interest.
* Which VPN routing technologies are people interested in? (L3VPN)
Also, since you ask I/we care about:
1) BGP controlled v4 and v6 L3VPNs, RFCs: 4760, 4360, 4364, 4659, 5512,
5566 RFC4364,4659
(and have code in various stages of readiness for upstreaming, and
have
previously posted the core set of these changes here.)
We should look at those again. Have you kept them updated to more recent
git?
2) BGP controlled EVPNs
(we have a non-standard EVPN-inspired implementation, and expect will
have lots of discussion on this, once the core/base VPN discussions take
place.)
* What kind of relations and lookups do we need, in terms of what kind of
identifiers (ifindices? VRF IDs? RDs? etc..)?
yes, interfaces (physical and logical), RDs and RTs.
Details of the maps from which identifiers/objects to what other
IDs/objects would be interesting.
A very good / interesting discussion. This goes to the discussion on
list at the end of last month. It's important to not forget all the
features that may be needed during import/export, in particular
filtering/route maps.
Does BGP provide all these tools already?
I.e. would using BGP pipes (in-process or IPC) be a good way to proceed?
(BGP is the routing swiss-army knife, the routing protocol that looks like
it's going to rule them all - we just need to add proper link-state
support into it...).
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
The world will end in 5 minutes. Please log out.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
