IDN.2.4.Same Entity Allocation
Describe how compliance will be achieved for second-level variant labels that arise from a registration based on a second-level IDN table where all allocatable variant labels in the set must only be allocated to the same entity or withheld for possible allocation only to that entity (e.g., all allocatable second-level labels {s1, s1v1, …} under the TLD.
Response
As described in the answer of 2.3.c, additional variants are activated for the primary name, cannot be registered separately. Once a primary name is registered, all variants can no longer be registered independently. The variants are stored in our database as associations to the primary name. The variants cannot have their own contacts or hosts. The variants are published into DNS zone files using the primary name’s host records. Therefore, there is no way for the variants of a registered primary name to be allocated to other entities even with the minimal registration data sets.
A Registrar can only submit one domain registration. And on their side that needs to be tied to a Registrant. Variant domains in our system are "attributes" of the domain. So when created they by default have to associated to the same Registrant that registered the domain. There is no possibility of a variant domain going to a different Registrant.
In addition to the technical restrictions we place in order to ensure that a Variant cannot have a different Registrant under the minimal data set, we will implement a contractual provision in our agreement with the Registry Operator (RO) requiring that the Registry Operator include a corresponding provision in the Registry-Registrar Agreement (RRA). This provision will obligate registrars to ensure that the registrant entity (RANT) for a variant domain name is identical to that of the primary domain name.
