Re: [bess] Mail regarding draft-rbickhart-evpn-ip-mac-proxy-adv

[Wen Lin]

Hi James,

Thank you for your comments.  Please see replies inline below.

Thanks,
Wen

From: "UTTARO, JAMES" 
Date: Wednesday, March 27, 2019 at 12:20 PM
To: "draft-rbickhart-evpn-ip-mac-proxy-...@ietf.org" 

Cc: "bess@ietf.org" 
Subject: Mail regarding draft-rbickhart-evpn-ip-mac-proxy-adv
Resent-From: 
Resent-To: , , , 

Resent-Date: Wednesday, March 27, 2019 at 12:20 PM

Wen,

  A few comments.

  I think I understand the why of this draft. One could take the 
view that a MAC/IP learned via a single PE on an ESI has actually gone away and 
will not be re-learned via other PEs on said ESI.. In that case incorrectness 
is being injected into the VPN state machine for said customer for as long as 
it takes the timer to expire. Is that right??

Wen:  This solution is more useful if the MAC/IP can be re-learned through the 
data plane by other PE(s) attached to the same multihoming ES.

Generally speaking state learned via the control plane is never allowed to be 
re-advertised so PE1->PE2->PEX is disallowed. I am assuming that split horizon 
will be disabled for a MAC/IP learned from PE1 advertised to PE2, subsequently 
advertised to PE3 ( Actually everywhere ) as the ESI is in common.

Wen:  This is about PE2 originates, instead of re-advertising, a type-2 MAC+IP 
advertisement based on the knowledge that the said MAC is learned in the data 
plane from its locally attached multihomed ES, but through its peer PE(s).  
Also in this case PE2 sets a proxy bit for the type2 MAC+IP route it originates.

You could also use BGP Persistence on PE3.. PE3 would enable persistence on 
MAC/IP:NH=PE1, ESI10 if ESI10 is also available at PE2.. In this manner PE3 
would continue sending traffic to MAC/IP via PE2 as long as the ESI is valid 
and the timer on PE3 did not expire.

Wen:  Yes, other mechanism(s) can be used to close this gap and avoid traffic 
loss. The proposed solution in this draft uses EVPN method among multihomed PEs 
and it does not rely on actions of other remote PEs that are not attached to 
the same multihomed ES while at the same avoid traffic loss for traffic 
destined to that MAC (assuming this MAC is not moved.)


Thanks,
  Jim Uttaro




___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] BDF Election in EVPN VPWS Single-Active Multihoming

[Satya Mohanty (satyamoh)]

Hi Muthu,

As you mentioned it is straightforward to calculate the BDF in the default DF 
Algorithm by taking the current DF out of reckoning.
It is my personal view that since this is self-evident it need not be 
explicitly stated.
But I will let others decide.


Thanks,
--Satya

From: Muthu Arul Mozhi Perumal 
Date: Monday, March 25, 2019 at 8:22 AM
To: "Satya Mohanty (satyamoh)" 
Cc: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
"bess@ietf.org" 
Subject: Re: [bess] BDF Election in EVPN VPWS Single-Active Multihoming

Hi Satya,

draft-ietf-bess-evpn-df-election-framework also does not describe how the BDF 
is to be calculated for the default DF election algo. Am I missing something?

I think my question still holds:
Though it is straightforward to calculate the BDF by eliminating the DF from 
the candidate list, would an implementation calculating the BDF that way for 
the default DF election algo interoperate without any problem?

Would it be better to update draft-ietf-bess-evpn-df-election-framework on how 
the BDF is to be calculated in general for any DF election algo (including the 
default DF election algo)?
[Satya] IMHO opinion, much as it appears obvious, we cannot say for certain 
that in every future DF algorithm (that may come into existence), the BDF 
computation will always be as simple as taking the current DF (PE) out of 
reckoning and doing the recomputation.

Regards,
Muthu

Best,
--Satya

On Sat, Mar 23, 2019 at 2:46 AM Satya Mohanty (satyamoh) 
mailto:satya...@cisco.com>> wrote:
Hi Muthu,

