Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-irb-mcast-04

[Wen Lin]

Support as co-author.  I am unaware of any undisclosed IPRs.

Thanks,
Wen

From: BESS  on behalf of "slitkows.i...@gmail.com" 

Date: Wednesday, February 26, 2020 at 9:26 AM
To: 'BESS' 
Cc: "bess-cha...@ietf.org" 
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Hi WG,

This email starts a two weeks Working Group Last Call on 
draft-ietf-bess-evpn-irb-mcast-04 [2]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until 11th March 2020.


We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently one IPR disclosed.

https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-bess-evpn-irb-mcast



We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations.

 Thank you,

Stephane

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

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

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-irb-mcast-04

[Walsh, Brian (Nokia - SG/Singapore)]

Support – this is highly relevant work.

Thx,
Brian

From: BESS  on behalf of "slitkows.i...@gmail.com" 

Date: Wednesday, 26 February 2020 at 22:26
To: 'BESS' 
Cc: "bess-cha...@ietf.org" 
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Hi WG,

This email starts a two weeks Working Group Last Call on 
draft-ietf-bess-evpn-irb-mcast-04 [2]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until 11th March 2020.


We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently one IPR disclosed.

https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-bess-evpn-irb-mcast



We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations.

 Thank you,

Stephane

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

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

Re: [bess] WG adoption poll for draft-gmsm-bess-evpn-bfd-04

[zhang.zheng]

Support the adoption.






Thanks,


Sandy









原始邮件



发件人：Bocci,Matthew(Nokia-GB) 
收件人：draft-gmsm-bess-evpn-...@ietf.org 
;bess@ietf.org ;
抄送人：bess-cha...@ietf.org ;
日 期 ：2020年02月26日 22:42
主 题 ：[bess] WG adoption poll for draft-gmsm-bess-evpn-bfd-04




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



Hello,


 


This email begins a two-weeks WG adoption poll
 for draft-gmsm-bess-evpn-bfd-04 [1] .


 


Please review the draft and post any comments to the BESS working group list.


 


We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).


 


If you are listed as an author or a contributor of this document, please 
respond to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR, copying the BESS mailing list. The document won't progress 
without
 answers from all the authors and contributors.


 


Currently, there are no IPR disclosures against this document.


 


If you are not listed as an author or a contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.


 


This poll for adoption closes
 on Wednesday 11th March 2020.  


 


Regards,


Matthew and Stephane


 


[1] https://datatracker.ietf.org/doc/draft-gmsm-bess-evpn-bfd/___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-irb-mcast-04

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

Support

From: BESS  on behalf of "slitkows.i...@gmail.com" 

Date: Wednesday, February 26, 2020 at 6:26 AM
To: 'BESS' 
Cc: "bess-cha...@ietf.org" 
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Hi WG,

This email starts a two weeks Working Group Last Call on 
draft-ietf-bess-evpn-irb-mcast-04 [2]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until 11th March 2020.


We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently one IPR disclosed.

https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-bess-evpn-irb-mcast



We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations.

 Thank you,

Stephane

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

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

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-irb-mcast-04

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

Support

From: BESS  On Behalf Of Henderickx, Wim (Nokia - 
BE/Antwerp)
Sent: Wednesday, February 26, 2020 1:39 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) ; 
slitkows.i...@gmail.com; 'BESS' 
Cc: bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Support.

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
Jorge Rabadan mailto:jorge.raba...@nokia.com>>
Date: Wednesday, 26 February 2020 at 16:12
To: "slitkows.i...@gmail.com" 
mailto:slitkows.i...@gmail.com>>, 
"bess@ietf.org" mailto:bess@ietf.org>>
Cc: "bess-cha...@ietf.org" 
mailto:bess-cha...@ietf.org>>
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Support for publication, as co-author. This is a very important and needed 
technology in EVPN networks.
Not aware of any undisclosed IPRs.

Nokia has an implementation of this draft.

Thank you.
Jorge

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
"slitkows.i...@gmail.com" 
mailto:slitkows.i...@gmail.com>>
Date: Wednesday, February 26, 2020 at 3:26 PM
To: 'BESS' mailto:bess@ietf.org>>
Cc: "bess-cha...@ietf.org" 
mailto:bess-cha...@ietf.org>>
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Hi WG,

