On 12/16/2015 9:41 AM, Paul Jakma wrote: > On Wed, 16 Dec 2015, Lou Berger wrote: > >> 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 honestly have no idea what range of VPN stuff people want to try > support. The only thing I know about VPN standards is that there seem to > be a plethora of them. ;) > >> 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. > Cool. > >> I'm not sure what you're asking here. RTs and RDs are pretty clearly >> defined in the standards. > Well, I don't know if there are also VPN standards with other > terminologies. > > As for the RD/RT MPLS/VPN stuff: that's a "clearly defined" by IDR > standards. Which means many things are deliberately left under-specified, > or unspecified. (And then, though it states RTs are supposed to be > unstructured and opaque so far as BGP goes, it goes and defines various > structures for them). > > E.g., exactly what mechanisms for relating exactly which attributes to > RDs, and egress to RTs, and VRFs to RTs and RDs (and what else?) are we > looking at? Maybe it'll be obvious from the code. But if it's easy to > write down clearly what it intended to be implemented, it'd be nice to do > that.
Agreed, and we've started having some discussions on related config, and certainly need more. I can share our config once we're ready for that phase of the discussion. > >> 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. > For more complex tagging and filtering, we at least have some mechanisms > and UI for BGP (and probably will have more generic tagging in the > future). If needs are simpler, ZServ perhaps. > > Depends what VPN users need? lot of layers of function here: - ribs - import/export rules - route filters - route maps Some will want/need a sub set, some will need all/more.... Lou > regards, _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
