Rare project developers

[mc36 <>]

hi,
right now sr-mpls supports a single intermediate in the dataplanes...
from that point, the packet will go on the best-path...
br,
cs


On 9/27/22 17:19, Cristina Klippel Dominicini wrote:
> Hi Csaba,
>
> We understand SR-MPLS is a more mature standard than SRv6, and this is 
> reflected in current protocol implementations. Considering the Tofino data 
> plane in the latest freeRtr release, could you please clarify the differences 
> between the SRv6 support and the SR-MPLS support?
>
> This is important for us to define if it is viable to include SRv6 in the 
> SC22 demo or limit to SR-MPLS only. For SR-MPLS, we understood that we only 
> support 1 label insertion, while in PolKA we can define explicit paths.
>
> Thank you,
> Cristina
>
> ________________________________________
> De:  <> em nome de 
> mc36 <>
> Enviado: quarta-feira, 21 de setembro de 2022 14:25
> Para: Marcos Felipe Schwarz; Cristina Klippel Dominicini; 
> ; Frederic LOUI
> Cc: Everson Borges; Magnos Martinello
> Assunto: Re: [rare-dev] RES: How to define explicit paths on Segment Routing
>
> hi,
> talking about the tofino, no, does not.
> br,
> cs
>
>
> On 9/21/22 16:55, Marcos Felipe Schwarz wrote:
> > Hi Csaba,
> >
> > Would FreeRtr Implementation of SRv6 be able to support longer explicit paths 
> > than the SR-MPLS implementation?
> >
> > Regards,
> >
> > Marcos Schwarz
> >
> > -----Mensagem original-----
> > De: Cristina Klippel Dominicini <>
> > Enviada em: quarta-feira, 21 de setembro de 2022 10:35
> > Para: mc36 <>; ; Frederic LOUI 
> > <>
> > Cc: Everson Borges <>; Marcos Felipe Schwarz 
> > <>; Magnos Martinello <>
> > Assunto: Re: How to define explicit paths on Segment Routing
> >
> >
> > Hi Csaba,
> >
> > Thank you for the information! So, for the demo, we will try to force some 
> > configuration in the hops to select the desired paths for each scenario the 
> > experiment.
> >
> > Best regards,
> > Cristina
> >
> > ________________________________________
> > De: mc36 <>
> > Enviado: quarta-feira, 21 de setembro de 2022 04:18
> > Para: Cristina Klippel Dominicini; ; Frederic LOUI
> > Cc: Everson Borges; Marcos Schwarz
> > Assunto: Re: How to define explicit paths on Segment Routing
> >
> > hi,
> > excellent question as usual... for sr-mpls we only support 1 label insertion 
> > in the dataplanes at the moment...
> > br,
> > cs
> >
> > On 9/21/22 01:31, Cristina Klippel Dominicini wrote:
> > > Hi Csaba and Frederic,
> > >
> > > We are working on the demo for the SuperComputing Conference, which compares 
> > > PolKA with Segment Routing.
> > >
> > > For this comparison, it would be important to define an explicit path
> > > for both protocols, where all the nodes of the path are explicitly defined, 
> > > independently of the shortest path between two nodes, as explained here:
> > >
> > > https://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k-r
> > > 6-4/segment-routing/configuration/guide/b-segment-routing-cg-asr9000-6
> > > 4x/b-segment-routing-cg-asr9000-64x_chapter_0111.html
> > >
> > > Using PolKA, the syntax is simple:
> > > RIO0001#configure terminal
> > > RIO0001(cfg)#interface tunnel1
> > > *RIO0001(cfg-if)#tunnel domain-name 20.20.20.1 20.20.20.4 20.20.20.3
> > > 20.20.20.2* RIO0001(cfg-if)#end
> > >
> > > However, for Segment Routing we have not been able to define the
> > > explicit path. Could you please confirm if this is supported in the
> > > current implementation of freeRtr? We searched the test cases here,
> > > but we could not identify one that uses explicit paths:
> > > http://docs.freertr.org/guides/reference/
> > > <http://docs.freertr.org/guides/reference/>
> > >
> > > Best regards,
> > > Cristina
> > >
> > >
> > >
> > > ----------------------------------------------------------------------
> > > ----------------------------------------------------------------------
> > > ----------------------------------------
> > >
> > > 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.