Changes

Line 112: Line 112:  
*After ICANN validates the delegation POC, obtain IANA token later used to start delegation <ref>http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf PDF Customer Portal User Guide: Transition to Delegation</ref>
 
*After ICANN validates the delegation POC, obtain IANA token later used to start delegation <ref>http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf PDF Customer Portal User Guide: Transition to Delegation</ref>
 
See ICANN's [http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf Customer Portal User Guide: Transition to Delegation PDF] for specific instructions.
 
See ICANN's [http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf Customer Portal User Guide: Transition to Delegation PDF] for specific instructions.
 +
====Tips====
 +
At ICANN 49, an IANA representative offered some advice to applicants to help their transition to IANA go more smoothly:<ref name="fortynine"></ref>
 +
*Know that every contact provided by the registry to IANA will be contacted and must respond from each email account listed, even if the accounts belong to the same person.
 +
*Make sure the appointed delegation POC is prepared to receive the pin via email.
 +
*IANA will ask for the name of the organization, the name provided by the delegation POC must exactly match the name on the RA; if it does not, it will fail IANA's verification mechanisms.
 +
*If you receive a notice from IANA regarding a technical failure on the part of the registry or its credentials, there may not be a need to panic. IANA's verification and checks are designed to be conservative and may result in false positives. If you are notified of this kind of failure, contact IANA.
    
===Delegation Process===
 
===Delegation Process===
231

edits