Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Thomas Morin]

Hi working group, authors,

A quick update on draft-ietf-bess-evpn-overlay, as mentioned during BESS 
meeting in Berlin:
- the door for comments is still open to have more reviews on this 
important document
- reminder to authors: the outcome of the discussion right before/during 
WGLC haven't yet been incorporated in a revision


Best,

-Thomas

thomas.mo...@orange.com :

Hello Working Group,

(Please read carefully, this e-mail contains new elements compared to 
WG LCs we were doing in a still recent past.)


This email starts a Working Group Last Call on
draft-ietf-bess-evpn-overlay [1].

* Please read the document if you haven't read the most recent
version yet, and send your comments to the list, no later than
*27th of June*.

Note that this is *not only* a call for comments on the document, but 
also a call for support (or not) publishing this document as a 
Proposed Standard RFC.


* We are also polling for knowledge of any undisclosed IPR that 
applies to draft-ietf-bess-evpn-overlay-04, to ensure that IPR has 
been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 
3669 and 5378 for more details) prior to moving forward.

If you are listed as a document Author or 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.


* We are also polling for knowledge of implementations of part or all 
of what this document specifies. This information is expected as per 
[2]. Please inform the mailing list, the chairs, or only one of the 
chairs.


* Finally, if you want to volunteer to be Document Shepherd for this 
document, please let us know.


Thank you,

Thomas/Martin


[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
[2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw 


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

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Nabeel Cocker]

Support. 

Regards,
Nabeel

> On Jun 13, 2016, at 8:25 AM,  
>  wrote:
> 
> Hello Working Group,
> 
> (Please read carefully, this e-mail contains new elements compared to WG LCs 
> we were doing in a still recent past.)
> 
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-overlay [1].
> 
> * Please read the document if you haven't read the most recent
> version yet, and send your comments to the list, no later than
> *27th of June*.
> 
> Note that this is *not only* a call for comments on the document, but also a 
> call for support (or not) publishing this document as a Proposed Standard RFC.
> 
> * We are also polling for knowledge of any undisclosed IPR that applies to 
> draft-ietf-bess-evpn-overlay-04, to ensure that IPR has been disclosed in 
> compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more 
> details) prior to moving forward.
> If you are listed as a document Author or 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.
> 
> * We are also polling for knowledge of implementations of part or all of what 
> this document specifies. This information is expected as per [2]. Please 
> inform the mailing list, the chairs, or only one of the chairs.
> 
> * Finally, if you want to volunteer to be Document Shepherd for this 
> document, please let us know.
> 
> Thank you,
> 
> Thomas/Martin
> 
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
> 
> _
> 
> 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 Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Dolganow, Andrew (Nokia - SG)]

Support.

Andrew

On 2016-06-13, 8:25 PM, "BESS on behalf of thomas.mo...@orange.com" wrote:

