BGP Engines with support to "RTFilter address-family"

Mailman List Mirror (Read Only)
1

We are implementing an interesting L3VPN scenario for distributed DFZ on mid-size PEs.

And we believe that the RT Constrained Route Distribution, RFC4684, will be ideal to solve the problems of operational levels for the intervention of configurations between PEs and Route-Reflectors.

However, I’m searching for BGP Engines that implement this address-family (AFI=1, SAFI=132), to avoid Lock-In.

In Cisco, this feature is covered, for example, in this document:
https://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-mpls/mpls/116062-technologies-technote-restraint-00.html

In Juniper, in that document:
https://www.juniper.net/documentation/us/en/software/junos/vpn-l3/topics/topic-map/l3-vpns-route-target-filtering.html

IP Infusion’s OCNOS also implements this functionality.

I think Nokia implements it too.

But I’m looking for an open-source engine that supports it.

The official FRR documentation does not mention anything about RFC 4364, or RTFilter address family.
So, I think FRR does not support RTFilter Constrained Route Distribution.

Do any of the colleagues have any suggestions on this?

2

Hello,

3

FRR hasn’t implemented RFC4364 (nor planning to my knowledge (unless someone comes and codes it ;-))
I believe - Arccus has implemented it (Keyur to confirm).

Cheers,
Jeff

4

RFC4364 ... I believe - Arccus has implemented it (Keyur to confirm)

i am not keyur and do not play one on the net, but ...

5

rustybgp and gobgp might support it.

$ grep -r -P "AFI,SAFI = 1,132" rustybgp gobgp
rustybgp/tools/pyang_plugins/gobgp.yang: "Route target membership
(AFI,SAFI = 1,132)";
gobgp/tools/pyang_plugins/gobgp.yang: "Route target membership
(AFI,SAFI = 1,132)";

Nothing on FRR

$ grep -P -r -i 'IANA_SAFI_.* = 1\d{2,}' frr
frr/lib/iana_afi.h: IANA_SAFI_MPLS_VPN = 128,
frr/lib/iana_afi.h: IANA_SAFI_FLOWSPEC = 133

The mentions in the FRR issue tracker are (now) old entries.

6

Searching for "RFC 4364"

http://docs.frrouting.org/en/latest/search.html?q="RFC+4364"&check_keywords=yes&area=default#

Yields the following search results in the user documentation portal

http://docs.frrouting.org/en/latest/bgp.html?highlight="RFC%204364"
http://docs.frrouting.org/en/latest/vnc.html?highlight="RFC%204364"
http://docs.frrouting.org/en/latest/ospfd.html?highlight="RFC%204364"
http://docs.frrouting.org/en/latest/extlog.html?highlight="RFC%204364"
http://docs.frrouting.org/en/latest/overview.html?highlight="RFC%204364"

7

FRR hasn’t implemented RFC4364 (nor planning to my knowledge (unless someone comes and codes it ;-))
I believe - Arccus has implemented it (Keyur to confirm).

Confirming the implementation support on ArcOS (from Arrcus). :slight_smile:

Best Regards,
Keyur

8

$ grep -P -r -i 'IANA_SAFI_.* = 1\d{2,}' frr
frr/lib/iana_afi.h: IANA_SAFI_MPLS_VPN = 128,
frr/lib/iana_afi.h: IANA_SAFI_FLOWSPEC = 133

No SAFI 132 [Route Target constrains]
(Subsequent Address Family Identifiers (SAFI) Parameters,
https://www.iana.org/go/rfc4684)

The mentions in the issue tracker are old entries,
RTC implementation in MP-BGP · Issue #5206 · FRRouting/frr · GitHub (Oct 2019)
Master version of basic vrf commands & some other missed fixes by louberger · Pull Request #101 · FRRouting/frr · GitHub
Issues · FRRouting/frr · GitHub

:expressionless:

9

$ grep -P -r -i 'IANA_SAFI_.* = 1\d{2,}' frr
frr/lib/iana_afi.h: IANA_SAFI_MPLS_VPN = 128,
frr/lib/iana_afi.h: IANA_SAFI_FLOWSPEC = 133

No SAFI 132 [Route Target constrains]

The mentions in the frr issue tracker for "rfc 4684" are now old entries.

:expressionless: