Network News Transfer Protocol (NNTP) Additions to LIST Command
RFC 6048

Note: This ballot was opened for revision 05 and is now closed.

Alexey Melnikov (was Discuss, Yes) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Adrian Farrel) No Objection

Comment (2010-08-11 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
It seems to me that [RFC2980] might usefully be a normative reference 
since this document purports to update it.

(Tim Polk) No Objection

(Dan Romascanu) No Objection

(Peter Saint-Andre) No Objection

Comment (2010-08-10 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
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).

(Robert Sparks) No Objection

(Sean Turner) No Objection

Comment (2010-08-11 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
#1) Sec 2: should "optional" be "OPTIONAL"?