[NNTP] Re: MODE READER

[Clive D.W. Feather]

I wrote:

> (2) Reader-only. MODE READER is a no-op. The client can *not* use any
> transit command (it gets 502), but can use all other commands at any time.
> 
> (3) Transit-only. MODE READER is a no-op. The client can *not* use any
> reader command (it gets 502), but can use all other commands at any time.

These two should be 503 ("not supported") rather than 502 ("wrong
authority").

> (4) Switching. Initially reader commands cannot be used; they get a 401
> response. Once MODE READER has been issued, transit commands cannot be
> used; they get a 502 response.

This one *is* 502, since reconnecting makes transit commands available.

> LIST EXTENSIONS can indicate which of the four cases
> applies (I would make (1) the default, with the others being READER_ONLY,
> TRANSIT_ONLY, and MODE_READER).

Ken writes:
> The only case which isn't addressed is a reader-only server, which
> really only effects IHAVE and I think returning a 503 solves this.

Actually, I agree with Mark here. If we're going to have core capabilities
described in LIST EXTENSIONS, let's not leave *anything* as "suck it and
see".

-- 
Clive D.W. Feather  | Work:  <clive at demon.net>   | Tel:    +44 20 8495 6138
Internet Expert     | Home:  <clive at davros.org>  | Fax:    +44 870 051 9937
Demon Internet      | WWW: http://www.davros.org | Mobile: +44 7973 377646
Thus plc            |                            |