Re: [bess] WG adoption for draft-skr-bess-evpn-redundant-mcast-source => need review from WG

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

Support.

G/

From: BESS  On Behalf Of slitkows.i...@gmail.com
Sent: Tuesday, January 5, 2021 15:18
To: bess@ietf.org; draft-skr-bess-evpn-redundant-mcast-sou...@ietf.org
Subject: Re: [bess] WG adoption for draft-skr-bess-evpn-redundant-mcast-source 
=> need review from WG

Hi,

We haven’t received a lot of feedback during the poll.
The draft can’t be adopted now.

We would like to encourage the WG to review the draft and extend the poll close 
date to 1/18. If we haven’t received more feedback, the document will not be 
adopted (but could still be adopted later as we haven’t received objections).

Brgds,

Stephane

From: Mankamana Mishra (mankamis) 
mailto:manka...@cisco.com>>
Sent: mardi 15 décembre 2020 16:19
To: slitkows.i...@gmail.com; 
bess@ietf.org; 
draft-skr-bess-evpn-redundant-mcast-sou...@ietf.org
Subject: Re: [bess] WG adoption for draft-skr-bess-evpn-redundant-mcast-source

Support the adoption.

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
"slitkows.i...@gmail.com" 
mailto:slitkows.i...@gmail.com>>
Date: Tuesday, December 1, 2020 at 1:32 AM
To: "bess@ietf.org" 
mailto:bess@ietf.org>>, 
"draft-skr-bess-evpn-redundant-mcast-sou...@ietf.org"
 
mailto:draft-skr-bess-evpn-redundant-mcast-sou...@ietf.org>>
Subject: [bess] WG adoption for draft-skr-bess-evpn-redundant-mcast-source

Hello,

This email begins a two-weeks WG adoption poll for 
draft-skr-bess-evpn-redundant-mcast-source
 [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 will not  progress 
without answers from all of 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 15th December 2020.

Regards,
Matthew and Stephane

[1]  
https://datatracker.ietf.org/doc/draft-skr-bess-evpn-redundant-mcast-source/




___
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] WG adoption poll and IPR poll for draft-snr-bess-evpn-loop-protect

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

Yes, Support adoption.

G/

From: BESS  On Behalf Of Stephane Litkowski
Sent: Thursday, September 19, 2019 16:06
To: stephane.litkow...@orange.com
Cc: draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org; 
bess@ietf.org
Subject: Re: [bess] WG adoption poll and IPR poll for 
draft-snr-bess-evpn-loop-protect

Hi,

The poll has ended.
I haven't seen a lot of support from the various vendor while Jorge has 
mentioned that there are multiple implementations. Before closing definitely 
this poll, I would like to let the opportunity to other vendors to raise their 
voice and support the draft especially if they have implementations.
I will let an additional week.

Stephane


On Mon, Sep 2, 2019 at 4:29 PM 
mailto:stephane.litkow...@orange.com>> wrote:
Hi,

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-evpn-loop-protect-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 16th September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/




[Orange logo]

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 

  NEW !
mobile: +33 6 71 63 27 50 

  NEW !
stephane.litkow...@orange.com


_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

Re: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07

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

Support to adopt.
I think this work is useful for the WG and the industry to progress.

Brgds,
G/

From: BESS  On Behalf Of Stephane Litkowski
Sent: Monday, August 19, 2019 21:32
To: bess@ietf.org
Subject: [bess] WG adoption call and IPR poll for 
draft-rabadan-bess-vendor-evpn-route-07

Hi,

This email begins a two-weeks WG adoption poll for 
draft-rabadan-bess-vendor-evpn-route-07 [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 2nd September 2019.

Regards,
Stephane and Matthew

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

Re: [bess] Second WG Last Call on draft-ietf-bess-evpn-proxy-arp-nd-06

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

Support publication,

I read the original drafts and this version -06 and was involved with problem 
scenarios described in the draft.

This work provides an answer to a real scalability problem experienced by IXPs, 
DCs
and other operators, and resolves that problem to have scalable distributed
proxy-arp/nd solution. This is important work.
G/

From: BESS  On Behalf Of Bocci, Matthew (Nokia - GB)
Sent: Friday, June 7, 2019 11:07
To: bess@ietf.org
Cc: bess-cha...@ietf.org; draft-ietf-bess-evpn-proxy-arp...@ietf.org
Subject: [bess] Second WG Last Call on draft-ietf-bess-evpn-proxy-arp-nd-06

WG

We ran a working group last call on this draft in August 2018. Although we had 
an Ops Area review, we did not get a lot of responses from participants who 
were not already authors of the draft. We are therefore running another working 
group last call on draft-ietf-bess-evpn-proxy-arp-nd-06.

Please indicate to the list if you have read the draft and support its 
publication as an RFC. Please also indicate to the list if you have read the 
draft and do not support its publication.

Please also send any other last call comments to the BESS list.

This last call ends on Friday 21st June 2019.

Regards

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

Re: [bess] WG Last Call and IPR Poll for draft-ietf-bess-evpn-vpls-seamless-integ-01.txt

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

Support

G/

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - 
GB)
Sent: Wednesday, March 28, 2018 14:50
To: draft-ietf-bess-evpn-vpls-seamless-in...@ietf.org; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: [bess] WG Last Call and IPR Poll for 
draft-ietf-bess-evpn-vpls-seamless-integ-01.txt

