On Sep 2, 2025, at 2:10 PM, Mike Bishop via Datatracker <[email protected]> wrote: > Consider introducing the term/abbreviation NAI in Sections 1 or 2. It's > expanded in the abstract and used in the definition of EPI (Section 2) with an > appropriate reference (thank you!), but the abbreviation isn't expanded in the > main text until Section 3.
Fixed. > Section 3.2, it seems strange to scope "experimental" use to ietf.org. > Experiments happen other places, too. Perhaps instead say that experiments > should happen exclusively within an appropriate vendor space, and > "*.ietf.org.v.eap.arpa" can be used for draft version of documents in an IETF > working group? Sure. > Only need to expand EPI once -- it's not necessary to re-introduce the > abbreviation in each section. Fixed, > Section 4 seems like it would be more useful folded into the Introduction, or > perhaps as an Appendix if you feel it's too long for that. I think it's better in the introduction. I'll move it there. > In Section 5.2, I would appreciate an informative reference for "802.11u NAI > realm". I'll try to find one. > Also, is it sufficient to advertise the entire universe of possible NAI > realms when what's supported is specifically "[email protected]"? Is it > possible to make a more specific advertisement with that mechanism, and if so, > why wouldn't we recommend that? > > === NITS FOLLOW === > > 3.4: Period at end of sentence > 3.4.1: "is no ... issues" => "is no ... issue" or "are no ... issues" > 3.4.2: "actoer" => "actors"? > 5.1: ". ." => "." and don't put commas around the parentheses > 6: "number IANA" => "number of IANA" > 8: delete comma after "registry" Fixed. Alan DeKok. _______________________________________________ Emu mailing list -- [email protected] To unsubscribe send an email to [email protected]
