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

2018-01-31 Thread Satya Mohanty (satyamoh) 
Yes, this will be consistent with the existing framework.

Thanks,
—Satya

From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> on behalf of 
"stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>" 
<stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>>
Date: Wednesday, January 31, 2018 at 12:55 AM
To: "jdr...@juniper.net<mailto:jdr...@juniper.net>" 
<jdr...@juniper.net<mailto:jdr...@juniper.net>>, "Rabadan, Jorge (Nokia - 
US/Mountain View)" <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>, 
"Van De Velde, Gunter (Nokia - BE/Antwerp)" 
<gunter.van_de_ve...@nokia.com<mailto:gunter.van_de_ve...@nokia.com>>, 
"bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto:draft-ietf-bess-evpn-ac-df.auth...@ietf.org>"
 
<draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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

Hi John,

Speaking as doc shepherd for the ac-df draft, I agree that this make sense and 
this will provide more backward compatibility with the behavior defined in 
RFC7432.

Brgds,

From: John E Drake [mailto:jdr...@juniper.net]
Sent: Tuesday, January 30, 2018 17:17
To: Rabadan, Jorge (Nokia - US/Mountain View); Van De Velde, Gunter (Nokia - 
BE/Antwerp); LITKOWSKI Stephane OBS/OINIS; bess@ietf.org<mailto:bess@ietf.org>; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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

Hi,

