[bess] Re: Rtgdir early review of draft-ietf-bess-evpn-geneve-07

Jonathan Thanks for your review. Authors: I intend to WG LC the draft soon, but please can you address the comments below before I start the WG LC. Regards Matthew From: Jonathan Hardwick via Datatracker Date: Wednesday, 5 June 2024 at 14:02 To: rtg-...@ietf.org Cc: bess@ietf.org ,

Re: [bess] Considering EVPN BFD as a candidate for the WG LC

We’ve added this to the queue on the BESS WG WiKi (BESS WG - BGP Enabled ServiceS | IETF Community Wiki). Authors, please can you also address Sasha’s comments/questions sent to the BESS list on 31st March. Matthew From: Jeff Tantsura Date: Friday, 22 March

[bess] Mail regarding draft-ietf-bess-evpn-geneve

Authors and BESS WG, draft-ietf-bess-evpn-geneve-06 is currently languishing due to a lack of implementation. However, it would be good to get this done as there is no current agreed specification for a control plane to

Re: [bess] Request for an expedited WG last call for draft-ietf-bess-bgp-srv6-args

possible so that new implementors become aware of the changes compared to RFC9252. Thanks, Jorge From: Matthew Bocci (Nokia) mailto:matthew.bo...@nokia.com>> Date: Tuesday, August 1, 2023 at 10:25 AM To: Ketan Talaulikar mailto:ketant.i...@gmail.com>>, bess-cha...@ietf.org<mailto:b

[bess] REMINDER: Slides for IETF 119 session

Presenters, Please send you slides to the chairs (bess-cha...@ietf.org) or upload them directly to the meeting materials as soon as possible, or by 6pm Australian EST on Wednesday 20th at the latest. Thanks Matthew ___

Re: [bess] Mail regarding draft-ietf-bess-rfc7432bis

Hi Authors Resending this and including the WG. I believe this is a similar question to the one posted by Menachem on RFC8214. Thanks in advance Matthew From: Matthew Bocci (Nokia) Date: Monday, 15 January 2024 at 12:40 To: draft-ietf-bess-rfc7432...@ietf.org Cc: bess-cha...@ietf.org

Re: [bess] WG Last Call for draft-ietf-bess-bgp-sdwan-usage-17

This poll is now closed. Thanks to those to reviewed the draft and provided comments. I will update the shepherd’s write-up and progress the draft to the next stage. Regards Matthew From: Matthew Bocci (Nokia) Date: Thursday, 16 November 2023 at 11:49 To: bess@ietf.org Subject: WG Last

Re: [bess] Rtgdir early review of draft-ietf-bess-evpn-fast-df-recovery-07

WG I haven’t seen any concerns regarding this draft being marked as updating RFC 8584. I will therefore proceed with the document shepherd’s write up and publication request process. Regards Matthew From: Matthew Bocci (Nokia) Date: Friday, 13 October 2023 at 17:49 To: Luc Andre Burdet

[bess] WG Last Call for draft-ietf-bess-bgp-sdwan-usage-17

This email begins a second working group last call for draft-ietf-bess-bgp-sdwan-usage-17 - BGP Usage for SD-WAN Overlay Networks A little bit of history: A previous version was adopted, completed WG last call, and publication

[bess] FW: NomCom 2023 Needs Your Feedback

A reminder to please provide feedback to NomCom. Details below. Regards Matthew From: IETF-Announce on behalf of NomCom Chair 2023 Date: Monday, 6 November 2023 at 07:28 To: IETF Announcement List Subject: NomCom 2023 Needs Your Feedback Hi, The NomCom met yesterday decided to keep

Re: [bess] WG adoption request: BGP MPLS Namespaces

Hi Kaliraj I have added the draft to the WG adoption poll queue on the Wiki. Matthew From: Kaliraj Vairavakkalai Date: Tuesday, 24 October 2023 at 03:37 To: bess-cha...@ietf.org , bess@ietf.org Cc: draft-kaliraj-bess-bgp-sig-private-mpls-lab...@ietf.org Subject: WG adoption request: BGP

Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

