Hi, I also agree with the proposal as long as it stays as “just reserving a route type range for experimental use” (which is what Jeff and Ketan confirmed). If the proposal was to allow running experiments on existing deployments, then all the issues mentioned by various people during the meeting would apply.
Thanks! Jorge From: Nitsan Dolev <[email protected]> Date: Friday, July 24, 2026 at 12:27 AM To: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: [bess] draft-tantsura-bess-evpn-route-type-exp-use-00 CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. Jeff and Ketan, We really need draft-tantsura-bess-evpn-route-type-exp-use-00 for our newly defined EVPN Route type. Refer also to Draft-jot-bess-evpn-mcast-router-sync-00 with newly proposed EVPN MRD route, for which your proposal address a vital need. So I fully support this draft, Nitsan Disclaimer This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
