IDN.3.4.Same Entity Allocation
Describe how this RSP’s implementation will comply with the following: For second-level variant labels that arise from a registration based on a second-level IDN table, 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 all allocated variant TLD labels {t1, t1v1, …}).
Response
Registry manages second-level IDN variant labels per IDNA 2008, RFC 7940 and EPP, abiding by the Minimal Data Set Policy. It realizes single-entity allocation via technical binding and lifecycle control: auto-reserving variants for the primary domain registrant, verifying ownership for activation, and revoking variants with the primary domain. The Registry maintains fully consistent disclosure rules for second-level IDN variant names under the RDDS framework, with no discrepancy in query behavior, results, or messages between WHOIS and RDAP. Active variants are queryable in both systems; inactive variants return "domain does not exist"; statuses are synchronized to ensure consistent registration data. Under the Minimal Data Set, it enforces single registrant via unique identifiers and registrar contracts, bans independent host objects for variants, and supports separate DS RRs and independent DNSSEC maintenance for primary and variant domains.
The Same Entity Allocation Principle applies uniformly to the entire TLD Set, covering the primary TLD and all corresponding variant TLDs. The registry implements consistent entity qualification verification and allocation control rules across the entire TLD Set, and will not set differentiated policies separately for the primary TLD or any individual variant TLD.
For details, please refer to the attachment.
Attachments