The HRW DF election draft defines a new extended community, the DF Election 
Extended Community 
(https://tools.ietf.org/html/draft-ietf-bess-evpn-df-election-03#section-7), 
which contains a DF election type registry.  Why don’t we define a value for 
AC-based DF election and have the PEs supporting it advertise the extended 
community w/ that value and either  include a normative reference to the HRW 
draft or move the extended community and the text describing its usage to the 
AC-based election draft?

Yours Irrespectively,

John

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Rabadan, Jorge (Nokia - 
US/Mountain View)
Sent: Tuesday, January 30, 2018 10:28 AM
To: Van De Velde, Gunter (Nokia - BE/Antwerp) 
<gunter.van_de_ve...@nokia.com<mailto:gunter.van_de_ve...@nokia.com>>; 
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>; 
bess@ietf.org<mailto:bess@ietf.org>; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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

Hi Gunter,

Thanks for the feedback.
About this:
I was wondering why this document, even though being backward compatible with 
RFC7432, is Informational track, and not standard track.

I just sent an email providing the initial reasoning discussed among the 
authors. If we still think Standards Track is more appropriate, I think it is 
ok to change it.

Thank you.
Jorge



From: "Van De Velde, Gunter (Nokia - BE/Antwerp)" 
<gunter.van_de_ve...@nokia.com<mailto:gunter.van_de_ve...@nokia.com>>
Date: Tuesday, January 30, 2018 at 10:46 AM
To: "stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>" 
<stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>>, 
"bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto:draft-ietf-bess-evpn-ac-df.auth...@ietf.org>"
 
<draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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
Resent-From: <alias-boun...@ietf.org<mailto:alias-boun...@ietf.org>>
Resent-To: <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>, 
<kiran.naga...@nokia.com<mailto:kiran.naga...@nokia.com>>, 
<senthil.sathap...@nokia.com<mailto:senthil.sathap...@nokia.com>>, 
<vinod.pra...@nokia.com<mailto:vinod.pra...@nokia.com>>, 
<h...@ciena.com<mailto:h...@ciena.com>>, 
<w...@juniper.net<mailto:w...@juniper.net>>
Resent-Date: Tuesday, January 30, 2018 at 10:46 AM

I support progress and publish as RFC.

The document is well written and resolves with a reasonable approach logical 
failures or human errors, that would otherwise result in significant service 
problems.
I was wondering why this document, eventhough being backward compatible with 
RFC7432, is Informational track, and not sta

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

2018-01-31 Thread stephane.litkowski 
Hi John,

Speaking as doc shepherd for the ac-df draft, I agree that this make sense and 
this will provide more backward compatibility with the behavior defined in 
RFC7432.

Brgds,

From: John E Drake [mailto:jdr...@juniper.net]
Sent: Tuesday, January 30, 2018 17:17
To: Rabadan, Jorge (Nokia - US/Mountain View); Van De Velde, Gunter (Nokia - 
BE/Antwerp); LITKOWSKI Stephane OBS/OINIS; 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

Hi,

The HRW DF election draft defines a new extended community, the DF Election 
Extended Community 
(https://tools.ietf.org/html/draft-ietf-bess-evpn-df-election-03#section-7), 
which contains a DF election type registry.  Why don’t we define a value for 
AC-based DF election and have the PEs supporting it advertise the extended 
community w/ that value and either  include a normative reference to the HRW 
draft or move the extended community and the text describing its usage to the 
AC-based election draft?

Yours Irrespectively,

John

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Rabadan, Jorge (Nokia - 
US/Mountain View)
Sent: Tuesday, January 30, 2018 10:28 AM
To: Van De Velde, Gunter (Nokia - BE/Antwerp) 
<gunter.van_de_ve...@nokia.com<mailto:gunter.van_de_ve...@nokia.com>>; 
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>; 
bess@ietf.org<mailto:bess@ietf.org>; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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

Hi Gunter,

Thanks for the feedback.
About this:
I was wondering why this document, even though being backward compatible with 
RFC7432, is Informational track, and not standard track.

I just sent an email providing the initial reasoning discussed among the 
authors. If we still think Standards Track is more appropriate, I think it is 
ok to change it.

Thank you.
Jorge



From: "Van De Velde, Gunter (Nokia - BE/Antwerp)" 
<gunter.van_de_ve...@nokia.com<mailto:gunter.van_de_ve...@nokia.com>>
Date: Tuesday, January 30, 2018 at 10:46 AM
To: "stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>" 
<stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>>, 
"bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto:draft-ietf-bess-evpn-ac-df.auth...@ietf.org>"
 
<draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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
Resent-From: <alias-boun...@ietf.org<mailto:alias-boun...@ietf.org>>
Resent-To: <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>, 
<kiran.naga...@nokia.com<mailto:kiran.naga...@nokia.com>>, 
<senthil.sathap...@nokia.com<mailto:senthil.sathap...@nokia.com>>, 
<vinod.pra...@nokia.com<mailto:vinod.pra...@nokia.com>>, 
<h...@ciena.com<mailto:h...@ciena.com>>, 
<w...@juniper.net<mailto:w...@juniper.net>>
Resent-Date: Tuesday, January 30, 2018 at 10:46 AM

I support progress and publish as RFC.

The document is well written and resolves with a reasonable approach logical 
failures or human errors, that would otherwise result in significant service 
problems.
I was wondering why this document, eventhough being backward compatible with 
RFC7432, is Informational track, and not standard track.

G/

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>
Sent: Monday, January 29, 2018 09:27
To: bess@ietf.org<mailto:bess@ietf.org>; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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 res

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

2018-01-30 Thread John E Drake 
Hi,

The HRW DF election draft defines a new extended community, the DF Election 
Extended Community 
(https://tools.ietf.org/html/draft-ietf-bess-evpn-df-election-03#section-7), 
which contains a DF election type registry.  Why don’t we define a value for 
AC-based DF election and have the PEs supporting it advertise the extended 
community w/ that value and either  include a normative reference to the HRW 
draft or move the extended community and the text describing its usage to the 
AC-based election draft?

Yours Irrespectively,

John

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Rabadan, Jorge (Nokia - 
US/Mountain View)
Sent: Tuesday, January 30, 2018 10:28 AM
To: Van De Velde, Gunter (Nokia - BE/Antwerp) <gunter.van_de_ve...@nokia.com>; 
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

Hi Gunter,

Thanks for the feedback.
About this:
I was wondering why this document, even though being backward compatible with 
RFC7432, is Informational track, and not standard track.

I just sent an email providing the initial reasoning discussed among the 
authors. If we still think Standards Track is more appropriate, I think it is 
ok to change it.

Thank you.
Jorge



From: "Van De Velde, Gunter (Nokia - BE/Antwerp)" 
<gunter.van_de_ve...@nokia.com<mailto:gunter.van_de_ve...@nokia.com>>
Date: Tuesday, January 30, 2018 at 10:46 AM
To: "stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>" 
<stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>>, 
"bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto:draft-ietf-bess-evpn-ac-df.auth...@ietf.org>"
 
<draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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
Resent-From: <alias-boun...@ietf.org<mailto:alias-boun...@ietf.org>>
Resent-To: <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>, 
<kiran.naga...@nokia.com<mailto:kiran.naga...@nokia.com>>, 
<senthil.sathap...@nokia.com<mailto:senthil.sathap...@nokia.com>>, 
<vinod.pra...@nokia.com<mailto:vinod.pra...@nokia.com>>, 
<h...@ciena.com<mailto:h...@ciena.com>>, 
<w...@juniper.net<mailto:w...@juniper.net>>
Resent-Date: Tuesday, January 30, 2018 at 10:46 AM

I support progress and publish as RFC.

The document is well written and resolves with a reasonable approach logical 
failures or human errors, that would otherwise result in significant service 
problems.
I was wondering why this document, eventhough being backward compatible with 
RFC7432, is Informational track, and not standard track.

G/

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>
Sent: Monday, January 29, 2018 09:27
To: bess@ietf.org<mailto:bess@ietf.org>; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Devpn-2Dac-2Ddf_=DwMGaQ=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI

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

2018-01-30 Thread Rabadan, Jorge (Nokia - US/Mountain View) 
Hi Gunter,

Thanks for the feedback.
About this:
I was wondering why this document, even though being backward compatible with 
RFC7432, is Informational track, and not standard track.

I just sent an email providing the initial reasoning discussed among the 
authors. If we still think Standards Track is more appropriate, I think it is 
ok to change it.

Thank you.
Jorge



From: "Van De Velde, Gunter (Nokia - BE/Antwerp)" 
<gunter.van_de_ve...@nokia.com>
Date: Tuesday, January 30, 2018 at 10:46 AM
To: "stephane.litkow...@orange.com" <stephane.litkow...@orange.com>, 
"bess@ietf.org" <bess@ietf.org>, "draft-ietf-bess-evpn-ac-df.auth...@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
Resent-From: <alias-boun...@ietf.org>
Resent-To: <jorge.raba...@nokia.com>, <kiran.naga...@nokia.com>, 
<senthil.sathap...@nokia.com>, <vinod.pra...@nokia.com>, <h...@ciena.com>, 
<w...@juniper.net>
Resent-Date: Tuesday, January 30, 2018 at 10:46 AM

I support progress and publish as RFC.

The document is well written and resolves with a reasonable approach logical 
failures or human errors, that would otherwise result in significant service 
problems.
I was wondering why this document, eventhough being backward compatible with 
RFC7432, is Informational track, and not standard track.

G/

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Monday, January 29, 2018 09:27
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

2018-01-30 Thread Van De Velde, Gunter (Nokia - BE/Antwerp) 
I support progress and publish as RFC.

The document is well written and resolves with a reasonable approach logical 
failures or human errors, that would otherwise result in significant service 
problems.
I was wondering why this document, eventhough being backward compatible with 
RFC7432, is Informational track, and not standard track.

G/

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Monday, January 29, 2018 09:27
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

2018-01-29 Thread Oya Luengo, Roberto (Nokia - US/Mountain View) 
Support

From: BESS <bess-boun...@ietf.org> on behalf of "stephane.litkow...@orange.com" 
<stephane.litkow...@orange.com>
Date: Monday, January 29, 2018 at 12:27 AM
To: "bess@ietf.org" <bess@ietf.org>, 
"draft-ietf-bess-evpn-ac-df.auth...@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

2018-01-29 Thread Jeff Tantsura 
Yes/support 

Regards,
Jeff

> On Jan 29, 2018, at 13:16, Nagaraj, Kiran (Nokia - US/Mountain View) 
> <kiran.naga...@nokia.com> 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) <wim.henderi...@nokia.com>; Rabadan, 
> Jorge (Nokia - US/Mountain View) <jorge.raba...@nokia.com>; 
> 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) <jorge.raba...@nokia.com>; 
> 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 <bess-boun...@ietf.org> on behalf of Jorge Rabadan 
> <jorge.raba...@nokia.com>
> Date: Monday, 29 January 2018 at 03:53
> To: Stephane Litkowski <stephane.litkow...@orange.com>, "bess@ietf.org" 
> <bess@ietf.org>, "draft-ietf-bess-evpn-ac-df.auth...@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" <stephane.litkow...@orange.com>
> Date: Monday, January 29, 2018 at 9:27 AM
> To: "bess@ietf.org" <bess@ietf.org>, 
> "draft-ietf-bess-evpn-ac-df.auth...@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: <alias-boun...@ietf.org>
> Resent-To: <jorge.raba...@nokia.com>, <kiran.naga...@nokia.com>, 
> <senthil.sathap...@nokia.com>, <vinod.pra...@nokia.com>, <h...@ciena.com>, 
> <w...@juniper.net>
> 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 susceptib

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

2018-01-29 Thread 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) <wim.henderi...@nokia.com>; Rabadan, 
Jorge (Nokia - US/Mountain View) <jorge.raba...@nokia.com>; 
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) 
<jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>; 
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>; 
bess@ietf.org<mailto:bess@ietf.org>; 
draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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 <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> on behalf of 
Jorge Rabadan <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>
Date: Monday, 29 January 2018 at 03:53
To: Stephane Litkowski 
<stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>>, 
"bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto:draft-ietf-bess-evpn-ac-df.auth...@ietf.org>"
 
<draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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<mailto:stephane.litkow...@orange.com>" 
<stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>>
Date: Monday, January 29, 2018 at 9:27 AM
To: "bess@ietf.org<mailto:bess@ietf.org>" 
<bess@ietf.org<mailto:bess@ietf.org>>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto:draft-ietf-bess-evpn-ac-df.auth...@ietf.org>"
 
<draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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: <alias-boun...@ietf.org<mailto:alias-boun...@ietf.org>>
Resent-To: <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>, 
<kiran.naga...@nokia.com<mailto:kiran.naga...@nokia.com>>, 
<senthil.sathap...@nokia.com<mailto:senthil.sathap...@nokia.com>>, 
<vinod.pra...@nokia.com<mailto:vinod.pra...@nokia.com>>, 
<h...@ciena.com<mailto:h...@ciena.com>>, 
<w...@juniper.net<mailto:w...@juniper.net>>
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 informatio

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

2018-01-29 Thread 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) <jorge.raba...@nokia.com>; 
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 <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> on behalf of 
Jorge Rabadan <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>
Date: Monday, 29 January 2018 at 03:53
To: Stephane Litkowski 
<stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>>, 
"bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto:draft-ietf-bess-evpn-ac-df.auth...@ietf.org>"
 
<draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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<mailto:stephane.litkow...@orange.com>" 
<stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>>
Date: Monday, January 29, 2018 at 9:27 AM
To: "bess@ietf.org<mailto:bess@ietf.org>" 
<bess@ietf.org<mailto:bess@ietf.org>>, 
"draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto:draft-ietf-bess-evpn-ac-df.auth...@ietf.org>"
 
