Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

[Oya Luengo, Roberto (Nokia - US/Mountain View)]

Support

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

Date: Monday, January 29, 2018 at 12:27 AM
To: "bess@ietf.org" , 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org" 

Subject: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df


Hello Working Group,



This email starts a Working Group Last Call on

draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

ready for a final working group review.



Please read this document if you haven't read the most recent version

yet, and send your comments to the list, no later than *12th of February*.

Note that this is *not only* a call for comments on the document; it is

also a call for support (or not) to publish this document as an 
Informational

RFC.



In addition, we are also polling for knowledge of any IPR that

applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

please respond to this email and indicate whether or not you are aware

of any relevant IPR.



Note that, as of today, no IPR has been disclosed against this document

or its earlier versions.



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, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

[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

Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

[Jeff Tantsura]

Yes/support 

Regards,
Jeff

> On Jan 29, 2018, at 13:16, Nagaraj, Kiran (Nokia - US/Mountain View) 
>  wrote:
> 
> Support this draft as well.
> Thanks
> Kiran
>  
> From: Sathappan, Senthil (Nokia - US/Mountain View) 
> [mailto:senthil.sathap...@nokia.com] 
> Sent: Monday, January 29, 2018 10:13 AM
> To: Henderickx, Wim (Nokia - BE/Antwerp) ; Rabadan, 
> Jorge (Nokia - US/Mountain View) ; 
> stephane.litkow...@orange.com; bess@ietf.org; 
> draft-ietf-bess-evpn-ac-df.auth...@ietf.org
> Subject: RE: [bess] WG Last Call (including implem status) for 
> draft-ietf-bess-evpn-ac-df
>  
> Support this document as co-author. Not aware of any related IPR.
> Thanks,
> Senthil.
>  
>  
> From: Henderickx, Wim (Nokia - BE/Antwerp) [mailto:wim.henderi...@nokia.com] 
> Sent: Monday, January 29, 2018 10:11 AM
> To: Rabadan, Jorge (Nokia - US/Mountain View) ; 
> stephane.litkow...@orange.com; bess@ietf.org; 
> draft-ietf-bess-evpn-ac-df.auth...@ietf.org
> Subject: Re: [bess] WG Last Call (including implem status) for 
> draft-ietf-bess-evpn-ac-df
>  
> Support as contributor, not aware of IPR related to this draft
>  
> From: BESS  on behalf of Jorge Rabadan 
> 
> Date: Monday, 29 January 2018 at 03:53
> To: Stephane Litkowski , "bess@ietf.org" 
> , "draft-ietf-bess-evpn-ac-df.auth...@ietf.org" 
> 
> Subject: Re: [bess] WG Last Call (including implem status) for 
> draft-ietf-bess-evpn-ac-df
>  
> Support this document, as co-author, for publication as Informational RFC.
> Not aware of any related IPR.
>  
> Nokia SROS has a full implementation of this draft.
>  
> Thank you.
> Jorge
>  
>  
> From: "stephane.litkow...@orange.com" 
> Date: Monday, January 29, 2018 at 9:27 AM
> To: "bess@ietf.org" , 
> "draft-ietf-bess-evpn-ac-df.auth...@ietf.org" 
> 
> Subject: WG Last Call (including implem status) for 
> draft-ietf-bess-evpn-ac-df 
> Resent-From: 
> Resent-To: , , 
> , , , 
> 
> Resent-Date: Monday, January 29, 2018 at 9:27 AM
>  
> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and
> ready for a final working group review.
>
> Please read this document if you haven't read the most recent version
> yet, and send your comments to the list, no later than *12th of February*.
> Note that this is *not only* a call for comments on the document; it is 
> also a call for support (or not) to publish this document as an 
> Informational
> RFC.
>
> In addition, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft
> please respond to this email and indicate whether or not you are aware
> of any relevant IPR.
>
> Note that, as of today, no IPR has been disclosed against this document
> or its earlier versions.
>
> 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, or the chairs, or only one of the chairs.
>
> Thank you,
> Stephane & Martin
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-ac-df/
> [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 

Re: [bess] [**EXTERNAL**] RE: WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

[Liu, Hua]

Support this document as co-author. Not aware of any related IPR.
Thanks,
Autumn

From: Sathappan, Senthil (Nokia - US/Mountain View) 
[mailto:senthil.sathap...@nokia.com]
Sent: Monday, January 29, 2018 1:13 PM
To: Henderickx, Wim (Nokia - BE/Antwerp) ; Rabadan, 
Jorge (Nokia - US/Mountain View) ; 
stephane.litkow...@orange.com; bess@ietf.org; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org
Subject: RE: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support this document as co-author. Not aware of any related IPR.
Thanks,
Senthil.


From: Henderickx, Wim (Nokia - BE/Antwerp) [mailto:wim.henderi...@nokia.com]
Sent: Monday, January 29, 2018 10:11 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) 
>; 
stephane.litkow...@orange.com; 
bess@ietf.org; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org
Subject: Re: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support as contributor, not aware of IPR related to this draft

From: BESS > on behalf of 
Jorge Rabadan >
Date: Monday, 29 January 2018 at 03:53
To: Stephane Litkowski 
>, 
"bess@ietf.org" >, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org"
 
>
Subject: Re: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support this document, as co-author, for publication as Informational RFC.
Not aware of any related IPR.

Nokia SROS has a full implementation of this draft.

Thank you.
Jorge


From: "stephane.litkow...@orange.com" 
>
Date: Monday, January 29, 2018 at 9:27 AM
To: "bess@ietf.org" 
>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org"
 
>
Subject: WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df
Resent-From: >
Resent-To: >, 
>, 
>, 
>, 
>, 
>
Resent-Date: Monday, January 29, 2018 at 9:27 AM


Hello Working Group,



This email starts a Working Group Last Call on

draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

ready for a final working group review.



Please read this document if you haven't read the most recent version

yet, and send your comments to the list, no later than *12th of February*.

Note that this is *not only* a call for comments on the document; it is

also a call for support (or not) to publish this document as an 
Informational

RFC.



In addition, we are also polling for knowledge of any IPR that

applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

please respond to this email and indicate whether or not you are aware

of any relevant IPR.



Note that, as of today, no IPR has been disclosed against this document

or its earlier versions.



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, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

[2] 

Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

[Nagaraj, Kiran (Nokia - US/Mountain View)]

Support this draft as well.
Thanks
Kiran

From: Sathappan, Senthil (Nokia - US/Mountain View) 
[mailto:senthil.sathap...@nokia.com]
Sent: Monday, January 29, 2018 10:13 AM
To: Henderickx, Wim (Nokia - BE/Antwerp) ; Rabadan, 
Jorge (Nokia - US/Mountain View) ; 
stephane.litkow...@orange.com; bess@ietf.org; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org
Subject: RE: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support this document as co-author. Not aware of any related IPR.
Thanks,
Senthil.


From: Henderickx, Wim (Nokia - BE/Antwerp) [mailto:wim.henderi...@nokia.com]
Sent: Monday, January 29, 2018 10:11 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) 
>; 
stephane.litkow...@orange.com; 
bess@ietf.org; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org
Subject: Re: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support as contributor, not aware of IPR related to this draft

