Also - << In our use case, we simply modeled the concept of "premium" domain names around launch phases. For each category of premium domain names, a launch phase exists in which only the names from the category are available. So here it's strictly policy (i.e., the lists or premium names in each category) that determines a name's availability in a launch phase, not whether or not the name already exists, or which data is passed along with the registration. >>
In this paragraph, it sounds like the domain:create command does not need a fee to be sent into create the premium domain. It only needs the correct phase? Is that correct? 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: Monday, August 07, 2017 10:58 AM To: Gould, James <jgo...@verisign.com>; regext@ietf.org Cc: supp...@tango-rs.com Subject: Re: [regext] TLD Phase Discovery James, On 07/08/2017 17:18, Gould, James wrote: > Thomas, > > My feedback is provided below with a “JG-“ prefix. > > From a high level, we need other registries and registrars to weigh in on > this topic to answer the following: > ... I can see the reasoning behind this outreach, though personally I wouldn't subscribe to a strictly "democratic" approach with regard to this topic (or any technical decision for that matter). For example, in my experience as a registrar client developer, many registries' EPP servers don't properly handle XML namespaces (in that they're requiring clients to use the specific namespace prefixes used in the RFC examples, but don't allow arbitrary other prefixes). Other registries' EPP servers do occasionally send EPP responses that violate the EPP schemas. While these are clearly violations of the relevant specs, someone might argue that EPP clients not using the "standard" XML namespace prefixes, or EPP clients actively validating EPP responses against the schemas, represent "corner cases" not worth supporting. Needless to say, I wouldn't agree. > JG-I believe the Available Check Form was added to fulfil the need of > determining whether a domain is available in a specific launch phase. The > Availability Check Form should be lightweight and it should not be very > difficult for a client to get what is needed once they know what the launch > phases are either out-of-band or via an extension like the Registry Mapping. Sure, but no command is "lightweight" from the server's perspective if it has to be sent multiple times to achieve its goal. > JG-Yes, the question for this use case is whether the availability is > strictly based on policy, meaning given the list of known launch phases would > the domain name be available in each phase based on its policy? In our use case, we simply modeled the concept of "premium" domain names around launch phases. For each category of premium domain names, a launch phase exists in which only the names from the category are available. So here it's strictly policy (i.e., the lists or premium names in each category) that determines a name's availability in a launch phase, not whether or not the name already exists, or which data is passed along with the registration. 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
