On May 29, 2024, at 2:29 PM, Warren Kumari via Datatracker <nore...@ietf.org> wrote: > 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).
The "updates 9427" is saying that the text in TEAP in 9427 is deprecated, and 7170bis is now the authoritative document. The text in 9427 isn't wrong, but people should be pointed to 7170bis for TEAP, and not 9427. Perhaps: This document obsoletes RFC 7170 and updates RFC 9427 by moving ownership of the TEAP updates from that document to this one. :( I'll think about something more intelligent to say. _______________________________________________ Emu mailing list -- emu@ietf.org To unsubscribe send an email to emu-le...@ietf.org
