[NNTP] draft-ietf-nntpext-base-25 comments
dmagda+nntpext at ee.ryerson.ca
Mon Mar 14 13:09:13 PST 2005
I haven't really been following the process too closely, so if any of
my suggestions / comments are old-hat please say so. Also, I'm not
subscribed so a CC would be appreciated.
A "keyword" MUST consist only of US-ASCII letters, digits, and the
characters dot (".") and dash ("-"), and must begin with a letter.
Should this be:
... and MUST begin with a letter.
3.1 Commands and Responses
NNTP operates over any reliable data stream 8-bit-wide
channel. Initially, the server host starts the NNTP service by
listening on a TCP port. When a client host wishes to make use
of the service, it MUST establish a TCP connection with the
server host by connecting to that host on the same port on which
the server is listening.
The first sentence says "any ... channel", but then there's a MUST
for using TCP. A bit contradictory? This would explicitly disallowd
using Unix sockets or pipes for connections.
NEWGROUPS date time [GMT]
The token "GMT" specifies that the date and time are given in
Coordinated Universal Time [TF.686-1]; if it is omitted then the
date and time are specified in the server's local timezone
Just curious: if you mean UTC, why not have "UTC". I know it's
probably for backwards compatibility, but perhaps a SHOULD for "UTC"
and MAY accept "GMT"?
David Magda <dmagda at ee.ryerson.ca>, http://www.magda.ca/
Because the innovator has for enemies all those who have done well under
the old conditions, and lukewarm defenders in those who may do well
under the new. -- Niccolo Machiavelli, _The Prince_, Chapter VI
More information about the ietf-nntp