Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

2017-06-21 Thread Martin Vigoureux 

WG,

the WG LC has ended and we have support to move forward.
I'll shepherd the document.

-m

Le 06/06/2017 à 16:11, Martin Vigoureux a écrit :

Hello Working Group,

This email starts a Working Group Last Call on
draft-ietf-bess-evpn-usage-04 [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
*20th of June*.
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.

*Coincidentally*, we are also polling for knowledge of any IPR that
applies to draft-ietf-bess-evpn-usage, 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
draft-ietf-bess-evpn-usage-04 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.

As opposed to the policy [2], we are not polling for knowledge of
implementations as it does not seem to make sense in that case. If you
feel otherwise, please let us know.

Thank you,
M

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

___
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 for draft-ietf-bess-evpn-usage

2017-06-20 Thread Aldrin Isaac 
I support to move this document forward to publication.  There are no
IPR that I am aware of related to this document.

Apologies for leaving out IPR statement.

Regards -- Aldrin



On Mon, Jun 12, 2017 at 12:52 PM Aldrin Isaac <aldrin.is...@gmail.com>
wrote:

> Yes. I support to move this forward.
>
> Regards -- Aldrin
> On Mon, Jun 12, 2017 at 3:39 PM UTTARO, JAMES <ju1...@att.com> wrote:
>
>> *Fully support as co-author..I am not aware of any IPR related to this
>> document..*
>>
>>
>>
>> *Thanks,*
>>
>> *Jim Uttaro*
>>
>>
>>
>> *From:* BESS [mailto:bess-boun...@ietf.org] *On Behalf Of *Senad IETF -
>> Internet Engineering Task Force
>> *Sent:* Monday, June 12, 2017 3:29 PM
>> *To:* Martin Vigoureux <martin.vigour...@nokia.com>
>> *Cc:* BESS <bess@ietf.org>
>> *Subject:* Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage
>>
>>
>>
>> Full support of this document for RFC publication.  As a co-author, I am
>> not aware of any IPR related to this document.
>>
>>
>>
>> On Tue, Jun 6, 2017 at 10:11 AM, Martin Vigoureux <
>> martin.vigour...@nokia.com> wrote:
>>
>> Hello Working Group,
>>
>> This email starts a Working Group Last Call on
>> draft-ietf-bess-evpn-usage-04 [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
>> *20th of June*.
>> 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.
>>
>> *Coincidentally*, we are also polling for knowledge of any IPR that
>> applies to draft-ietf-bess-evpn-usage, 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
>> draft-ietf-bess-evpn-usage-04 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.
>>
>> As opposed to the policy [2], we are not polling for knowledge of
>> implementations as it does not seem to make sense in that case. If you feel
>> otherwise, please let us know.
>>
>> Thank you,
>> M
>>
>> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Devpn-2Dusage_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8=RuJG5P3GiwU0kDVlo12PU41vXQ4DzY-_xqvgolWjkq4=>
>> [2]
>> https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8=tLVXhULe4bJzbVBsBOybultgu62EreH6szg5v5-j5As=>
>>
>> ___
>> BESS mailing list
>> BESS@ietf.org
>> https://www.ietf.org/mailman/listinfo/bess
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8=ocQqmy844e0BOlY73StBUg5Zh5vxs8JaCD6hhDXfm7Q=>
>>
>>
>> ___
>> 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 for draft-ietf-bess-evpn-usage

2017-06-14 Thread Keyur Patel 
I support publication of this document. I am not aware of any IPR related to 
this doc that hasn’t already been disclosed.

Regards,
Keyur


On 6/12/17, 9:27 AM, "BESS on behalf of Martin Vigoureux" 
 wrote:

WG, Authors/Contributors, this is a reminder.
Thank you
-m


Le 06/06/2017 à 16:11, Martin Vigoureux a écrit :
> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-usage-04 [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
> *20th of June*.
> 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.
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-evpn-usage, 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
> draft-ietf-bess-evpn-usage-04 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.
>
> As opposed to the policy [2], we are not polling for knowledge of
> implementations as it does not seem to make sense in that case. If you
> feel otherwise, please let us know.
>
> Thank you,
> M
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
> ___
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
>

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


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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

2017-06-14 Thread Walsh, Brian (Nokia - SG/Singapore) 
Support.

Thx,
Brian

-Original Message-
From: BESS <bess-boun...@ietf.org> on behalf of Martin Vigoureux 
<martin.vigour...@nokia.com>
Date: Tuesday, 6 June 2017 at 10:11 PM
To: BESS <bess@ietf.org>
Subject: [bess] WG Last Call for draft-ietf-bess-evpn-usage

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-evpn-usage-04 [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
*20th of June*.
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.

*Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-evpn-usage, 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
draft-ietf-bess-evpn-usage-04 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.

As opposed to the policy [2], we are not polling for knowledge of 
implementations as it does not seem to make sense in that case. If you 
feel otherwise, please let us know.

Thank you,
M

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

___
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 for draft-ietf-bess-evpn-usage

2017-06-13 Thread Jeff Tantsura 
Yes/support 

Regards,
Jeff

> On Jun 12, 2017, at 23:40, 
> On 6/6/17, 10:11 AM, "BESS on behalf of Martin Vigoureux"
>  wrote:
> 
>> Hello Working Group,
>> 
>> This email starts a Working Group Last Call on
>> draft-ietf-bess-evpn-usage-04 [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
>> *20th of June*.
>> 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.
>> 
>> *Coincidentally*, we are also polling for knowledge of any IPR that
>> applies to draft-ietf-bess-evpn-usage, 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
>> draft-ietf-bess-evpn-usage-04 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.
>> 
>> As opposed to the policy [2], we are not polling for knowledge of
>> implementations as it does not seem to make sense in that case. If you
>> feel otherwise, please let us know.
>> 
>> Thank you,
>> M
>> 
>> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
>> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>> 
>> ___
>> BESS mailing list
>> BESS@ietf.org
>> https://www.ietf.org/mailman/listinfo/bess
> 
> ___
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess

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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

2017-06-12 Thread Ali Sajassi (sajassi) 

I support publication of this document. I am not aware of any IPR related
to this doc that hasn¹t already been disclosed.

Regards,
Ali

On 6/6/17, 7:11 AM, "BESS on behalf of Martin Vigoureux"
 wrote:

>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-usage-04 [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
>*20th of June*.
>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.
>
>*Coincidentally*, we are also polling for knowledge of any IPR that
>applies to draft-ietf-bess-evpn-usage, 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
>draft-ietf-bess-evpn-usage-04 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.
>
>As opposed to the policy [2], we are not polling for knowledge of
>implementations as it does not seem to make sense in that case. If you
>feel otherwise, please let us know.
>
>Thank you,
>M
>
>[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
>[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>___
>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 for draft-ietf-bess-evpn-usage

2017-06-12 Thread Acee Lindem (acee) 
I support publication.
Thanks,
Acee

On 6/6/17, 10:11 AM, "BESS on behalf of Martin Vigoureux"
 wrote:

>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-usage-04 [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
>*20th of June*.
>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.
>
>*Coincidentally*, we are also polling for knowledge of any IPR that
>applies to draft-ietf-bess-evpn-usage, 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
>draft-ietf-bess-evpn-usage-04 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.
>
>As opposed to the policy [2], we are not polling for knowledge of
>implementations as it does not seem to make sense in that case. If you
>feel otherwise, please let us know.
>
>Thank you,
>M
>
>[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
>[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>___
>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 for draft-ietf-bess-evpn-usage

2017-06-12 Thread Henderickx, Wim (Nokia - BE/Antwerp) 
Support as co-author. Not aware of IPR related to this draft

From: BESS <bess-boun...@ietf.org> on behalf of Senad IETF - Internet 
Engineering Task Force <senad.i...@gmail.com>
Date: Monday, 12 June 2017 at 21:28
To: "Vigoureux, Martin (Nokia - FR/Nozay)" <martin.vigour...@nokia.com>
Cc: BESS <bess@ietf.org>
Subject: Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

Full support of this document for RFC publication.  As a co-author, I am not 
aware of any IPR related to this document.

On Tue, Jun 6, 2017 at 10:11 AM, Martin Vigoureux 
<martin.vigour...@nokia.com<mailto:martin.vigour...@nokia.com>> wrote:
Hello Working Group,

This email starts a Working Group Last Call on draft-ietf-bess-evpn-usage-04 
[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
*20th of June*.
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.

*Coincidentally*, we are also polling for knowledge of any IPR that applies to 
draft-ietf-bess-evpn-usage, 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
draft-ietf-bess-evpn-usage-04 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.

As opposed to the policy [2], we are not polling for knowledge of 
implementations as it does not seem to make sense in that case. If you feel 
otherwise, please let us know.

Thank you,
M

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

___
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 for draft-ietf-bess-evpn-usage

2017-06-12 Thread Oya Luengo, Roberto (Nokia - US/Mountain View) 
Support


On 6/6/17, 7:11 AM, "BESS on behalf of Martin Vigoureux"  wrote:

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-evpn-usage-04 [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
*20th of June*.
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.

*Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-evpn-usage, 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
draft-ietf-bess-evpn-usage-04 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.

As opposed to the policy [2], we are not polling for knowledge of 
implementations as it does not seem to make sense in that case. If you 
feel otherwise, please let us know.

Thank you,
M

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

___
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 for draft-ietf-bess-evpn-usage

2017-06-12 Thread Aldrin Isaac 
Yes. I support to move this forward.

Regards -- Aldrin
On Mon, Jun 12, 2017 at 3:39 PM UTTARO, JAMES <ju1...@att.com> wrote:

> *Fully support as co-author..I am not aware of any IPR related to this
> document..*
>
>
>
> *Thanks,*
>
> *Jim Uttaro*
>
>
>
> *From:* BESS [mailto:bess-boun...@ietf.org] *On Behalf Of *Senad IETF -
> Internet Engineering Task Force
> *Sent:* Monday, June 12, 2017 3:29 PM
> *To:* Martin Vigoureux <martin.vigour...@nokia.com>
> *Cc:* BESS <bess@ietf.org>
> *Subject:* Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage
>
>
>
> Full support of this document for RFC publication.  As a co-author, I am
> not aware of any IPR related to this document.
>
>
>
> On Tue, Jun 6, 2017 at 10:11 AM, Martin Vigoureux <
> martin.vigour...@nokia.com> wrote:
>
> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-usage-04 [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
> *20th of June*.
> 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.
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-evpn-usage, 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
> draft-ietf-bess-evpn-usage-04 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.
>
> As opposed to the policy [2], we are not polling for knowledge of
> implementations as it does not seem to make sense in that case. If you feel
> otherwise, please let us know.
>
> Thank you,
> M
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Devpn-2Dusage_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8=RuJG5P3GiwU0kDVlo12PU41vXQ4DzY-_xqvgolWjkq4=>
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8=tLVXhULe4bJzbVBsBOybultgu62EreH6szg5v5-j5As=>
>
> ___
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8=ocQqmy844e0BOlY73StBUg5Zh5vxs8JaCD6hhDXfm7Q=>
>
>
> ___
> 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 for draft-ietf-bess-evpn-usage

2017-06-12 Thread UTTARO, JAMES 
Fully support as co-author..I am not aware of any IPR related to this document..

Thanks,
Jim Uttaro

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Senad IETF - Internet 
Engineering Task Force
Sent: Monday, June 12, 2017 3:29 PM
To: Martin Vigoureux <martin.vigour...@nokia.com>
Cc: BESS <bess@ietf.org>
Subject: Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

Full support of this document for RFC publication.  As a co-author, I am not 
aware of any IPR related to this document.

On Tue, Jun 6, 2017 at 10:11 AM, Martin Vigoureux 
<martin.vigour...@nokia.com<mailto:martin.vigour...@nokia.com>> wrote:
Hello Working Group,

This email starts a Working Group Last Call on draft-ietf-bess-evpn-usage-04 
[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
*20th of June*.
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.

*Coincidentally*, we are also polling for knowledge of any IPR that applies to 
draft-ietf-bess-evpn-usage, 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
draft-ietf-bess-evpn-usage-04 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.

As opposed to the policy [2], we are not polling for knowledge of 
implementations as it does not seem to make sense in that case. If you feel 
otherwise, please let us know.

Thank you,
M

[1] 
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Devpn-2Dusage_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8=RuJG5P3GiwU0kDVlo12PU41vXQ4DzY-_xqvgolWjkq4=>
[2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8=tLVXhULe4bJzbVBsBOybultgu62EreH6szg5v5-j5As=>

___
BESS mailing list
BESS@ietf.org<mailto:BESS@ietf.org>
https://www.ietf.org/mailman/listinfo/bess<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8=ocQqmy844e0BOlY73StBUg5Zh5vxs8JaCD6hhDXfm7Q=>

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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

2017-06-12 Thread Senad IETF - Internet Engineering Task Force 
Full support of this document for RFC publication.  As a co-author, I am
not aware of any IPR related to this document.

On Tue, Jun 6, 2017 at 10:11 AM, Martin Vigoureux <
martin.vigour...@nokia.com> wrote:

> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-usage-04 [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
> *20th of June*.
> 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.
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-evpn-usage, 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
> draft-ietf-bess-evpn-usage-04 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.
>
> As opposed to the policy [2], we are not polling for knowledge of
> implementations as it does not seem to make sense in that case. If you feel
> otherwise, please let us know.
>
> Thank you,
> M
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
> ___
> 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 for draft-ietf-bess-evpn-usage

2017-06-12 Thread Martin Vigoureux 

WG, Authors/Contributors, this is a reminder.
Thank you
-m


Le 06/06/2017 à 16:11, Martin Vigoureux a écrit :

Hello Working Group,

This email starts a Working Group Last Call on
draft-ietf-bess-evpn-usage-04 [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
*20th of June*.
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.

*Coincidentally*, we are also polling for knowledge of any IPR that
applies to draft-ietf-bess-evpn-usage, 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
draft-ietf-bess-evpn-usage-04 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.

As opposed to the policy [2], we are not polling for knowledge of
implementations as it does not seem to make sense in that case. If you
feel otherwise, please let us know.

Thank you,
M

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

___
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 for draft-ietf-bess-evpn-usage

2017-06-06 Thread Nabeel Cocker 
Support

Regards,
Nabeel

> On Jun 6, 2017, at 10:11 AM, Martin Vigoureux  
> wrote:
> 
> Hello Working Group,
> 
> This email starts a Working Group Last Call on draft-ietf-bess-evpn-usage-04 
> [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
> *20th of June*.
> 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.
> 
> *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to draft-ietf-bess-evpn-usage, 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
> draft-ietf-bess-evpn-usage-04 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.
> 
> As opposed to the policy [2], we are not polling for knowledge of 
> implementations as it does not seem to make sense in that case. If you feel 
> otherwise, please let us know.
> 
> Thank you,
> M
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
> 
> ___
> 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 for draft-ietf-bess-evpn-usage

2017-06-06 Thread Dolganow, Andrew (Nokia - SG/Singapore) 
support

Andrew

-Original Message-
From: BESS <bess-boun...@ietf.org> on behalf of MARTIN VIGOUREUX 
<martin.vigour...@nokia.com>
Date: Tuesday, June 6, 2017 at 7:11 AM
To: BESS <bess@ietf.org>
Subject: [bess] WG Last Call for draft-ietf-bess-evpn-usage

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-evpn-usage-04 [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
*20th of June*.
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.

*Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-evpn-usage, 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
draft-ietf-bess-evpn-usage-04 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.

As opposed to the policy [2], we are not polling for knowledge of 
implementations as it does not seem to make sense in that case. If you 
feel otherwise, please let us know.

Thank you,
M

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

___
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 for draft-ietf-bess-evpn-usage

2017-06-06 Thread Rabadan, Jorge (Nokia - US/Mountain View) 
I fully support this document for RFC publication. 
As a co-author, I’m not aware of any related IPR.

Thanks.
Jorge


On 6/6/17, 7:11 AM, "BESS on behalf of Martin Vigoureux"  wrote:

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-evpn-usage-04 [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
*20th of June*.
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.

*Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-evpn-usage, 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
draft-ietf-bess-evpn-usage-04 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.

As opposed to the policy [2], we are not polling for knowledge of 
implementations as it does not seem to make sense in that case. If you 
feel otherwise, please let us know.

Thank you,
M

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

___
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 for draft-ietf-bess-evpn-usage

2017-06-06 Thread Jeff Tantsura 
Yes/support

Regards,
Jeff

> On Jun 6, 2017, at 10:11, Martin Vigoureux  wrote:
> 
> Hello Working Group,
> 
> This email starts a Working Group Last Call on draft-ietf-bess-evpn-usage-04 
> [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
> *20th of June*.
> 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.
> 
> *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to draft-ietf-bess-evpn-usage, 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
> draft-ietf-bess-evpn-usage-04 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.
> 
> As opposed to the policy [2], we are not polling for knowledge of 
> implementations as it does not seem to make sense in that case. If you feel 
> otherwise, please let us know.
> 
> Thank you,
> M
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
> 
> ___
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess

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

[bess] WG Last Call for draft-ietf-bess-evpn-usage

2017-06-06 Thread Martin Vigoureux 

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-evpn-usage-04 [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
*20th of June*.
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.


*Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-evpn-usage, 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
draft-ietf-bess-evpn-usage-04 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.


As opposed to the policy [2], we are not polling for knowledge of 
implementations as it does not seem to make sense in that case. If you 
feel otherwise, please let us know.


Thank you,
M

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

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