Re: [regext] EPP and rate-limiting

On 17 Jan 2020, at 7:21, Patrick Mevzek wrote: > If you look at what happens in the wild, you can come to the conclusion that > there is probably no proper way to handle it in EPP... as many registries > with this need do things in very different ways: Hi *, I agree with Patrick here, there ar

Re: [regext] EPP and rate-limiting

On Fri, Jan 17, 2020, at 09:30, Stephane Bortzmeyer wrote: > Sometimes, some clients are too talkative and, for instance, try > too often to grab a domain. I'm not sure of the best error > code to return when such behaviour is detected. HTTP has 429 "Too Many > Requests" (RFC 6585) but I don't

Re: [regext] EPP and rate-limiting

+1, there is no exact match, but 2502 is the closest match that also indicates that the connection will be closed. -- JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com On 1/17/20, 10:04 AM,

Re: [regext] EPP and rate-limiting

Hello, On 1/17/20 15:49, bortzme...@nic.fr wrote: > On Fri, Jan 17, 2020 at 02:43:02PM +, > Hollenbeck, Scott 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 se

[regext] The REGEXT WG has placed draft-gould-regext-secure-authinfo-transfer in state "Candidate for WG Adoption"

The REGEXT WG has placed draft-gould-regext-secure-authinfo-transfer in state Candidate for WG Adoption (entered by James Galvin) The document is available at https://datatracker.ietf.org/doc/draft-gould-regext-secure-authinfo-transfer/ ___ regext mai

Re: [regext] EPP and rate-limiting

On Fri, Jan 17, 2020 at 02:43:02PM +, Hollenbeck, Scott 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". __

[regext] Milestones changed for regext WG

Changed milestone "Submit for publication "Domain Name Registration Data (DNRD) Objects Mapping"", resolved as "Done". URL: https://datatracker.ietf.org/wg/regext/about/ ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regex

Re: [regext] 2nd WG LAST CALL: draft-ietf-regext-dnrd-objects-mapping-01

This WGLC was scheduled to close on 8 November 2019. There has been some discussion of a few issues on the mailing list but all have been resolved and a new version has been published addressing all concerns and maintaining backwards compatibility. The original WGLC had 10 indications of supp

Re: [regext] EPP and rate-limiting

> -Original Message- > From: regext On Behalf Of Stephane > Bortzmeyer > Sent: Friday, January 17, 2020 9:30 AM > To: regext@ietf.org > Subject: [EXTERNAL] [regext] EPP and rate-limiting > > Sometimes, some clients are too talkative and, for instance, try too > often to grab a domain. I'

[regext] Milestones changed for regext WG

Changed milestone "Submit for publication "Registry Data Escrow Specification"", resolved as "Done". URL: https://datatracker.ietf.org/wg/regext/about/ ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext

[regext] Publication has been requested for draft-ietf-regext-dnrd-objects-mapping-05

James Galvin has requested publication of draft-ietf-regext-dnrd-objects-mapping-05 as Proposed Standard on behalf of the REGEXT working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-regext-dnrd-objects-mapping/ ___

[regext] Publication has been requested for draft-ietf-regext-data-escrow-04

James Galvin has requested publication of draft-ietf-regext-data-escrow-04 as Proposed Standard on behalf of the REGEXT working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-regext-data-escrow/ ___ regext mai

Re: [regext] EPP and rate-limiting

Hello Stephane, On 1/17/20 15:30, Stephane Bortzmeyer wrote: > Sometimes, some clients are too talkative and, for instance, try > too often to grab a domain. I'm not sure of the best error > code to return when such behaviour is detected. HTTP has 429 "Too Many > Requests" (RFC 6585) but I don't

Re: [regext] WG LAST CALL: draft-ietf-regext-data-escrow-01 draft-ietf-regext-dnrd-objects-mapping-01

This WGLC was to be closed on 4 October 2019. There was some discussion about some editorial changes in draft-ietf-regext-data-escrow and there were a few material changes to regext-dnrd-objects-mapping. The changes to the latter document maintained backward compatibility but a separate secon

[regext] EPP and rate-limiting

Sometimes, some clients are too talkative and, for instance, try too often to grab a domain. I'm not sure of the best error code to return when such behaviour is detected. HTTP has 429 "Too Many Requests" (RFC 6585) but I don't find a proper code in EPP. Any idea?

[regext] Agenda items for IETF 107 Vancouver

Hello Working Group, It is time to start thinking of scheduling a WG meeting for IETF 107 in Vancouver. The deadline for requesting a meeting slot is due in 3 weeks. To get an impression on if and for how long a meeting slot we will need, this is a first call for agenda items. Does anybody have