This email begins a two-week working group last call for 
draft-ietf-bess-evpn-vpls-seamless-integ-01.txt

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 is one IPR declaration 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.

We are also polling for any existing implementations.

The working group last call closes on Wednesday 11th April.

Regards,

Matthew and Stéphane
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

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

Yes, support. This is meaningful work.

G/

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Monday, March 26, 2018 16:21
To: bess@ietf.org
Subject: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework


Hello working group,



This email starts a two-week Working Group Last Call on 
draft-ietf-bess-evpn-df-election-framework-00 [1]



This poll runs until *the 9th of April*.



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

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



Currently no IPR has been disclosed against this Document.



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



We are also polling for any existing implementation.



Thank you



Matthew, Stéphane

bess chairs



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



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

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

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

I support progress and publish as RFC.

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

G/

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Monday, January 29, 2018 09:27
To: bess@ietf.org; draft-ietf-bess-evpn-ac-df.auth...@ietf.org
Subject: [bess] WG Last Call (including implem status) for 
draft-ietf-bess-evpn-ac-df


Hello Working Group,



This email starts a Working Group Last Call on

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

ready for a final working group review.



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

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

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

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

RFC.



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

applies to draft-ietf-bess-evpn-ac-df, to ensure that IPR has

been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879,

3669 and 5378 for more details).



If you are listed as a document Author or Contributor of the draft

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

of any relevant IPR.



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

or its earlier versions.



We are **also polling for knowledge of implementations** of part or all

of what this document specifies. This information is expected as per [2].

Please inform the mailing list, or the chairs, or only one of the chairs.



Thank you,

Stephane & Martin



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

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






_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

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

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

Yep, support

G/

-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
Sent: Thursday, January 11, 2018 11:12
To: bess@ietf.org
Cc: draft-lin-bess-evpn-irb-mc...@ietf.org
Subject: [bess] Call for adoption: draft-lin-bess-evpn-irb-mcast

Hello working group,

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

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

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

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

Currently no IPR has been disclosed against this Document.

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

Thank you

Martin & Stéphane
bess chairs

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

___
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] DC ROUTING BOF at IETF100 - call for meeting topics

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

Hi All,

Apologies for the cross posting.

Data Center Routing 
(DCROUTING) will be having a 
non-working-group-forming BOF during IETF100. Over the last year, there have 
been discussions in a number of routing area working groups about proposals 
aimed at routing within a data center. Because of their topologies (traditional 
and emerging), traffic patterns, need for fast restoration, and need for low 
human intervention, among other things, data centers are driving a set of 
routing solutions specific to them. The intent of this BOF is to discuss the 
special circumstances that surround routing in the data center and potential 
new solutions. The objective is not to select a single solution, but to 
determine whether there is interest and energy in the community to work on any 
of the proposals.

If you have a draft and would like to see it discussed during the BOF meeting, 
then please send the note to the BOF co-chairs and copy the 
dcrout...@ietf.org email address.

A rough agenda overview leads to following preliminary agenda intent:


  *   Agenda bash, scribe, minute taker
  *   DC Problem Statement Intro’s (DC testimonial summaries)
  *   Solution Space Proposals
  *   Summary

To contribute and join the BOF email list:

List address: ​dcrout...@ietf.org
Mailing List: 
​https://www.ietf.org/mailman/listinfo/dcrouting
Archive: 
​https://mailarchive.ietf.org/arch/search/?email_list=dcrouting
To subscribe: 
​https://www.ietf.org/mailman/listinfo/dcrouting

Kind Regards,

Victor & Gunter
co-chairs DC Routing BOF

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