Yes, the BDF is as per what you have mentioned.
https://tools.ietf.org/html/draft-ietf-bess-evpn-df-election-framework-09 
formally defines it.

Thanks,
--Satya

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
Muthu Arul Mozhi Perumal mailto:muthu.a...@gmail.com>>
Date: Friday, March 22, 2019 at 11:41 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" 
mailto:jorge.raba...@nokia.com>>
Cc: "bess@ietf.org" mailto:bess@ietf.org>>
Subject: Re: [bess] BDF Election in EVPN VPWS Single-Active Multihoming

Thanks, Jorge. Need another clarification. RFC 7432 does not describe how to 
calculate the BDF for the default DF algo. Though it is straightforward to 
calculate the BDF by eliminating the DF from the candidate list, would an 
implementation calculating the BDF that way for the default DF algo 
interoperate without any problem?

Regards,
Muthu

On Fri, Mar 22, 2019 at 11:45 PM Rabadan, Jorge (Nokia - US/Mountain View) 
mailto:jorge.raba...@nokia.com>> wrote:
Hi,

Well, everyone has to support the default DF Alg, based on RFC7432. So that one 
for sure. And in addition there are others that have been implemented. For 
instance, Pref DF election has been implemented by multiple vendors.
Thanks,
Jorge


From: Muthu Arul Mozhi Perumal 
mailto:muthu.a...@gmail.com>>
Sent: Friday, March 22, 2019 10:41
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Re: [bess] BDF Election in EVPN VPWS Single-Active Multihoming

Hi Jorge,

I didn't mean using different algorithms for electing the DF and BFD. I am just 
asking which algorithm is most widely implemented/used for electing the DF 
*and* BDF for EVPN VPWS single-active multihoming.

Regards,
Muthu

On Fri, Mar 22, 2019 at 7:47 PM Rabadan, Jorge (Nokia - US/Mountain View) 
mailto:jorge.raba...@nokia.com>> wrote:
The implementations I know use the same DF Alg for DF election _and_ backup DF 
Election. And I don’t see why you would use something different?
In other words, if you use e.g., Pref based DF Alg, use it for DF and BDF 
elections. Only that the BDF election excludes the DF from the candidate list.

Thx
Jorge

From:BESS mailto:bess-boun...@ietf.org>> on behalf of 
Muthu Arul Mozhi Perumal mailto:muthu.a...@gmail.com>>
Date: Friday, March 22, 2019 at 4:23 AM
To: "bess@ietf.org" mailto:bess@ietf.org>>
Subject: [bess] BDF Election in EVPN VPWS Single-Active Multihoming

While RFC 8214 doesn't recommend any DF election algorithm capable of electing 
the BDF in EVPN VPWS single-active multihoming for deciding the backup PE, any 
feedback on what is(are) the widely implemented/supported DF election  
algorithm(s) by vendors?

Regards,
Muthu
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] Mail regarding draft-rbickhart-evpn-ip-mac-proxy-adv

[UTTARO, JAMES]

Wen,

  A few comments.

  I think I understand the why of this draft. One could take the 
view that a MAC/IP learned via a single PE on an ESI has actually gone away and 
will not be re-learned via other PEs on said ESI.. In that case incorrectness 
is being injected into the VPN state machine for said customer for as long as 
it takes the timer to expire. Is that right??

Generally speaking state learned via the control plane is never allowed to be 
re-advertised so PE1->PE2->PEX is disallowed. I am assuming that split horizon 
will be disabled for a MAC/IP learned from PE1 advertised to PE2, subsequently 
advertised to PE3 ( Actually everywhere ) as the ESI is in common.

You could also use BGP Persistence on PE3.. PE3 would enable persistence on 
MAC/IP:NH=PE1, ESI10 if ESI10 is also available at PE2.. In this manner PE3 
would continue sending traffic to MAC/IP via PE2 as long as the ESI is valid 
and the timer on PE3 did not expire.


Thanks,
  Jim Uttaro




