Paul,
On 12/16/2015 4:44 AM, Paul Jakma wrote: > 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. :) Sure. Although some of what we're talking about is quite mature (VPNs SAFI, encap attribute) and others are more recent (e.g., VXLAN tunnel type.) >> 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? Sort of. In addition to the original submit, the LabN github has had the 0.99.24.1 and master versions for a while. I really haven't spent time updating since right before the last IETF. Based on this discussion and the call for 99.25 features I'll update to the current master in next few days (late this week, early next week). The core function and it's config should be pretty non-controversial. Our changes to the show command are likely to need some discussion as we tried to standardize on a show bgp <afi> <safi> syntax. As part of the update mentioned above, I'll refactor the commits to separate these two so it'll be possible to get the core changes in (and full VPN & Encap SAFI RR capability) independent of the show changes. > >> 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. I'm not sure what you're asking here. RTs and RDs are pretty clearly defined in the standards. >> 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? Yes, although I'd that there will be some changes/additions that will be needed (to our code) to get the full function set that I expect will get agreed upon. > I.e. would using BGP pipes (in-process or IPC) be a good way to proceed? I think there are multiple options here. For the intra-BGP cases I've been assuming zebra+vrf_ids, at least initially. Again, some good discussions to be had here. > (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...). ;-) Lou > regards, _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
