[ietf-nntp] MODE READER and formal specification of extensions
Ken Murchison
ken at oceana.com
Thu Nov 4 13:04:14 PST 2004
The recent MODE READER discussion has brought some language to light in
the base spec and the existing extension specs.
All of the formal specifications of extensions, whether in the base doc
or elsewhere, are required to state "whether the extension can be used
before or after the MODE READER command". Given the fact that MODE
READER may or may not be required by a server (based on implementation),
the language currently being used can be confusing and/or ambiguous.
For example, in nntp-24 it states "The LISTGROUP command can only be
used after MODE READER command". This seems to *require* the client to
issue MODE READER, even if not required by the server, before it can use
LISTGROUP. I don't *think* this is the intent of the statement - I
think we're just trying to tag it as a "reader" command. Perhaps the
statement should say something along the lines of:
"On servers that require the use of the MODE READER command, the
LISTGROUP command can only be used after the MODE READER command."
Whatever language we come up with would also apply to OVER and HDR.
The STARTTLS and AUTHINFO drafts have a slightly different problem with
the MODE READER which I also need to fix.
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
More information about the ietf-nntp
mailing list