subject:"Re\: \[bess\] WG adoption poll and IPR poll for draft\-snr\-bess\-evpn\-loop\-protect"

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-07 Thread JOSE MANUEL CRESPO GARCIA

Hi

Just 2 comments:

“There are many ways for fixing loop and I do not see why it needs to be common 
to all vendor.”
We think that’s the spirit of the standardization organizations. Operators use 
to have multiple vendors in our networks, so for us, is  better to have common 
an uniform solutions. We think that it is also good for vendors, it saves time 
to all of us.

“Having a separate draft (especially informal) allows customers to request 
compliancy with…. Which I disagree.”
Regardless of if it is in a draft, in an RFC or none of them, all the RFQs for 
L2VPN devices that we have been running since 2002, include  mandatory 
requirements for  loop protection mechanisms.  At the moment, we have an RFQ 
open and it includes not only the funcionality of this draft but also other 
loop protection mechanisms: “Port loop protection (TX and RX connection)”, 
“automatic mac pinning”, “interface blocking in case of mac move situations”, 
“hierarchy in the order of interface blocking”, etc…
After 17 years  of experience with L2VPN services, we would never deploy a 
network solution with a vendor that doesn’t implement strong loop protection 
mechanisms in order to protect our customer services.
Asumming that loops are not only a problem for Telefónica, we would like to 
have, at least for EVPN, the loop protection solutions included in an RFC, so 
that all vendor will solve the problem in the same way.

Regards

De: Patrice Brissette (pbrisset) 
Enviado el: viernes, 4 de octubre de 2019 18:59
Para: Rabadan, Jorge (Nokia - US/Mountain View) ; 
Stephane Litkowski ; stephane.litkow...@orange.com
CC: draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org; 
bess@ietf.org
Asunto: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

This is my last email on this… looks like the message doesn’t go thru …maybe 
there is a loop somewhere.

This informal draft is like a suggestion … It is about an action output of a 
well document procedure in RFC7432.
A suggestion may be vendor specific or not. There is nothing for vendors to 
interop with.

The fact that I’m seeing MUST in the draft and the fact it has been pushed to 
EANTC, it looks to me that it is not just a suggestion.
There is kind of hidden agenda there.
I simply disagree with that. I don’t want customer to ask me if we support your 
vendor specific solution.
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
mailto:jorge.raba...@nokia.com>>
Date: Friday, October 4, 2019 at 11:55
To: Patrice Brissette mailto:pbris...@cisco.com>>, Stephane 
Litkowski mailto:slitkows.i...@gmail.com>>, 
"stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>" 
mailto:stephane.litkow...@orange.com>>
Cc: 
"draft-snr-bess-evpn-loop-prot...@ietf.org<mailto:draft-snr-bess-evpn-loop-prot...@ietf.org>"
 
mailto:draft-snr-bess-evpn-loop-prot...@ietf.org>>,
 "bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>" 
mailto:bess-cha...@ietf.org>>, 
"bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

:-)

Patrice,
Our draft is Informational because it does not require to change the EVPN 
control plane, so we thought it was the right track.

Thanks.
Jorge

From: "Patrice Brissette (pbrisset)" 
mailto:pbris...@cisco.com>>
Date: Friday, October 4, 2019 at 5:17 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" 
mailto:jorge.raba...@nokia.com>>, Stephane Litkowski 
mailto:slitkows.i...@gmail.com>>, 
"stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>" 
mailto:stephane.litkow...@orange.com>>
Cc: 
"draft-snr-bess-evpn-loop-prot...@ietf.org<mailto:draft-snr-bess-evpn-loop-prot...@ietf.org>"
 
mailto:draft-snr-bess-evpn-loop-prot...@ietf.org>>,
 "bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>" 
mailto:bess-cha...@ietf.org>>, 
"bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Jorge,

If that is the case…since it looks like you were able to push the blackhole MAC 
at EANTC (not sure what magic you have done to get privilege), why is your 
draft informal?
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smar

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-04 Thread Patrice Brissette (pbrisset)

This is my last email on this… looks like the message doesn’t go thru …maybe 
there is a loop somewhere.

This informal draft is like a suggestion … It is about an action output of a 
well document procedure in RFC7432.
A suggestion may be vendor specific or not. There is nothing for vendors to 
interop with.

The fact that I’m seeing MUST in the draft and the fact it has been pushed to 
EANTC, it looks to me that it is not just a suggestion.
There is kind of hidden agenda there.
I simply disagree with that. I don’t want customer to ask me if we support your 
vendor specific solution.
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Friday, October 4, 2019 at 11:55
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

:-)

Patrice,
Our draft is Informational because it does not require to change the EVPN 
control plane, so we thought it was the right track.

Thanks.
Jorge

From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 5:17 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Jorge,

If that is the case…since it looks like you were able to push the blackhole MAC 
at EANTC (not sure what magic you have done to get privilege), why is your 
draft informal?
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Friday, October 4, 2019 at 09:20
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

Having a common way to solve loops is beneficial for the community. And if 
there are better ways, we should discuss them and maybe modify the document.

An informational draft that explains how some vendors solve this, I think, is 
relevant to the WG.
There is a public report where you have proof of multivendor support.

http://www.eantc.de/fileadmin/eantc/downloads/News/2019/EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf
(page 11)

Thanks.
Jorge

From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 2:49 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

It is difficult to argue against an informal draft since it does not provides 
any obligation to any vendor to do it. There are many ways for fixing loop and 
I do not see why it needs to be common to all vendor.

That said, a paragraph in RFC7432bis reminding people about the problem is a 
good thing.

Having a separate draft (especially informal) allows customers to request 
compliancy with…. Which I disagree.

Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Friday, October 4, 2019 at 03:13
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

Thank

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-04 Thread Rabadan, Jorge (Nokia - US/Mountain View)

:-)

Patrice,
Our draft is Informational because it does not require to change the EVPN 
control plane, so we thought it was the right track.

Thanks.
Jorge

From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 5:17 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Jorge,

