A clause providing for a derogation from the code of conduct is contained in the provisions of the tender specifications. Therefore, any registry operator who requests specification 13 from the RA is not obliged to request a separate derogation from the code of conduct. All registries must select an ICANN-authorized data escrow agent (DEA) for the provision of data-escrow services. Compliance verifies whether valid deposits have been made by the DEA and whether the Registry has sent fiduciary notifications to ICANN. Registries that have completed the form of the new gTLD registration agreement must comply with certain mandatory and voluntary public interest obligations (if any). Mandatory provisions include certain provisions of the Registry-Registrar Agreement (RRA) and the carrying out of periodic technical analyses. These obligations can be implemented through the Public Interest Dispute Resolution Process (PICDRP). [Update October 20, 2017: The final framework for Registry Operator to Security Threats is available here: www.icann.org/resources/pages/framework-registry-operator-respond-security-threats-2017-10-20-en] Loggers who have completed the new gTLD registration agreement form must not use DNS-Platzhalter resource entries, methods of summarizing DNS resource entries, or hijacking at all levels inside DNA for domain names that are not registered or have not provided valid NS entries. When viewing these domain names, authorizing name servers must return a “Name Error” response (also known as NXDOMAIN), RCODE 3 as described in RFC 1035 and related RFCs.

. . .