Hi Ketan Thanks. That works. Matthew From: Ketan Talaulikar Date: Monday, 23 October 2023 at 12:07 To: Matthew Bocci (Nokia) Cc: bess@ietf.org , draft-trr-bess-bgp-srv6-a...@ietf.org Subject: Re: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 CAUTION: This is an external

Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

WG, There is consensus to adopt this draft as a BESS WG document. Authors: please respond to the one comment form Bruno and upload a new version of the draft as draft-ietf-bess-bgp-srv6-args-00. Thanks Matthew From: Matthew Bocci (Nokia) Date: Thursday, 28 September 2023 at 15:49 To: bess

Re: [bess] Rtgdir early review of draft-ietf-bess-evpn-fast-df-recovery-07

Authors, Working Group, I would like to gauge the consensus of the group on the question below about the draft updating 8584. The meaning of “updates” is perhaps a little ambiguous, and the interpretation I had used when suggesting that we should mark the draft as updating 8584 was that it

Re: [bess] WG Adoption Poll for draft-ietf-bess-bgp-sdwan-uasge-16

of draft-ietf-idr-sdwan-edge-discovery, and changing another informative reference to MEF3.0 to IEEE802.3. I did not see any other comments that required changes, so I believe there is consensus to adopt the draft. Matthew From: Matthew Bocci (Nokia) Date: Thursday, 5 October 2023 at 11:45

[bess] WG Adoption Poll for draft-ietf-bess-bgp-sdwan-uasge-16

WG This email starts a one-week WG adoption poll for draft-ietf-bess-bgp-sdwan-uasge-16 [1] A little bit of history: A previous version was adopted, completed WG last call, and publication requested as an Informational RFC. v15 of this draft was reviewed by the IESG and found to have a

[bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

This email begins a two-week WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 [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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

WG, Authors There is consensus to merge the individual drafts into the working group draft. Given that the working group draft will be expanded in scope, I think it makes sense to update the name of the draft as proposed by Gyan, as follows: draft-ietf-bess-ipv6-only-pe-design-04 ->

Re: [bess] 2nd WG last call for draft-ietf-bess-evpn-virtual-eth-segment-12

: Ali Sajassi (sajassi) Date: Saturday, 5 August 2023 at 23:55 To: Matthew Bocci (Nokia) , bess@ietf.org Cc: bess-cha...@ietf.org , John Scudder Subject: Re: 2nd WG last call for draft-ietf-bess-evpn-virtual-eth-segment-12 CAUTION: This is an external email. Please be very careful when clicking

[bess] 2nd WG last call for draft-ietf-bess-evpn-virtual-eth-segment-12

This email begins a two-week working group last call on draft-ietf-bess-evpn-virtual-eth-segment-12 (draft-ietf-bess-evpn-virtual-eth-segment-12 - EVPN Virtual Ethernet Segment) Please review the draft and post any

Re: [bess] Request for an expedited WG adoption call for draft-trr-bess-bgp-srv6-args

Hi Ketan If we can do a quick implementation poll for the changes proposed in the draft, that would help. Thanks Matthew From: Ketan Talaulikar Date: Thursday, 27 July 2023 at 15:02 To: bess-cha...@ietf.org Cc: draft-trr-bess-bgp-srv6-a...@ietf.org , BESS Subject: Request for an expedited

[bess] IMPORTANT: Missing slides from BESS session tomorrow

I am missing a number of slide sets from the BESS session on Thursday morning. Please make sure that I have these before 6pm Pacific time today (26th July), otherwise I may remove you from the agenda. Thanks Matthew ___ BESS mailing list

Re: [bess] Rtgdir early review of draft-ietf-bess-evpn-fast-df-recovery-07

Adrian Thanks for the RTGDir review. Authors: Please can you look at the review and address Adrian’s comments. Regards Matthew From: Adrian Farrel via Datatracker Date: Saturday, 27 May 2023 at 20:42 To: rtg-...@ietf.org Cc: bess@ietf.org ,

Re: [bess] Document shepherd's review of draft-ietf-bess-bgp-sdwan-usage-07

and Route 12.1.1.x/24 can only be..” Can you fix these example addresses and try to clear this error, please, as it will come back later? Regards Matthew From: Linda Dunbar Date: Tuesday, 27 June 2023 at 23:59 To: Matthew Bocci (Nokia) , bess@ietf.org , draft-ietf-bess-bgp-sdwan-us

Re: [bess] Document shepherd's review of draft-ietf-bess-bgp-sdwan-usage-07

reason why there should be more. One way to resolve this is to list the editors as authors and move others to a ‘contributors’ section. Please can you resolve this. Thanks Matthew From: BESS on behalf of Matthew Bocci (Nokia) Date: Monday, 26 June 2023 at 11:14 To: Linda Dunbar , bess

Re: [bess] Document shepherd's review of draft-ietf-bess-bgp-sdwan-usage-07

ch 2023 at 08:07 To: Matthew Bocci (Nokia) , bess@ietf.org , draft-ietf-bess-bgp-sdwan-us...@ietf.org Subject: RE: Document shepherd's review of draft-ietf-bess-bgp-sdwan-usage-07 CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See h

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

) , Matthew Bocci (Nokia) , bess-cha...@ietf.org Cc: bess@ietf.org , draft-sajassi-bess-secure-e...@ietf.org Subject: Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06 CAUTION: This is an external email. Please be very careful when clicking links or opening attachments

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

. Regards Matthew From: Matthew Bocci (Nokia) Date: Thursday, 25 May 2023 at 11:35 To: bess@ietf.org Cc: draft-sajassi-bess-secure-e...@ietf.org , bess-cha...@ietf.org Subject: WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06 Hello, This email begins a two-week WG adoption poll

[bess] Request for IDR WG review of draft-ietf-bess-ebgp-dmz-02

Hi IDR WG The BESS chairs would like to request review of draft-ietf-bess-ebgp-dmz-02 (draft-ietf-bess-ebgp-dmz-02 - Cumulative DMZ Link Bandwidth and load-balancing), for which we are considering starting a working group last call.

[bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

Hello, This email begins a two-week WG adoption poll for draft-sajassi-bess-secure-evpn-06 [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

Re: [bess] Document shepherd's review of draft-ietf-bess-bgp-sdwan-usage-07

Thanks Linda This looks fine to me. Regards Matthew From: Linda Dunbar Date: Tuesday, 21 March 2023 at 22:40 To: Matthew Bocci (Nokia) , bess@ietf.org , draft-ietf-bess-bgp-sdwan-us...@ietf.org Subject: RE: Document shepherd's review of draft-ietf-bess-bgp-sdwan-usage-07 CAUTION

[bess] Document shepherd's review of draft-ietf-bess-bgp-sdwan-usage-07

Authors, As is customary, please find attached my documents shepherd’s review of draft-ietf-bess-bgp-sdwan-usage-07. There are a fair number of mostly editorial comments scattered throughout the draft, prefixed by ‘MB>’. Please treat these as you would any other WG last call comments. Best

Re: [bess] Implementaion status and request for early allocation of code points for draft-ietf-bess-evpn-geneve

is to allocate from the Standards Action range, but please can you confirm? Thanks Matthew From: Matthew Bocci (Nokia) Date: Wednesday, 30 November 2022 at 10:06 To: bess@ietf.org Cc: bess-cha...@ietf.org Subject: Implementaion status and request for early allocation of code points for draft-ietf

[bess] Implementaion status and request for early allocation of code points for draft-ietf-bess-evpn-geneve

WG, There was recently consensus to request publication of this draft. The BESS Working Group has a policy that at least one implementation must exist before progressing a standards track draft. We therefore must hold this draft for the time being awaiting any implementations. Please notify

[bess] Document shepherd review of draft-ietf-bess-pbb-evpn-isid-cmacflush-05

Authors As is customary, I have reviewed this draft. It is clear and readable. I have a few minor comments which I would appreciate if you can address before we move this forward: * It would be helpful in the introduction section if you could expand all acronyms on first use. These are

Re: [bess] WGLC, IPR and Implementation Poll for draft-ietf-bess-evpn-fast-df-recovery-03

Authors and WG A further question about this document. Do you consider that it updates the procedures in RFC8584? The abstract says the following: “This document improves these procedures by providing a fast Designated Forwarder (DF) election upon recovery of the failed link or node