If that is the case…since it looks like you were able to push the blackhole MAC 
at EANTC (not sure what magic you have done to get privilege), why is your 
draft informal?
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Friday, October 4, 2019 at 09:20
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

Having a common way to solve loops is beneficial for the community. And if 
there are better ways, we should discuss them and maybe modify the document.

An informational draft that explains how some vendors solve this, I think, is 
relevant to the WG.
There is a public report where you have proof of multivendor support.

http://www.eantc.de/fileadmin/eantc/downloads/News/2019/EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf
(page 11)

Thanks.
Jorge

From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 2:49 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

It is difficult to argue against an informal draft since it does not provides 
any obligation to any vendor to do it. There are many ways for fixing loop and 
I do not see why it needs to be common to all vendor.

That said, a paragraph in RFC7432bis reminding people about the problem is a 
good thing.

Having a separate draft (especially informal) allows customers to request 
compliancy with…. Which I disagree.

Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Friday, October 4, 2019 at 03:13
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

Thanks for explaining.

So I think you agree with the goal behind the draft, and the fact that has to 
be specified somewhere since you suggest rfc7432bis.
What you are arguing is whether it has to be in an already published document, 
or a yet-to-be-published document. Sure, that should be decided by WG rough 
consensus and chairs.

Some other points to your comments:

-It is informational because it does not change any control plane element 
in RFC7432.

-It explains the whole mac duplication process for the benefit of the reader

-The use of Normative language can be certainly discussed

-Loops are important and we think EVPN specs are not complete without 
addressing them. They can be resolved in different ways. This is an approach 
that tries to have a uniform behavior across implementations. That’s why we 
thought a draft was needed, and in particular, the Service Provider that 
co-authors the draft thought that way.

Thanks.
Jorge


From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 3:43 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-04 Thread Patrice Brissette (pbrisset)

Jorge,

If that is the case…since it looks like you were able to push the blackhole MAC 
at EANTC (not sure what magic you have done to get privilege), why is your 
draft informal?
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Friday, October 4, 2019 at 09:20
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

Having a common way to solve loops is beneficial for the community. And if 
there are better ways, we should discuss them and maybe modify the document.

An informational draft that explains how some vendors solve this, I think, is 
relevant to the WG.
There is a public report where you have proof of multivendor support.

http://www.eantc.de/fileadmin/eantc/downloads/News/2019/EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf
(page 11)

Thanks.
Jorge

From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 2:49 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

It is difficult to argue against an informal draft since it does not provides 
any obligation to any vendor to do it. There are many ways for fixing loop and 
I do not see why it needs to be common to all vendor.

That said, a paragraph in RFC7432bis reminding people about the problem is a 
good thing.

Having a separate draft (especially informal) allows customers to request 
compliancy with…. Which I disagree.

Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Friday, October 4, 2019 at 03:13
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

Thanks for explaining.

So I think you agree with the goal behind the draft, and the fact that has to 
be specified somewhere since you suggest rfc7432bis.
What you are arguing is whether it has to be in an already published document, 
or a yet-to-be-published document. Sure, that should be decided by WG rough 
consensus and chairs.

Some other points to your comments:

-It is informational because it does not change any control plane element 
in RFC7432.

-It explains the whole mac duplication process for the benefit of the reader

-The use of Normative language can be certainly discussed

-Loops are important and we think EVPN specs are not complete without 
addressing them. They can be resolved in different ways. This is an approach 
that tries to have a uniform behavior across implementations. That’s why we 
thought a draft was needed, and in particular, the Service Provider that 
co-authors the draft thought that way.

Thanks.
Jorge


From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 3:43 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Jorge,


As I mentioned, the draft is actually pretty thin as stated in section 4.2: 
This document enhances the EVPN MAC Duplication Mechanism by extending it with 
an optional Loop-protection action that is applied on the duplicate-MAC 
addresses.

The document describes at glance the problem. I agree that the problem is real 
and must be fixed.
However, the extension is simply an action on the MAC duplication mechanism to 
install a blackhole MAC as an option.
I’m not sure why there is a need for a draft. The action can be vendor 
spe

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-04 Thread Rabadan, Jorge (Nokia - US/Mountain View)

Hi Patrice,

Having a common way to solve loops is beneficial for the community. And if 
there are better ways, we should discuss them and maybe modify the document.

An informational draft that explains how some vendors solve this, I think, is 
relevant to the WG.
There is a public report where you have proof of multivendor support.

http://www.eantc.de/fileadmin/eantc/downloads/News/2019/EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf
(page 11)

Thanks.
Jorge

From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 2:49 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

It is difficult to argue against an informal draft since it does not provides 
any obligation to any vendor to do it. There are many ways for fixing loop and 
I do not see why it needs to be common to all vendor.

That said, a paragraph in RFC7432bis reminding people about the problem is a 
good thing.

Having a separate draft (especially informal) allows customers to request 
compliancy with…. Which I disagree.

Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Friday, October 4, 2019 at 03:13
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

Thanks for explaining.

So I think you agree with the goal behind the draft, and the fact that has to 
be specified somewhere since you suggest rfc7432bis.
What you are arguing is whether it has to be in an already published document, 
or a yet-to-be-published document. Sure, that should be decided by WG rough 
consensus and chairs.

Some other points to your comments:

-It is informational because it does not change any control plane element 
in RFC7432.

-It explains the whole mac duplication process for the benefit of the reader

-The use of Normative language can be certainly discussed

-Loops are important and we think EVPN specs are not complete without 
addressing them. They can be resolved in different ways. This is an approach 
that tries to have a uniform behavior across implementations. That’s why we 
thought a draft was needed, and in particular, the Service Provider that 
co-authors the draft thought that way.

Thanks.
Jorge


From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 3:43 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Jorge,


As I mentioned, the draft is actually pretty thin as stated in section 4.2: 
This document enhances the EVPN MAC Duplication Mechanism by extending it with 
an optional Loop-protection action that is applied on the duplicate-MAC 
addresses.

The document describes at glance the problem. I agree that the problem is real 
and must be fixed.
However, the extension is simply an action on the MAC duplication mechanism to 
install a blackhole MAC as an option.
I’m not sure why there is a need for a draft. The action can be vendor 
specific. The fact that the draft is informal makes more sense. However, there 
is a requirement section with *MUST* keywords…. I’m confuse about this…since it 
is informal.

