[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LANGUAGE/COMPARATOR review




Ken Murchison writes:
Mostly nits, but a couple of corrections.

- Conventions and Normative reference [2]: The reference to RFC 2234 should be updated to RFC 4234.

- Section 3 and Informative reference [16]: The reference to the "ANNOTATEMORE extension" should be updated to "METADATA extension".

I did those on Tuesday. Didn't quite finish the overhaul yet (catching up is hard work...)

- Section 3.4, first paragraph. I don't really like the MUST and MUST NOT combination in the two sentences. Could they be merged into one positive sentence something like the following?

    If the server supports the IMAP4 NAMESPACE command [4], and
    it is in the authenticated state, the server MUST return an
    untagged NAMESPACE response when a language is negotiated.

Good suggestion. Will do.

- Section 4, first paragraph, second sentence: This should be changed to "The SORT and THREAD extensions [15] to IMAP allow ..."

- Section 4, third paragraph: Since both of the currently defined THREADing algorithms sort by subject, both instances of "SEARCH and SORT" should be changed to either "SEARCH, SORT, and THREAD" or "SEARCH and SORT/THREAD".

- Section 4, fourth paragraph AND Section 4.1, third paragraph: The THREAD=REFERENCES algorithm also sorts by subject, so this needs to be accounted for in the text. It doesn't matter to me whether both THREADing algorithms are listed, or if the text just mentions THREAD in general.

Will do all of this.

- Section 5.1, second paragraph, second sentence: "... the current latest ACL drafts." seems redundant. I think one of either "current" or "latest" would suffice.

Another Tuesday change was to replace it with a reference to the published RFC.

Arnt