Last Call Review of draft-ietf-eai-rfc5721bis-

Request Review of draft-ietf-eai-rfc5721bis
Requested rev. no specific revision (document currently at 08)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2012-09-20
Requested 2012-09-06
Authors Randall Gellens, Chris Newman, Jiankang Yao, Kazunori Fujiwara
Draft last updated 2012-09-20
Completed reviews Genart Last Call review of -?? by Ben Campbell
Secdir Last Call review of -?? by Yoav Nir
Assignment Reviewer Ben Campbell 
State Completed
Review review-ietf-eai-rfc5721bis-genart-lc-campbell-2012-09-20
Review result Ready with Nits
Review completed: 2012-09-20


I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<> .

Please resolve these comments along with any other Last Call comments
you may receive.

Document:  draft-ietf-eai-rfc5721bis-07
Reviewer: Ben Campbell
Review Date: 2012-09-18
IETF LC End Date: 2012-09-20

Summary:   The draft is mostly ready for publication as a draft standard. I have a few editorial comments that should be considered prior to publication.

Major issues: None

Minor issues: 

Nits/editorial comments:

-- IDNits has some complaints; please check.

-- The abstract should mention that this obsoletes 5721

-- section 2.1, 2nd paragraph: "The character encoding format of maildrops may not be UTF-8 or ASCII."

I'm confused by this sentence, as it seems to say that the format can't be UTF-8 or ASCII, which otherwise seem to be the only ones contemplated by the draft.  Do you mean to say that it may be some format other than those?

-- same paragraph : "The UTF8 command MAY fail."

Under what circumstances? (this seems sort of tacked onto the paragraph--does it belong there?)

-- 2.1, 4th paragraph: "...need not be accurate, but it is preferable if they were."

Not preferable enough for a SHOULD? (Note that the previous sentence used SHOULD for reporting actual message size counts)

-- section 7, 3rd paragraph: "It is possible for a man-in-the-middle attacker to insert a LANG command in the command stream, thus making protocol-level diagnostic responses unintelligible to the user."

This seems a bit unnecessary to call out, given that a MiTM could just change the diagnostic responses into Klingon even in the absence of the LANG command. It's at least worth mentioning that the LANG command really doesn't make this issue worse than it already was.