Rare project developers

[mc36 <>]

hi,

On 11/9/21 14:08, Cristina Klippel Dominicini wrote:
> Hi Csaba,
>
> Thank you very much for the instructions, the PolKA tests, and the addition 
> of the 'show' commands. It helped a lot to understand the inner workings.
you're welcome! :)

> We are now studying the resources in the blog 
> (https://wiki.geant.org/pages/viewpage.action?pageId=148083801) and the 
> youtube channel 
> (https://www.youtube.com/channel/UCzEhsAYKJs2qSNcjuooxCOg/videos), and having 
> fun while learning about freeRouter =) It is such a powerful platform. 
> Congratulations for all this great work!
nicee!

> Once we learn the basics, we can try to understand how to plug a central 
> controller. You talked about ODL... would it connect via P4 Runtime 
> interface? How is the interaction with freeRouter?
so if we stay on the ietf way then the freerouter-->controller (topology 
export) is the bgp-ls,
the controller-->freerouter (computed paths) is the pcep... it would be the 
nicest imho...
alternatively, we have a still standardized, but freerouter specific way is 
to go with yang,
or a fully freerouter proprietary way is freerouter's own rest api...
any of these can work, just pick one... :)


> @Frederic, I also sent a post to the p4-dev list about the CRC hash 
> programming in P4 Runtime: 
> https://lists.p4.org/empathy/thread/XEOG2MF6BWGCWC6ABLPNVGJXPZEPVZUT
nice, thanks for the effort!

regards,
cs

> Best regards,
> Cristina
>
> ________________________________________
> De: mc36 <>
> Enviado: domingo, 7 de novembro de 2021 10:31
> Para: Moises R. N. Ribeiro
> Cc: ; Cristina Klippel Dominicini; Frédéric LOUI; 
> Magnos Martinello; Rafael Silva Guimarães
> Assunto: Re: [rare-dev] polka is approaching rare... was: Re: custom crc32 
> library in freerouter
>
> hi,
>
> i go inline...
>
> On 11/7/21 13:41, Moises R. N. Ribeiro wrote:
> > Csaba & Frederic et al.
> >
> > These showcase initiative of yours is key for helping us (and others) getting into your 
> > "Freerouter universe". :-) Thanks a lot for your attention to my 
> > questions/concerns in our last VC!
>
> you're welcome... :) it was my shame that i had to explain by hand instead 
> that i could showed from the routers itself...
>
>
> > On extending PolKA to a centralized approach, it seems that we are in tune in 
> > terms of pursuing a PCE-oriented design. Regarding the relevance of this 
> > effort, I believe that PCE module would match RARE's current policy-based TE 
> > efforts, right?
> exactly...
>
> > So, can you please address the following points?
> > 1) is there an specific application you're aiming at (e.g., CERN/Harvey large 
> > data transfers)?
> nothing as far as i know...
>
> > 2) when you need such PCEP implementation to be funtional (for meeting those 
> > supposed demands from policy-based TE use cases)?
>
> take your time...:)
>
>
> > My point here is that our (small and yet brave) development team needs to set 
> > priorities to a (long) list of tasks...and they see a lot o potential still to be 
> > exploited in "PolKA-Freerouter as is". And with an application (and a 
> > deadline) in mind, it would be easier for us to prioritize funtionalities of our future 
> > PCE module.
>
> feel free to experiment, and any suggestions, ideas, or even patches are 
> highly welcomed! :)
>
>
> > Last but not least, I guess competing/complementing with Segment Routing 
> > seems to be PolKA's ninche (not to mention that Scaba's Freerouter 
> > implementation has used it as a template). Thus, I guess studing the RFC 8664 
> > could be our staring point, right? Any other ways in your mind?
>
> well, so rfc8664 is the pcep for sr... it's a nice example on how to extend 
> pcep, but here we could have two approaches...
> 1) if we're good with the indexes, then we can agree that we'll reuse labels 
> as nodeids then freerouter can construct the routeid...
> 2) if we're braver then we can define a new pcep route object type which is 
> the polka routeid itself and then the controller calculates it...
> but it's just the controller-->router direction... keep in mind that to be 
> able to perform the path computation, you'll need the topology...
> for that, the ietf way is rfc7752, bgp link state extensions...
> these two together are a huge work! the best i'm aware of is opendaylight...
>
> regards,
> cs
>
>
>
>
>
> > Regards,
> > Moises
> > PS. It seems that Frederic has been doing his tricks too...Rafael has already spotted 
> > PolKA in RARE's "Complete feature list": 
> > https://wiki.geant.org/display/RARE/Home
> >
> > ----- Em 6 de Nov de 2021, em 8:34, mc36  escreveu:
> >
> > hi,
> > as there was a lot of questions about it during the last vc, and having shows 
> > is always good,
> > with 
> > https://github.com/mc36/freeRouter/commit/baa7245013f3eb480b9dc0f8878dfb20ad7903d1
> > i addes some shows for polka... below the runs from "java -jar rtr.jar test tester 
> > mpls-polka10 wait"
> > the first two are to query the static configuration of the interfaces with 
> > the polynomials,
> > this is where each node picks up it's own poly... the last one is the 
> > generated routeid and
> > decode of it both with poly and crc classes... in the given example, the 
> > tunnel from r1 to r4,
> > so the nodes are 1,2,3,4, and that's what in the decode... and as discussed, 
> > r1 itself does
> > not encode anything for himself, and r4 decodes 0 so it'll perform a route 
> > lookup....
> > regards,
> > cs
> >
> >
> >
> > r1#show polka interfaces
> > interface packet
> > loopback0 false
> > ethernet1 true
> > tunnel1 false
> > tunnel2 false
> >
> > r1#show polka interfaces eth1
> > index deg coeff poly
> > 0 16 00010000 10000000000000000
> > 1 16 00010001 10000000000000001
> > 2 16 00010003 10000000000000011
> > 3 16 00010005 10000000000000101
> > 4 16 00010009 10000000000001001
> > 5 16 0001000f 10000000000001111
> > 6 16 00010011 10000000000010001
> > 7 16 0001001b 10000000000011011
> > 8 16 0001001d 10000000000011101
> > 9 16 0001002b 10000000000101011
> >
> > r1#show polka routeid tun1
> > mode routeid
> > hex 000000000000000000004003fff0401c
> > poly 10000000000001111111111111100000100000000011100
> >
> > index coeff poly crc equal
> > 0 00010000 16412 16412 true
> > 1 00010001 65519 65519 true
> > 2 00010003 3 3 true
> > 3 00010005 4 4 true
> > 4 00010009 0 0 true
> > 5 0001000f 67 67 true
> > 6 00010011 1872 1872 true
> > 7 0001001b 1259 1259 true
> > 8 0001001d 1396 1396 true
> > 9 0001002b 10011 10011 true
> >
> > r1#
> >
> >
> >
> >
> > On 11/4/21 23:01, Cristina Klippel Dominicini wrote:
> >
> >
> >
> > 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:
> >
> > BQ_BEGIN
> >
> > 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:
> >
> > BQ_BEGIN
> >
> > 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 !
> >
> >
> > BQ_BEGIN
> > 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:
> >
> > BQ_BEGIN
> > 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:
> >
> > BQ_BEGIN
> >
> > 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:
> >
> > BQ_BEGIN
> >
> > 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>
>
>
> ________________________________
>
> 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.