This email starts a two weeks Working Group Last Call on 
draft-ietf-bess-evpn-irb-mcast-04 [2]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until 11th March 2020.


We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently one IPR disclosed.

https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-bess-evpn-irb-mcast



We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations.

 Thank you,

Stephane

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

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

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-irb-mcast-04

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

Support.

From: BESS  on behalf of Jorge Rabadan 

Date: Wednesday, 26 February 2020 at 16:12
To: "slitkows.i...@gmail.com" , "bess@ietf.org" 

Cc: "bess-cha...@ietf.org" 
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Support for publication, as co-author. This is a very important and needed 
technology in EVPN networks.
Not aware of any undisclosed IPRs.

Nokia has an implementation of this draft.

Thank you.
Jorge

From: BESS  on behalf of "slitkows.i...@gmail.com" 

Date: Wednesday, February 26, 2020 at 3:26 PM
To: 'BESS' 
Cc: "bess-cha...@ietf.org" 
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Hi WG,

This email starts a two weeks Working Group Last Call on 
draft-ietf-bess-evpn-irb-mcast-04 [2]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until 11th March 2020.


We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently one IPR disclosed.

https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-bess-evpn-irb-mcast



We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations.

 Thank you,

Stephane

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

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

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-irb-mcast-04

[John E Drake]

Support and not aware of any IPR

Yours Irrespectively,

John



Juniper Business Use Only
From: BESS  On Behalf Of slitkows.i...@gmail.com
Sent: Wednesday, February 26, 2020 9:25 AM
To: 'BESS' 
Cc: bess-cha...@ietf.org
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Hi WG,

This email starts a two weeks Working Group Last Call on 
draft-ietf-bess-evpn-irb-mcast-04 [2]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until 11th March 2020.


We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently one IPR disclosed.

https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-bess-evpn-irb-mcast



We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations.

 Thank you,

Stephane

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

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

Re: [bess] REMINDER Re: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-datacenter-gateway-04

[John E Drake]

Support and not aware of any IPR

Yours Irrespectively,

John



Juniper Business Use Only
From: Bocci, Matthew (Nokia - GB) 
Sent: Wednesday, February 26, 2020 6:29 AM
To: draft-ietf-bess-datacenter-gate...@ietf.org; bess@ietf.org
Subject: REMINDER Re: [bess] WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-datacenter-gateway-04

WG

I have only seen one IPR responses to this WG last call and no comments. I will 
therefore extend it for another two weeks.

Regards

Matthew

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
"Bocci, Matthew (Nokia - GB)" 
mailto:matthew.bo...@nokia.com>>
Date: Monday, 10 February 2020 at 16:17
To: 
"draft-ietf-bess-datacenter-gate...@ietf.org"
 
mailto:draft-ietf-bess-datacenter-gate...@ietf.org>>,
 "bess@ietf.org" mailto:bess@ietf.org>>
Subject: [bess] WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-datacenter-gateway-04

This email starts a two-week working group last call for 
draft-ietf-bess-datacenter-gateway-04
Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until Monday 24th February 2020.

We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
If you are listed as an Author or a Contributor of this document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently no IPR disclosed.

We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations of the modified protocol described in 
this draft.

 Thank you,

Matthew

[1] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw


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

Re: [bess] WG adoption poll for draft-gmsm-bess-evpn-bfd-04

[Greg Mirsky]

Hi Matthew, et al.,
I am not aware of any undisclosed IPR related to this draft.

I support the adoption of this draft by BESS WG (as co-author).

Regards,
Greg

On Wed, Feb 26, 2020 at 6:42 AM Bocci, Matthew (Nokia - GB) <
matthew.bo...@nokia.com> wrote:

