2013 RAA | Frequently Asked Questions
On 17 May 2018 the ICANN Board adopted a Temporary Specification for gTLD Registration Data. This page is under review and will be updated to address the Temporary Specification.
Adoption of the 2013 Agreement
How can I sign on to the 2013 RAA?
Registrars currently have two options for adopting the 2013 RAA: they may wait until their current RAA expires, or they may adopt the 2013 RAA early. Registrars whose accreditation agreements are not due to expire soon might wish to consider the early adoption path, as only registrars on the 2013 RAA will be permitted to sell registrations in new gTLDs.
If you would like to adopt the 2013 RAA early, you can request an early adoption form by submitting an email to firstname.lastname@example.org.
Where can I see the difference between the 2009 and 2013 RAA?
Please find a link to a redline of the 2013 RAA against the 2009 RAA here: Redline of 2013 RAA against 2009 RAA [PDF, 425 KB].
Are the fees the same for the 2013 and the 2009 RAA?
Yes. Annual accreditation fees are fees that all registrars are required to pay annually to maintain accreditation. The fee is $4,000 per year. Unless a registrar is operating under the 2001 version of the RAA, registrars have the option of paying the annual $4,000 accreditation fee in quarterly installments of $1,000.
Variable accreditation fees are determined based on the transaction type and volume of each registrar. There are two types of fees associated with the variable accreditation fees:
Variable fees for all registrars in the aggregate are budgeted at $3.8 million but are expected at $3.4 million for FY14. The variable fee is divided among all registrars based on a validated concept that ICANN often expends the same quantum of effort in providing services to a registrar regardless of size. However, provided that the registrar is considerably smaller in size and in activity, some registrars will continue to be eligible for "forgiveness" of two-thirds of the standard per-registrar variable fee. To be eligible for forgiveness, the registrar must have (1) less than 350,000 gTLD names under its management and (2) no more than 200 attempted adds per successful net add in any TLD. Forgiveness will be granted each quarter to all registrars that qualify.
The amount of the variable fee payable per registrar is calculated each quarter by dividing $950 thousand (one-fourth of $3.8 million) equally among all registrars that have at least been accredited for one full quarter or have made at least one transaction, taking into consideration the forgiveness factor.
- Transaction-based fees are assessed on each annual increment of an add, renew or a transfer transaction that has survived a related add or auto-renew grace period. This fee will be billed at $0.20 per transaction for registrars operating under the 2001 RAA, and $0.18 per transaction for registrars operating under the 2009 or 2013 RAA.
When I submit the 2013 Request Form, how long will it take for ICANN to process it?
When the early request form is received, a member of the Registrar Services Team will acknowledge receipt of the form. ICANN will then run a preliminary compliance check to confirm that the registrar is in compliance with its current RAA, e.g., 2001 RAA or 2009 RAA. This process will take approximately 2-3 weeks. ICANN will then get back to the registrar with the results of the preliminary compliance check and either send the 2013 RAA for signing or inform the registrar of any outstanding compliance issues.
The RAA will be sent via DocuSign for electronic signing. If the registrar prefers a hard copy of the RAA, the registrar can select the "sign on paper" option. Please print out two copies, and sign pages 39, 63 and 67, and return via courier to ICANN at the following address:
Internet Corporation for Assigned Names and Numbers
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
The fax sheet must also be completed and returned to DocuSign.
Is there a list of what is required upon signing vs. what is required on 1 January 2014?
Yes. Please refer to the ICANN Compliance presentation from the 2013 RAA Outreach Session. The last two slides of the presentation show these details. The link to the presentation can be found here: http://www.icann.org/en/resources/compliance/outreach/raa-22aug13-en.pdf [PDF, 298 KB].
Registrar Data Directory Service (Whois) Specification
Does my Registrar Data Directory Service (Whois) response format have to follow the same order as the example in Section 1.4.2 of the RDDS (Whois) Specification?
Yes. The format of responses shall contain all the elements in the provided order.
The Registrar Data Directory Service (Whois) Specification requires me to provide a Registrar Abuse Contact Phone in my Whois output. Would it be okay to display the text "please contact us by email" in this field?
No. The Registrar Data Directory Service (Whois) Specification requires the registrar to provide a Registrar Abuse Contact Email and a Registrar Abuse Telephone Number. An actual valid telephone number needs to be provided for the telephone field.
Regarding the Registration Data Directory Service (Whois) Specification, the name servers of the domain name must be listed in the Whois records. In a case where a name server depends on the same domain name (e.g. the domain name is icann.org and one of the name servers is ns.icann.org), must a glue record be listed and in which format?
Glue records are not required; however, registrars have the option to add more fields. Therefore, a registrar could add the IP addresses for glue data. If a registrar were to do that, it should add the fields using the format defined in the new gTLD base agreement:
IP Address: 192.0.2.123
IP Address: 2001:0DB8::1
Section 1.4.2 of the RDDSS gives an example of compliant Whois output. That output shows the following DNSSEC status: DNSSEC: signedDelegation. What are the other possible values for this field?
The two possible values are:
Is DNSSEC mandatory?
Registrars are not required to offer DNS hosting (which might or might not include DNSSEC service), but they must facilitate DNSSEC entries to the registry.
What are the sanctions for Service Level Agreement failures in the RDDS Specification?
ICANN Compliance will follow its standard procedure found here: http://www.icann.org/en/resources/compliance/approach-processes. Additionally, the registrar may be asked to provide a root cause analysis, explaining why the problem occurred and identifying short and long-term solutions.
Data Retention Specification
How can I request a waiver from compliance for items in the Data Retention Specification that would violate my local laws?
The 2013 Registrar Accreditation Agreement (RAA) includes within its Data Retention Specification (DRS) a provision by which registrars may request a waiver from compliance with specific terms and conditions of the DRS. Registrars who wish to request a DRS waiver can find the relevant form and process here: ttp://www.icann.org/en/resources/registrars/updates/retention.
In addition, please make sure to indicate (a) the specific allegedly offending data collection and retention elements that you believe would violate your local law and those that would not violate your local law; (b) the specific period(s) of time that you believe retention of various data elements would and would not be permitted under your local law; and (c) the specific provisions of your local law that you believe would be violated.
Can I submit a data retention waiver request on behalf of my back-end provider or reseller(s)?
Registrars may submit a data retention waiver request on behalf of third parties, and ICANN will review the requests on a case-by-case basis. The request(s) must come through the registrar itself; requests from non ICANN-accredited registrars will not be evaluated by ICANN.
Am I required to retain the data in the event of a change to the registration data, or is it acceptable to collect required information only at the time of registration?
Changes to registration data must be retained, just as any changes to registration data had to be retained under the 2009 RAA.
Is my reseller responsible for retaining data?
While registrars may outsource some of the requirements of the RAA to resellers, please note that the registrar is ultimately responsible for compliance with the RAA. If ICANN observes that a reseller is not in compliance with the RAA or any ICANN consensus policy, ICANN would commence its compliance inquiry directly with the sponsoring registrar (not the reseller).
If a registrar is only offering new gTLDs, is the registrar required to offer Whois via Port 43?
The registrar will only have to provide Port 43 access for thin registries. For all registries, including new gTLDs, the registrar is still required to provide web-based access.
New Posting and Disclosure Requirements
Does the abuse point of contact need to be on my homepage or can it be on a page to which the homepage links? Is a "Contact Us" page okay for this requirement?
The abuse point of contact needs to be conspicuous and readily accessible for those that need to search for it. The rationale for using the term "homepage" is so that the email for the abuse point of contact is not buried under several links. From an ICANN Compliance perspective, it would not be a problem to have a link from the main page that goes to a second page. It does, however, need to be conspicuously posted on the registrar's site. It cannot, for example, be behind a log in page or sub-linked down several pages that would require a number of clicks. It would be best if the contact is on the main page or a second page accessible by a link prominently displayed on the main page.
If the link to the "Contact Us" page is readily accessible on the registrar's homepage and includes the abuse point of contact (et. al.), that would be compliant under the 2013 RAA.
Is it OK if we expose a link to a contact form to reach the abuse desk, rather than expose the email address?
No. Section 3.18.1 provides that an actual email address needs to be provided. Providing a contact form would not be compliant under the 2013 RAA.
Do we need to post names of all of our officers on our web site(s)?
Further to Item 17 of the Registrar Information Specification, officer names and positions must be published on the registrar's website. Officer email addresses are not required to be posted to the registrar's website. All items of the Registrar Information Specification that have an asterisk (*) next to them must be published on the registrar's website.
How is officer defined?
The definition of officer will depend on what constitutes an officer for a corporation or other entity under the law of the registrar's jurisdiction.
Do I have to maintain a unique law enforcement contact, or can a law enforcement contact be shared among registrars?
The email address and telephone number do not have to be unique, but they must be monitored 24 hours per day and 7 days per week. Additionally, well-founded reports of abuse must be responded to within 24 hours further to Section 3.18.2 of the RAA.
Do website disclosures apply irrespective of the registrar business model? For example, if we operate on a purely reseller basis (i.e. all registrants purchase through resellers) do the website disclosures still need to be made?
Yes. Website disclosures must be made irrespective of the registrar's business model.
We are required to make our renewal fees, post-expiration renewal fees (if different), and redemption/restore fees reasonably available to registered name holders and prospective registered name holders at the time of registration of a gTLD name. How are we expected to comply with this obligation when the registration is made through a reseller? We do not set resellers' prices as this would be illegal.
There are a number of ways registrars could comply with this provision of the ERRP. ICANN does not dictate a specific process your registrar must use. We have provided some suggestions below, which you might wish to consider:
- Include all of the ERRP reseller obligations in the agreement between your registrar and its resellers and attach consequences for contract non-compliance.
- Implement monitoring processes whereby your registrar periodically looks at its resellers' websites to be certain they are allowing your registrar to maintain compliance with ERRP obligations.
- Include annual reporting requirements in the agreement between your registrar and its resellers that would require resellers to provide evidence that they are in compliance with the ERRP obligations and other RAA obligations.
If ICANN observes that a reseller is not in compliance with an ICANN consensus policy, such as the ERRP, or any provision of the RAA, ICANN would commence its compliance inquiry directly with the sponsoring registrar (not the reseller).
It would be acceptable for the registrar/reseller to post the highest fee it would charge for renewal/redemption as fees may be different depending on the business model, i.e., discounts for bulk registrations or other factors determined by the registrar.
Section 3.17 of the RAA states that Information related to Registrars needs to be published on the website as per the Registrar Information Specification. What information from the Specification needs to be published on our website?
The items from the Registrar Information Specification that need to be published on the registrar's website are:
Item 7, the correspondence address for the Registrar;
Item 11 (If the location or address of Registrar's principal place of business is different from the address provided in 7, provide details including address, phone number, fax number and email address);
Item 17, Officer names and positions; and
Item 22 (List the ultimate parent entity of the Registrar, if applicable)
All other information in the Registrar Information Specification must be submitted to ICANN as per 3.17 of the RAA, but it does not have to be published on the registrar's website.
Section 3.7.11 of the RAA provides that registrars shall make available a description of the customer service handling processes available to Registered Name Holders regarding Registrar Services, including a description of the processes for submitting complaints and resolving disputes regarding the Registrar Services. How much detail must this process include?
ICANN will validate that a description of the Customer Service Handling Process is available to the public on a registrar's website(s) in which a registrar offers Registrar Services, or whether it is provided upon request. The Customer Service Handling Process must contain sufficient detail to qualify as a valid Customer Service Handling Process.
Section 3.18.2 provides that well-founded reports of Illegal Activity submitted to the registrar must be reviewed within 24 hours by an individual who is empowered by Registrar to take necessary and appropriate actions in response to the report. In responding to any such reports, Registrar will not be required to take any action in contravention of applicable law. What does "well-founded" mean?
ICANN will consider this on a case-by-case basis, taking into account factors such as substantiation, demonstration, corroboration or evidence of Illegal Activity, but cannot specify in any particular circumstance what qualifies as "well-founded" as that may vary based upon the situation. If the registrar believes the request is not "well-founded," it should document the reasons for this decision.
Section 3.12 of the RAA requires me to maintain written agreements with my resellers. Would a digital signature be okay for this requirement?
The answer to this question depends on the law of the registrar's jurisdiction. If, for example, the registrar's jurisdiction recognizes digital signatures as legally enforceable, a digital signature would be okay for this requirement of the RAA.
Section 3.12.6 provides that I must use "commercially reasonable efforts" to enforce reseller compliance. Can you provide an example of commercially reasonable efforts?
The list below is a non-exhaustive list of examples that would be evidence that the registrar is enforcing its agreement with the reseller:
- Include all of the reseller obligations in the agreement between your registrar and its resellers and attach consequences for contract non-compliance
- Implement monitoring processes whereby your registrar periodically looks at its resellers' websites to ensure compliance with certain RAA obligations (such as website posting requirements)
- Include annual reporting requirements in the agreement between your registrar and its resellers that would require resellers to provide evidence that they are in compliance with RAA obligations
Whois Accuracy Verification Specification
How would registrars demonstrate compliance for manual or verbal verifications?
ICANN will require a written confirmation of verbal verifications, such as an email or note indicating with whom the registrar spoke as well as the date, time, phone number, and a description of the substance of the conversation.
2013 RAA Webinars
Where can I find links to 2013 RAA webinars?
19 September Webinar on New Website Posting Requirements:
Link to recording: http://icann.adobeconnect.com/p94n1sd2m19/
Link to slides: http://www.icann.org/en/resources/registrars/raa/info-disclose-25sep13-en.pdf [PDF, 235 KB]
3 October Webinar on Resellers:
Link to recording: http://youtu.be/hgix6GUwY-g
Link to Slides: http://www.icann.org/en/resources/registrars/raa/resellers-03oct13-en.pdf [PDF, 218 KB]
17 October Webinar on Changes to Registrar-Registrant Agreement and New Compliance Certificate Requirement:
Link to recording: http://youtu.be/gSluQRFN5bg
Link to slides: http://www.icann.org/en/resources/registrars/raa/registrant-agreement-compliance-17oct13-en.pdf [PDF, 207 KB]
31 October Webinar on Whois
Link to recording: http://youtu.be/5OVxXzRDkhQ
Link to slides: http://www.icann.org/en/resources/registrars/raa/whois-inaccuracy-rdds-31oct13-en.pdf [PDF, 227 KB]