[NNTP] draft-ietf-nntpext-tls-nntp-02.txt

[Clive D.W. Feather]

>>>> (Perhaps we could add a caution to client authors in the Generic
>>>> Responses section of the base spec, warning not to DOS the server by
>>>> rapidly retrying many times after receiving a 400 response?)

Proposed change:

    If the server has to terminate the connection for some reason, it
    MUST give a 400 response code to the next command and then immediately
+   close the TCP connection.  Following a 400 response, clients SHOULD
+   NOT simply reconnect immediately and retry the same actions.  Rather,
+   a client SHOULD either use an exponentially increasing delay between
+   retries (e.g. double the waiting time after each 400 response) or
+   present any associated text to the user for them to decide whether and
+   when to retry.

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