ietf-nntp Response codes - debugging, authentication & unknown

[Clive D.W. Feather]

Lee Kindness said:
>> This forbids a client from saying "This server is broken, I'm
>> quitting.".
> 
> In which case it's more likely that the client is broken. This
> requirement allows the NNTP spec to grow in the future - a new
> response code could be added to an existing command without breaking
> deployed clients.

No. We are listing the responses that a server should give, and saying that
servers must not give any other responses unless the appropriate extension
is invoked. So we do *not* want to encourage servers to add random new
responses.

>> It also forbids it from saying "Oh, I know what a 407 response is: in this
>> context it's really a success".
> In which case the 407 respose would be documented somewhere, and
> explicitly checked for... Yes?

Sort of. But it's not in our document, so it's undocumented in the context
of the wording.

-- 
Clive D.W. Feather  | Work:  <clive at demon.net>   | Tel:  +44 20 8371 1138
Internet Expert     | Home:  <clive at davros.org>  | Fax:  +44 20 8371 1037
Demon Internet      | WWW: http://www.davros.org | DFax: +44 20 8371 4037
Thus plc            |                            | Mobile: +44 7973 377646