Re: [regext] RFC 8748, EPP Registry Fee Extension: availability check result depending on fee extension?

2020-07-14 Thread Thomas Corte (TANGO support)
James, On 7/13/20 21:46, Gould, James wrote: > Thomas, > > Signaling support for fee-1.0 in the login services is not material for this > use case. The key element is whether the create of the premium domain name > will fail if the client does not know the correct fee and the fee extension

Re: [regext] RFC 8748, EPP Registry Fee Extension: availability check result depending on fee extension?

2020-07-14 Thread Gould, James
Thomas, The versions of the fee extension that you reference have similar language associated with returning avail="0" for premium domains: 1. fee-0.23 - https://tools.ietf.org/html/draft-ietf-regext-epp-fees-08#section-4 2. fee-0.21 - https://tools.ietf.org/html/draft-ietf-regext-epp-fees-05#

Re: [regext] RFC 8748, EPP Registry Fee Extension: availability check result depending on fee extension?

2020-07-14 Thread Thomas Corte (TANGO support)
Hello James, On 7/14/20 14:01, Gould, James wrote: > Thomas, > > The versions of the fee extension that you reference have similar language > associated with returning avail="0" for premium domains: > > 1. fee-0.23 - > https://tools.ietf.org/html/draft-ietf-regext-epp-fees-08#section-4 > 2. f

Re: [regext] RFC 8748, EPP Registry Fee Extension: availability check result depending on fee extension?

2020-07-14 Thread Gould, James
Thomas, > By the way, you're right that fee-0.8 is very old, however you'd be > surprised that, for many registries, it is still the latest version they > will support, with some only supporting even *older* versions (like > fee-0.5 in the case of CentralNic). > This has led to the

[regext] =?UTF-8?Q?Re:__RFC_8748, _EPP_Registry_Fee_Extension:_availabilit?= y check result depending on fee extension?

2020-07-14 Thread Patrick Mevzek
On Tue, Jul 14, 2020, at 07:26, Thomas Corte (TANGO support) wrote: > Based on this experience, I'm afraid it will take a long time until > fee-1.0 will be widely adopted by registries or registrars, if ever. It was exactly the same situation when EPP was being specified, registries implemented

Re: [regext] EPP Registry Fee Extension: availability check result depending on fee extension?

2020-07-14 Thread Thomas Corte (TANGO support)
Hello, On 7/14/20 17:21, Patrick Mevzek wrote: > It is a classical chicken and egg problem based on the fact that registries, > once they got one version working have no or very little incentive to change > (being similar as other registries is not a strong force for them) and for > registrars

Re: [regext] EPP Registry Fee Extension: availability check result depending on fee extension?

2020-07-14 Thread Patrick Mevzek
On Tue, Jul 14, 2020, at 10:48, Thomas Corte (TANGO support) wrote: > As long as they keep supporting ancient versions of the extension (or, in > the case of Donuts, use their own proprietary one), the larger registrars > will see no incentive to implement newer versions, and will in turn > pre