Jeff T. and Jeff Haas: draft-ietf-bess-ebgp-dmz – can you update the wiki with the implementation report for FRR (SONiC) and Nvidia Cumulus.
Cheers, Sue From: Jeff Tantsura <[email protected]> Sent: Friday, February 13, 2026 8:23 PM To: Jeffrey Haas <[email protected]> Cc: [email protected]; BESS <[email protected]>; idr-chairs <[email protected]> Subject: [bess] Re: draft-ietf-bess-ebgp-dmz - preparation for working group last call Hi Jeff, Thanks for your review. IPR - I’m not aware after any IPR that applies to the draft. Implementation report: I can confirm implementations in FRR (SONiC) and Nvidia Cumulus. While at MSFT i have also tested and achieved interoperability NkdkJdXPPEBannerStart Be Careful With This Message From (Jeff Tantsura <[email protected]>)<https://godaddy2.cloud-protect.net/email-details/?k=k1&payload=53616c7465645f5f385e84cac6eb90a8f579ef42c76ed530987e3d2a4834c00dcfa04a98d8d8be197eb0d6fbbd3fd0568d7d59d51b0ad8899ba6887e32eb219076425f556b89e6502e569d86b8a49b6336df6f610d6384b0b3781f1c2cd5d708e0797f007a994145ef95584fc015462aa923eaa64a25f8269f09d6bd3ad53292e9c00e17079a426aefb9f8124376e22adf0d3936f51e00f1091ffa37e6266e26d1eb966c0da1a13059fce67e99380aebe1a1f15212c3633d6e27371428cdf99fe489dcb811df481692c1c93838eacec7ce922b4ea5e79be56b7ef167a0feb852> Learn More<https://godaddy2.cloud-protect.net/email-details/?k=k1&payload=53616c7465645f5f385e84cac6eb90a8f579ef42c76ed530987e3d2a4834c00dcfa04a98d8d8be197eb0d6fbbd3fd0568d7d59d51b0ad8899ba6887e32eb219076425f556b89e6502e569d86b8a49b6336df6f610d6384b0b3781f1c2cd5d708e0797f007a994145ef95584fc015462aa923eaa64a25f8269f09d6bd3ad53292e9c00e17079a426aefb9f8124376e22adf0d3936f51e00f1091ffa37e6266e26d1eb966c0da1a13059fce67e99380aebe1a1f15212c3633d6e27371428cdf99fe489dcb811df481692c1c93838eacec7ce922b4ea5e79be56b7ef167a0feb852> Potential Impersonation The sender's identity could not be verified and someone may be impersonating the sender. Take caution when interacting with this message. NkdkJdXPPEBannerEnd Hi Jeff, Thanks for your review. IPR - I’m not aware after any IPR that applies to the draft. Implementation report: I can confirm implementations in FRR (SONiC) and Nvidia Cumulus. While at MSFT i have also tested and achieved interoperability with Arista EOS, but would let Arista co-authors to confirm. Wrt number of co-authors: All original co-authors contributed to different parts of the document, where Arie and I contributed use cases/deployment strategy at our hyperscale employers at the time and vendors details, ensuring interoperability. All of original co-authors should be there. Cheers, Jeff > On Feb 13, 2026, at 15:38, Jeffrey Haas > <[email protected]<mailto:[email protected]>> wrote: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Debgp-2Ddmz_shepherdwriteup_&d=DwIGaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=3QxUPy-fV0G16Z4tIRByiA&m=HqrltyKVFrP1Su44C4_2b-bEJ3cxjsFWMd1DC7X_3ZGCOi_2ab8K51vTItki74y4&s=SPFAE8-bh5QNIxHxI3tsTvskb8uuGvulM2iVav6nN40&e= > > In November 2025, the IDR chairs corresponded with the BESS chairs about the > disposition of the DMZ draft. As you know from the long history of this > draft, the link-bandwidth one, and the work that came to be part of RFC > 4360-bis, we've discussed leaving the DMZ draft in BESS and running > concurrent WGLC's on this draft along with RFC 4360-bis. > > As part of this concurrent WGLC, I've completed an initial shepherd report > for the DMZ draft. Please review its contents for correctness. A few items > have been identified that will be needing to be addressed prior to starting > the last call. They are: > > - Author count > 5. I've not recommended changes since I've not been a > participant in those discussions. The chairs have been urged to discuss what > to do about it. > > - Proposed status. Ketan, as part of the link-bandwidth draft AD review, > suggested that the DMZ draft should likely be informational. > > - IPR declarations were partially gathered during document adoption. While I > have not been deeply thorough in my review of the IETF mailarchive for search > terms covering this draft, my cursory review suggests we're missing IPR > declarations for some of the authors. If you're one of the authors > identified in the shepherd writeup, please either make an appropriate > declaration or perhaps provide a pointer in the archive for a prior one. > > - The authors have left a NOTE in the draft suggesting a bit of doubt about > the disposition of one of the points regarding zero link-bandwidth. > Discussion about this was part of our last minute link-bandwidth document > changes in IDR - so this isn't surprising. The authors are requested to > please address this lingering point in the draft. > > - While there are no normative procedures specified in the draft, the > procedures do raise questions about supporting implementations. I won't > speak for the chairs in terms of expectations of formal implementation > reports for their working group. If such an implementation report exists for > one of your implementations, please disclose it so it can be added to the > report. > > - The document may benefit from a routing-directorate review. I was unable to > identify a prior review for this document from the mail archives. > > In general, the document is in good shape. > > I'll be working on a similar shepherd report for RFC 4360-bis in IDR. IDR > does have a requirement for at least two implementations in order to progress > the document. Since part of the motivation for RFC 4360-bis was addressing > the transitivity considerations needed for this document, I find it highly > likely that there are implementations from authors participating in the DMZ > draft for the RFC 4360-bis work. Please contribute to IDR's implementation > report so that we can send both documents to the IESG at the same time when > they've completed their reviews. > > -- Jeff (as document shepherd) > _______________________________________________ BESS mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