___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG adoption and IPR poll for draft-malhotra-bess-evpn-irb-extended-mobility-04

[Gaurav Dawra]

Support 

Sent from my iPhone

> On Mar 27, 2019, at 10:15 AM, UTTARO, JAMES  wrote:
> 
> Support
>  
> Thanks,
>   Jim Uttaro
>  
> From: BESS  On Behalf Of Krishna Muddenahally 
> Ananthamurthy (kriswamy)
> Sent: Wednesday, March 27, 2019 2:58 AM
> To: stephane.litkow...@orange.com; bess@ietf.org; 
> draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org
> Cc: bess-cha...@ietf.org
> Subject: Re: [bess] WG adoption and IPR poll for 
> draft-malhotra-bess-evpn-irb-extended-mobility-04
>  
> I support.
>  
> Thanks
> Krishna
>  
>  
> From: BESS  on behalf of 
> "stephane.litkow...@orange..com" 
> Date: Tuesday, March 5, 2019 at 9:43 AM
> To: "bess@ietf.org" , 
> "draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org" 
> 
> Cc: "bess-cha...@ietf.org" 
> Subject: [bess] WG adoption and IPR poll for 
> draft-malhotra-bess-evpn-irb-extended-mobility-04
>  
> Hi,
>  
> This email begins a two-week poll for adoption of 
> draft-malhotra-bess-evpn-irb-extended-mobility-04
> [1]
>  
> Please review the draft and post any comments to the BESS working group list.
>  
> We are also polling for knowledge of any undisclosed IPR that applies to this 
> Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
> rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
>  
> If you are listed as an author or a contributor of this document, please 
> respond to this email and indicate whether or not you are aware of any 
> relevant undisclosed IPR, copying the BESS mailing list. The document won't 
> progress without answers from all the authors and contributors.
> Currently, there are no IPR disclosures against this document.
>  
> If you are not listed as an author or a contributor, then please explicitly 
> respond only if you are aware of any IPR that has not yet been disclosed in 
> conformance with IETF rules.
>  
> This poll for adoption closes on 19th March 2019.  
>  
> Regards,
> Stephane and Matthew
>  
> [1] 
> https://datatracker.ietf.org/doc/draft-malhotra-bess-evpn-irb-extended-mobility/
>  
> _
>  
> 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.
> ___
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG adoption and IPR poll for draft-malhotra-bess-evpn-irb-extended-mobility-04

[UTTARO, JAMES]

Support

Thanks,
  Jim Uttaro

From: BESS  On Behalf Of Krishna Muddenahally 
Ananthamurthy (kriswamy)
Sent: Wednesday, March 27, 2019 2:58 AM
To: stephane.litkow...@orange.com; bess@ietf.org; 
draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org
Cc: bess-cha...@ietf.org
Subject: Re: [bess] WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04

I support.

Thanks
Krishna


From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
"stephane.litkow...@orange.com" 
mailto:stephane.litkow...@orange.com>>
Date: Tuesday, March 5, 2019 at 9:43 AM
To: "bess@ietf.org" 
mailto:bess@ietf.org>>, 
"draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org"
 
mailto:draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org>>
Cc: "bess-cha...@ietf.org" 
mailto:bess-cha...@ietf.org>>
Subject: [bess] WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04

Hi,


This email begins a two-week poll for adoption of 
draft-malhotra-bess-evpn-irb-extended-mobility-04
[1]

Please review the draft and post any comments to the BESS working group list.

We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an author or a contributor of this document, please 
respond to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR, copying the BESS mailing list. The document won't progress 
without answers from all the authors and contributors.
Currently, there are no IPR disclosures against this document.

If you are not listed as an author or a contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

This poll for adoption closes on 19th March 2019.

Regards,
Stephane and Matthew

[1] 
https://datatracker.ietf.org/doc/draft-malhotra-bess-evpn-irb-extended-mobility/



_



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.
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] I-D Action: draft-ietf-bess-evpn-irb-extended-mobility-00.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.

