Hi Bruno,

The main salient points in this draft are about:


  *   Defining a service SRGB for services.
  *   Getting rid of overlay convergence and using underlay anycast SID 
convergence to converge all services riding on this anycast SID.
  *   Use of an underlay node/anycast SID to learn mac against in Dataplane. 
(Keep in mind we are not proposing any change to data plane MAC learning 
mechanisms like aging, move, security, etc…) But rather how with the SR encap 
we will learn the MAC against the source SID under the service SID in the SR 
encap. NVO3 defining VxLAN, Geneve, etc.. where MAC is learned against Source 
IP address in the encap didn’t go to discuss this in BESS.

Are you saying we should discuss the above in the BESS working group?

We are not making any relevant changes to the ELAN service, it is true we would 
need to define a new BGP message to auto-discover the services that will apply 
to BESS and we will have a draft on that to discuss in BESS.

Thanks,

Sami
From: bruno.decra...@orange.com <bruno.decra...@orange.com>
Date: Wednesday, March 16, 2022 at 2:40 PM
To: Boutros, Sami <sbout...@ciena.com>
Cc: spring@ietf.org <spring@ietf.org>, bess-cha...@ietf.org 
<bess-cha...@ietf.org>, James Guichard <james.n.guich...@futurewei.com>, Joel 
Halpern Direct <jmh.dir...@joelhalpern.com>
Subject: [**EXTERNAL**] RE: WG adoption for 
draft-boutros-spring-elan-services-over-sr-00
[+bess chairs]

Dear Sami, authors,

SPRING and BESS chairs believe this work would be better addressed in the BESS 
WG.

Thanks,
Regards,
--Bruno, Jim, Joel



Orange Restricted
From: Boutros, Sami <sbout...@ciena.com>
Sent: Monday, March 14, 2022 6:23 PM
To: DECRAENE Bruno INNOV/NET <bruno.decra...@orange.com>; James Guichard 
<james.n.guich...@futurewei.com>; Joel Halpern Direct 
<jmh.dir...@joelhalpern.com>
Cc: spring@ietf.org
Subject: WG adoption for draft-boutros-spring-elan-services-over-sr-00

Dear WG Chairs,

The authors would like to request a WG adoption for this draft, the draft was 
presented at last IETF.

We could present the draft at this IETF too, if you folks like.

Thanks,

Sami

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Reply via email to