IMO, I would rather add a text to RFC7432bis to suggest what can be done. That 
will highlight the importance of such problem.

Having too many draft dilute the strength of our work.
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Thursday, October 3, 2019 at 08:37
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-04 Thread Patrice Brissette (pbrisset)

Hi,

It is difficult to argue against an informal draft since it does not provides 
any obligation to any vendor to do it. There are many ways for fixing loop and 
I do not see why it needs to be common to all vendor.

That said, a paragraph in RFC7432bis reminding people about the problem is a 
good thing.

Having a separate draft (especially informal) allows customers to request 
compliancy with…. Which I disagree.

Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Friday, October 4, 2019 at 03:13
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

Thanks for explaining.

So I think you agree with the goal behind the draft, and the fact that has to 
be specified somewhere since you suggest rfc7432bis.
What you are arguing is whether it has to be in an already published document, 
or a yet-to-be-published document. Sure, that should be decided by WG rough 
consensus and chairs.

Some other points to your comments:

-It is informational because it does not change any control plane element 
in RFC7432.

-It explains the whole mac duplication process for the benefit of the reader

-The use of Normative language can be certainly discussed

-Loops are important and we think EVPN specs are not complete without 
addressing them. They can be resolved in different ways. This is an approach 
that tries to have a uniform behavior across implementations. That’s why we 
thought a draft was needed, and in particular, the Service Provider that 
co-authors the draft thought that way.

Thanks.
Jorge


From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 3:43 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Jorge,


As I mentioned, the draft is actually pretty thin as stated in section 4.2: 
This document enhances the EVPN MAC Duplication Mechanism by extending it with 
an optional Loop-protection action that is applied on the duplicate-MAC 
addresses.

The document describes at glance the problem. I agree that the problem is real 
and must be fixed.
However, the extension is simply an action on the MAC duplication mechanism to 
install a blackhole MAC as an option.
I’m not sure why there is a need for a draft. The action can be vendor 
specific. The fact that the draft is informal makes more sense. However, there 
is a requirement section with *MUST* keywords…. I’m confuse about this…since it 
is informal.

IMO, I would rather add a text to RFC7432bis to suggest what can be done. That 
will highlight the importance of such problem.

Having too many draft dilute the strength of our work.
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Thursday, October 3, 2019 at 08:37
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

I understand that you may not support the draft.
However, it would help if you clarify the reason why:


-Is it because you don’t think loops should be protected in the way the 
draft describes? If so please elaborate.

-Or is it that you do support the idea in the draft, but think that it does 
not deserves its own document

-Or maybe none of them? :-)

I think it is important to clarify that on the list.

Thank you.
Jorge


From: "Patrice Brissette (pbrisset)" 
Date: Thursday, October 3, 2019 at 2:25 PM
To: Stephane Litkowski , 
"stephane.litkow...@orange.com" 
Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bes

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-04 Thread Rabadan, Jorge (Nokia - US/Mountain View)

Hi Patrice,

Thanks for explaining.

So I think you agree with the goal behind the draft, and the fact that has to 
be specified somewhere since you suggest rfc7432bis.
What you are arguing is whether it has to be in an already published document, 
or a yet-to-be-published document. Sure, that should be decided by WG rough 
consensus and chairs.

Some other points to your comments:

  *   It is informational because it does not change any control plane element 
in RFC7432.
  *   It explains the whole mac duplication process for the benefit of the 
reader
  *   The use of Normative language can be certainly discussed
  *   Loops are important and we think EVPN specs are not complete without 
addressing them. They can be resolved in different ways. This is an approach 
that tries to have a uniform behavior across implementations. That’s why we 
thought a draft was needed, and in particular, the Service Provider that 
co-authors the draft thought that way.

Thanks.
Jorge


From: "Patrice Brissette (pbrisset)" 
Date: Friday, October 4, 2019 at 3:43 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" , 
Stephane Litkowski , "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Jorge,


As I mentioned, the draft is actually pretty thin as stated in section 4.2: 
This document enhances the EVPN MAC Duplication Mechanism by extending it with 
an optional Loop-protection action that is applied on the duplicate-MAC 
addresses.

The document describes at glance the problem. I agree that the problem is real 
and must be fixed.
However, the extension is simply an action on the MAC duplication mechanism to 
install a blackhole MAC as an option.
I’m not sure why there is a need for a draft. The action can be vendor 
specific. The fact that the draft is informal makes more sense. However, there 
is a requirement section with *MUST* keywords…. I’m confuse about this…since it 
is informal.

IMO, I would rather add a text to RFC7432bis to suggest what can be done. That 
will highlight the importance of such problem.

Having too many draft dilute the strength of our work.
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Thursday, October 3, 2019 at 08:37
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

I understand that you may not support the draft.
However, it would help if you clarify the reason why:


-Is it because you don’t think loops should be protected in the way the 
draft describes? If so please elaborate.

-Or is it that you do support the idea in the draft, but think that it does 
not deserves its own document

-Or maybe none of them? :-)

I think it is important to clarify that on the list.

Thank you.
Jorge


From: "Patrice Brissette (pbrisset)" 
Date: Thursday, October 3, 2019 at 2:25 PM
To: Stephane Litkowski , 
"stephane.litkow...@orange.com" 
Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect
Resent-From: 
Resent-To: , , 
, , 

Resent-Date: Thursday, October 3, 2019 at 2:24 PM

Hi,

I do not support that draft. I think it is a very tiny minor update which can 
incorporated in RFC7432bis.

Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: BESS  on behalf of Stephane Litkowski 

Date: Thursday, September 19, 2019 at 05:05
To: "stephane.litkow...@orange.com" 
Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definit

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-03 Thread Patrice Brissette (pbrisset)

Hi Jorge,


As I mentioned, the draft is actually pretty thin as stated in section 4.2: 
This document enhances the EVPN MAC Duplication Mechanism by extending it with 
an optional Loop-protection action that is applied on the duplicate-MAC 
addresses.

