Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

[Gaurav Dawra]

Support.

Sent from my iPhone

> On Mar 26, 2018, at 7:21 AM,  
>  wrote:
> 
> Hello working group,
>  
> This email starts a two-week Working Group Last Call on 
> draft-ietf-bess-evpn-df-election-framework-00 [1]
>  
> This poll runs until *the 9th of April*.
>  
> 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. The Document won't progress without answers from 
> all the Authors and Contributors.
>  
> Currently no IPR has been disclosed 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.
>  
> We are also polling for any existing implementation.
>  
> Thank you
>  
> Matthew, Stéphane
> bess chairs
>  
> [1] 
> https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/
>  
> _
> 
> 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] WGLC on draft-ietf-bess-evpn-df-election-framework

[Rabadan, Jorge (Nokia - US/Mountain View)]

Hi Stephane,

Please see in-line.
Thanks.
Jorge

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

Date: Tuesday, March 27, 2018 at 8:48 AM
To: "bess@ietf.org" 
Subject: Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

Hi Authors,

Speaking as a WG member, I have two comments:

-  As I have pointed during the BESS meeting, it would be good to have 
a clear definition of what is a DF type vs a capability.
[JORGE] yes, we can clarify this in the next rev along with any other comments 
made during this LC.


-  I think it would be good to have the draft telling that the 
implementation of HRW and AC-DF are optionals.
[JORGE] Is that necessary? Since the draft is not updating RFC7432, aren’t 
those options implicitly optional for RFC7432 implementations?

Brgds,

Stephane

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Monday, March 26, 2018 16:21
To: bess@ietf.org
Subject: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework


Hello working group,



This email starts a two-week Working Group Last Call on 
draft-ietf-bess-evpn-df-election-framework-00 [1]



This poll runs until *the 9th of April*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



Currently no IPR has been disclosed 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.



We are also polling for any existing implementation.



Thank you



Matthew, Stéphane

bess chairs



[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/



_



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

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

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

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



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

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

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

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

Thank you.

_



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

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

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

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



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

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

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

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

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

[bess] Protocol Action: 'Extensions to BGP Signaled Pseudowires to support Flow-Aware Transport Labels' to Proposed Standard (draft-ietf-bess-fat-pw-bgp-04.txt)

[The IESG]

The IESG has approved the following document:
- 'Extensions to BGP Signaled Pseudowires to support Flow-Aware Transport
   Labels'
  (draft-ietf-bess-fat-pw-bgp-04.txt) as Proposed Standard

This document is the product of the BGP Enabled ServiceS Working Group.

The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-fat-pw-bgp/





Technical Summary

   This draft defines protocol extensions required to synchronize flow
   label states among PEs when using the BGP-based signaling procedures.
   These protocol extensions are equally applicable to point-to-point
   Layer2 Virtual Private Networks (L2VPNs). This draft updates RFC 4761
   by defining new flags in the Control Flags field of the Layer2 Info
   Extended Community.

Working Group Summary

  Normal process, nothing special to highlight.

Document Quality

  At least one implementation exists. The Document is fairly simple.

Personnel

   Martin Vigoureux is the Document Shepherd
   Alvaro Retana is the Responsible AD

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

[bess] Last Call: (IP Prefix Advertisement in EVPN) to Proposed Standard

[The IESG]

The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - 'IP Prefix Advertisement in EVPN'
   as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
i...@ietf.org mailing lists by 2018-04-10. Exceptionally, comments may be
sent to i...@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   EVPN provides a flexible control plane that allows intra-subnet
   connectivity in an MPLS and/or NVO-based network. In some networks,
   there is also a need for a dynamic and efficient inter-subnet
   connectivity across Tenant Systems and End Devices that can be
   physical or virtual and do not necessarily participate in dynamic
   routing protocols. This document defines a new EVPN route type for
   the advertisement of IP Prefixes and explains some use-case examples
   where this new route-type is used.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-prefix-advertisement/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-prefix-advertisement/ballot/


No IPR declarations have been submitted directly on this I-D.




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

Re: [bess] AD Review of draft-ietf-bess-evpn-prefix-advertisement-09

[Alvaro Retana]

Thanks Jorge!

I started the IETF LC.

Alvaro.

On February 27, 2018 at 4:41:35 PM, Rabadan, Jorge (Nokia - US/Mountain
View) (jorge.raba...@nokia.com) wrote:

Thank you so much for such a thorough review.

You had very good points here (see in-line for my replies).

I posted rev 10 addressing all your comments.
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

[Sathappan, Senthil (Nokia - US/Mountain View)]

Support.

Not aware of any relevant IPR related to this document.

Thanks,

Senthil.

From: BESS > on behalf of 
"stephane.litkow...@orange.com" 
>
Date: Monday, March 26, 2018 at 3:21 PM
To: "bess@ietf.org" >
Subject: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework


Hello working group,



This email starts a two-week Working Group Last Call on 
draft-ietf-bess-evpn-df-election-framework-00 [1]



This poll runs until *the 9th of April*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



Currently no IPR has been disclosed 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.



We are also polling for any existing implementation.



Thank you



Matthew, Stéphane

bess chairs



[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/



_



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] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

[UTTARO, JAMES]

Mankamana,

If not a requirements draft than a usage draft indicating what 
solutions are applicable for the different inter-connect solutions. I think 
this would be quite useful to architects/designers..

Thanks,
Jim Uttaro

From: Mankamana Mishra (mankamis) [mailto:manka...@cisco.com]
Sent: Tuesday, March 27, 2018 11:32 AM
To: UTTARO, JAMES ; John E Drake ; Rabadan, 
Jorge (Nokia - US/Mountain View) ; Eric Rosen 
; Sandy Breeze ; Satya Mohanty 
(satyamoh) 
Cc: bess@ietf.org; Ali Sajassi (sajassi) 
Subject: Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on 
problem description

Hi Jim,
About your pointing of writing down requirement draft for multicast. I had 
discussion with Ali in this IETF (After we discussed). But looks like it might 
be too late for now to write requirement, as there are many multicast related 
solution draft already in BESS working group.  But still if majority thinks we 
need it. We can think about it.

Thanks
Mankamana

From: BESS > on behalf of 
"UTTARO, JAMES" >
Date: Monday, March 26, 2018 at 10:46 AM
To: "Ali Sajassi (sajassi)" >, John 
E Drake >, "Rabadan, Jorge (Nokia 
- US/Mountain View)" >, 
Eric Rosen >, Sandy Breeze 
>, "Satya Mohanty 
(satyamoh)" >
Cc: "bess@ietf.org" >
Subject: Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on 
problem description

