Network News Transfer Protocol (NNTP) Additions to LIST Command
draft-elie-nntp-list-additions-05

[Ballot comment]
This specification is clear, complete, and well-written. Here are a few small items to consider.

1. In Section 2.3.2, the phrase "at least all" is awkward -- I suggest changing it to "all".

2. In Section 2.4.2, the text "although these situations SHOULD NOT occur if the news server is an injecting agent that carries moderated newsgroups" is merely informative, so it would be good to change "SHOULD NOT occur" to "should not occur" or "are unexpected" or something else non-normative.

3. In Section 2.5.2, change "date of last modification date" to "date of last modification" or "last modification date".

4. In Section 7, the definition does not include a descriptive name for the extension. However, perhaps the descriptive name is "LIST"?

5. In Section 7, the "Contact for Further Information" is "Author of this document", but no contact information is provided (e.g., an email address).

IANA questions/comments:

- The IANA Considerations section is unclear about the actions
this document is asking IANA to perform. What exactly is IANA
supposed to do? There is no registry of "LIST Capabilities." Are
you just asking that we add a reference to this document for the
LIST NNTP extension?

Upon approval of this document, IANA will make the following changes in
the "Network News Transfer Protocol (NNTP) Parameters" registry at
http://www.iana.org/assignments/nntp-parameters/nntp-parameters.xhtml
sub-registry "NNTP capability labels"

OLD:

Label Meaning Reference
---- ------- ---------
LIST LIST command variants [RFC3977]

NEW:

Label Meaning Reference
---- ------- ---------
LIST LIST command variants [RFC3977][RFC-elie-nntp-list-additions-03]


We understand the above to be the only IANA Action for this document.