The document describes at glance the problem. I agree that the problem is real 
and must be fixed.
However, the extension is simply an action on the MAC duplication mechanism to 
install a blackhole MAC as an option.
I’m not sure why there is a need for a draft. The action can be vendor 
specific. The fact that the draft is informal makes more sense. However, there 
is a requirement section with *MUST* keywords…. I’m confuse about this…since it 
is informal.

IMO, I would rather add a text to RFC7432bis to suggest what can be done. That 
will highlight the importance of such problem.

Having too many draft dilute the strength of our work.
Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Thursday, October 3, 2019 at 08:37
To: Patrice Brissette , Stephane Litkowski 
, "stephane.litkow...@orange.com" 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi Patrice,

I understand that you may not support the draft.
However, it would help if you clarify the reason why:


-Is it because you don’t think loops should be protected in the way the 
draft describes? If so please elaborate.

-Or is it that you do support the idea in the draft, but think that it does 
not deserves its own document

-Or maybe none of them? :-)

I think it is important to clarify that on the list.

Thank you.
Jorge


From: "Patrice Brissette (pbrisset)" 
Date: Thursday, October 3, 2019 at 2:25 PM
To: Stephane Litkowski , 
"stephane.litkow...@orange.com" 
Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect
Resent-From: 
Resent-To: , , 
, , 

Resent-Date: Thursday, October 3, 2019 at 2:24 PM

Hi,

I do not support that draft. I think it is a very tiny minor update which can 
incorporated in RFC7432bis.

Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: BESS  on behalf of Stephane Litkowski 

Date: Thursday, September 19, 2019 at 05:05
To: "stephane.litkow...@orange.com" 
Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definitely 
this poll, I would like to let the opportunity to other vendors to raise their 
voice and support the draft especially if they have implementations.
I will let an additional week.

Stephane


On Mon, Sep 2, 2019 at 4:29 PM 
mailto:stephane.litkow...@orange.com>> wrote:
Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/




[Orange logo]<http://www.orange.com/>

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-03 Thread slitkows.ietf

Hi all,

 

This adoption call is running for a long time. The WG adoption was a bit tough 
or at least unusual.

 

I hold on this call waiting for a sync-up with my co-chair to decide how we 
proceed.

 

We keep you posted asap.

 

Stephane

 

 

From: Rabadan, Jorge (Nokia - US/Mountain View)  
Sent: jeudi 3 octobre 2019 00:51
To: Ali Sajassi (sajassi) ; stephane.litkow...@orange.com; 
bess@ietf.org; draft-snr-bess-evpn-loop-prot...@ietf.org
Cc: bess-cha...@ietf.org
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

 

Hi Ali,

 

Thank you for your feedback.

 

The draft is going through a WG adoption call, and although during the first 
part of the adoption call there was not much feedback, the draft has now fair 
good support from several Service Providers and vendors. We also got the 
feedback from a Service Provider that the topic is important enough to deserve 
a separate document where the WG can throw feedback and can be improved to make 
sure all cases are covered. So I believe it has to be adopted as an 
(Informational) WG document. 

 

When 7432bis is WG adopted (it’s not even published yet!), as a WG we can 
decide if loop-protection is part of it or not. My co-authors, other WG members 
and chairs can express their opinion as well.

 

About backhole mac vs ACL – backhole is more generic. You can implement it via 
ACL or flags in the bridge table or any other way. We don’t mandate how to do 
it, only the required behavior. If you do it via an “automatic” ACL, that’s 
your implementation choice. 

 

About the timer, it would be good if you can elaborate why it is questionable. 
We are very interested in your feedback and we would like to encourage the WG 
to also participate in the discussion, if the WG thinks loops are an important 
topic.

 

Thanks.

Jorge

 

 

From: "Ali Sajassi (sajassi)" mailto:saja...@cisco.com> >
Date: Thursday, October 3, 2019 at 8:17 AM
To: "stephane.litkow...@orange.com <mailto:stephane.litkow...@orange.com> " 
mailto:stephane.litkow...@orange.com> >, 
"bess@ietf.org <mailto:bess@ietf.org> " mailto:bess@ietf.org> 
>, "draft-snr-bess-evpn-loop-prot...@ietf.org 
<mailto:draft-snr-bess-evpn-loop-prot...@ietf.org> " 
mailto:draft-snr-bess-evpn-loop-prot...@ietf.org> >
Cc: "bess-cha...@ietf.org <mailto:bess-cha...@ietf.org> " mailto:bess-cha...@ietf.org> >
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect
Resent-From: mailto:alias-boun...@ietf.org> >
Resent-To: mailto:jorge.raba...@nokia.com> >, 
mailto:senthil.sathap...@nokia.com> >, 
mailto:kiran.naga...@nokia.com> >, 
mailto:julio.buenohernan...@telefonica.com> >, 
mailto:josemanuel.crespogar...@telefonica.com> >
Resent-Date: Thursday, October 3, 2019 at 8:17 AM

 

 

We need to cover the loop protection for EVPN as we needed to cover MAC 
duplicate detection in EVPN. However, I am wondering why not simply cover it in 
couple of paragraphs in RFC7432bis. I made this comment when this draft was 
presented for the first time. My rational for it is as follow:

 

1)  The detection mechanism for loop protection is identical to MAC 
duplicate detection as described in section 15.1 of RFC 7432. As the matter of 
fact the procedure described in section 15.1 of RFC 7432 is repeated in this 
new draft.

2)  The only difference is action taken. For MAC duplicate detection, we 
stop advertising the learned MAC address; whereas, for loop prevention, we 
install an ACL for the duplicate MAC.

3)  We should also try to use commonly used terms as opposed to inventing 
new terms – i.e., instead of creating a new section in describing what 
blackhole MAC is, we should simply say we want to install ACL for MAC SA (to 
get discarded). 

4)  The new timer for flushing MAC SA and restarting the process IMO is 
questionable and should not be used.

 

