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

[Jody Kolker <[e-mail]>]

Hi Thomas,

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

With the launch of the new gTLDs, we have numerous examples of domains that are reserved by the registry, but are available for sale given some circumstances.  For this reason, we would like all reserved domains to be assigned a fee.


Thanks,
Jody Kolker
319-294-3933 (office)
319-329-9805 (mobile) Please contact my direct supervisor Charles Beadnall ([e-mail]) with any feedback.

This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.



-----Original Message-----
From: regext [mailto:[e-mail]] On Behalf Of Thomas Corte
Sent: Wednesday, March 29, 2017 3:42 AM
To: [e-mail]
Cc: [e-mail]
Subject: Re: [regext] draft-ietf-regext-epp-fees-02.txt: currency error handling, command wildcard

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

_______________________________________________
regext mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/regext