Ali,

So, is this going to be a family of drafts dealing with 
inter-connection aspects across a set of use cases ? Would it be useful to 
right up a requirements draft like we did with EVPN??

Thanks,
Jim Uttaro

From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Monday, March 26, 2018 1:20 PM
To: UTTARO, JAMES >; John E Drake 
>; Rabadan, Jorge (Nokia - 
US/Mountain View) >; 
Eric Rosen >; Sandy Breeze 
>; Satya Mohanty 
(satyamoh) >
Cc: bess@ietf.org
Subject: Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on 
problem description

Hi Jim,

draft-mohanty-bess-evpn-bum-opt will focus on L2 only between EVPN overlay 
(VxLAN) access domain and EVPN MPLS core. Connectivity EVPN IRB core (or EVPN 
L3 core) will be covered in the other drafts that I mentioned below because 
they are  already doing it for other use cases.

Cheers,
Ali

From: "UTTARO, JAMES" >
Date: Monday, March 26, 2018 at 10:03 AM
To: Cisco Employee >, John E Drake 
>, "Rabadan, Jorge (Nokia - 
US/Mountain View)" >, 
Eric Rosen >, Sandy Breeze 
>, "Satya Mohanty 
(satyamoh)" >
Cc: "bess@ietf.org" >
Subject: RE: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on 
problem description

Ali,

So is the plan to incorporate Sandy’s work in these docs??

Thanks,
Jim Uttaro


From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Monday, March 26, 2018 11:55 AM
To: UTTARO, JAMES >; John E Drake 
>; Rabadan, Jorge (Nokia - 
US/Mountain View) >; 
Eric Rosen >; Sandy Breeze 
>; Satya Mohanty 
(satyamoh) >
Cc: bess@ietf.org; Ali Sajassi (sajassi) 
>
Subject: Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on 
problem description


Hi Jim,

Wrt multicast for L2 EVPN<-> L3 EVPN, that should be covered in corresponding 
EVPN multicast drafts:

Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

[Mankamana Mishra (mankamis)]

Hi Jim,
About your pointing of writing down requirement draft for multicast. I had 
discussion with Ali in this IETF (After we discussed). But looks like it might 
be too late for now to write requirement, as there are many multicast related 
solution draft already in BESS working group.  But still if majority thinks we 
need it. We can think about it.

Thanks
Mankamana

From: BESS  on behalf of "UTTARO, JAMES" 
Date: Monday, March 26, 2018 at 10:46 AM
To: "Ali Sajassi (sajassi)" , John E Drake 
, "Rabadan, Jorge (Nokia - US/Mountain View)" 
, Eric Rosen , Sandy Breeze 
, "Satya Mohanty (satyamoh)" 
Cc: "bess@ietf.org" 
Subject: Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on 
problem description

Ali,