From: BESS > on behalf of 
Jorge Rabadan >
Date: Monday, 29 January 2018 at 03:53
To: Stephane Litkowski 
>, 
"bess@ietf.org" >, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org"
 
>
Subject: Re: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support this document, as co-author, for publication as Informational RFC.
Not aware of any related IPR.

Nokia SROS has a full implementation of this draft.

Thank you.
Jorge


From: "stephane.litkow...@orange.com" 
>
Date: Monday, January 29, 2018 at 9:27 AM
To: "bess@ietf.org" 
>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org"
 
>
Subject: WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df
Resent-From: >
Resent-To: >, 
>, 
>, 
>, 
>, 
>
Resent-Date: Monday, January 29, 2018 at 9:27 AM


Hello Working Group,



This email starts a Working Group Last Call on

draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

ready for a final working group review.



Please read this document if you haven't read the most recent version

yet, and send your comments to the list, no later than *12th of February*.

Note that this is *not only* a call for comments on the document; it is

also a call for support (or not) to publish this document as an 
Informational

RFC.



In addition, we are also polling for knowledge of any IPR that

applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

please respond to this email and indicate whether or not you are aware

of any relevant IPR.



Note that, as of today, no IPR has been disclosed against this document

or its earlier versions.



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, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

[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 

Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

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

Support this document as co-author. Not aware of any related IPR.
Thanks,
Senthil.


From: Henderickx, Wim (Nokia - BE/Antwerp) [mailto:wim.henderi...@nokia.com]
Sent: Monday, January 29, 2018 10:11 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) ; 
stephane.litkow...@orange.com; bess@ietf.org; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org
Subject: Re: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support as contributor, not aware of IPR related to this draft

