Rare project developers

[Cristina Klippel Dominicini <>]

Thank you for the instructions, Csaba!

We will study and learn about the freeRouter platform  to explore its 
features in our use case.

Best regards,
Cristina

________________________________________
De:  <> em 
nome de mc36 <>
Enviado: quinta-feira, 4 de novembro de 2021 18:42
Para: ; Cristina Klippel Dominicini; Frédéric LOUI
Cc: Magnos Martinello; Rafael Silva Guimarães; Moises R. N. Ribeiro
Assunto: Re: [rare-dev] polka is approaching rare... was: Re: custom crc32 
library in freerouter

hi,
to have the environment up and running at your side, just pick up a linux and 
install openjdk (java, javac) to it...
then do the following as a regular user:

wget freertr.net/rtr.zip
unzip rtr.zip
cd src
./c.sh
java -jar rtr.jar test tester mpls-polka01 wait

then you can access your virtual routers at
telnet localhost 20001
telnet localhost 20002
telnet localhost 20003

good luck and feel free to ask if you get lost somewhere... :)
thanks,
cs



On 11/4/21 22:16, Cristina Klippel Dominicini wrote:
>
> Hi Csaba,
>
> Thank you very much for the demo on Tuesday! We were really happy to see 
> PolKA integrated into freeRouter... with PolKA tunnels, PBR, ... and the 
> full set of features that comes with freeRouter =)
>
> Actions points from our side now:
> - install a freeRouter virtual testbed;
> - reproduce the demo from Csaba in virtual environment;
> - document the changes to integrate PolKA in the repository by checking the 
> commits;
> - reproduce the demo in the RARE testbed (after Frederic applies the 
> modifications); and
> - generate the RFC initial version.
>
> @Jordi, is it possible please to give access to the recordings of the three 
> last meetings (#0005, #0006 and #0007)? I checked in the youtube channel 
> (https://www.youtube.com/channel/UCzEhsAYKJs2qSNcjuooxCOg/videos), but they 
> are not there yet. It would be very helpful to have access to the 
> recordings to tackle the action points.
>
> Thank you!
> Cristina
>
> ________________________________________
> De:  <> em 
> nome de mc36 <>
> Enviado: terça-feira, 2 de novembro de 2021 11:58
> Para: ; Cristina Klippel Dominicini; Frédéric LOUI
> Cc: Magnos Martinello; Rafael Silva Guimarães; Moises R. N. Ribeiro
> Assunto: Re: [rare-dev] polka is approaching rare... was: Re: custom crc32 
> library in freerouter
>
> hi,
> scroll back on this thread and check out those commits i mentioned...
> these two are too far and have much other stuff...
> regards,
> cs
>
>
> On 11/2/21 15:53, Cristina Klippel Dominicini wrote:
>>
>> Hi, Frederic,
>>
>> No problem. It was good that we have more time to explore the huge (and 
>> super fast) effort Csaba did to include PolKA into freeRouter.
>>
>> @Csaba, I am comparing these two commits. Are they good references of 
>> start and end of PolKA development?
>> https://github.com/mc36/freeRouter/compare/04f6a662d44b1e618bcb099346693c4be8e5ed52...41a71b143c2ad63249155711d8e166ab5b11fd0d
>>
>> Best regards,
>> Cristina
>>
>> ________________________________________
>> De: FrÃf©dÃf©ric LOUI <>
>> Enviado: terÃf§a-feira, 2 de novembro de 2021 11:47
>> Para: 
>> Cc: Cristina Klippel Dominicini; Magnos Martinello; Rafael Silva 
>> GuimarÃf£es; Moises R. N. Ribeiro
>> Assunto: Re: [rare-dev] polka is approaching rare... was: Re: custom crc32 
>> library in freerouter
>>
>> My bad, wrongly assumed that the Ã'« S Ã'» in CEST was "S"aving time 
>> like in Daily Saving Time  :3
>>
>> My bad IâEUR(tm)d would put CET from now on !
>>
>>> Le 2 nov. 2021 Ãf  15:23, mc36 <> a Ãf©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ÃffÃ?'Ãf'Ã'§a-feira, 2 de novembro de 2021 11:15
>>>>> Para: Cristina Klippel Dominicini; Magnos Martinello; 
>>>>> FrÃffÃ?'Ãf'Ã'©dÃffÃ?'Ãf'Ã'©ric LOUI; 
>>>>> Cc: Rafael Silva GuimarÃffÃ?'Ãf'Ã'£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ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§a-feira, 2 de novembro de 
>>>>>> 2021 10:55
>>>>>> *Para:* Magnos Martinello; 
>>>>>> FrÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©dÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©ric LOUI
>>>>>> *Cc:* ; ; Rafael Silva 
>>>>>> GuimarÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£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ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©dÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©ric 
>>>>>> LOUI
>>>>>> *Cc:* Cristina Klippel Dominicini; ; ; 
>>>>>> Rafael Silva GuimarÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£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,ÃffÃ?'Ãf'âEURs 
>>>>>> 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ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©dÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©ric LOUI 
>>>>>> < <>> wrote:
>>>>>>
>>>>>>
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > @Frederic, is tomorrow freeRouter's meeting 
>>>>>> confirmed?
>>>>>> Ãf' Ãf' Ãf' Ãf'  Of course ! IIRC, we have planned to have Csaba doing 
>>>>>> a RARE/freeRtr Polka demo ÃffÃ?'Ãf'Ã'¢EURÃffâEURsÃf'Ã'¦
>>>>>>
>>>>>> Ãf' Ãf' Ãf' Ãf'  So I strongly advise the UFES gang :) ton join us !
>>>>>>
>>>>>>
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Le 1 nov. 2021 ÃffÃ?'Ãf'Ã?'Ãf'  22:30, Cristina 
>>>>>> Klippel Dominicini < 
>>>>>> <>> a 
>>>>>> ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©crit :
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Hi Csaba,
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > 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
>>>>>> Ãf' Ãf' Ãf' Ãf'  modifications in the freeRouter code to understand 
>>>>>> how to contribute.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > @Frederic, is tomorrow freeRouter's meeting 
>>>>>> confirmed? I think it would be a good opportunity to wrap up our 
>>>>>> current status and next steps.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Regarding the nodeIDs, in the Chinese Remainder 
>>>>>> Theorem, it is sufficient if the nodeID polynomials are pairwise 
>>>>>> relatively prime (Section 17.4 of
>>>>>> Ãf' Ãf' Ãf' Ãf'  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
>>>>>> Ãf' Ãf' Ãf' Ãf'  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
>>>>>> Ãf' Ãf' Ãf' Ãf'  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
>>>>>> Ãf' Ãf' Ãf' Ãf'  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
>>>>>> Ãf' Ãf' Ãf' Ãf'  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.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Regarding the design choices, the discussions 
>>>>>> with you, Frederic and Jordi, were very helpful to tune our arguments 
>>>>>> about the potential benefits of PolKA:
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > - 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
>>>>>> Ãf' Ãf' Ãf' Ãf'  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
>>>>>> Ãf' Ãf' Ãf' Ãf'  seems to be a very good solution. We still reduce the 
>>>>>> management burden of maintaining routing tables when compared with 
>>>>>> traditional approaches.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > - 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
>>>>>> Ãf' Ãf' Ãf' Ãf'  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.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > - 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
>>>>>> Ãf' Ãf' Ãf' Ãf'  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
>>>>>> Ãf' Ãf' Ãf' Ãf'  in segment routing.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > From your previous email:
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >>> 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)
>>>>>> Ãf' Ãf' Ãf' Ãf'  through a polka domain... 
>>>>>> https://github.com/mc36/freeRouter/commit/aa261c3e3a5bf33f85e8068cf7555653f24c4e85
>>>>>> Ãf' Ãf' Ãf' Ãf'  
>>>>>> <https://github.com/mc36/freeRouter/commit/aa261c3e3a5bf33f85e8068cf7555653f24c4e85>
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > 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.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Best Regards,
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Cristina
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > ________________________________________
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > De: mc36 < <>>
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Enviado: sÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡bado, 30 
>>>>>> de outubro de 2021 06:24
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Para:  
>>>>>> <>; 
>>>>>> FrÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©dÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©ric LOUI
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Cc: Cristina Klippel Dominicini; Rafael Silva 
>>>>>> GuimarÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£es; Moises R. N. Ribeiro; Magnos 
>>>>>> Martinello
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Assunto: Re: [rare-dev] polka is approaching 
>>>>>> rare... was: Re: custom crc32 library in freerouter
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >>
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >> So basically Polka should be live and kicking 
>>>>>> in P4 LAB using RARE/freeRtr ?
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >>
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >> PS: Please let me know if you need P4 
>>>>>> dataplane and bf_forwarder.py to be upgraded.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >>
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > so yeahhh, the freerouter upgrade does not 
>>>>>> carry (at the moment:) the tofino.bin....
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > so well the lab need a fresh bfrouter and 
>>>>>> bfforwarder... also, some features needed
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > to be taken out here because we ran out of 
>>>>>> stages... at my case it was multicast,
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > as it's a core (P) router here so no need for 
>>>>>> raw ip multicast, bier is enough 4 me...
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > attaching the constants table used to configure 
>>>>>> my stordis...
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > regards,
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > cs
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > ________________________________
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Esta mensagem (incluindo anexos) 
>>>>>> contÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©m 
>>>>>> informaÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o 
>>>>>> confidencial destinada a um usuÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡rio 
>>>>>> especÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'­fico e seu 
>>>>>> conteÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'ºdo ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'© 
>>>>>> protegido por lei. Se vocÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'ª 
>>>>>> nÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'© o 
>>>>>> destinatÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡rio correto
>>>>>> Ãf' Ãf' Ãf' Ãf'  deve apagar esta mensagem.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  >
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > O emitente desta mensagem 
>>>>>> ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'© responsÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡vel 
>>>>>> por seu conteÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'ºdo e 
>>>>>> endereÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§amento.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > Cabe ao destinatÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡rio 
>>>>>> cuidar quanto ao tratamento adequado. A 
>>>>>> divulgaÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o, 
>>>>>> reproduÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o e/ou 
>>>>>> distribuiÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o sem 
>>>>>> a devida 
>>>>>> autorizaÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o ou 
>>>>>> qualquer outra 
>>>>>> aÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o sem 
>>>>>> conformidade com as
>>>>>> Ãf' Ãf' Ãf' Ãf'  normas internas do Ifes 
>>>>>> sÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o proibidas e 
>>>>>> passÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'­veis de 
>>>>>> sanÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o 
>>>>>> disciplinar, cÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'­vel e criminal.
>>>>>> Ãf' Ãf' Ãf' Ãf' Ãf'  > <poly.pdf>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> ---
>>>>>> Magnos Martinello
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>>>>
>>>>>> Esta mensagem (incluindo anexos) contÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©m 
>>>>>> informaÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o 
>>>>>> confidencial destinada a um usuÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡rio 
>>>>>> especÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'­fico e seu 
>>>>>> conteÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'ºdo ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'© 
>>>>>> protegido por lei. Se vocÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'ª 
>>>>>> nÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'© o 
>>>>>> destinatÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡rio correto deve
>>>>>> apagar esta mensagem.
>>>>>>
>>>>>> O emitente desta mensagem ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'© 
>>>>>> responsÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡vel por seu 
>>>>>> conteÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'ºdo e 
>>>>>> endereÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§amento.
>>>>>> Cabe ao destinatÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡rio cuidar quanto ao 
>>>>>> tratamento adequado. A 
>>>>>> divulgaÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o, 
>>>>>> reproduÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o e/ou 
>>>>>> distribuiÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o sem 
>>>>>> a devida 
>>>>>> autorizaÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o ou 
>>>>>> qualquer outra 
>>>>>> aÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o sem 
>>>>>> conformidade com as normas
>>>>>> internas do Ifes sÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o proibidas e 
>>>>>> passÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'­veis de 
>>>>>> sanÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o 
>>>>>> disciplinar, cÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'­vel e criminal.
>>>>>>
>>>>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>>>>
>>>>>> Esta mensagem (incluindo anexos) contÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'©m 
>>>>>> informaÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o 
>>>>>> confidencial destinada a um usuÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡rio 
>>>>>> especÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'­fico e seu 
>>>>>> conteÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'ºdo ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'© 
>>>>>> protegido por lei. Se vocÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'ª 
>>>>>> nÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'© o 
>>>>>> destinatÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡rio correto deve
>>>>>> apagar esta mensagem.
>>>>>>
>>>>>> O emitente desta mensagem ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'© 
>>>>>> responsÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡vel por seu 
>>>>>> conteÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'ºdo e 
>>>>>> endereÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§amento.
>>>>>> Cabe ao destinatÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'¡rio cuidar quanto ao 
>>>>>> tratamento adequado. A 
>>>>>> divulgaÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o, 
>>>>>> reproduÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o e/ou 
>>>>>> distribuiÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o sem 
>>>>>> a devida 
>>>>>> autorizaÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o ou 
>>>>>> qualquer outra 
>>>>>> aÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o sem 
>>>>>> conformidade com as normas
>>>>>> internas do Ifes sÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o proibidas e 
>>>>>> passÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'­veis de 
>>>>>> sanÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'§ÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'£o 
>>>>>> disciplinar, cÃffÃ?'Ãf'Ã?'ÃffâEURsÃf'Ã'­vel e criminal.
>>>>>
>>>>>
>>>>> ________________________________
>>>>>
>>>>> Esta mensagem (incluindo anexos) contÃffÃ?'Ãf'Ã'©m 
>>>>> informaÃffÃ?'Ãf'Ã'§ÃffÃ?'Ãf'Ã'£o confidencial destinada a um 
>>>>> usuÃffÃ?'Ãf'Ã'¡rio especÃffÃ?'Ãf'Ã'­fico e seu conteÃffÃ?'Ãf'Ã'ºdo 
>>>>> ÃffÃ?'Ãf'Ã'© protegido por lei. Se vocÃffÃ?'Ãf'Ã'ª nÃffÃ?'Ãf'Ã'£o 
>>>>> ÃffÃ?'Ãf'Ã'© o destinatÃffÃ?'Ãf'Ã'¡rio correto deve apagar esta 
>>>>> mensagem.
>>>>>
>>>>> O emitente desta mensagem ÃffÃ?'Ãf'Ã'© responsÃffÃ?'Ãf'Ã'¡vel por seu 
>>>>> conteÃffÃ?'Ãf'Ã'ºdo e endereÃffÃ?'Ãf'Ã'§amento.
>>>>> Cabe ao destinatÃffÃ?'Ãf'Ã'¡rio cuidar quanto ao tratamento adequado. 
>>>>> A divulgaÃffÃ?'Ãf'Ã'§ÃffÃ?'Ãf'Ã'£o, 
>>>>> reproduÃffÃ?'Ãf'Ã'§ÃffÃ?'Ãf'Ã'£o e/ou 
>>>>> distribuiÃffÃ?'Ãf'Ã'§ÃffÃ?'Ãf'Ã'£o sem a devida 
>>>>> autorizaÃffÃ?'Ãf'Ã'§ÃffÃ?'Ãf'Ã'£o ou qualquer outra 
>>>>> aÃffÃ?'Ãf'Ã'§ÃffÃ?'Ãf'Ã'£o sem conformidade com as normas internas do 
>>>>> Ifes sÃffÃ?'Ãf'Ã'£o proibidas e passÃffÃ?'Ãf'Ã'­veis de 
>>>>> sanÃffÃ?'Ãf'Ã'§ÃffÃ?'Ãf'Ã'£o disciplinar, cÃffÃ?'Ãf'Ã'­vel e 
>>>>> criminal.
>>>>>
>>
>>
>>
>> ________________________________
>>
>> Esta mensagem (incluindo anexos) contÃf©m informaÃf§Ãf£o confidencial 
>> destinada a um usuÃf¡rio especÃf­fico e seu conteÃfºdo Ãf© protegido 
>> por lei. Se vocÃfª nÃf£o Ãf© o destinatÃf¡rio correto deve apagar esta 
>> mensagem.
>>
>> O emitente desta mensagem Ãf© responsÃf¡vel por seu conteÃfºdo e 
>> endereÃf§amento.
>> Cabe ao destinatÃf¡rio cuidar quanto ao tratamento adequado. A 
>> divulgaÃf§Ãf£o, reproduÃf§Ãf£o e/ou distribuiÃf§Ãf£o sem a devida 
>> autorizaÃf§Ãf£o ou qualquer outra aÃf§Ãf£o sem conformidade com as 
>> normas internas do Ifes sÃf£o proibidas e passÃf­veis de sanÃf§Ãf£o 
>> disciplinar, cÃf­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.