Again, if we were not doing RFC7432bis, I would have been very supportive of 
this draft as we do need to cover loop protection; however, given that we can 
cover this loop protection by just adding one or two paragraphs to section 
15.1, then I really don’t see the need to create unnecessary reading materials 
for our community.

 

Cheers,

Ali

 

 

 

From: BESS mailto:bess-boun...@ietf.org> > on behalf of 
"stephane.litkow...@orange.com <mailto:stephane.litkow...@orange.com> " 
mailto:stephane.litkow...@orange.com> >
Date: Monday, September 2, 2019 at 7:29 AM
To: "bess@ietf.org <mailto:bess@ietf.org> " mailto:bess@ietf.org> >, "draft-snr-bess-evpn-loop-prot...@ietf.org 
<mailto:draft-snr-bess-evpn-loop-prot...@ietf.org> " 
mailto:draft-snr-bess-evpn-loop-prot...@ietf.org> >
Cc: "bess-cha...@ietf.org <mailto:bess-cha...@ietf.org> " mailto:bess-cha...@ietf.org&

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-03 Thread Rabadan, Jorge (Nokia - US/Mountain View)

Hi Patrice,

I understand that you may not support the draft.
However, it would help if you clarify the reason why:


  *   Is it because you don’t think loops should be protected in the way the 
draft describes? If so please elaborate.
  *   Or is it that you do support the idea in the draft, but think that it 
does not deserves its own document
  *   Or maybe none of them? :-)

I think it is important to clarify that on the list.

Thank you.
Jorge


From: "Patrice Brissette (pbrisset)" 
Date: Thursday, October 3, 2019 at 2:25 PM
To: Stephane Litkowski , 
"stephane.litkow...@orange.com" 
Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect
Resent-From: 
Resent-To: , , 
, , 

Resent-Date: Thursday, October 3, 2019 at 2:24 PM

Hi,

I do not support that draft. I think it is a very tiny minor update which can 
incorporated in RFC7432bis.

Regards,
Patrice Brissette, Principal Engineer
Cisco Systems
Help us track your SP SR/EVPN Customer Opportunity/Status by filling these 
forms: Segment 
Routing<https://app.smartsheet.com/b/form/185833ace35b4894b324dfb8afbd2060> / 
EVPN<https://app.smartsheet.com/b/form/136bd5c3a22641bf92316523e79d6f22>

http://e-vpn.io, http://go2.cisco.com/evpn




From: BESS  on behalf of Stephane Litkowski 

Date: Thursday, September 19, 2019 at 05:05
To: "stephane.litkow...@orange.com" 
Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definitely 
this poll, I would like to let the opportunity to other vendors to raise their 
voice and support the draft especially if they have implementations.
I will let an additional week.

Stephane


On Mon, Sep 2, 2019 at 4:29 PM 
mailto:stephane.litkow...@orange.com>> wrote:
Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/




[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
  NEW !
mobile: +33 6 71 63 27 50 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
  NEW !
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>


_



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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-03 Thread Rabadan, Jorge (Nokia - US/Mountain View)

Hi Ali,

Thank you for your feedback.

The draft is going through a WG adoption call, and although during the first 
part of the adoption call there was not much feedback, the draft has now fair 
good support from several Service Providers and vendors. We also got the 
feedback from a Service Provider that the topic is important enough to deserve 
a separate document where the WG can throw feedback and can be improved to make 
sure all cases are covered. So I believe it has to be adopted as an 
(Informational) WG document.

When 7432bis is WG adopted (it’s not even published yet!), as a WG we can 
decide if loop-protection is part of it or not. My co-authors, other WG members 
and chairs can express their opinion as well.

About backhole mac vs ACL – backhole is more generic. You can implement it via 
ACL or flags in the bridge table or any other way. We don’t mandate how to do 
it, only the required behavior. If you do it via an “automatic” ACL, that’s 
your implementation choice.

About the timer, it would be good if you can elaborate why it is questionable. 
We are very interested in your feedback and we would like to encourage the WG 
to also participate in the discussion, if the WG thinks loops are an important 
topic.

Thanks.
Jorge


From: "Ali Sajassi (sajassi)" 
Date: Thursday, October 3, 2019 at 8:17 AM
To: "stephane.litkow...@orange.com" , 
"bess@ietf.org" , "draft-snr-bess-evpn-loop-prot...@ietf.org" 

Cc: "bess-cha...@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect
Resent-From: 
Resent-To: , , 
, , 

Resent-Date: Thursday, October 3, 2019 at 8:17 AM


We need to cover the loop protection for EVPN as we needed to cover MAC 
duplicate detection in EVPN. However, I am wondering why not simply cover it in 
couple of paragraphs in RFC7432bis. I made this comment when this draft was 
presented for the first time. My rational for it is as follow:


1)  The detection mechanism for loop protection is identical to MAC 
duplicate detection as described in section 15.1 of RFC 7432. As the matter of 
fact the procedure described in section 15.1 of RFC 7432 is repeated in this 
new draft.

2)  The only difference is action taken. For MAC duplicate detection, we 
stop advertising the learned MAC address; whereas, for loop prevention, we 
install an ACL for the duplicate MAC.

3)  We should also try to use commonly used terms as opposed to inventing 
new terms – i.e., instead of creating a new section in describing what 
blackhole MAC is, we should simply say we want to install ACL for MAC SA (to 
get discarded).

4)  The new timer for flushing MAC SA and restarting the process IMO is 
questionable and should not be used.

Again, if we were not doing RFC7432bis, I would have been very supportive of 
this draft as we do need to cover loop protection; however, given that we can 
cover this loop protection by just adding one or two paragraphs to section 
15.1, then I really don’t see the need to create unnecessary reading materials 
for our community.

Cheers,
Ali



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

Date: Monday, September 2, 2019 at 7:29 AM
To: "bess@ietf.org" , 
"draft-snr-bess-evpn-loop-prot...@ietf.org" 

Cc: "bess-cha...@ietf.org" 
Subject: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/




[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
  NEW !
mobile: +33 6 71 63 27 50 
<https://monsi.sso.francete

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-03 Thread Ali Sajassi (sajassi)


We need to cover the loop protection for EVPN as we needed to cover MAC 
duplicate detection in EVPN. However, I am wondering why not simply cover it in 
couple of paragraphs in RFC7432bis. I made this comment when this draft was 
presented for the first time. My rational for it is as follow:


  1.  The detection mechanism for loop protection is identical to MAC duplicate 
detection as described in section 15.1 of RFC 7432. As the matter of fact the 
procedure described in section 15.1 of RFC 7432 is repeated in this new draft.
  2.  The only difference is action taken. For MAC duplicate detection, we stop 
advertising the learned MAC address; whereas, for loop prevention, we install 
an ACL for the duplicate MAC.
  3.  We should also try to use commonly used terms as opposed to inventing new 
terms – i.e., instead of creating a new section in describing what blackhole 
MAC is, we should simply say we want to install ACL for MAC SA (to get 
discarded).
  4.  The new timer for flushing MAC SA and restarting the process IMO is 
questionable and should not be used.

Again, if we were not doing RFC7432bis, I would have been very supportive of 
this draft as we do need to cover loop protection; however, given that we can 
cover this loop protection by just adding one or two paragraphs to section 
15.1, then I really don’t see the need to create unnecessary reading materials 
for our community.

Cheers,
Ali



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

Date: Monday, September 2, 2019 at 7:29 AM
To: "bess@ietf.org" , 
"draft-snr-bess-evpn-loop-prot...@ietf.org" 

Cc: "bess-cha...@ietf.org" 
Subject: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/




[Orange logo]

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 

  NEW !
mobile: +33 6 71 63 27 50 

  NEW !
stephane.litkow...@orange.com


_



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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-02 Thread Wen Lin

Support.  It is a very useful to EVPN.

Wen

From: BESS  on behalf of "Oya Luengo, Roberto (Nokia - 
US/Mountain View)" 
Date: Wednesday, October 2, 2019 at 2:01 PM
To: Stephane Litkowski , 
"stephane.litkow...@orange.com" 
Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Support

From: BESS  On Behalf Of Stephane Litkowski
Sent: Thursday, September 19, 2019 16:06
To: stephane.litkow...@orange.com
Cc: draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org; 
bess@ietf.org
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definitely 
this poll, I would like to let the opportunity to other vendors to raise their 
voice and support the draft especially if they have implementations.
I will let an additional week.

Stephane

On Mon, Sep 2, 2019 at 4:29 PM 
mailto:stephane.litkow...@orange.com>> wrote:
Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] 
https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/__;!8WoA6RjC81c!S0E43uyJeLkK7BR14WqqIExBidS7nhMJefx_y5jBClb0yVgwy5UMh1HV59JpPg$>

[Orange 
logo]<https://urldefense.com/v3/__http:/www.orange.com/__;!8WoA6RjC81c!S0E43uyJeLkK7BR14WqqIExBidS7nhMJefx_y5jBClb0yVgwy5UMh1G_RMEOKw$>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 
<https://urldefense.com/v3/__https:/monsi.sso.francetelecom.fr/index.asp?target=http*3A*2F*2Fclicvoice.sso.francetelecom.fr*2FClicvoiceV2*2FToolBar.do*3Faction*3Ddefault*26rootservice*3DSIGNATURE*26to*3D*33*202*2023*2028*2049*2083*20__;JSUlJSUlJSUlJSUrJSUlJSUl!8WoA6RjC81c!S0E43uyJeLkK7BR14WqqIExBidS7nhMJefx_y5jBClb0yVgwy5UMh1EMsq5fHw$>
  NEW !
mobile: +33 6 71 63 27 50 
<https://urldefense.com/v3/__https:/monsi.sso.francetelecom.fr/index.asp?target=http*3A*2F*2Fclicvoice.sso.francetelecom.fr*2FClicvoiceV2*2FToolBar.do*3Faction*3Ddefault*26rootservice*3DSIGNATURE*26to*3D*33*206*2037*2086*2097*2052*20__;JSUlJSUlJSUlJSUrJSUlJSUl!8WoA6RjC81c!S0E43uyJeLkK7BR14WqqIExBidS7nhMJefx_y5jBClb0yVgwy5UMh1HbQElheg$>
  NEW !
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>

_

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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-02 Thread Oya Luengo, Roberto (Nokia - US/Mountain View)

Support

From: BESS  On Behalf Of Stephane Litkowski
Sent: Thursday, September 19, 2019 16:06
To: stephane.litkow...@orange.com
Cc: draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org; 
bess@ietf.org
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definitely 
this poll, I would like to let the opportunity to other vendors to raise their 
voice and support the draft especially if they have implementations.
I will let an additional week.

Stephane

On Mon, Sep 2, 2019 at 4:29 PM 
mailto:stephane.litkow...@orange.com>> wrote:
Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
  NEW !
mobile: +33 6 71 63 27 50 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
  NEW !
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>

_

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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-02 Thread Siddhesh Dindorkar

I support this draft as it will help consolidate the implementations

Thanks

On Tue, Oct 1, 2019, 8:34 AM Bidgoli, Hooman (Nokia - CA/Ottawa) <
hooman.bidg...@nokia.com> wrote:

> Support, useful draft
>
>
>
> Regards
>
>
>
> Hooman
>
>
>
> *From:* BESS  *On Behalf Of *Van De Velde, Gunter
> (Nokia - BE/Antwerp)
> *Sent:* Monday, September 30, 2019 10:59 PM
> *To:* Stephane Litkowski ;
> stephane.litkow...@orange.com
> *Cc:* draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org;
> bess@ietf.org
> *Subject:* Re: [bess] WG adoption poll and IPR poll for
> draft-snr-bess-evpn-loop-protect
>
>
>
> Yes, Support adoption.
>
>
>
> G/
>
>
>
> *From:* BESS  *On Behalf Of *Stephane Litkowski
> *Sent:* Thursday, September 19, 2019 16:06
> *To:* stephane.litkow...@orange.com
> *Cc:* draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org;
> bess@ietf.org
> *Subject:* Re: [bess] WG adoption poll and IPR poll for
> draft-snr-bess-evpn-loop-protect
>
>
>
> Hi,
>
>
>
> The poll has ended.
>
> I haven't seen a lot of support from the various vendor while Jorge has
> mentioned that there are multiple implementations. Before closing
> definitely this poll, I would like to let the opportunity to other vendors
> to raise their voice and support the draft especially if they have
> implementations.
>
> I will let an additional week.
>
>
>
> Stephane
>
>
>
>
>
> On Mon, Sep 2, 2019 at 4:29 PM  wrote:
>
> Hi,
>
>
>
> This email begins a two-weeks WG adoption poll
> for draft-snr-bess-evpn-loop-protect-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 16th September 2019.
>
>
>
> Regards,
>
> Stephane and Matthew
>
>
>
> [1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/
>
>
>
>
>
>
>
>
>
> [image: Orange logo] <http://www.orange.com/>
>
>
>
> *Stephane Litkowski *
> Network Architect
> Orange/SCE/EQUANT/OINIS/NET
>
> Orange Expert Future Networks
>
> phone: +33 2 23 *06* 49 83
> <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
>  NEW !
> mobile: +33 6 71 63 27 50
> <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
>  NEW !
> stephane.litkow...@orange.com
>
>
>
> _
>
>
>
> 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 poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-02 Thread Walsh, Brian (Nokia - SG/Singapore)

+1 support.

Thx,
Brian

From: BESS  on behalf of "Van De Velde, Gunter (Nokia - 
BE/Antwerp)" 
Date: Tuesday, 1 October 2019 at 11:59
To: Stephane Litkowski , 
"stephane.litkow...@orange.com" 
Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Yes, Support adoption.

G/

From: BESS  On Behalf Of Stephane Litkowski
Sent: Thursday, September 19, 2019 16:06
To: stephane.litkow...@orange.com
Cc: draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org; 
bess@ietf.org
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definitely 
this poll, I would like to let the opportunity to other vendors to raise their 
voice and support the draft especially if they have implementations.
I will let an additional week.

Stephane

On Mon, Sep 2, 2019 at 4:29 PM 
mailto:stephane.litkow...@orange.com>> wrote:
Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
  NEW !
mobile: +33 6 71 63 27 50 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
  NEW !
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>

_

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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-10-01 Thread Bidgoli, Hooman (Nokia - CA/Ottawa)

Support, useful draft

Regards

Hooman

From: BESS  On Behalf Of Van De Velde, Gunter (Nokia - 
BE/Antwerp)
Sent: Monday, September 30, 2019 10:59 PM
To: Stephane Litkowski ; stephane.litkow...@orange.com
Cc: draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org; 
bess@ietf.org
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Yes, Support adoption.

G/

From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of 
Stephane Litkowski
Sent: Thursday, September 19, 2019 16:06
To: stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>
Cc: 
draft-snr-bess-evpn-loop-prot...@ietf.org<mailto:draft-snr-bess-evpn-loop-prot...@ietf.org>;
 bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>; 
bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definitely 
this poll, I would like to let the opportunity to other vendors to raise their 
voice and support the draft especially if they have implementations.
I will let an additional week.

Stephane

On Mon, Sep 2, 2019 at 4:29 PM 
mailto:stephane.litkow...@orange.com>> wrote:
Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
  NEW !
mobile: +33 6 71 63 27 50 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
  NEW !
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>

_

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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-09-30 Thread Henderickx, Wim (Nokia - BE/Antwerp)

Support adoption,  as this is useful addition to EPVN

From: BESS  on behalf of Gunter VAN DE VELDE 

Date: Tuesday, 1 October 2019 at 04:59
To: Stephane Litkowski , Stephane Litkowski 

Cc: "draft-snr-bess-evpn-loop-prot...@ietf.org" 
, "bess-cha...@ietf.org" 
, "bess@ietf.org" 
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Yes, Support adoption.

G/

From: BESS  On Behalf Of Stephane Litkowski
Sent: Thursday, September 19, 2019 16:06
To: stephane.litkow...@orange.com
Cc: draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org; 
bess@ietf.org
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definitely 
this poll, I would like to let the opportunity to other vendors to raise their 
voice and support the draft especially if they have implementations.
I will let an additional week.

Stephane

On Mon, Sep 2, 2019 at 4:29 PM 
mailto:stephane.litkow...@orange.com>> wrote:
Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
  NEW !
mobile: +33 6 71 63 27 50 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
  NEW !
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>

_

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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-09-30 Thread Van De Velde, Gunter (Nokia - BE/Antwerp)

Yes, Support adoption.

G/

From: BESS  On Behalf Of Stephane Litkowski
Sent: Thursday, September 19, 2019 16:06
To: stephane.litkow...@orange.com
Cc: draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org; 
bess@ietf.org
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definitely 
this poll, I would like to let the opportunity to other vendors to raise their 
voice and support the draft especially if they have implementations.
I will let an additional week.

Stephane

On Mon, Sep 2, 2019 at 4:29 PM 
mailto:stephane.litkow...@orange.com>> wrote:
Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
  NEW !
mobile: +33 6 71 63 27 50 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
  NEW !
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>

_

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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-09-30 Thread Khatri, Paresh (Nokia - AU/Brisbane)

I support this draft.

Regards,
Paresh

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

Date: Tuesday, 3 September 2019 at 12:29 am
To: "bess@ietf.org" , 
"draft-snr-bess-evpn-loop-prot...@ietf.org" 

Cc: "bess-cha...@ietf.org" 
Subject: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

[Orange logo]

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 

  NEW !
mobile: +33 6 71 63 27 50 

  NEW !
stephane.litkow...@orange.com

_

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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-09-27 Thread Gyan Mishra



As a technical representative of Verizon from an operator and network designer 
perspective I support the draft as it stands and don’t know of any non 
disclosed IPRs.



Regards,

Gyan S. Mishra
IT Network Engineering & Technology 
Verizon Communications Inc. (VZ)
13101 Columbia Pike FDC1 3rd Floor
Silver Spring, MD 20904
United States
Phone: 301 502-1347
Email: gyan.s.mis...@verizon.com
www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERTSent from my iPhone