> Hello,
>
>
>
> This email begins a two-weeks WG adoption poll for
> draft-gmsm-bess-evpn-bfd-04 [1] .
>
>
>
> Please review the draft and post any comments to the BESS working group
> list.
>
>
>
> We are also polling for knowledge of any undisclosed IPR that applies to
> this Document, to ensure that IPR has been disclosed in compliance with
> IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
>
>
>
> If you are listed as an author or a contributor of this document, please
> respond to this email and indicate whether or not you are aware of any
> relevant undisclosed IPR, copying the BESS mailing list. The document won't
> progress without answers from all the authors and contributors.
>
>
>
> Currently, there are no IPR disclosures against this document.
>
>
>
> If you are not listed as an author or a contributor, then please
> explicitly respond only if you are aware of any IPR that has not yet been
> disclosed in conformance with IETF rules.
>
>
>
> This poll for adoption closes on Wednesday 11th March 2020.
>
>
>
> Regards,
>
> Matthew and Stephane
>
>
>
> [1] https://datatracker.ietf.org/doc/draft-gmsm-bess-evpn-bfd/
>
>
>
>
>
>
>
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-irb-mcast-04

[Van De Velde, Gunter (Nokia - BE/Antwerp)]

Support. This draft is needed and used within my customer architectures
The draft is ready to be published

G/

From: BESS  On Behalf Of slitkows.i...@gmail.com
Sent: Wednesday, February 26, 2020 15:25
To: 'BESS' 
Cc: bess-cha...@ietf.org
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Hi WG,

This email starts a two weeks Working Group Last Call on 
draft-ietf-bess-evpn-irb-mcast-04 [2]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until 11th March 2020.


We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently one IPR disclosed.

https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-bess-evpn-irb-mcast



We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations.

 Thank you,

Stephane

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

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

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-irb-mcast-04

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

Support for publication, as co-author. This is a very important and needed 
technology in EVPN networks.
Not aware of any undisclosed IPRs.

Nokia has an implementation of this draft.

Thank you.
Jorge

From: BESS  on behalf of "slitkows.i...@gmail.com" 

Date: Wednesday, February 26, 2020 at 3:26 PM
To: 'BESS' 
Cc: "bess-cha...@ietf.org" 
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-irb-mcast-04

Hi WG,

This email starts a two weeks Working Group Last Call on 
draft-ietf-bess-evpn-irb-mcast-04 [2]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until 11th March 2020.


We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently one IPR disclosed.

https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-bess-evpn-irb-mcast



We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations.

 Thank you,

Stephane

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

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

[bess] WG adoption poll for draft-gmsm-bess-evpn-bfd-04

[Bocci, Matthew (Nokia - GB)]

Hello,

This email begins a two-weeks WG adoption poll for draft-gmsm-bess-evpn-bfd-04 
[1] .

Please review the draft and post any comments to the BESS working group list.

We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an author or a contributor of this document, please 
respond to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR, copying the BESS mailing list. The document won't progress 
without answers from all the authors and contributors.

Currently, there are no IPR disclosures against this document.

If you are not listed as an author or a contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

This poll for adoption closes on Wednesday 11th March 2020.

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/draft-gmsm-bess-evpn-bfd/



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

[bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-irb-mcast-04

[slitkows.ietf]

Hi WG,

 

This email starts a two weeks Working Group Last Call on
draft-ietf-bess-evpn-irb-mcast-04 [2]

 

Please review the draft and send any comments to the BESS list. Also, please
indicate if you support publishing the draft as a standards track RFC.

 

This poll runs until 11th March 2020.

 

We are also polling for knowledge of any undisclosed IPR that applies to
this Document, to ensure that IPR has been disclosed in compliance with IETF
IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please
respond to this email and indicate whether or not you are aware of any
relevant undisclosed IPR. The Document won't progress without answers from
all the Authors and Contributors. 

There is currently one IPR disclosed.  

 

https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-bess-evp
n-irb-mcast

 

We are also polling for any existing implementation as per [1]. Please
indicate if you are aware of any implementations.

 Thank you,

Stephane

 

[1]

https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

[2]  
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-mcast/

 

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

[bess] Shepherd's Review of draft-ietf-bess-evpn-pref-df

[slitkows.ietf]

Hi Authors,

 

 

Here is my review of the document:

 

Please look at the nits and fix them.

 

https://www6.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft
-ietf-bess-evpn-pref-df-05.txt

 

 

Section 3:

*   Is the DF preference field only there when DF Alg=2 ? I mean if DF
Alg !=2, can the reserved field be encoded differently ? This should be
clear IMO.

 

Section 4.1:

" Note that, by default, the Highest-Preference is chosen for each

   ES or vES, however the ES configuration can be changed to the

   Lowest-Preference algorithm as long as this option is consistent

   in all the PEs in the ES.

I don't think it is a good idea to open this modification. People can play
with preference values to achieve the required behavior while always keeping
high pref.

We have no way to ensure consistency, except if we advertise the behavior as
part of the exct. Consistency of DF election is key and needs to be ensured
as much as we can.

 

In case of equal Preference in two or more PEs in the ES, the
   tie-breakers will be the DP bit and the lowest IP PE, in that
   order.  For instance:

The sentence is not clear enough and must use normative language.

Example: In case of equal Preference between two or more PEs in the ES, an
implementation MUST first prefer PEs advertising the DP bit set and then
prefer the PE with the lowest IP address.

Which IP address are we talking about exactly here ?

 

 

Section 4.3:

Typo on:

A new "Don't Preempt Me" capability is defined on a per-PE per-ES
   Basis
 
Should be : "A new "Don't Preempt Me" capability is defined on a per-PE
   basis

 

s/however this document do not enforces the/however this document does not
enforce the/
Question: Why don't you enforce consistency ? What is the side effect of not
ensuring consistency ?
 
 
"When PE3's vES2 comes back up, PE3 will start a boot-timer (if
   booting up) or hold-timer (if the port or EVC recovers).  That
   timer will allow some time for PE3 to receive the ES routes from
   PE1 and PE2. >
 
Are you changing the way the DF election works ? Usually, PE advertises its
route and then wait to receive other routes.
What happens if all PEs on the ES are failing at the same time or the ES
booting up on all the PEs at the same time ? you have no way to hear what is
the pref from the remote.
 
Shouldn't the "no preemption" thing be valuable being agnostic to DF Alg ?
 
On 6)
Consider that we had:
PE3 advertising <300,1>
PE2 advertising <200,1>
PE1 advertising <100,1>
 
PE3 fails and come back, advertising [200,0], leading to PE2 being DF.
PE2 fails, but in a similar time PE1 changes its pref to 250. This leads to
PE1 being DF while in this case PE3 should be DF because it should have
recovered its preference but it can't.
 
 
References:
I think vES should be set as normative as people really need to understand
what vES is to understand the document.
 

 

Brgds,

 

Stephane

 

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

[bess] REMINDER Re: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-datacenter-gateway-04

[Bocci, Matthew (Nokia - GB)]

WG

I have only seen one IPR responses to this WG last call and no comments. I will 
therefore extend it for another two weeks.

Regards

Matthew

From: BESS  on behalf of "Bocci, Matthew (Nokia - GB)" 

Date: Monday, 10 February 2020 at 16:17
To: "draft-ietf-bess-datacenter-gate...@ietf.org" 
, "bess@ietf.org" 
Subject: [bess] WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-datacenter-gateway-04

This email starts a two-week working group last call for 
draft-ietf-bess-datacenter-gateway-04
Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until Monday 24th February 2020.

We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
If you are listed as an Author or a Contributor of this document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently no IPR disclosed.

We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations of the modified protocol described in 
this draft.

 Thank you,

Matthew

[1] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw


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

[bess] Publication has been requested for draft-ietf-bess-evpn-bum-procedure-updates-08

[Stephane Litkowski via Datatracker]

Stephane Litkowski has requested publication of 
draft-ietf-bess-evpn-bum-procedure-updates-08 as Proposed Standard on behalf of 
the BESS working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-bum-procedure-updates/


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

[bess] Publication has been requested for draft-ietf-bess-mvpn-fast-failover-10

[Stephane Litkowski via Datatracker]

Stephane Litkowski has requested publication of 
draft-ietf-bess-mvpn-fast-failover-10 as Proposed Standard on behalf of the 
BESS working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-fast-failover/


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