<draft-ietf-bess-evpn-ac-df.auth...@ietf.org<mailto: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: <alias-boun...@ietf.org<mailto:alias-boun...@ietf.org>>
Resent-To: <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>, 
<kiran.naga...@nokia.com<mailto:kiran.naga...@nokia.com>>, 
<senthil.sathap...@nokia.com<mailto:senthil.sathap...@nokia.com>>, 
<vinod.pra...@nokia.com<mailto:vinod.pra...@nokia.com>>, 
<h...@ciena.com<mailto:h...@ciena.com>>, 
<w...@juniper.net<mailto:w...@juniper.net>>
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

2018-01-29 Thread Henderickx, Wim (Nokia - BE/Antwerp) 
Support as contributor, not aware of IPR related to this draft

From: BESS <bess-boun...@ietf.org> on behalf of Jorge Rabadan 
<jorge.raba...@nokia.com>
Date: Monday, 29 January 2018 at 03:53
To: Stephane Litkowski <stephane.litkow...@orange.com>, "bess@ietf.org" 
<bess@ietf.org>, "draft-ietf-bess-evpn-ac-df.auth...@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" <stephane.litkow...@orange.com>
Date: Monday, January 29, 2018 at 9:27 AM
To: "bess@ietf.org" <bess@ietf.org>, 
"draft-ietf-bess-evpn-ac-df.auth...@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: <alias-boun...@ietf.org>
Resent-To: <jorge.raba...@nokia.com>, <kiran.naga...@nokia.com>, 
<senthil.sathap...@nokia.com>, <vinod.pra...@nokia.com>, <h...@ciena.com>, 
<w...@juniper.net>
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

2018-01-29 Thread 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<mailto:stephane.litkow...@orange.com>" 
<stephane.litkow...@orange.com<mailto: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<mailto: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

2018-01-29 Thread 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

2018-01-29 Thread Nabeel Cocker 
Support 

Regards,
Nabeel

> On Jan 29, 2018, at 3:51 AM, Rabadan, Jorge (Nokia - US/Mountain View) 
> <jorge.raba...@nokia.com> 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" <stephane.litkow...@orange.com>
> Date: Monday, January 29, 2018 at 9:27 AM
> To: "bess@ietf.org" <bess@ietf.org>, 
> "draft-ietf-bess-evpn-ac-df.auth...@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: <alias-boun...@ietf.org>
> Resent-To: <jorge.raba...@nokia.com>, <kiran.naga...@nokia.com>, 
> <senthil.sathap...@nokia.com>, <vinod.pra...@nokia.com>, <h...@ciena.com>, 
> <w...@juniper.net>
> 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

2018-01-29 Thread 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" <stephane.litkow...@orange.com>
Date: Monday, January 29, 2018 at 9:27 AM
To: "bess@ietf.org" <bess@ietf.org>, 
"draft-ietf-bess-evpn-ac-df.auth...@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: <alias-boun...@ietf.org>
Resent-To: <jorge.raba...@nokia.com>, <kiran.naga...@nokia.com>, 
<senthil.sathap...@nokia.com>, <vinod.pra...@nokia.com>, <h...@ciena.com>, 
<w...@juniper.net>
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

2018-01-29 Thread 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