Title   : Extended Mobility Procedures for EVPN-IRB
Authors : Neeraj Malhotra
  Ali Sajassi
  Aparna Pattekar
  Avinash Lingala
  Jorge Rabadan
  John Drake
Filename: draft-ietf-bess-evpn-irb-extended-mobility-00.txt
Pages   : 23
Date: 2019-03-27

Abstract:
   The procedure to handle host mobility in a layer 2 Network with EVPN
   control plane is defined as part of RFC 7432. EVPN has since evolved
   to find wider applicability across various IRB use cases that include
   distributing both MAC and IP reachability via a common EVPN control
   plane. MAC Mobility procedures defined in RFC 7432 are extensible to
   IRB use cases if a fixed 1:1 mapping between VM IP and MAC is assumed
   across VM moves. Generic mobility support for IP and MAC that allows
   these bindings to change across moves is required to support a
   broader set of EVPN IRB use cases, and requires further
   consideration. EVPN all-active multi-homing further introduces
   scenarios that require additional consideration from mobility
   perspective. Intent of this draft is to enumerate a set of design
   considerations applicable to mobility across EVPN IRB use cases and
   define generic sequence number assignment procedures to address these
   IRB use cases.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-extended-mobility/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bess-evpn-irb-extended-mobility-00
https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-extended-mobility-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG adoption and IPR poll for draft-malhotra-bess-evpn-irb-extended-mobility-04

[stephane.litkowski]

Hi WG,

We have now a good amount of support for this document.
It is adopted as a new WG item.

Authors,

Pls republish the document as draft-ietf-bess-evpn-irb-extended-mobility-00


Thanks

From: stephane.litkow...@orange.com [mailto:stephane.litkow...@orange.com]
Sent: Wednesday, March 20, 2019 13:51
To: LITKOWSKI Stephane OBS/OINIS; bess@ietf.org; 
draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org
Cc: bess-cha...@ietf.org
Subject: RE: WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04

Hi WG,

Apart from the authors, we haven't received a lot of feedback for this draft 
(positive or negative).
I would like to expand the poll to an additional week (ends at 26th March) to 
see if we can get more support on the list.

Brgds,

From: stephane.litkow...@orange.com [mailto:stephane.litkow...@orange.com]
Sent: Tuesday, March 05, 2019 09:43
To: bess@ietf.org; draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04

Hi,


This email begins a two-week poll for adoption of 
draft-malhotra-bess-evpn-irb-extended-mobility-04
[1]

Please review the draft and post any comments to the BESS working group list.

We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an author or a contributor of this document, please 
respond to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR, copying the BESS mailing list. The document won't progress 
without answers from all the authors and contributors.
Currently, there are no IPR disclosures against this document.

If you are not listed as an author or a contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

This poll for adoption closes on 19th March 2019.

Regards,
Stephane and Matthew

[1] 
https://datatracker.ietf.org/doc/draft-malhotra-bess-evpn-irb-extended-mobility/



_



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.

_



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.

_

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 

Re: [bess] WG adoption and IPR poll for draft-malhotra-bess-evpn-irb-extended-mobility-04

[Krishna Muddenahally Ananthamurthy (kriswamy)]

I support.

Thanks
Krishna


From: BESS  on behalf of "stephane.litkow...@orange.com" 

Date: Tuesday, March 5, 2019 at 9:43 AM
To: "bess@ietf.org" , 
"draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org" 

Cc: "bess-cha...@ietf.org" 
Subject: [bess] WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04

Hi,


This email begins a two-week poll for adoption of 
draft-malhotra-bess-evpn-irb-extended-mobility-04
[1]

Please review the draft and post any comments to the BESS working group list.

We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an author or a contributor of this document, please 
respond to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR, copying the BESS mailing list. The document won't progress 
without answers from all the authors and contributors.
Currently, there are no IPR disclosures against this document.

If you are not listed as an author or a contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

This poll for adoption closes on 19th March 2019.

Regards,
Stephane and Matthew

[1] 
https://datatracker.ietf.org/doc/draft-malhotra-bess-evpn-irb-extended-mobility/



_



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.
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess