Warren Kumari has entered the following ballot position for draft-ietf-emu-rfc7170bis-17: No Objection
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 https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-emu-rfc7170bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for writing this document; it is useful and important. Also, thank you to Bo Wu for the Ops-Dir review (https://datatracker.ietf.org/doc/review-ietf-emu-rfc7170bis-15-opsdir-lc-wu-2024-03-11/) and Ralf Weber for the (multiple) DNSIR reviews (https://datatracker.ietf.org/doc/review-ietf-emu-rfc7170bis-16-dnsdir-telechat-weber-2024-04-29/), and to the author for addressing these. My primary remaining comment is that Abstract for the document briefly should say *how* it updates RFC9427 - that way when someone reads RFC9427 they need only check this new document's Abstract to know if they need to read the whole document. I don't have great text to suggest, but perhaps something like: "This document obsoletes RFC 7170 and updates RFC 9427 by prohibiting resumption for the inner EAP methods" (*clearly* I'm not a TEAP/EAP/TLS person and so this will likely need to be edited). _______________________________________________ Emu mailing list -- emu@ietf.org To unsubscribe send an email to emu-le...@ietf.org