>Hello Working Group,
>
>(Please read carefully, this e-mail contains new elements compared to WG
>LCs we were doing in a still recent past.)
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-overlay [1].
>
>* Please read the document if you haven't read the most recent
>version yet, and send your comments to the list, no later than
>*27th of June*.
>
>Note that this is *not only* a call for comments on the document, but
>also a call for support (or not) publishing this document as a Proposed
>Standard RFC.
>
>* We are also polling for knowledge of any undisclosed IPR that applies
>to draft-ietf-bess-evpn-overlay-04, to ensure that IPR has been
>disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669
>and 5378 for more details) prior to moving forward.
>If you are listed as a document Author or 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.
>
>* We are also polling for knowledge of implementations of part or all of
>what this document specifies. This information is expected as per [2].
>Please inform the mailing list, the chairs, or only one of the chairs.
>
>* Finally, if you want to volunteer to be Document Shepherd for this
>document, please let us know.
>
>Thank you,
>
>Thomas/Martin
>
>
>[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
>[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>__
>___
>
>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 Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Ravi Shekhar]

Support as a co-author. Not aware of any IPR.
- Ravi.

-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Ali Sajassi (sajassi)
Sent: Sunday, July 03, 2016 9:48 PM
To: EXT - thomas.mo...@orange.com <thomas.mo...@orange.com>; BESS 
<bess@ietf.org>
Cc: draft-ietf-bess-evpn-over...@tools.ietf.org
Subject: Re: [bess] WG Last Call (including implem status & shepherd) for 
draft-ietf-bess-evpn-overlay


I support WG LC of this draft as a co-author. This draft has been implemented 
in Cisco switches for a while. Furthermore, I am not aware of any IPR that 
hasn¹t been already disclosed.

Regards,
Ali


On 6/13/16, 5:25 AM, "BESS on behalf of thomas.mo...@orange.com"
<bess-boun...@ietf.org on behalf of thomas.mo...@orange.com> wrote:

>Hello Working Group,
>
>(Please read carefully, this e-mail contains new elements compared to 
>WG LCs we were doing in a still recent past.)
>
>This email starts a Working Group Last Call on 
>draft-ietf-bess-evpn-overlay [1].
>
>* Please read the document if you haven't read the most recent version 
>yet, and send your comments to the list, no later than *27th of June*.
>
>Note that this is *not only* a call for comments on the document, but 
>also a call for support (or not) publishing this document as a Proposed 
>Standard RFC.
>
>* We are also polling for knowledge of any undisclosed IPR that applies 
>to draft-ietf-bess-evpn-overlay-04, to ensure that IPR has been 
>disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 
>and 5378 for more details) prior to moving forward.
>If you are listed as a document Author or 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.
>
>* We are also polling for knowledge of implementations of part or all 
>of what this document specifies. This information is expected as per [2].
>Please inform the mailing list, the chairs, or only one of the chairs.
>
>* Finally, if you want to volunteer to be Document Shepherd for this 
>document, please let us know.
>
>Thank you,
>
>Thomas/Martin
>
>
>[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
>[2] 
>https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>___
>___ ___
>
>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

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

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Satya Mohanty (satyamoh)]

Support.

Thanks,
—Satya




>
>> -Original Message-
>> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
>> thomas.mo...@orange.com
>> Sent: Monday, June 13, 2016 5:26 AM
>> To: BESS <bess@ietf.org>
>> Cc: draft-ietf-bess-evpn-over...@tools.ietf.org
>> Subject: [bess] WG Last Call (including implem status & shepherd) for 
>> draft-ietf-bess-evpn-overlay
>> 
>> Hello Working Group,
>> 
>> (Please read carefully, this e-mail contains new elements compared to WG
>> LCs we were doing in a still recent past.)
>> 
>> This email starts a Working Group Last Call on
>> draft-ietf-bess-evpn-overlay [1].
>> 
>> * Please read the document if you haven't read the most recent
>> version yet, and send your comments to the list, no later than
>> *27th of June*.
>> 
>> Note that this is *not only* a call for comments on the document, but
>> also a call for support (or not) publishing this document as a Proposed
>> Standard RFC.
>> 
>> * We are also polling for knowledge of any undisclosed IPR that applies
>> to draft-ietf-bess-evpn-overlay-04, to ensure that IPR has been
>> disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669
>> and 5378 for more details) prior to moving forward.
>> If you are listed as a document Author or 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.
>> 
>> * We are also polling for knowledge of implementations of part or all of
>> what this document specifies. This information is expected as per [2].
>> Please inform the mailing list, the chairs, or only one of the chairs.
>> 
>> * Finally, if you want to volunteer to be Document Shepherd for this
>> document, please let us know.
>> 
>> Thank you,
>> 
>> Thomas/Martin
>> 
>> 
>> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
>> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>> 
>> 
>> _
>> 
>> 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
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Jakob Heitz (jheitz)]

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

Thanks,
Jakob.

> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of thomas.mo...@orange.com
> Sent: Monday, June 13, 2016 5:26 AM
> To: BESS <bess@ietf.org>
> Cc: draft-ietf-bess-evpn-over...@tools.ietf.org
> Subject: [bess] WG Last Call (including implem status & shepherd) for 
> draft-ietf-bess-evpn-overlay
> 
> Hello Working Group,
> 
> (Please read carefully, this e-mail contains new elements compared to WG
> LCs we were doing in a still recent past.)
> 
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-overlay [1].
> 
> * Please read the document if you haven't read the most recent
> version yet, and send your comments to the list, no later than
> *27th of June*.
> 
> Note that this is *not only* a call for comments on the document, but
> also a call for support (or not) publishing this document as a Proposed
> Standard RFC.
> 
> * We are also polling for knowledge of any undisclosed IPR that applies
> to draft-ietf-bess-evpn-overlay-04, to ensure that IPR has been
> disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669
> and 5378 for more details) prior to moving forward.
> If you are listed as a document Author or 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.
> 
> * We are also polling for knowledge of implementations of part or all of
> what this document specifies. This information is expected as per [2].
> Please inform the mailing list, the chairs, or only one of the chairs.
> 
> * Finally, if you want to volunteer to be Document Shepherd for this
> document, please let us know.
> 
> Thank you,
> 
> Thomas/Martin
> 
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
> 
> 
> _
> 
> 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 Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Jeff Tantsura]

Support!


> 
>> On 6/13/16, 5:25 AM, "BESS on behalf of thomas.mo...@orange.com" 
>>  wrote:
>> 
>> Hello Working Group,
>> 
>> (Please read carefully, this e-mail contains new elements compared to WG 
>> LCs we were doing in a still recent past.)
>> 
>> This email starts a Working Group Last Call on
>> draft-ietf-bess-evpn-overlay [1].
>> 
>> * Please read the document if you haven't read the most recent
>> version yet, and send your comments to the list, no later than
>> *27th of June*.
>> 
>> Note that this is *not only* a call for comments on the document, but 
>> also a call for support (or not) publishing this document as a Proposed 
>> Standard RFC.
>> 
>> * We are also polling for knowledge of any undisclosed IPR that applies 
>> to draft-ietf-bess-evpn-overlay-04, to ensure that IPR has been 
>> disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 
>> and 5378 for more details) prior to moving forward.
>> If you are listed as a document Author or 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.
>> 
>> * We are also polling for knowledge of implementations of part or all of 
>> what this document specifies. This information is expected as per [2]. 
>> Please inform the mailing list, the chairs, or only one of the chairs.
>> 
>> * Finally, if you want to volunteer to be Document Shepherd for this 
>> document, please let us know.
>> 
>> Thank you,
>> 
>> Thomas/Martin
>> 
>> 
>> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
>> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>> 
>> _
>> 
>> 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

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

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Henderickx, Wim (Nokia - BE)]

Support as standard.
Not aware of IPR related to this draft

We have implemented this in multiple products in Nokia: 7x50 product family and 
Nuage.

