Skip to Content.
Sympa Menu

rare-dev - Re: [rare-dev] RARE/freeRtr status @EANTC

Subject: Rare project developers

List archive

Re: [rare-dev] RARE/freeRtr status @EANTC


Chronological Thread 
  • From: mc36 <>
  • To: Kaliraj Vairavakkalai <>, "" <>, Natrajan Venkataraman <>, Anton Elita <>, Frédéric LOUI <>
  • Cc: Simon Leinen <>, Reshma Das <>, Krzysztof Szarkowicz <>, Alexander Gall <>
  • Subject: Re: [rare-dev] RARE/freeRtr status @EANTC
  • Date: Sun, 19 Mar 2023 05:16:29 +0100

whereas in freerouter these are still the same table, regardless which afi
the prefixes communicated through,

so that was why i asked originally my question.... :)

so as you know we mimic the cisco behavior and they just recently did started
separating the afis,

but i think they not yet finished it fully, and it'll be a hard work, well,
bgp-lu is out, and

it'll be hard to change all the existing configurations.... :)

clearly speaking, our geant's bgp-lu in prod looks like this at the moment on
our asr9912:

address-family ipv4 unicast
allocate-label route-policy internal-loopback
neighbor 62.40.102.26
address-family ipv4 labeled-unicast



On 3/19/23 05:10, mc36 wrote:
okkk, thanks, i think i can live with that :))


On 3/19/23 05:09, Kaliraj Vairavakkalai wrote:
:-D. It s just the future roadmap. There s nothing to hide. :)

Also, I don t expect customers to jump from LU to CT immediately. ;-)

So, CT stays a complementing companion to LU for the time being, instead of replacing it.
Thanks

Kaliraj

*From: *mc36 <>
*Date: *Saturday, March 18, 2023 at 8:50 PM
*To: *Kaliraj Vairavakkalai <>, <>, Natrajan Venkataraman <>, Anton Elita <>, Fr d ric LOUI <>
*Cc: *Simon Leinen <>, Reshma Das <>, Krzysztof
Szarkowicz <>, Alexander Gall <>
*Subject: *Re: [rare-dev] RARE/freeRtr status @EANTC

[External Email. Be cautious of content]


ommmmmmmm a way soo sorry, now the list heard a way more than expected,
thanks for the transparency! :)

thanks,

cs


On 3/19/23 04:46, Kaliraj Vairavakkalai wrote:
That s exactly right thinking Csaba.

Just that, today Junos BGP-CT implementation doesn t support carrying
best-effort tunnels, installing them in inet fib, etc. (So that PE1<->PE2
control plane packets can take the
CT LSP).

IOW, BGP-CT learnt routes can be used as nexthop to resolve other BGP routes,
but cannot themselves be installed in FIB.

This is a TODO item in Junos. Once that is implemented, then LU can be
avoided. You are right.

Thanks

Kaliraj

*From: *mc36 <>
*Date: *Saturday, March 18, 2023 at 8:35 PM
*To: * <>, Natrajan Venkataraman
<>, Kaliraj Vairavakkalai <>, Anton Elita
<>,
Fr d ric LOUI <>
*Cc: *Simon Leinen <>, Reshma Das <>, Krzysztof
Szarkowicz <>, Alexander Gall <>
*Subject: *Re: [rare-dev] RARE/freeRtr status @EANTC

only one question, is rhere a specific reason that the best effort is not
just an other color in the bgp-ct?

btw im fine with the bgp-lu for that, but then freerouter would not need an
additinal process then?


Juniper Business Use Only



Juniper Business Use Only




Archive powered by MHonArc 2.6.24.

Top of Page