Re: [bess] WG Last Call for draft-ietf-bess-fat-pw-bgp

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

Andrew

Sent from my iPhone

> On Jun 13, 2017, at 12:28 AM, Martin Vigoureux  
> wrote:
> 
> Hello Working Group,
> 
> This email starts a Working Group Last Call on draft-ietf-bess-fat-pw-bgp-02 
> [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
> *26th 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 a Proposed Standard 
> RFC.
> 
> ¤ *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to draft-ietf-bess-fat-pw-bgp, 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-fat-pw-bgp-02 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,
> M
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-fat-pw-bgp/
> [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 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-fat-pw-bgp

2017-06-12 Thread Satya Mohanty (satyamoh) 
Support.

Thanks,
—Satya




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

>Hello Working Group,
>
>This email starts a Working Group Last Call on 
>draft-ietf-bess-fat-pw-bgp-02 [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
>*26th 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 a Proposed 
>Standard RFC.
>
>¤ *Coincidentally*, we are also polling for knowledge of any IPR that 
>applies to draft-ietf-bess-fat-pw-bgp, 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-fat-pw-bgp-02 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,
>M
>
>[1] https://datatracker.ietf.org/doc/draft-ietf-bess-fat-pw-bgp/
>[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  on behalf of Senad IETF - Internet 
Engineering Task Force 
Date: Monday, 12 June 2017 at 21:28
To: "Vigoureux, Martin (Nokia - FR/Nozay)" 
Cc: BESS 
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 
> 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 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-fat-pw-bgp

2017-06-12 Thread UTTARO, JAMES 
Support.

Jim Uttaro

-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Rabadan, Jorge (Nokia - 
US/Mountain View)
Sent: Monday, June 12, 2017 3:14 PM
To: Vigoureux, Martin (Nokia - FR/Nozay) ; BESS 

Subject: Re: [bess] WG Last Call for draft-ietf-bess-fat-pw-bgp

As a co-author I support this document for publication as a Proposed Standard 
RFC.



I’m not aware of any related IPR.

Thanks.

Jorge







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



Hello Working Group,



This email starts a Working Group Last Call on 

draft-ietf-bess-fat-pw-bgp-02 [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

*26th 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 a Proposed 

Standard RFC.



¤ *Coincidentally*, we are also polling for knowledge of any IPR that 

applies to draft-ietf-bess-fat-pw-bgp, 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-fat-pw-bgp-02 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,

M



[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Dfat-2Dpw-2Dbgp_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=P_ZdihBQVa1AyhreAxJdjnZG411-YedlmZk53X7xWIc=KljzQIrOJ_XB2tu3RgwOVV_L5GwpfmgeziTAMBWPMMQ=
 

[2] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=P_ZdihBQVa1AyhreAxJdjnZG411-YedlmZk53X7xWIc=06LbDOfQR-6fk2fOnVtzdqFXja3wM_Oz3rQxDD-4LYc=
 



___

BESS mailing list

BESS@ietf.org


https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=P_ZdihBQVa1AyhreAxJdjnZG411-YedlmZk53X7xWIc=rqTY4jIpnox3BvGPRzra4-c4Hkh8Yr-JxitF_PMU8nM=
 





___
BESS mailing list
BESS@ietf.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=s7ZzB4JbPv3nYuoSx5Gy8Q=P_ZdihBQVa1AyhreAxJdjnZG411-YedlmZk53X7xWIc=rqTY4jIpnox3BvGPRzra4-c4Hkh8Yr-JxitF_PMU8nM=
 
___
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  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 
> *Cc:* BESS 
> *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/
> 
> [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 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 
Cc: BESS 
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 
> 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 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-fat-pw-bgp

2017-06-12 Thread Sami Boutros 
Hi Martin,

I'm not aware of any IPR.

Thanks,

Sami

> On Jun 12, 2017, at 9:27 AM, Martin Vigoureux  
> wrote:
> 
> Hello Working Group,
> 
> This email starts a Working Group Last Call on draft-ietf-bess-fat-pw-bgp-02 
> [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
> *26th 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 a Proposed Standard 
> RFC.
> 
> ¤ *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to draft-ietf-bess-fat-pw-bgp, 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-fat-pw-bgp-02 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,
> M
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-fat-pw-bgp/
> [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-fat-pw-bgp

2017-06-12 Thread Jose Liste (jliste) 

As a co-author, I support publication of this document as a Proposed Standard 
RFC
I am not aware of any relevant IPR

Thanks,
Jose

-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
Sent: Monday, June 12, 2017 9:28 AM
To: BESS 
Subject: [bess] WG Last Call for draft-ietf-bess-fat-pw-bgp

Hello Working Group,

This email starts a Working Group Last Call on
draft-ietf-bess-fat-pw-bgp-02 [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 *26th 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 a Proposed Standard RFC.

¤ *Coincidentally*, we are also polling for knowledge of any IPR that applies 
to draft-ietf-bess-fat-pw-bgp, 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-fat-pw-bgp-02 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,
M

[1] https://datatracker.ietf.org/doc/draft-ietf-bess-fat-pw-bgp/
[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-fat-pw-bgp

2017-06-12 Thread Rabadan, Jorge (Nokia - US/Mountain View) 
As a co-author I support this document for publication as a Proposed Standard 
RFC.

I’m not aware of any related IPR.
Thanks.
Jorge



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

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-fat-pw-bgp-02 [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
*26th 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 a Proposed 
Standard RFC.

¤ *Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-fat-pw-bgp, 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-fat-pw-bgp-02 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,
M

[1] https://datatracker.ietf.org/doc/draft-ietf-bess-fat-pw-bgp/
[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

[bess] WG Last Call for draft-ietf-bess-fat-pw-bgp

2017-06-12 Thread Martin Vigoureux 

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-fat-pw-bgp-02 [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
*26th 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 a Proposed 
Standard RFC.


¤ *Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-fat-pw-bgp, 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-fat-pw-bgp-02 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,
M

[1] https://datatracker.ietf.org/doc/draft-ietf-bess-fat-pw-bgp/
[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

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

[bess] IPR Disclosure Huawei Technologies Co., Ltd's Statement about IPR related to draft-ietf-bess-nsh-bgp-control-plane

2017-06-12 Thread IETF Secretariat 
Dear Adrian Farrel, John Drake, Eric C. Rosen, Jim Uttaro, Luay Jalil:


An IPR disclosure that pertains to your Internet-Draft entitled "BGP
Control Plane for NSH SFC" (draft-ietf-bess-nsh-bgp-control-plane) was
submitted to the IETF Secretariat on  and has been posted on the "IETF Page
of Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/3011/). The title of the IPR disclosure is
"Huawei Technologies Co.,Ltd's Statement about IPR related to
draft-ietf-bess-nsh-bgp-control-plane"


Thank you

IETF Secretariat

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

Re: [bess] MIBDoc review of draft-ietf-bess-mvpn-mib-02.txt

2017-06-12 Thread Glenn Mansfield Keeni 

Hi Tsuno,
   Got this. I will be working on this. It is massive-
40 pages. I hope to get back to you on this by the end
of next week.

Cheers,

Glenn
On 2017/06/07 1:22, Hiroshi Tsunoda wrote:

Hi Glenn,

I posted a new revision (-04) of MVPN-MIB document.
In this revision, "Summary of MIB Module" has been rewritten.
I hope this change improves the readability.

URL:https://www.ietf.org/internet-drafts/draft-ietf-bess-mvpn-mib-04.txt
Htmlized: https://tools.ietf.org/html/draft-ietf-bess-mvpn-mib-04
Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-bess-mvpn-mib-04
Diff:  https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-mvpn-mib-04

Please see notes below for other changes.

2017-03-01 16:00 GMT+01:00 Hiroshi Tsunoda :

1.  Abstract:
1.2 "In particular, it describes managed objects to configure and/or
 monitor Multicast in MPLS/BGP IP VPNs (MVPN) on a router."
Is this for any router or, a "Provider Edge" router ?
Please fix accordingly.


This point will be fixed in the next revision.


Fixed. "Provide Edge" router is correct.


2.  Introduction
Are the objects "generic" to PIM-MVPN and BGP-MVPN or "common"
to  PIM-MVPN and BGP-MVPN ? Please change accordingly.


This point will be fixed in the next revision.


Fixed. "common" is correct.


2.5 The terminology section is a bit terse. Explaining the terms
that are used, with reference to the protocol documents will
improve readability.
e.g.
 - MVPN, PE, PMSI/tunnels,
 - C-multicast routing exchange protocol (PIM or BGP),
   C-multicast states
 - I-PMSI, S-PMSI, provider tunnels


Partially fixed. I will give more detailed explanation in the next revision.


I have added some more explanation in this revision.


3.  MVPN MIB.
This gives the overview of the MVPN MIB.
The MIB module aims to provide "configuring and/or monitoring"
3.1 In
 "This MIB enables configuring and/or monitoring of MVPNs on PE
 devices: the whole multicast VPN machinery."
"the whole multicast VPN machinery" is very difficult to define.
Please use precisely defined terms.
3.2 In "To represent them,"
"them" seems ambiguous, please clarify.
3.3 The diagram needs some explanation.
What do the boxes represent? Tables ? The labels are meant to be
table names ? The table names do not match the labels.
What do the arrows signify? Please explain.
3.4 The short explanation of the tables could be augmented with some
information on what they represent and an idea of how they will
be used. ( RFC 4382 provides a good example).


I have rewritten "Sec.3.1 Summary of MIB Module".
Eight tables can be categorized into two groups: tables for configuration and
tables for monitoring.
In this revision, the diagram representing the relationship among tables is
divided to two separated diagrams based on the roles of tables.


MIB definitions:
7. Wherever possible, please provide references for objects used in the
MIB. The references will point to specific sections/sub-sections of
RFCs defining the protocol for which the MIB is being designed.


This will be addressed in the next revision.


I have added some references but more are required.
I will keep working on this.


8. MOs.
8.2 mvpnMvrfNumber OBJECT-TYPE
   SYNTAX Unsigned32
   DESCRIPTION
   "The total number of MVRFs that are present on this device,
whether for IPv4, IPv6, or mLDP C-Multicast."
o Please make the description precise. E.g. if it is the sum of
  IPv4 MVRFs, IPv6 MVRFs and mLDP C-Multicast MVRFs state it
  explicitly.
o The expression "present on this device" is used.
  Does "present" imply "configured" MVRFs or "active" MVRFs.
  If it is number of active MVRFs then one would expect that
  the number will vary (increase or decrease). If that is the
  case:
  replace
   SYNTAXUnsigned32
  by
   SYNTAXGauge32


I will try to update description in the next revision.


8.5 mvpnGenOperStatusChange OBJECT-TYPE
SYNTAX  INTEGER { createdMvrf(1),
  deletedMvrf(2),
  modifiedMvrfIpmsiConfig(3),
 modifiedMvrfSpmsiConfig(4)
}
   DESCRIPTION
   "This object describes the last operational change that
o The name does not look right. From the SYNTAX and the DESCRIPTION
  it appears that this is about config or MVRF change rather than
  "OperStatus" change. Please check and fix.
o Please confirm that the values in the row itself will not be changed
  after creation. ( you do not have a 'modifiedMvrfConfig')


The name has been changed into mvpnGenMvrfStatusChange.
The name of the related object (mvpnGenOperStatusChangeTime) has
also been changed into mvpnGenMvrfStatusChangeTime.


8.6 mvpnGenCmcastRouteProtocol OBJECT-TYPE
   MAX-ACCESS