>
>On 6/13/16, 5:25 AM, "BESS on behalf of thomas.mo...@orange.com"
> wrote:
>
>>Hello Working Group,
>>
>>(Please read carefully, this e-mail contains new elements compared to WG
>>LCs we were doing in a still recent past.)
>>
>>This email starts a Working Group Last Call on
>>draft-ietf-bess-evpn-overlay [1].
>>
>>* Please read the document if you haven't read the most recent
>>version yet, and send your comments to the list, no later than
>>*27th of June*.
>>
>>Note that this is *not only* a call for comments on the document, but
>>also a call for support (or not) publishing this document as a Proposed
>>Standard RFC.
>>
>>* We are also polling for knowledge of any undisclosed IPR that applies
>>to draft-ietf-bess-evpn-overlay-04, to ensure that IPR has been
>>disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669
>>and 5378 for more details) prior to moving forward.
>>If you are listed as a document Author or 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.
>>
>>* We are also polling for knowledge of implementations of part or all of
>>what this document specifies. This information is expected as per [2].
>>Please inform the mailing list, the chairs, or only one of the chairs.
>>
>>* Finally, if you want to volunteer to be Document Shepherd for this
>>document, please let us know.
>>
>>Thank you,
>>
>>Thomas/Martin
>>
>>
>>[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
>>[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>>
>>__
>>___
>>
>>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 Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Rabadan, Jorge (Nokia - US)]

Thomas et al.

My apologies for the delay.
I support the publication of this document as Proposed Standard RFC.
It is a key DC technology and has been implemented by multiple vendors. In 
particular, Nokia has implemented it in multiple platforms.

Also, I think it is important to note that multi-vendor interoperability has 
been publicly demonstrated by an independent organization during last February. 
Report was published here: 
http://www.eantc.de/fileadmin/eantc/downloads/events/2011-2015/MPLSSDNNFV_2016/EANTC-MPLSSDNNFV2016-WhitePaper_Final.pdf

Thank you.
Jorge




On 6/13/16, 5:25 AM, "BESS on behalf of thomas.mo...@orange.com" 
 wrote:

>Hello Working Group,
>
>(Please read carefully, this e-mail contains new elements compared to WG 
>LCs we were doing in a still recent past.)
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-overlay [1].
>
>* Please read the document if you haven't read the most recent
>version yet, and send your comments to the list, no later than
>*27th of June*.
>
>Note that this is *not only* a call for comments on the document, but 
>also a call for support (or not) publishing this document as a Proposed 
>Standard RFC.
>
>* We are also polling for knowledge of any undisclosed IPR that applies 
>to draft-ietf-bess-evpn-overlay-04, to ensure that IPR has been 
>disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 
>and 5378 for more details) prior to moving forward.
>If you are listed as a document Author or 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.
>
>* We are also polling for knowledge of implementations of part or all of 
>what this document specifies. This information is expected as per [2]. 
>Please inform the mailing list, the chairs, or only one of the chairs.
>
>* Finally, if you want to volunteer to be Document Shepherd for this 
>document, please let us know.
>
>Thank you,
>
>Thomas/Martin
>
>
>[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
>[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>_
>
>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 Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[John E Drake]

Thomas,

I'm sorry for the tardy response.  I support the publication of this draft as 
it describes a de-facto industry standard control plane for NVO3 networks;  
Juniper has implemented it on multiple platforms.  I'm not aware of any IPR. 

Yours Irrespectively,

John

> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of thomas.mo...@orange.com
> Sent: Monday, June 13, 2016 8:26 AM
> To: BESS
> Cc: draft-ietf-bess-evpn-over...@tools.ietf.org
> Subject: [bess] WG Last Call (including implem status & shepherd) for 
> draft-ietf-bess-evpn-
> overlay
> 
> Hello Working Group,
> 
> (Please read carefully, this e-mail contains new elements compared to WG LCs 
> we were
> doing in a still recent past.)
> 
> This email starts a Working Group Last Call on draft-ietf-bess-evpn-overlay 
> [1].
> 
> * Please read the document if you haven't read the most recent version yet, 
> and send your
> comments to the list, no later than *27th of June*.
> 
> Note that this is *not only* a call for comments on the document, but also a 
> call for support
> (or not) publishing this document as a Proposed Standard RFC.
> 
> * We are also polling for knowledge of any undisclosed IPR that applies to 
> draft-ietf-bess-
> evpn-overlay-04, to ensure that IPR has been disclosed in compliance with 
> IETF IPR rules
> (see RFCs 3979, 4879, 3669 and 5378 for more details) prior to moving forward.
> If you are listed as a document Author or 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.
> 
> * We are also polling for knowledge of implementations of part or all of what 
> this document
> specifies. This information is expected as per [2].
> Please inform the mailing list, the chairs, or only one of the chairs.
> 
> * Finally, if you want to volunteer to be Document Shepherd for this 
> document, please let
> us know.
> 
> Thank you,
> 
> Thomas/Martin
> 
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
> 
> _
> 
> 
> 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

[bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[thomas.morin]

Hello Working Group,

(Please read carefully, this e-mail contains new elements compared to WG 
LCs we were doing in a still recent past.)


This email starts a Working Group Last Call on
draft-ietf-bess-evpn-overlay [1].

* Please read the document if you haven't read the most recent
version yet, and send your comments to the list, no later than
*27th of June*.

Note that this is *not only* a call for comments on the document, but 
also a call for support (or not) publishing this document as a Proposed 
Standard RFC.


* We are also polling for knowledge of any undisclosed IPR that applies 
to draft-ietf-bess-evpn-overlay-04, to ensure that IPR has been 
disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 
and 5378 for more details) prior to moving forward.

If you are listed as a document Author or 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.


* We are also polling for knowledge of implementations of part or all of 
what this document specifies. This information is expected as per [2]. 
Please inform the mailing list, the chairs, or only one of the chairs.


* Finally, if you want to volunteer to be Document Shepherd for this 
document, please let us know.


Thank you,

Thomas/Martin


[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

_

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