Hello,
On 1/17/20 15:49, bortzme...@nic.fr wrote:
> On Fri, Jan 17, 2020 at 02:43:02PM +0000,
> Hollenbeck, Scott <shollenb...@verisign.com> wrote
> a message of 21 lines which said:
>
>> Perhaps 2002 ("Command use error")?
>
> May be but the text in RFC 5730 limits it to "the command cannot
> be executed due to a sequencing or context error".
Admittedly, looking at this, our 2502 doesn't seem to be overly suitable
either:
2502 "Session limit exceeded; server closing connection"
This response code MUST be returned when a server receives
a <login> command and the command cannot be completed
because the client has exceeded a system-defined limit on
the number of sessions that the client can establish. It
might be possible to establish a session by ending
existing unused sessions and closing inactive connections.
(as this clearly refers to the number of open registry connections only).
I guess we interpreted "Session limit exceeded" in a liberal fashion, in
the sense that exceeding a rate limit means exceeding a limit *of* this
session, not the limit to the number of sessions.
Anyway, as the goal is to stop the client from further hitting the
server, closing the session (as opposed to let subsequent commands fail,
allowing the load on the server to continue) is IMHO a good way to react,
and in that case this seems to be the most suitable response code.
Best regards,
Thomas
--
TANGO REGISTRY SERVICES®
Knipp Medien und Kommunikation GmbH Thomas Corte
Technologiepark Phone: +49 231 9703-222
Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200
D-44227 Dortmund E-Mail: thomas.co...@knipp.de
Germany
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
