Hi Sasha, Thanks for your follow up and the reporting of this errata.
This delay is on me. I saw your reported errata but did not come to process it due to other priorities. Yesterday I had a chat with BESS chairs and will soon check with BESS WG. There are two open BESS errata currently to process. G/ ________________________________ From: Alexander Vainshtein <[email protected]> Sent: Monday, July 20, 2026 6:05 PM To: '[email protected]' <[email protected]> Cc: [email protected] <[email protected]> Subject: [bess] Erratum 9000 on RFC 9135 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. Hi all, I have posted Erratum 9000 on RFC 9135<https://errata.rfc-editor.org/eid9000/> on 10-Jun-2026 (i.e., 40 days ago). The erratum has been recognized as Technical, but it seems to be stuck in Reported state. Any ideas as to what (if anything) should be done to speed up its progress to Verified? I am asking because, IMHO and FWIW it reports a real gap in RFC 9135. My 2c, Sasha 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]
