Rare project developers

[Frédéric LOUI <>]

My bad, wrongly assumed that the « S » in CEST was "S"aving time like in 
Daily Saving Time  :3

My bad I’d would put CET from now on !

> Le 2 nov. 2021 à 15:23, mc36 <> a écrit :
> 
> okk, the meeting room is closed again so let's wait then... :)
> 
> On 11/2/21 15:21, mc36 wrote:
>> hihi,
>> my bad, frederic really said ceSt in the mail so it's summer time...
>> anyway if you're in them im going too... :)
>> regards,
>> cs
>> On 11/2/21 15:20, Cristina Klippel Dominicini wrote:
>>> 
>>> Sorry... the invitation was in CEST and we didn't realize the timezone 
>>> change. Jordi opened the VC and explained it.
>>> 
>>> It's because we're looking forward to the demo :-D
>>> 
>>> Thanks,
>>> Cristina
>>> 
>>> ________________________________________
>>> De:  <> 
>>> em nome de mc36 <>
>>> Enviado: terça-feira, 2 de novembro de 2021 11:15
>>> Para: Cristina Klippel Dominicini; Magnos Martinello; Frédéric 
>>> LOUI; 
>>> Cc: Rafael Silva Guimarães; Moises R. N. Ribeiro
>>> Assunto: Re: [rare-dev] polka is approaching rare... was: Re: custom 
>>> crc32 library in freerouter
>>> 
>>> hi,
>>> since we moved to the winter time so you'll have to wait an additional 
>>> hour... :)
>>> thanks,
>>> cs
>>> 
>>> 
>>> On 11/2/21 15:08, Cristina Klippel Dominicini wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> 
>>>> The VC meeting is not opening here... did the timezone change? The 
>>>> invitation was for 4PM CEST, which is 11AM in Brazil.
>>>> 
>>>> 
>>>> Thanks,
>>>> 
>>>> Cristina
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>> *De:*  
>>>> <> em nome de Cristina Klippel 
>>>> Dominicini <>
>>>> *Enviado:* terça-feira, 2 de novembro de 2021 10:55
>>>> *Para:* Magnos Martinello; Frédéric LOUI
>>>> *Cc:* ; ; Rafael Silva Guimarães; 
>>>> Moises R. N. Ribeiro
>>>> *Assunto:* Re: [rare-dev] polka is approaching rare... was: Re: custom 
>>>> crc32 library in freerouter
>>>> 
>>>> 
>>>> That is great, Frederic! :-D
>>>> 
>>>> 
>>>> Rafael, Moises and I will join the meeting.
>>>> 
>>>> 
>>>> Best regards,
>>>> 
>>>> Cristina
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>> *De:* Magnos Martinello <>
>>>> *Enviado:* segunda-feira, 1 de novembro de 2021 19:05
>>>> *Para:* Frédéric LOUI
>>>> *Cc:* Cristina Klippel Dominicini; ; ; 
>>>> Rafael Silva Guimarães; Moises R. N. Ribeiro
>>>> *Assunto:* Re: [rare-dev] polka is approaching rare... was: Re: custom 
>>>> crc32 library in freerouter
>>>> Guys,
>>>> 
>>>> We are very happy with the PolKA integration in the free router.
>>>> 
>>>> Tomorrow I cannot join the meeting tomorrow at 11 AM, but maybe the 
>>>> others will attend the meeting . I am out of Vitoria so if you may 
>>>> record the call, that will be great.
>>>> 
>>>> Cheers
>>>> 
>>>> 
>>>> 
>>>> On Mon, 1 Nov 2021 at 18:58, Frédéric LOUI 
>>>> < <>> wrote:
>>>> 
>>>> 
>>>> Â Â Â Â Â  > @Frederic, is tomorrow freeRouter's meeting confirmed?
>>>> Â Â Â Â  Of course ! IIRC, we have planned to have Csaba doing a 
>>>> RARE/freeRtr Polka demo âEUR¦
>>>> 
>>>> Â Â Â Â  So I strongly advise the UFES gang :) ton join us !
>>>> 
>>>> 
>>>>       > Le 1 nov. 2021 à 22:30, Cristina Klippel Dominicini 
>>>> < 
>>>> <>> a écrit :
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > Hi Csaba,
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > Thank you very much for your support. We are very happy 
>>>> with the fast progress of the PolKA integration into freeRouter. We are 
>>>> now trying to test and exploring your
>>>> Â Â Â Â  modifications in the freeRouter code to understand how to 
>>>> contribute.
>>>> Â Â Â Â Â  > @Frederic, is tomorrow freeRouter's meeting confirmed? I 
>>>> think it would be a good opportunity to wrap up our current status and 
>>>> next steps.
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > Regarding the nodeIDs, in the Chinese Remainder Theorem, it 
>>>> is sufficient if the nodeID polynomials are pairwise relatively prime 
>>>> (Section 17.4 of
>>>> Â Â Â Â  https://shoup.net/ntb/ntb-v2.pdf 
>>>> <https://shoup.net/ntb/ntb-v2.pdf>). For simplicity purposes, we use 
>>>> irreducible polynomials to assure this condition for any case (similar to
>>>> Â Â Â Â  prime numbers in the integer arithmetic). Please, find attached 
>>>> an example table of irreducible polynomials. I refactored the code and 
>>>> have just submitted a new commit in the
>>>> Â Â Â Â  shared repository to include the computation of nodeID 
>>>> polynomials with some examples (a random test and also a test using the 
>>>> values from the ONDM paper). I added a simple
>>>> Â Â Â Â  code that tests all the bit possibilities to generate a list of 
>>>> n irreducible polynomials of a specific degree (for real scenarios, I 
>>>> believe the best approach is to lookup a
>>>> Â Â Â Â  precomputed list of nodeids). Please let me know if this code 
>>>> helps. We still have to produce more mature control plane 
>>>> functionalities that explore these basic functions.
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > Regarding the design choices, the discussions with you, 
>>>> Frederic and Jordi, were very helpful to tune our arguments about the 
>>>> potential benefits of PolKA:
>>>> Â Â Â Â Â  > - Tables: In the paper, one argument was that PolKA reduces 
>>>> the number of states by not relying on tables. However, I agree with you 
>>>> that the use of an almost static table
>>>> Â Â Â Â  to map the index of the next hops does not discredit the 
>>>> original argument. Thus, your suggestion to use BGP/IGP for node 
>>>> discovery and reuse the Segment Routing identifiers
>>>> Â Â Â Â  seems to be a very good solution. We still reduce the 
>>>> management burden of maintaining routing tables when compared with 
>>>> traditional approaches.
>>>> Â Â Â Â Â  > - Header rewrite: In the paper, one argument was that PolKA 
>>>> does not need to rewrite the routeid in the packet in each hop. However, 
>>>> I agree with you that we need to rewrite
>>>> Â Â Â Â  at least a TTL field and ethernet address to prevent loops and 
>>>> allow PolKA packets to traverse bridged networks, respectively. Thus, I 
>>>> think we shouldn't focus on this argument.
>>>> Â Â Â Â Â  > - Fixed header size: In the paper, we briefly show that 
>>>> PolKA's pipeline is simpler to implement when compared to a list based 
>>>> approach, because it does not need to operate
>>>> Â Â Â Â  over variable headers. As you said, this can be a strong 
>>>> benefit considering the current hardware limitations in the maximum 
>>>> number of hops for var header operations, as used
>>>> Â Â Â Â  in segment routing.
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > From your previous email:
>>>> Â Â Â Â Â  >>> some more progess here, as you're carrying ethertype 
>>>> within polka header, i added some mpls over polka test cases... so one 
>>>> can tunnel mpls vpns (both layer2 and layer3)
>>>> Â Â Â Â  through a polka domain... 
>>>> https://github.com/mc36/freeRouter/commit/aa261c3e3a5bf33f85e8068cf7555653f24c4e85
>>>> Â Â Â Â  
>>>> <https://github.com/mc36/freeRouter/commit/aa261c3e3a5bf33f85e8068cf7555653f24c4e85>
>>>> Â Â Â Â Â  > Nice! We used the Ethernet header as a Proof of Concept, 
>>>> but we could encapsulate the PolKA header in other protocols if you 
>>>> think it is more adequate.
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > Best Regards,
>>>> Â Â Â Â Â  > Cristina
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > ________________________________________
>>>> Â Â Â Â Â  > De: mc36 < <>>
>>>>       > Enviado: sábado, 30 de outubro de 2021 06:24
>>>> Â Â Â Â Â  > Para:  
>>>> <>; Frédéric LOUI
>>>> Â Â Â Â Â  > Cc: Cristina Klippel Dominicini; Rafael Silva 
>>>> Guimarães; Moises R. N. Ribeiro; Magnos Martinello
>>>> Â Â Â Â Â  > Assunto: Re: [rare-dev] polka is approaching rare... was: 
>>>> Re: custom crc32 library in freerouter
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  >>
>>>> Â Â Â Â Â  >> So basically Polka should be live and kicking in P4 LAB 
>>>> using RARE/freeRtr ?
>>>> Â Â Â Â Â  >>
>>>> Â Â Â Â Â  >> PS: Please let me know if you need P4 dataplane and 
>>>> bf_forwarder.py to be upgraded.
>>>> Â Â Â Â Â  >>
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > so yeahhh, the freerouter upgrade does not carry (at the 
>>>> moment:) the tofino.bin....
>>>> Â Â Â Â Â  > so well the lab need a fresh bfrouter and bfforwarder... 
>>>> also, some features needed
>>>> Â Â Â Â Â  > to be taken out here because we ran out of stages... at my 
>>>> case it was multicast,
>>>> Â Â Â Â Â  > as it's a core (P) router here so no need for raw ip 
>>>> multicast, bier is enough 4 me...
>>>> Â Â Â Â Â  > attaching the constants table used to configure my 
>>>> stordis...
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > regards,
>>>> Â Â Â Â Â  > cs
>>>> Â Â Â Â Â  >
>>>> Â Â Â Â Â  > ________________________________
>>>> Â Â Â Â Â  >
>>>>       > Esta mensagem (incluindo anexos) contém 
>>>> informação confidencial destinada a um usuário 
>>>> específico e seu conteúdo é protegido por lei. Se 
>>>> você não é o destinatário correto
>>>> Â Â Â Â  deve apagar esta mensagem.
>>>> Â Â Â Â Â  >
>>>>       > O emitente desta mensagem é responsável por 
>>>> seu conteúdo e endereçamento.
>>>>       > Cabe ao destinatário cuidar quanto ao tratamento 
>>>> adequado. A divulgação, reprodução e/ou 
>>>> distribuição sem a devida autorização ou 
>>>> qualquer outra ação sem conformidade com as
>>>>      normas internas do Ifes são proibidas e passíveis 
>>>> de sanção disciplinar, cível e criminal.
>>>> Â Â Â Â Â  > <poly.pdf>
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> ---
>>>> Magnos Martinello
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>> 
>>>> Esta mensagem (incluindo anexos) contém informação 
>>>> confidencial destinada a um usuário específico e seu 
>>>> conteúdo é protegido por lei. Se você não 
>>>> é o destinatário correto deve
>>>> apagar esta mensagem.
>>>> 
>>>> O emitente desta mensagem é responsável por seu 
>>>> conteúdo e endereçamento.
>>>> Cabe ao destinatário cuidar quanto ao tratamento adequado. A 
>>>> divulgação, reprodução e/ou 
>>>> distribuição sem a devida autorização ou 
>>>> qualquer outra ação sem conformidade com as normas
>>>> internas do Ifes são proibidas e passíveis de 
>>>> sanção disciplinar, cível e criminal.
>>>> 
>>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>> 
>>>> Esta mensagem (incluindo anexos) contém informação 
>>>> confidencial destinada a um usuário específico e seu 
>>>> conteúdo é protegido por lei. Se você não 
>>>> é o destinatário correto deve
>>>> apagar esta mensagem.
>>>> 
>>>> O emitente desta mensagem é responsável por seu 
>>>> conteúdo e endereçamento.
>>>> Cabe ao destinatário cuidar quanto ao tratamento adequado. A 
>>>> divulgação, reprodução e/ou 
>>>> distribuição sem a devida autorização ou 
>>>> qualquer outra ação sem conformidade com as normas
>>>> internas do Ifes são proibidas e passíveis de 
>>>> sanção disciplinar, cível e criminal.
>>> 
>>> 
>>> ________________________________
>>> 
>>> Esta mensagem (incluindo anexos) contém informação confidencial 
>>> destinada a um usuário específico e seu conteúdo é protegido 
>>> por lei. Se você não é o destinatário correto deve apagar 
>>> esta mensagem.
>>> 
>>> O emitente desta mensagem é responsável por seu conteúdo e 
>>> endereçamento.
>>> Cabe ao destinatário cuidar quanto ao tratamento adequado. A 
>>> divulgação, reprodução e/ou distribuição sem a devida 
>>> autorização ou qualquer outra ação sem conformidade com as 
>>> normas internas do Ifes são proibidas e passíveis de sanção 
>>> disciplinar, cível e criminal.
>>>