Subject: [bess] Re: Working Group Last Call on draft-ietf-bess-ebgp-dmz (ending 16 March, 2026)
From: "Mankamana Mishra (mankamis)" <[email-masked]>
To: Jeffrey Haas <[email-masked]>, BESS <[email-masked]>
Cc: "[email-masked]" <[email-masked]>, idr-chairs <[email-masked]>
Date: Wed, 4 Mar 2026 14:41:55 +0000
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>

As WG member support moving forward with publication of this document.

Mankamana

From: Jeffrey Haas <[email-masked]>
Date: Tuesday, March 3, 2026 at 9:07 AM
To: BESS <[email-masked]>
Cc: [email-masked] <[email-masked]>, idr-chairs <[email-masked]>
Subject: [bess] Working Group Last Call on draft-ietf-bess-ebgp-dmz (ending 16 March, 2026)

https://datatracker.ietf.org/doc/draft-ietf-bess-ebgp-dmz/

As the shepherd for the DMZ draft, this starts a working group last call for draft-ietf-bess-ebgp-dmz..  This last call ends on 16 March.

Please indicate to the mailing list whether you think this document is ready to advance to publication or not.

The shepherd writeup for this document is located here:
https://datatracker.ietf.org/doc/draft-ietf-bess-ebgp-dmz/shepherdwriteup/

Note that we are still waiting for an IPR attestation from Arie Vayner.  Other working group members that are aware of undisclosed IPR are requested to attest to it as part of IETF BCP 78/79.

As per BESS practices, this last call is also polling for the existence of implementations of this draft.  See this prior note on the practice:
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw/

Please also note that there is a related last call happening in IDR relating to RFC 4360-bis.  As BESS WG members are aware, the DMZ work was motivated to address the transitivity aspects of the BGP link-bandwidth extended community as part of the DMZ aggregation procedures.  The link bandwidth draft has completed IDR last call and has been sent to the IESG for publication.  The related work to address originating non-transitive BGP extended communities was moved into the RFC 4360-bis work.

Thus, if you believe DMZ should progress, please respond to the IDR last call on 4360-bis to help both works advance together.

https://mailarchive.ietf.org/arch/msg/idr/fftaCU5jpiYynWFfgex0dkjXB4E/

-- Jeff