> On Sep 2, 2019, at 11:10 AM, Rabadan, Jorge (Nokia - US/Mountain View) 
>  wrote:
> 
> As a co-author I support this document for WG adoption. It has multiple 
> implementations and it was tested between different vendors at the last EANTC 
> interoperability event.
>  
> I am not aware of any IPR relevant to this document.
>  
> Thank you.
> Jorge
>  
> From: "stephane.litkow...@orange.com" 
> Date: Monday, September 2, 2019 at 4:29 PM
> To: "bess@ietf.org" , 
> "draft-snr-bess-evpn-loop-prot...@ietf.org" 
> 
> Cc: "bess-cha...@ietf.org" 
> Subject: WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect
> Resent-From: 
> Resent-To: , , 
> , , 
> 
> Resent-Date: Monday, September 2, 2019 at 4:29 PM
>  
> Hi,
>  
> This email begins a two-weeks WG adoption poll for 
> draft-snr-bess-evpn-loop-protect-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 16th September 2019.  
>  
> Regards,
> Stephane and Matthew
>  
> [1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/
>  
>  
>  
>  
> 
>  
> Stephane Litkowski 
> Network Architect 
> Orange/SCE/EQUANT/OINIS/NET
> Orange Expert Future Networks
> phone: +33 2 23 06 49 83  NEW !
> mobile: +33 6 71 63 27 50  NEW !
> stephane.litkow...@orange.com
>  
> _
>  
> 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 poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-09-09 Thread JOSE MANUEL CRESPO GARCIA

Hi

As a co-author, I support the adoption. I am not aware of any 
IPR relevant to this document.


Regards



From: "stephane.litkow...@orange.com" 
mailto:stephane.litkow...@orange.com>>
Date: Monday, September 2, 2019 at 4:29 PM
To: "bess@ietf.org" 
mailto:bess@ietf.org>>, 
"draft-snr-bess-evpn-loop-prot...@ietf.org"
 
mailto:draft-snr-bess-evpn-loop-prot...@ietf.org>>
Cc: "bess-cha...@ietf.org" 
mailto:bess-cha...@ietf.org>>
Subject: WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect
Resent-From: mailto:alias-boun...@ietf.org>>
Resent-To: mailto:jorge.raba...@nokia.com>>, 
mailto:senthil.sathap...@nokia.com>>, 
mailto:kiran.naga...@nokia.com>>, 
mailto:julio.buenohernan...@telefonica.com>>,
 
mailto:josemanuel.crespogar...@telefonica.com>>
Resent-Date: Monday, September 2, 2019 at 4:29 PM

Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/




[Orange logo]

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 

  NEW !
mobile: +33 6 71 63 27 50 

  NEW !
stephane.litkow...@orange.com


_



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.



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede 
contener información privilegiada o confidencial y es para uso exclusivo de la 
persona o entidad de destino. Si no es usted. el destinatario indicado, queda 
notificado de que la lectura, utilización, divulgación y/o copia sin 
autorización puede estar prohibida en virtud de la legislación vigente. Si ha 
recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente 
por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential 
information intended only for the use of the individual or entity named above. 
If the reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this transmission in error, do not 
read it. Please immediately reply to the sender that you have received this 
communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode 
conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa 
ou

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-09-03 Thread Nagaraj, Kiran (Nokia - US/Mountain View)

I am unaware of any undisclosed IPR related to this draft.
Thanks
Kiran

From: stephane.litkow...@orange.com 
Sent: Monday, September 02, 2019 7:29 AM
To: bess@ietf.org; draft-snr-bess-evpn-loop-prot...@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

[Orange logo]

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 

  NEW !
mobile: +33 6 71 63 27 50 

  NEW !
stephane.litkow...@orange.com

_

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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-09-03 Thread Sathappan, Senthil (Nokia - US/Mountain View)

As a co-author, I support the adoption. I am not aware of any IPR relevant to 
this document.
Thanks,
Senthil.
From: stephane.litkow...@orange.com 
Sent: Monday, September 02, 2019 7:29 AM
To: bess@ietf.org; draft-snr-bess-evpn-loop-prot...@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

[Orange logo]

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 

  NEW !
mobile: +33 6 71 63 27 50 

  NEW !
stephane.litkow...@orange.com

_

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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-09-02 Thread Jeff Tantsura

Yes/support adoption 

Regards,
Jeff

> On Sep 2, 2019, at 07:29,  
>  wrote:
> 
> Hi,
>  
> This email begins a two-weeks WG adoption poll for 
> draft-snr-bess-evpn-loop-protect-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 16th September 2019.  
>  
> Regards,
> Stephane and Matthew
>  
> [1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/
>  
>  
>  
>  
> 
>  
> Stephane Litkowski 
> Network Architect 
> Orange/SCE/EQUANT/OINIS/NET
> Orange Expert Future Networks
> phone: +33 2 23 06 49 83  NEW !
> mobile: +33 6 71 63 27 50  NEW !
> stephane.litkow...@orange.com
>  
> _
> 
> 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 poll and IPR poll for draft-snr-bess-evpn-loop-protect

2019-09-02 Thread Rabadan, Jorge (Nokia - US/Mountain View)

As a co-author I support this document for WG adoption. It has multiple 
implementations and it was tested between different vendors at the last EANTC 
interoperability event.

I am not aware of any IPR relevant to this document.

Thank you.
Jorge

From: "stephane.litkow...@orange.com" 
Date: Monday, September 2, 2019 at 4:29 PM
To: "bess@ietf.org" , 
"draft-snr-bess-evpn-loop-prot...@ietf.org" 

Cc: "bess-cha...@ietf.org" 
Subject: WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect
Resent-From: 
Resent-To: , , 
, , 

Resent-Date: Monday, September 2, 2019 at 4:29 PM

Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/




[Orange logo]

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 

  NEW !
mobile: +33 6 71 63 27 50 

  NEW !
stephane.litkow...@orange.com


_



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

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

Re: [bess] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

26 matches

Site Navigation

Mail list logo

Footer information