- Why is "not inconsistent" used rather than "consistent" for the policy recommendations being implemented? Does it mean the same thing?
- When the board was considering the recommendations, they found some recommendations "inconsistent" with the GAC Advice. And, these "inconsistent" recommendation were not adapted for implementation. In contrast, the recommendations that were "not inconsistent" were adapted for implementation. Therefore, "not inconsistent" and "consistent" do mean the same for the purposes of our implementation.
- When will the "inconsistent" recommendation be resolved for implementation?
- The timing and the process for resolving these inconsistencies depends on activities outside of this policy implementation team and the IRT. Discussion related to these other GNSO policy recommendations relating to other RCRC and IGO identifiers that has not been adapted by the board can be found on the community wiki page:https://community.icann.org/x/eoPRAw.
- Does this policy apply to all gTLDs or just new gTLDs?
- The policy applies to all gTLDs. However, the timing of the implementation effective dates will determine the practical impact that it has to the gTLDs. Please review the final policy document and its effective date for careful consideration.
- Does the INGO Claims Service that's required for the first 90 days of registration availability apply to the gTLDs that have already been delegated?
- The INGO Claims Service only applies to the gTLDs delegated after this consensus policy is effective (Section 5.1 Scope.) It does not apply to INGO names that may be available for registration after the policy effective date if the gTLD has been delegated prior to the policy effective date.
- Who should I contact if I have questions?
Submit questions via firstname.lastname@example.org with the following subject heading “Inquiry – IGO/INGO Identifier Protection Policy.”