[NNTP] Extension snapshots 2

[Ken Murchison]

Russ Allbery wrote:

> Ken Murchison <ken at oceana.com> writes:
> 
> 
>>http://www.oceana.com/ftp/drafts/draft-ietf-nntpext-authinfo-06pre2.txt
> 
> 
> I believe we should not allow AUTHINFO both before and after MODE READER.
> In other words, if you're going to send MODE READER, do it first before
> you do anything else.  You can either not send it at all or send it as the
> first thing you do, but you can't authenticate, use some transit commands,
> and then send MODE READER to switch over to the reader server.

So, do you want to prohibit this unilaterally, e.g.:

"Servers MUST NOT allow the use of MODE READER after successful 
authentication."


Or only prohibit it on mode-switching servers, e.g.:

"Mode-switching servers MUST NOT allow the use of MODE READER after 
successful authentication."


I'm open to different/additional text if you have any ideas.  Of course, 
all of this is moot if we decide to get rid of MODE READER.  Where do we 
stand on this?


> It's not clear to me what the utility of noting whether an extension is a
> transit, reader, or general command, given that they have their own
> capabilities.  Could someone remind me why that's needed?

It probably isn't needed, and I was about to remove it, but I noticed 
that the "standard" extensions in section 8 of base-pre5 note that they 
are all reader commands, as do the IANA registrations in Appendix C.

Can you make a formal decision on whether we want this or not, so we can 
have the base doc and extension docs do the same thing?

-- 
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