Just to be clear, as a registrar performs a fee check, we expect to receive the command cost for the domain at the time the check is performed, not what it was at the time of creation. We also expect that fees for domains are not changed without registrars being notified well in advance.
Thanks, Jody Kolker 319-294-3933 (office) 319-329-9805 (mobile) Please contact my direct supervisor Charles Beadnall (cbeadn...@godaddy.com) 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:regext-boun...@ietf.org] On Behalf Of Thomas Corte Sent: Wednesday, March 29, 2017 12:26 PM To: regext@ietf.org Cc: supp...@tango-rs.com Subject: Re: [regext] draft-ietf-regext-epp-fees Hello James, On 29/03/2017 19:04, Gould, James wrote: > The availability of the domain name and the availability of the fee > information can be separate. Consider the use case where a client > does a check for an existing domain name (e.g., > "existing-domain.example"), where the availability check returns > "false" but the fee extension could return the fee information, which > may be useful if the existing domain name is in pendingDelete. Let me > be clear that the fee information for an existing domain name is based > strictly off the fee tables and not looking at the fee and credit information > of the existing domain itself. I think it may in some cases be necessary to actually look at the domain instead of some static "fee table". E.g. it's possible that the domain, at the time when it was created, was on some "premium" list that caused a certain set of higher tariffs (also for renewals and transfer) to be permanently attached to it. This would mean that any registrar who transfers the domain to his account needs to be aware of the higher costs. That domain name could have been subsequently taken off the "premium" list, but that doesn't necessarily change the pricing for the existing domain. In this situation, the "static" pricing looks normal to the server, while the actual pricing for the existing domain is still higher than normal. If the <fee:check> command would only look at a static "premium" name list, it would return a wrong pricing information to e.g. a registrar that wants to transfer the name, or renew it. In fact, one of the main reasons why we implemented the fee extension in our system is to ensure that registrars don't accidentally transfer domain names into their portfolio that involve higher costs due to the configuration of the system at the time of their creation. Best regards, Thomas -- TANGO REGISTRY SERVICES® is a product of: Knipp Medien und Kommunikation GmbH Technologiepark Phone: +49 231 9703-222 Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200 D-44227 Dortmund E-Mail: supp...@tango-rs.com Germany _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