So, is this going to be a family of drafts dealing with 
inter-connection aspects across a set of use cases ? Would it be useful to 
right up a requirements draft like we did with EVPN??

Thanks,
Jim Uttaro

From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Monday, March 26, 2018 1:20 PM
To: UTTARO, JAMES ; John E Drake ; Rabadan, 
Jorge (Nokia - US/Mountain View) ; Eric Rosen 
; Sandy Breeze ; Satya Mohanty 
(satyamoh) 
Cc: bess@ietf.org
Subject: Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on 
problem description

Hi Jim,

draft-mohanty-bess-evpn-bum-opt will focus on L2 only between EVPN overlay 
(VxLAN) access domain and EVPN MPLS core. Connectivity EVPN IRB core (or EVPN 
L3 core) will be covered in the other drafts that I mentioned below because 
they are  already doing it for other use cases.

Cheers,
Ali

From: "UTTARO, JAMES" >
Date: Monday, March 26, 2018 at 10:03 AM
To: Cisco Employee >, John E Drake 
>, "Rabadan, Jorge (Nokia - 
US/Mountain View)" >, 
Eric Rosen >, Sandy Breeze 
>, "Satya Mohanty 
(satyamoh)" >
Cc: "bess@ietf.org" >
Subject: RE: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on 
problem description

Ali,

So is the plan to incorporate Sandy’s work in these docs??

Thanks,
Jim Uttaro


From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Monday, March 26, 2018 11:55 AM
To: UTTARO, JAMES >; John E Drake 
>; Rabadan, Jorge (Nokia - 
US/Mountain View) >; 
Eric Rosen >; Sandy Breeze 
>; Satya Mohanty 
(satyamoh) >
Cc: bess@ietf.org; Ali Sajassi (sajassi) 
>
Subject: Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on 
problem description


Hi Jim,

Wrt multicast for L2 EVPN<-> L3 EVPN, that should be covered in corresponding 
EVPN multicast drafts:

https://tools.ietf.org/html/draft-ietf-bess-evpn-irb-mcast-00
https://tools.ietf.org/html/draft-sajassi-bess-evpn-mvpn-seamless-interop-00

I will update my draft to address Eric’s comments as well as capture the L2 
EVPN <-> L3 EVPN explicitly in a few weeks.

Cheers,
Ali

From: "UTTARO, JAMES" >
Date: Monday, March 26, 2018 at 6:25 AM
To: Cisco Employee >, John E Drake 
>, "Rabadan, Jorge (Nokia - 
US/Mountain View)" >, 
Eric Rosen >, Sandy Breeze 
>, "Satya Mohanty 
(satyamoh)" >
Cc: 

Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

[UTTARO, JAMES]

Support..

Thanks,
Jim Uttaro

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Jeff Tantsura
Sent: Monday, March 26, 2018 6:26 PM
To: stephane.litkow...@orange.com; bess@ietf.org
Subject: Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

Yes/support

Cheers,
Jeff
From: BESS > on behalf of 
>
Date: Monday, March 26, 2018 at 07:21
To: "bess@ietf.org" >
Subject: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework


Hello working group,



This email starts a two-week Working Group Last Call on 
draft-ietf-bess-evpn-df-election-framework-00 [1]



This poll runs until *the 9th of April*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



Currently no IPR has been disclosed 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.



We are also polling for any existing implementation.



Thank you



Matthew, Stéphane

bess chairs



[1] 
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/



_



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] WGLC on draft-ietf-bess-evpn-df-election-framework

[stephane.litkowski]

Hi Authors,

Speaking as a WG member, I have two comments:

-  As I have pointed during the BESS meeting, it would be good to have 
a clear definition of what is a DF type vs a capability.

-  I think it would be good to have the draft telling that the 
implementation of HRW and AC-DF are optionals.

Brgds,

Stephane

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Monday, March 26, 2018 16:21
To: bess@ietf.org
Subject: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework


Hello working group,



This email starts a two-week Working Group Last Call on 
draft-ietf-bess-evpn-df-election-framework-00 [1]



This poll runs until *the 9th of April*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



Currently no IPR has been disclosed 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.



We are also polling for any existing implementation.



Thank you



Matthew, Stéphane

bess chairs



[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/



_



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

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

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

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



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

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

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

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

Thank you.

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

[Van De Velde, Gunter (Nokia - BE/Antwerp)]

Yes, support. This is meaningful work.

G/

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Monday, March 26, 2018 16:21
To: bess@ietf.org
Subject: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework


Hello working group,



This email starts a two-week Working Group Last Call on 
draft-ietf-bess-evpn-df-election-framework-00 [1]



This poll runs until *the 9th of April*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



Currently no IPR has been disclosed 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.



We are also polling for any existing implementation.



Thank you



Matthew, Stéphane

bess chairs



[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/



_



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