Re: [bess] John Scudder's Discuss on draft-ietf-bess-mvpn-evpn-aggregation-label-12: (with DISCUSS and COMMENT)

2023-10-03 Thread Jeffrey (Zhaohui) Zhang
Hi John, Thanks for your review and for catching those issues. I posted -13 revision that addresses them (and some comments from others). https://author-tools.ietf.org/iddiff?url1=draft-ietf-bess-mvpn-evpn-aggregation-label-12&url2=draft-ietf-bess-mvpn-evpn-aggregation-label-13&difftype=--html Pl

[bess] I-D Action: draft-ietf-bess-mvpn-evpn-aggregation-label-13.txt

2023-10-03 Thread internet-drafts
Internet-Draft draft-ietf-bess-mvpn-evpn-aggregation-label-13.txt is now available. It is a work item of the BGP Enabled ServiceS (BESS) WG of the IETF. Title: MVPN/EVPN Tunnel Aggregation with Common Labels Authors: Zhaohui Zhang Eric Rosen Wen Lin Zhen

[bess] John Scudder's Discuss on draft-ietf-bess-mvpn-evpn-aggregation-label-12: (with DISCUSS and COMMENT)

2023-10-03 Thread John Scudder via Datatracker
John Scudder has entered the following ballot position for draft-ietf-bess-mvpn-evpn-aggregation-label-12: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Pleas

Re: [bess] John Scudder's Discuss on draft-ietf-bess-mvpn-evpn-aggregation-label-12: (with DISCUSS and COMMENT)

2023-10-03 Thread John Scudder
+idr-chairs One further point — I suspect my DISCUSS would have been caught if there had been review from IDR. Searching for the draft name in the IDR mailing list archive doesn’t surface any traffic about it, so I’m guessing this didn’t occur. —John > On Oct 3, 2023, at 5:56 PM, John Scudde

[bess] John Scudder's Discuss on draft-ietf-bess-mvpn-evpn-aggregation-label-12: (with DISCUSS and COMMENT)

2023-10-03 Thread John Scudder via Datatracker
John Scudder has entered the following ballot position for draft-ietf-bess-mvpn-evpn-aggregation-label-12: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Pleas

Re: [bess] A question regarding sections 15.2 and 15.3 of draft-ietf-bess-rfc7432bis

2023-10-03 Thread Ali Sajassi (sajassi)
Hi Sasha, As always thanks for your insightful comments and questions and sorry for the delayed response. Please refer to my responses inline marked with [AS]. From: BESS on behalf of Alexander Vainshtein Date: Tuesday, September 26, 2023 at 2:56 AM To: draft-ietf-bess-rfc7432bis.auth...@ietf

[bess] Secdir telechat review of draft-ietf-bess-bgp-sdwan-usage-15

2023-10-03 Thread Stephen Farrell via Datatracker
Reviewer: Stephen Farrell Review result: Has Issues Roman has covered all the points I would have raised in his dicuss ballot already, so I'm filing this just for completeness and the authors shouldn't feel any need to respond to me. In particular though, I've no idea if it's realistic (or not) to

Re: [bess] Lars Eggert's No Objection on draft-ietf-bess-mvpn-evpn-aggregation-label-12: (with COMMENT)

2023-10-03 Thread Jeffrey (Zhaohui) Zhang
Hi Lars, Thanks for your review. I have fixed the issues below (I will submit a revision when I finish addressing some comments from others), but have two clarifications - please see zzh> below. Juniper Business Use Only -Original Message- From: Lars Eggert via Datatracker Sent: Tues

Re: [bess] [Gen-art] Genart last call review of draft-ietf-bess-bgp-sdwan-usage-14

2023-10-03 Thread Lars Eggert
Dan, thank you for your review. I have entered a Discuss ballot for this document based on my own review. Lars > On Jul 26, 2023, at 10:15, Dan Romascanu via Datatracker > wrote: > > Reviewer: Dan Romascanu > Review result: Ready with Issues > > I am the assigned Gen-ART reviewer for this d

[bess] Lars Eggert's Discuss on draft-ietf-bess-bgp-sdwan-usage-15: (with DISCUSS and COMMENT)

2023-10-03 Thread Lars Eggert via Datatracker
Lars Eggert has entered the following ballot position for draft-ietf-bess-bgp-sdwan-usage-15: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to h