Re: [regext] draft-ietf-regext-epp-fees-02.txt: currency error handling, command wildcard

[Thomas Corte <[e-mail]>]

Hello James,

On 28/03/2017 20:10, Gould, James wrote:

> Jody, 
> 
> Yes, the fee information should be returned for a reserved domain if pricing information does exist.  

Not sure what this would mean. If a domain is reserved, that usually
means that it's not available for registration under *any* circumstances.
Therefore there should never be a pricing information available for such
a domain.

The alternative would be to return the *fictitious* price for the domain
should it ever *become* available in the future, but that's impossible to
assess and would not provide useful information to the registrar.


In our current implementation, the fee information returned by a
<fee:check> is generally identical to the fee information that would be
returned if the registrar actually tried to execute the given transform
command on the given domain name, in the given launch phase, with the
given period. That includes a check for the name's actual availability.
It's essentially a simulation of the given operation on the name.

While I agree that the availability check is already a task that the
standard <check> command accomplishes, the fee extension provides the
opportunity to extend its basic functionality. If e.g. a registry
releases premium names by allowing their registration in specific launch
phases, each with specific prices, the fee extension provides (at least
in version fee-0.15) a way to tell the registrar in which of these phases
a name is available, and at which price.

Best regards,

Thomas

-- 
TANGO REGISTRY SERVICES® is a product of:
Knipp Medien und Kommunikation GmbH
Technologiepark                             Phone: [phone]
Martin-Schmeisser-Weg 9                       Fax: [phone]
D-44227 Dortmund                       E-Mail: [e-mail]
Germany