ietf-nntp NNTP AUTH draft update

[Howard Swinehart]

> I'd like to get constructive comments on this issue -- I'm
> relatively agnostic about the solution.  It's easy to say a draft is
> wrong, but that's worthless.  If you want to comment, please say how
> to fix the draft.
>
> I can't say I'm particularly fond of "LIST EXTENSIONS" having
> side-effects from a protocol design standpoint.  But backwards
> compatibility regularly compromises good design.

How about allowing the client to send it's own list of extensions
after it receives the server's extensions?  The server then uses this
information to decide which response codes to send.  If the client
sends no extensions list, send it the old responses.