From: BESS > on behalf of 
Jorge Rabadan >
Date: Monday, 29 January 2018 at 03:53
To: Stephane Litkowski 
>, 
"bess@ietf.org" >, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org"
 
>
Subject: Re: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support this document, as co-author, for publication as Informational RFC.
Not aware of any related IPR.

Nokia SROS has a full implementation of this draft.

Thank you.
Jorge


From: "stephane.litkow...@orange.com" 
>
Date: Monday, January 29, 2018 at 9:27 AM
To: "bess@ietf.org" 
>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org"
 
>
Subject: WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df
Resent-From: >
Resent-To: >, 
>, 
>, 
>, 
>, 
>
Resent-Date: Monday, January 29, 2018 at 9:27 AM


Hello Working Group,



This email starts a Working Group Last Call on

draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

ready for a final working group review.



Please read this document if you haven't read the most recent version

yet, and send your comments to the list, no later than *12th of February*.

Note that this is *not only* a call for comments on the document; it is

also a call for support (or not) to publish this document as an 
Informational

RFC.



In addition, we are also polling for knowledge of any IPR that

applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

please respond to this email and indicate whether or not you are aware

of any relevant IPR.



Note that, as of today, no IPR has been disclosed against this document

or its earlier versions.



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, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

[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

Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

[Henderickx, Wim (Nokia - BE/Antwerp)]

Support as contributor, not aware of IPR related to this draft

From: BESS  on behalf of Jorge Rabadan 

Date: Monday, 29 January 2018 at 03:53
To: Stephane Litkowski , "bess@ietf.org" 
, "draft-ietf-bess-evpn-ac-df.auth...@ietf.org" 

Subject: Re: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support this document, as co-author, for publication as Informational RFC.
Not aware of any related IPR.

Nokia SROS has a full implementation of this draft.

Thank you.
Jorge


From: "stephane.litkow...@orange.com" 
Date: Monday, January 29, 2018 at 9:27 AM
To: "bess@ietf.org" , 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org" 

Subject: WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df
Resent-From: 
Resent-To: , , 
, , , 

Resent-Date: Monday, January 29, 2018 at 9:27 AM


Hello Working Group,



This email starts a Working Group Last Call on

draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

ready for a final working group review.



Please read this document if you haven't read the most recent version

yet, and send your comments to the list, no later than *12th of February*.

Note that this is *not only* a call for comments on the document; it is

also a call for support (or not) to publish this document as an 
Informational

RFC.



In addition, we are also polling for knowledge of any IPR that

applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

please respond to this email and indicate whether or not you are aware

of any relevant IPR.



Note that, as of today, no IPR has been disclosed against this document

or its earlier versions.



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, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

[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

Re: [bess] Call for adoption: draft-lin-bess-evpn-irb-mcast

[Eric C Rosen]

Support (as co-author).  I am not aware of any relevant IPR.

On 1/11/2018 5:11 AM, Martin Vigoureux wrote:

Hello working group,

This email starts a two-week call for adoption on 
draft-lin-bess-evpn-irb-mcast-04 [1] as a BESS Working Group Document.


Please state on the list if you support the adoption or not (in both 
cases, please also state the reasons).


This poll runs until *the 26th of January*.

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.


Thank you

Martin & Stéphane
bess chairs

[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dlin-2Dbess-2Devpn-2Dirb-2Dmcast_=DwID-g=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo=7stPyA6kx51d5f5KWpyDfBgEFvAcVWze4dSLeBo-CU0=z4hVPM7sSHQ0TMPjGtGCgLP0bm6MtvyY2ctPT6kbSCQ=


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

Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

[Bidgoli, Hooman (Nokia - CA/Ottawa)]

Support

Regards

Hooman

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Dolganow, Andrew (Nokia 
- SG/Singapore)
Sent: Monday, January 29, 2018 4:57 AM
To: stephane.litkow...@orange.com
Cc: draft-ietf-bess-evpn-ac-df.auth...@ietf.org; bess@ietf.org
Subject: Re: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df

Support
Andrew

Sent from my iPhone

On Jan 29, 2018, at 4:27 PM, 
"stephane.litkow...@orange.com" 
> wrote:

Hello Working Group,



This email starts a Working Group Last Call on

draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

ready for a final working group review.



Please read this document if you haven't read the most recent version

yet, and send your comments to the list, no later than *12th of February*.

Note that this is *not only* a call for comments on the document; it is

also a call for support (or not) to publish this document as an 
Informational

RFC.



In addition, we are also polling for knowledge of any IPR that

applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

please respond to this email and indicate whether or not you are aware

of any relevant IPR.



Note that, as of today, no IPR has been disclosed against this document

or its earlier versions.



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, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

[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] AD Review of draft-ietf-bess-evpn-usage-06

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

Hi Alvaro,

Thank you very much for reviewing it.
I couldn’t agree more that it would have been nice to have published it way 
earlier.

Just published rev 07 which fixed the two nits below.

Looking forward to the next step.
Thank you.

Jorge

From: Alvaro Retana 
Date: Friday, January 26, 2018 at 11:47 PM
To: "draft-ietf-bess-evpn-us...@ietf.org" 
Cc: "bess@ietf.org" , "bess-cha...@ietf.org" 
, "Vigoureux, Martin (Nokia - FR/Paris-Saclay)" 

Subject: AD Review of draft-ietf-bess-evpn-usage-06
Resent-From: 
Resent-To: , , 
, , 
Resent-Date: Friday, January 26, 2018 at 11:47 PM

Dear authors:

Not much I can say about this document, except that it would have been nice if 
it was published earlier to provide background to other EVPN document.

Thanks for your work!!

I just have a couple of comments on the references (see below).  I am starting 
the IETF Last Call.

Alvaro.


R1. These references can be Informative: rfc4761, rfc4762, rfc6074

R2. There is no reference in the text to rfc4364, rfc7117

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

Re: [bess] AD Review of draft-ietf-bess-dci-evpn-overlay-05

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

Hi Alvaro,

I just fixed the two nits referred below, added a sentence requested by Anoop, 
and published rev 07.
See my comments below. Please let us know if there is anything else to do.
Thank you.
Jorge

From: Alvaro Retana 
Date: Friday, January 26, 2018 at 10:17 PM
To: "draft-ietf-bess-dci-evpn-over...@ietf.org" 
, "Rabadan, Jorge (Nokia - 
US/Mountain View)" 
Cc: "Vigoureux, Martin (Nokia - FR/Paris-Saclay)" , 
"bess-cha...@ietf.org" , "bess@ietf.org" 
Subject: Re: AD Review of draft-ietf-bess-dci-evpn-overlay-05

Jorge:

Thanks for the update.

I’m starting the IETF LC, but I need you to please fix the nits related to the 
references:

  == Missing Reference: 'RFC8174' is mentioned on line 125, but not defined
[JORGE] fixed. thx

  -- No information found for draft-ietf-bess-evpn-vpls-integration - is the
 name correct?
[JORGE] the correct reference should have been 
draft-ietf-bess-evpn-vpls-seamless-integ-00, however with the small change in 
the text (see rev 07 diff), and given it was an informative reference and 
expired, I don’t think we even need to refer to that draft, so I removed the 
reference.



Thanks!

Alvaro.



On January 22, 2018 at 4:16:35 PM, Rabadan, Jorge (Nokia - US/Mountain View) 
(jorge.raba...@nokia.com) wrote:
Hi Alvaro,

Thank you very much for your detailed review.
Revision 06 has just been uploaded. This rev addresses all your comments.
Please see some responses in-line with [JORGE].

Thanks.
Jorge


From: Alvaro Retana >
Date: Thursday, January 18, 2018 at 5:08 PM
To: 
"draft-ietf-bess-dci-evpn-over...@ietf.org"
 
>
Cc: "bess@ietf.org" 
>, 
"bess-cha...@ietf.org" 
>, "Vigoureux, Martin (Nokia 
- FR/Paris-Saclay)" 
>
Subject: AD Review of draft-ietf-bess-dci-evpn-overlay-05
Resent-From: >
Resent-To: >, 
>, 
>, 
>, 
>
Resent-Date: Thursday, January 18, 2018 at 5:08 PM

Dear authors:

I just finished reading this document.

As with draft-ietf-bess-evpn-overlay, it seems to me that this document is 
better suited as an Applicability Statement [1] instead of a Technical 
Specification -- both would result in a Standards Track document.  It is hard 
for me to clearly identify what this document is specifying, vs explaining how 
to use existing mechanisms (already specified elsewhere) to achieve the DCI.  I 
don't want to dig too deep into this point, but it would be nice if you at 
least considered refocusing the text.

[JORGE] While a good part of the document describes how different Technical 
Specifications can be applied to the DCI case, the document also describes new 
procedures or extensions of its normative Technical Specs. In particular, the 
new EVPN extensions are:
• The Interconnect Ethernet Segment (I-ES), its definition and usage 
are different than the one in [RFC7432]
• The use of the Unknown MAC route in I-ES
• The processing of EVPN routes on Gateways with MAC-VRFs connecting 
EVPN-Overlay to EVPN-MPLS networks.
I changed the abstract and the introduction to reflect that.


I do have some more comments below.  I'll wait for an updated draft before 
starting the IETF Last Call.

Thanks!

Alvaro.

[1] https://tools.ietf.org/html/rfc2026#section-3.2

Major:

M1. I don't feel too good about using Normative Language to describe the 
requirements (2.1 and 3.1) because the normative part of this document should 
be the solution itself, not the requirements (which the solution will then 
solve).  As I read the requirements, with the Normative Language in them, there 
are questions that come up, which wouldn't be there if rfc2119 keywords were 
not used.

[JORGE] OK. I changed sections 2.1 and 3.1 and removed Normative Language.


M1.1. There's an important use of the words "supported" and "implemented", what 
do they mean from a Normative point of view?  Are you using them from the point 
of view of the operator implementing something in their network, or the 
solution (the software feature) including them?  How do you Normatively enforce 
that?  Some examples of their use are: "Per-service load balancing MUST be 
supported. Per-flow load balancing 

[bess] I-D Action: draft-ietf-bess-dci-evpn-overlay-07.txt

[internet-drafts]

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

Title   : Interconnect Solution for EVPN Overlay networks
Authors : Jorge Rabadan
  Senthil Sathappan
  Wim Henderickx
  Ali Sajassi
  John Drake
Filename: draft-ietf-bess-dci-evpn-overlay-07.txt
Pages   : 26
Date: 2018-01-29

Abstract:
   This document describes how Network Virtualization Overlays (NVO) can
   be connected to a Wide Area Network (WAN) in order to extend the
   layer-2 connectivity required for some tenants. The solution analyzes
   the interaction between NVO networks running Ethernet Virtual Private
   Networks (EVPN) and other L2VPN technologies used in the WAN, such as
   Virtual Private LAN Services (VPLS), VPLS extensions for Provider
   Backbone Bridging (PBB-VPLS), EVPN or PBB-EVPN. It also describes how
   the existing Technical Specifications apply to the Interconnection
   and extends the EVPN procedures needed in some cases. In particular,
   this document describes how EVPN routes are processed on Gateways
   (GWs) that interconnect EVPN-Overlay and EVPN-MPLS networks, as well
   as the Interconnect Ethernet Segment (I-ES) to provide multi-homing,
   and the use of the Unknown MAC route to avoid MAC scale issues on
   Data Center Network Virtualization Edge (NVE) devices.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-dci-evpn-overlay/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bess-dci-evpn-overlay-07
https://datatracker.ietf.org/doc/html/draft-ietf-bess-dci-evpn-overlay-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-dci-evpn-overlay-07


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

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

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

Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

[Dolganow, Andrew (Nokia - SG/Singapore)]

Support

Andrew

Sent from my iPhone

On Jan 29, 2018, at 4:27 PM, 
"stephane.litkow...@orange.com" 
> wrote:


Hello Working Group,



This email starts a Working Group Last Call on

draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

ready for a final working group review.



Please read this document if you haven't read the most recent version

yet, and send your comments to the list, no later than *12th of February*.

Note that this is *not only* a call for comments on the document; it is

also a call for support (or not) to publish this document as an 
Informational

RFC.



In addition, we are also polling for knowledge of any IPR that

applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

please respond to this email and indicate whether or not you are aware

of any relevant IPR.



Note that, as of today, no IPR has been disclosed against this document

or its earlier versions.



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, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

[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) for draft-ietf-bess-evpn-ac-df

[Nabeel Cocker]

Support 

Regards,
Nabeel

> On Jan 29, 2018, at 3:51 AM, Rabadan, Jorge (Nokia - US/Mountain View) 
>  wrote:
> 
> Support this document, as co-author, for publication as Informational RFC.
> Not aware of any related IPR.
>  
> Nokia SROS has a full implementation of this draft.
>  
> Thank you.
> Jorge
>  
>  
> From: "stephane.litkow...@orange.com" 
> Date: Monday, January 29, 2018 at 9:27 AM
> To: "bess@ietf.org" , 
> "draft-ietf-bess-evpn-ac-df.auth...@ietf.org" 
> 
> Subject: WG Last Call (including implem status) for 
> draft-ietf-bess-evpn-ac-df 
> Resent-From: 
> Resent-To: , , 
> , , , 
> 
> Resent-Date: Monday, January 29, 2018 at 9:27 AM
>  
> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and
> ready for a final working group review.
>
> Please read this document if you haven't read the most recent version
> yet, and send your comments to the list, no later than *12th of February*.
> Note that this is *not only* a call for comments on the document; it is
> also a call for support (or not) to publish this document as an 
> Informational
> RFC.
>
> In addition, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft
> please respond to this email and indicate whether or not you are aware
> of any relevant IPR.
>
> Note that, as of today, no IPR has been disclosed against this document
> or its earlier versions.
>
> 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, or the chairs, or only one of the chairs.
>
> Thank you,
> Stephane & Martin
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-ac-df/
> [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) for draft-ietf-bess-evpn-ac-df

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

Support this document, as co-author, for publication as Informational RFC.
Not aware of any related IPR.

Nokia SROS has a full implementation of this draft.

Thank you.
Jorge


From: "stephane.litkow...@orange.com" 
Date: Monday, January 29, 2018 at 9:27 AM
To: "bess@ietf.org" , 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org" 

Subject: WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df
Resent-From: 
Resent-To: , , 
, , , 

Resent-Date: Monday, January 29, 2018 at 9:27 AM


Hello Working Group,



This email starts a Working Group Last Call on

draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

ready for a final working group review.



Please read this document if you haven't read the most recent version

yet, and send your comments to the list, no later than *12th of February*.

Note that this is *not only* a call for comments on the document; it is

also a call for support (or not) to publish this document as an 
Informational

RFC.



In addition, we are also polling for knowledge of any IPR that

applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

please respond to this email and indicate whether or not you are aware

of any relevant IPR.



Note that, as of today, no IPR has been disclosed against this document

or its earlier versions.



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, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

[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] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

[stephane.litkowski]

Hello Working Group,



This email starts a Working Group Last Call on

draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and

ready for a final working group review.



Please read this document if you haven't read the most recent version

yet, and send your comments to the list, no later than *12th of February*.

Note that this is *not only* a call for comments on the document; it is

also a call for support (or not) to publish this document as an 
Informational

RFC.



In addition, we are also polling for knowledge of any IPR that

applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft

please respond to this email and indicate whether or not you are aware

of any relevant IPR.



Note that, as of today, no IPR has been disclosed against this document

or its earlier versions.



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, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

[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