Hello James, On 2017-03-20 19:22, Gould, James wrote:
> Inclusion of grace period credits is timed based (logic executed at > the time of the delete) and is much more involved than returning the > applicable prices. The extension of the availability check command > in draft-ietf-regext-epp-fees-02 is already far beyond what is > reasonable for an extension to check, so we should look to separate > this into an extension to info in the form of a fee info command. > The RGP extension already includes information associated with the > applicable grace periods, so inclusion of the actual credit values > may not be necessary. Granted, knowledge about the applicable grace periods reveals potential refunds upon deletion, but not the actual amounts. That said, I agree that conducting time-based checks based on a concrete domain's life cycle status for a <fee:check> seems excessive, especially since the actual outcome of a deletion may be different even if it is performed only seconds later. While our current implementation of <fee:check> (for fee-0.11) returns expected fees based on the launch phase a specified domain was registered in (if the domain exists), it does not consider any other attributes of the domain in question. I believe it a good idea to retain this behavior for checks on domain deletion, effectively meaning that (in a standard pricing model where deletions are free and no refund is granted outside of grace periods) no fees or credits would ever be returned by a fee check for the "delete" command. However (going back to Matthieu's question), I believe the fee extension in a response to an actual <domain:delete> should indeed return the actual credits granted if the domain is within some grace period(s) at the time of deletion. 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