Hello James, On 28/03/2017 20:09, Gould, James wrote:
> Thomas, > > Putting the avail attribute at the level of fee:cd addresses use cases > where the domain name is invalid, reserved (without pricing), and the > currency is invalid. In these cases, you would not want to return all > the commands with an avail=false to indicate that the fee information > is not available for the domain. If the server needs to get down to > the detail of providing availability at the command level, then the > avail attribute could be added there as well, but there is an extra > level of complexity to handle it at the command level. If the command > is invalid, the period is invalid, having the avail flag only at the > fee:cd level would fast-fail to not provide any of the fee > information. Although this may not be as functional, it allows the > server to fast fail the fee check which is important to keep the > availability check more lightweight. I would prefer to fast fail if > possible. I agree that a fast fail is preferable if the domain name or currency prevent the name from being available in any case. The use case I'm thinking of refers to the provision in fee-0.15 that allows the server to return availability information for all active launch phases. In fee-0.15, this is possible by returning <fee:command> elements with avail="true" for launch phases permitting the name, and elements with avail="false" for launch phases not permitting it. But I guess in the new approach (with avail in the framing element) this is still possible by simply omitting the non-available results and only including <fee:command> elements for the phases that support the operation. The registrar doesn't need to learn about existing launch phases that do not allow the registration of the name. 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
