FIB routing compaction / compression
Hello List, is there a fib routing compaction or compression plugin available? While having only a bunch of upstreams / peers 64k fib size of a standard switch would be enough for a full bgp table in rib. If not what‘s needed for frr? Greets, Stefan
Stefan - This is not yet been implemented. There is definitely interest from the FRR community about this. Just need time for someone to do this work. donald On Fri, Mar 15, 2019 at 7:27 AM Stefan Priebe - Profihost AG <s.priebe@profihost.ag> wrote:
Hello List,
is there a fib routing compaction or compression plugin available?
While having only a bunch of upstreams / peers 64k fib size of a standard switch would be enough for a full bgp table in rib.
If not what‘s needed for frr?
Greets, Stefan
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
I‘m willing to sponsor the development. Stefan
Am 15.03.2019 um 13:03 schrieb Donald Sharp <sharpd@cumulusnetworks.com>:
Stefan -
This is not yet been implemented. There is definitely interest from the FRR community about this. Just need time for someone to do this work.
donald
On Fri, Mar 15, 2019 at 7:27 AM Stefan Priebe - Profihost AG <s.priebe@profihost.ag> wrote:
Hello List,
is there a fib routing compaction or compression plugin available?
While having only a bunch of upstreams / peers 64k fib size of a standard switch would be enough for a full bgp table in rib.
If not what‘s needed for frr?
Greets, Stefan
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
I toyed around with this 7 years ago after having first done an extensive research survey. It's pretty straightforward in theory and there are numerous approaches that can be combined. At that time there was no research article showing the full combination of techniques. The capabilities of the various forwarding chips potentially limits the full scope of what's possible. My early simulations were quite promising. The effort has been enjoying project shelf/vacation since then. One of the main downsides with the approach is that it is very hard to get a feel for how well the forwarding table can compress, and you are more than usually at the mercy of what your peers are sending you. Best, Martin On Fri, Mar 15, 2019 at 1:21 PM Stefan Priebe - Profihost AG < s.priebe@profihost.ag> wrote:
I‘m willing to sponsor the development.
Stefan
Am 15.03.2019 um 13:03 schrieb Donald Sharp <sharpd@cumulusnetworks.com :
Stefan -
This is not yet been implemented. There is definitely interest from the FRR community about this. Just need time for someone to do this work.
donald
On Fri, Mar 15, 2019 at 7:27 AM Stefan Priebe - Profihost AG <s.priebe@profihost.ag> wrote:
Hello List,
is there a fib routing compaction or compression plugin available?
While having only a bunch of upstreams / peers 64k fib size of a
standard switch would be enough for a full bgp table in rib.
If not what‘s needed for frr?
Greets, Stefan
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
On Sat, Mar 16, 2019 at 06:28:25PM +0100, Martin Millnert wrote:
I toyed around with this 7 years ago after having first done an extensive research survey. It's pretty straightforward in theory and there are numerous approaches that can be combined. At that time there was no research article showing the full combination of techniques.
Out of curiosity, on this:
The capabilities of the various forwarding chips potentially limits the full scope of what's possible.
Do you mean support for noncontiguous subnet masks / full ternary matching? If not, what do you mean? -David
My early simulations were quite promising. The effort has been enjoying project shelf/vacation since then. One of the main downsides with the approach is that it is very hard to get a feel for how well the forwarding table can compress, and you are more than usually at the mercy of what your peers are sending you.
Best, Martin
On Fri, Mar 15, 2019 at 1:21 PM Stefan Priebe - Profihost AG < s.priebe@profihost.ag> wrote:
I‘m willing to sponsor the development.
Stefan
Am 15.03.2019 um 13:03 schrieb Donald Sharp <sharpd@cumulusnetworks.com :
Stefan -
This is not yet been implemented. There is definitely interest from the FRR community about this. Just need time for someone to do this work.
donald
On Fri, Mar 15, 2019 at 7:27 AM Stefan Priebe - Profihost AG <s.priebe@profihost.ag> wrote:
Hello List,
is there a fib routing compaction or compression plugin available?
While having only a bunch of upstreams / peers 64k fib size of a
standard switch would be enough for a full bgp table in rib.
If not what‘s needed for frr?
Greets, Stefan
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
Am 16.03.19 um 18:28 schrieb Martin Millnert:
I toyed around with this 7 years ago after having first done an extensive research survey. It's pretty straightforward in theory and there are numerous approaches that can be combined. At that time there was no research article showing the full combination of techniques. The capabilities of the various forwarding chips potentially limits the full scope of what's possible. My early simulations were quite promising. The effort has been enjoying project shelf/vacation since then. One of the main downsides with the approach is that it is very hard to get a feel for how well the forwarding table can compress, and you are more than usually at the mercy of what your peers are sending you.
I think the easiest thing is to start just with compacting routes. Ex.: 192.168.0.0/24 => GW 1.2.3.4 192.168.1.0/24 => GW 1.2.3.4 => 192.168.0.0/23 => GW 1.2.3.4 Greets, Stefan
Best, Martin
On Fri, Mar 15, 2019 at 1:21 PM Stefan Priebe - Profihost AG <s.priebe@profihost.ag <mailto:s.priebe@profihost.ag>> wrote:
I‘m willing to sponsor the development.
Stefan
> Am 15.03.2019 um 13:03 schrieb Donald Sharp <sharpd@cumulusnetworks.com <mailto:sharpd@cumulusnetworks.com>>: > > Stefan - > > This is not yet been implemented. There is definitely interest from > the FRR community about this. Just need time for someone to do this > work. > > donald > > On Fri, Mar 15, 2019 at 7:27 AM Stefan Priebe - Profihost AG > <s.priebe@profihost.ag <mailto:s.priebe@profihost.ag>> wrote: >> >> Hello List, >> >> is there a fib routing compaction or compression plugin available? >> >> While having only a bunch of upstreams / peers 64k fib size of a standard switch would be enough for a full bgp table in rib. >> >> If not what‘s needed for frr? >> >> Greets, >> Stefan >> >> _______________________________________________ >> frog mailing list >> frog@lists.frrouting.org <mailto:frog@lists.frrouting.org> >> https://lists.frrouting.org/listinfo/frog
_______________________________________________ frog mailing list frog@lists.frrouting.org <mailto:frog@lists.frrouting.org> https://lists.frrouting.org/listinfo/frog
participants (4)
-
David Lamparter -
Donald Sharp -
Martin Millnert -
Stefan Priebe - Profihost AG