SlideShare a Scribd company logo
Text
Text
#ICANN49
2013 Registrar Accreditation
Agreement FAQs
Text
#ICANN49
26 March 2014
• Caitlin Tubergen
o Registrar Relations and Contracts Manager
• Owen Smigelski
o Senior Manager, Contractual Compliance
Text
#ICANN49
Agenda
• 2013 RAA Statistics
• How to Request 2013 RAA and Process Time
• New Website Posting Requirements
• Whois Accuracy + RDDS Specification
• Dealings with Resellers
• Transfer of Accreditation to Wholly-owned
Subsidiaries
• Compliance
Text
#ICANN49
 2013 RAA Statistics
 Adopting the 2013
RAA
Text
#ICANN49
2013 RAA Statistics
* As of 21 March 2014
Total Registrar Count – 1008
335
(33.17%)
675
(66.83%)
Domains Under Management
125,299,774
(82.88%)
25,878,274
(17.12%)
2013 RAA 2009 RAA
Text
#ICANN49
7
Adopting the 2013 RAA
• To request the 2013 RAA, fill out the early
adoption form on ICANN website
• Process:
o Submit Form
o ICANN acknowledges receipt
o ICANN runs preliminary compliance check
o If approved, ICANN sends Registrar Information
Specification and 2013 RAA to the Registrar via
DocuSign
Text
#ICANN49
 New Requirements:
Registrars’ Websites
Text
#ICANN49
Website Requirements
• Provide links to the following:
o 3.7.10 Registrants’ Benefits and Responsibilities
Specification
o https://www.icann.org/en/resources/registrars/registrant-rights/benefits
o 3.16 Link to Registrant Educational Information
o https://www.icann.org/en/resources/registrars/registrant-rights/educational
Text
#ICANN49
Website Requirements (cont.)
• 3.17 Registrar Information Specification
o Defines items that a Registrar must publish on its
website:
 Item 7. Correspondence Address for the Registrar
 Must be able to accept notice of legal process
 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. Full name, contact information and position of all
officers of the Registrar
 Item 22. The ultimate parent entity of Registrar (if applicable)
i
Text
#ICANN49
Website Requirements (cont.)
• 3.18.1 Abuse Contact
o Publish an email address to receive such
reports on the homepage of Registrar’s
website
• 3.18.3 Tracking Abuse
o Supply a description of registrar’s
procedures for the receipt, handling and
tracking of abuse reports
Text
#ICANN49
 Whois Accuracy
 RDDS (Whois)
Specification
Text
#ICANN49
13
Whois Accuracy Specification
• Required as of 1 January 2014
• Requires validation and verification of registrant
and account holder data
• Deletion or suspension of registrations now
explicitly required in cases of:
o Willful provision of inaccurate / unreliable data (RAA
3.7.7.2)
o Willful failure to update data promptly (RAA 3.7.7.2)
o Failure to respond to registrar data accuracy inquiry
within 15 days (Section 4 of Whois Accuracy Spec)
Text
#ICANN49
Whois Validation
• Registrant and account holder “validation” required
within 15 days of:
o Registration
o Transfer
o Registrant or account holder data change
 Required fields must be filled (RAA 3.3.1)
 Email addresses format specified (RFC 5322)
 Telephone numbers format specified (ITU-T E.164)
 Postal addresses format specified (UPU S42)
 Cross-field validation (not required until mutual agreement
between ICANN and WG) (Transition Addendum)
Text
#ICANN49
Whois Verification
• Registrant & account holder “verification” required:
o Within 15 days of registration, transfer, or registrant or
account holder data change, email address or telephone
number verification is required (1(f) of Whois Accuracy Spec)
o Within 15 days of bounce or other evidence of inaccuracy –
email verification required (4 of Whois Accuracy Spec)
• Verification process requires affirmative response
o Non-response by registrant requires either manual verification
by registrar or suspension
o Non-response by account holder requires registrar to perform
manual verification only
Text
#ICANN49
Whois Accuracy Specification Exceptions
• Verification / validation not required if:
o Previously performed by registrar on identical data
o Registrar has no reason to believe the data has
become inaccurate or invalid
 Example: Whois inaccuracy complaint or email bounce back
Text
#ICANN49
 Whois Accuracy
Examples
Text
#ICANN49
Example 1: Updated Postal Address
• Registered Name Holder updates its postal
address
• Registrar must:
 Validate that the postal address is the proper format (Section
1(d) of Whois Accuracy Spec)
• Registrar is not required to:
 Re-verify the email address or the telephone number (Section
1(f))
Text
#ICANN49
Example 2: Updated Email Address
• Registered Name Holder updates its email
address
• Registrar must:
o Validate that the email address is the proper format
(Section 1(d) of Whois Accuracy Spec)
o Verify the email address if registrar previously
verified the email address pursuant to 1(f)(i). If
registrar verified this registered name holder
through a telephone number 1(f)(ii), registrar does
not have to verify the email address. (unless reason
to believe it is inaccurate)
Text
#ICANN49
Example 3: Updated Telephone Number
• Registered Name Holder updates its
telephone number
• Registrar must:
o Validate that the telephone number is the proper
format (Section 1(c) of Whois Accuracy Spec)
o Verify the telephone number if registrar verified tel.
numbers pursuant to 1(f)(ii). If registrar verified
this registered name holder through an email
address 1(f)(i), registrar does not have to verify the
telephone number.
Text
#ICANN49
 New Requirements:
RDDS (“Whois”)
Specification
Text
#ICANN49
New Whois Requirements
• Requirements in RDDS Specification
• Additional Whois fields required
• Uniform Whois query and output formats
• EPP status values required exclusively
• SLA for Whois service (Section 2.2 of RDDS Spec)
• IPv6 accessibility required
• Port 43 Whois only required for “thin” registries
(RAA 3.3.1)
Text
#ICANN49
New Whois Fields
• As of 1 January 2014
• Registry Domain ID
• Registrar Abuse
Contact Email
• Registrar Abuse
Contact Phone
• Domain Status
• Registry Registrant ID
• Registrant Phone
• Registrant Phone Ext
• Registrant Fax
• Registrant Fax Ext
• Registrant Email
• Registry Admin ID
• Registry Tech ID
• DNSSEC
• Last update of
WHOIS database
i
Text
#ICANN49
Output Field Details
• Registry Domain ID
o Does not change for length of registration
• Registrar Abuse Contact Email and Phone
o Registrar discretion, separate from LEA contact in RAA 3.18.2
• Domain Status – EPP status codes
• IDs: Registry Registrant, Registry Admin, Registry Tech
o May be left blank if not available from registry
• DNSSEC:
o Two options:
 DNSSEC: signedDelegation
 DNSSEC: unsigned
i
Text
#ICANN49
 Relationship with
Resellers
 Compliance Certificate
 Transfer of Accreditation
to Wholly-owned
Subsidiary
Text
#ICANN49
How Registrars Can “Ensure”
• Examples:
o Include all of reseller obligations in the agreement between
your registrar and its resellers and attach consequences for
contract non-compliance
o Implement monitoring processes whereby your registrar
periodically looks at its resellers' websites to ensure
compliance with certain RAA obligations (such as website
posting requirements)
o 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
Text
#ICANN49
Compliance Certificate
• Section 3.15 of RAA
o Registrar shall complete and deliver to ICANN
within twenty (20) days following the end of each
calendar year, a certificate executed by the
president, chief executive officer, chief financial
officer or chief operating officer (or their
equivalents) of Registrar certifying compliance with
the terms and conditions of this Agreement.
• Form is Compliance Certificate (Table of
Contents – 11)
Text
#ICANN49
Transfer of Accreditation to Wholly-owned Subsidiary
• Section 7.3.1 of RAA
• Required documentation:
o Documentation proving that the transferee entity is, in fact, a
wholly-owned subsidiary of the ICANN-accredited registrar.
o A letter, on company letterhead, from the ICANN-accredited
registrar (the transferor) acknowledging that it would like to
transfer its accreditation to the transferee
o A letter, on company letterhead, from the transferee,
acknowledging that it assumes and will be responsible for all
the existing obligations and liabilities of the Transferer
o Primary Contact Update (if applicable)
Text
#ICANN49
 Compliance
Text
#ICANN49
WHOIS Inaccuracy Verification & Validation Summary
o Registrar must verify or re-verify email address of
the Registered Name Holder (“RNH”) and if
different, the Account Holder (“AH”).
o The domain must be suspended or the registrar
must provide proof of manual verification.
o 1st notice response deadline will remain 15 business
days.
o Beginning with the second notice, ICANN will
inquire why registrars did not suspend or delete
registrations.
o 2 concurrent parallel tracks (next 2 slides)
Text
#ICANN49
Whois Inaccuracy
• Section 3.7.8 RAA & Section 5 of WHOIS Accuracy
Specification
o Registrar sends inquiry to RNH- starts 15-calendar day timeline.
o ICANN looking for three results
 1. WHOIS updated (within 15 days of inquiry sent to RNH)
 Registrar provides validation (and verified updates, including
affirmative responses if previously verified email or phone
was updated).
 2. No Response from RNH within 15 calendar days- Domain
suspended/terminated until Registrar has validated
information
 3. Registrar verified WHOIS information correct (within 15
days of inquiry sent to RNH) and Registrar has provided
documentation of verification
Text
#ICANN49
Whois Inaccuracy Requirements
• Section 4 of WHOIS Accuracy Specification
o Receipt of Notice starts 15-calendar day timeline.
o Registrar must verify or re-verify email address of the Registered
Name Holder (“RNH”) and if different, the Account Holder
(“AH”).
o Registrar must demonstrate an affirmative response from the
RNH to verify.
o If Registrar does not receive affirmative response from the RNH
within 15 days, the domain must be suspended or the registrar
must provide proof of manual verification.
o If Registrar does not receive affirmative response from AH, must
provide proof of manual verification. Suspension not required.
Text
#ICANN49
Registrar must verify email &
investigate complaint
WHOIS Inaccuracy
Complaint
1- WHOIS updated & validated
- OR -
2-Suspend if no response
- OR -
3- Verified correct & validated
(RAA Section 3.7.8 &
2013 Whois Accuracy Program Spec. 5)
Affirmative response to
email verification
(2013 Whois Accuracy
Program Spec. 4)
Whois Inaccuracy Example 2013 RAA
Text
#ICANN49
Abuse Reports Requirements
• Section 3.18 of the 2013 RAA
o Registrars must take reasonable and prompt steps to
investigate and respond appropriately to any reports of abuse
o Law enforcement reports: can be from any applicable
jurisdiction
o Registrars must include abuse email & phone number in Whois
output
o Abuse email address must be conspicuously on website, and
cannot be a web form
o Registrars cannot require a court order to investigate reports of
abuse, unless they inform ICANN of a specific local law or
regulation
Text
#ICANN49
 Question & Answer
Session
 You can submit further questions to
RAAquestions@icann.org

More Related Content

Viewers also liked

The gift of the magi
The gift of the magiThe gift of the magi
The gift of the magi
Alcira Vargas
 

Viewers also liked (15)

Paper discussion series- is an account receivables increase a cash outflows
Paper discussion series- is an account receivables increase a cash outflowsPaper discussion series- is an account receivables increase a cash outflows
Paper discussion series- is an account receivables increase a cash outflows
 
英國肥胖檔案 - 為什麼政府要課糖水稅?
英國肥胖檔案 - 為什麼政府要課糖水稅?英國肥胖檔案 - 為什麼政府要課糖水稅?
英國肥胖檔案 - 為什麼政府要課糖水稅?
 
Building a Serverless Pipeline
Building a Serverless PipelineBuilding a Serverless Pipeline
Building a Serverless Pipeline
 
Kubernetes Community Growth and Use Case
Kubernetes Community Growth and Use CaseKubernetes Community Growth and Use Case
Kubernetes Community Growth and Use Case
 
A Serverless Data Pipeline
A Serverless Data PipelineA Serverless Data Pipeline
A Serverless Data Pipeline
 
PixieDust
PixieDustPixieDust
PixieDust
 
The gift of the magi
The gift of the magiThe gift of the magi
The gift of the magi
 
Ipsos MORI Political Monitor - March 2016
Ipsos MORI Political Monitor - March 2016Ipsos MORI Political Monitor - March 2016
Ipsos MORI Political Monitor - March 2016
 
Ipsos MORI - BBC Newsnight Post-Referendum Research
Ipsos MORI - BBC Newsnight Post-Referendum ResearchIpsos MORI - BBC Newsnight Post-Referendum Research
Ipsos MORI - BBC Newsnight Post-Referendum Research
 
#MNBlogCon - The Marketer Abides: 5 Lessons in Creative Content Marketing Fro...
#MNBlogCon - The Marketer Abides: 5 Lessons in Creative Content Marketing Fro...#MNBlogCon - The Marketer Abides: 5 Lessons in Creative Content Marketing Fro...
#MNBlogCon - The Marketer Abides: 5 Lessons in Creative Content Marketing Fro...
 
Bus Bar Protection
Bus Bar ProtectionBus Bar Protection
Bus Bar Protection
 
AWS re:Invent 2016 recap (part 2)
AWS re:Invent 2016 recap (part 2) AWS re:Invent 2016 recap (part 2)
AWS re:Invent 2016 recap (part 2)
 
[DSC 2016] 系列活動:李泳泉 / 星火燎原 - Spark 機器學習初探
[DSC 2016] 系列活動:李泳泉 / 星火燎原 - Spark 機器學習初探[DSC 2016] 系列活動:李泳泉 / 星火燎原 - Spark 機器學習初探
[DSC 2016] 系列活動:李泳泉 / 星火燎原 - Spark 機器學習初探
 
Test Driven Design - GDG DevFest Istanbul 2016
Test Driven Design - GDG DevFest Istanbul 2016Test Driven Design - GDG DevFest Istanbul 2016
Test Driven Design - GDG DevFest Istanbul 2016
 
How to Successfully Run a Remote Team
How to Successfully Run a Remote TeamHow to Successfully Run a Remote Team
How to Successfully Run a Remote Team
 

Similar to 2013 Registrar Accreditation Agreement FAQs from ICANN 49

Registrars + law enforcement icann53
Registrars + law enforcement icann53Registrars + law enforcement icann53
Registrars + law enforcement icann53
ICANN
 
ITA SHAKEN Presentation Draft.pptx
ITA SHAKEN Presentation Draft.pptxITA SHAKEN Presentation Draft.pptx
ITA SHAKEN Presentation Draft.pptx
imranCCIE
 

Similar to 2013 Registrar Accreditation Agreement FAQs from ICANN 49 (20)

gTLD Registry Ongoing Operations from ICANN 49
gTLD Registry Ongoing Operations from ICANN 49gTLD Registry Ongoing Operations from ICANN 49
gTLD Registry Ongoing Operations from ICANN 49
 
TLD Launch Process Experiences & Registry Onboarding from ICANN 49
TLD Launch Process Experiences & Registry Onboarding from ICANN 49TLD Launch Process Experiences & Registry Onboarding from ICANN 49
TLD Launch Process Experiences & Registry Onboarding from ICANN 49
 
Registrars + law enforcement icann53
Registrars + law enforcement icann53Registrars + law enforcement icann53
Registrars + law enforcement icann53
 
ICANN 51: New gTLD Program Update
ICANN 51: New gTLD Program UpdateICANN 51: New gTLD Program Update
ICANN 51: New gTLD Program Update
 
Brander Group Buy IPv4 Address Blocks
Brander Group Buy IPv4 Address BlocksBrander Group Buy IPv4 Address Blocks
Brander Group Buy IPv4 Address Blocks
 
ICANN 51: Registry Services Update
ICANN 51: Registry Services UpdateICANN 51: Registry Services Update
ICANN 51: Registry Services Update
 
Improving the IPv4 transfer experience
Improving the IPv4 transfer experienceImproving the IPv4 transfer experience
Improving the IPv4 transfer experience
 
ITA SHAKEN Presentation Draft.pptx
ITA SHAKEN Presentation Draft.pptxITA SHAKEN Presentation Draft.pptx
ITA SHAKEN Presentation Draft.pptx
 
Battling Robocall Fraud with STIR/SHAKEN
Battling Robocall Fraud with STIR/SHAKENBattling Robocall Fraud with STIR/SHAKEN
Battling Robocall Fraud with STIR/SHAKEN
 
9. tmch presentation
9. tmch presentation9. tmch presentation
9. tmch presentation
 
Ename5
Ename5Ename5
Ename5
 
Making Optimal Use of the IRS Get Transcript Feature
Making Optimal Use of the IRS Get Transcript FeatureMaking Optimal Use of the IRS Get Transcript Feature
Making Optimal Use of the IRS Get Transcript Feature
 
Contact Discovery Vendor Process
Contact Discovery Vendor ProcessContact Discovery Vendor Process
Contact Discovery Vendor Process
 
California Real Estate Licensing Statistics Update and more
California Real Estate Licensing Statistics Update and moreCalifornia Real Estate Licensing Statistics Update and more
California Real Estate Licensing Statistics Update and more
 
The IANA Stewardship Transition Overview & Background
The IANA Stewardship Transition Overview & Background The IANA Stewardship Transition Overview & Background
The IANA Stewardship Transition Overview & Background
 
OpenBazaar Flow - Services
OpenBazaar Flow - ServicesOpenBazaar Flow - Services
OpenBazaar Flow - Services
 
Battling Robocall Fraud with STIR/SHAKEN
Battling Robocall Fraud with STIR/SHAKENBattling Robocall Fraud with STIR/SHAKEN
Battling Robocall Fraud with STIR/SHAKEN
 
ICANN 51: Rights Protection Mechanisms: User Feedback Session
ICANN 51: Rights Protection Mechanisms:  User Feedback SessionICANN 51: Rights Protection Mechanisms:  User Feedback Session
ICANN 51: Rights Protection Mechanisms: User Feedback Session
 
How to Navigate Getting IPv4 Addresses in a Post Run Out World
How to Navigate Getting IPv4 Addresses in a Post Run Out WorldHow to Navigate Getting IPv4 Addresses in a Post Run Out World
How to Navigate Getting IPv4 Addresses in a Post Run Out World
 
Spring fest 2018 ewrb
Spring fest 2018 ewrbSpring fest 2018 ewrb
Spring fest 2018 ewrb
 

More from ICANN

More from ICANN (20)

Call for Volunteers: Accountability & Transparency Review Team_PT
Call for Volunteers: Accountability & Transparency Review Team_PTCall for Volunteers: Accountability & Transparency Review Team_PT
Call for Volunteers: Accountability & Transparency Review Team_PT
 
Call for Volunteers: Accountability & Transparency Review Team_ZH
Call for Volunteers: Accountability & Transparency Review Team_ZHCall for Volunteers: Accountability & Transparency Review Team_ZH
Call for Volunteers: Accountability & Transparency Review Team_ZH
 
Call for Volunteers: Accountability & Transparency Review Team_ES
Call for Volunteers: Accountability & Transparency Review Team_ESCall for Volunteers: Accountability & Transparency Review Team_ES
Call for Volunteers: Accountability & Transparency Review Team_ES
 
Call for Volunteers: Accountability & Transparency Review Team_AR
Call for Volunteers: Accountability & Transparency Review Team_ARCall for Volunteers: Accountability & Transparency Review Team_AR
Call for Volunteers: Accountability & Transparency Review Team_AR
 
Call for Volunteers: Accountability & Transparency Review Team_FR
Call for Volunteers: Accountability & Transparency Review Team_FRCall for Volunteers: Accountability & Transparency Review Team_FR
Call for Volunteers: Accountability & Transparency Review Team_FR
 
Call for Volunteers: Accountability & Transparency Review Team_RU
Call for Volunteers: Accountability & Transparency Review Team_RUCall for Volunteers: Accountability & Transparency Review Team_RU
Call for Volunteers: Accountability & Transparency Review Team_RU
 
Call for Volunteers: Accountability & Transparency Review Team
Call for Volunteers: Accountability & Transparency Review TeamCall for Volunteers: Accountability & Transparency Review Team
Call for Volunteers: Accountability & Transparency Review Team
 
ICANN Expected Standards of Behavior | French
ICANN Expected Standards of Behavior | FrenchICANN Expected Standards of Behavior | French
ICANN Expected Standards of Behavior | French
 
ICANN Expected Standards of Behavior
ICANN Expected Standards of BehaviorICANN Expected Standards of Behavior
ICANN Expected Standards of Behavior
 
ICANN Expected Standards of Behavior | Russian
ICANN Expected Standards of Behavior | RussianICANN Expected Standards of Behavior | Russian
ICANN Expected Standards of Behavior | Russian
 
ICANN Expected Standards of Behavior | Arabic
ICANN Expected Standards of Behavior | ArabicICANN Expected Standards of Behavior | Arabic
ICANN Expected Standards of Behavior | Arabic
 
ICANN Expected Standards of Behavior | Chinese
ICANN Expected Standards of Behavior | ChineseICANN Expected Standards of Behavior | Chinese
ICANN Expected Standards of Behavior | Chinese
 
ICANN Expected Standards of Behavior | Spanish
ICANN Expected Standards of Behavior | SpanishICANN Expected Standards of Behavior | Spanish
ICANN Expected Standards of Behavior | Spanish
 
Policy Development Process Infographic Turkish
Policy Development Process Infographic TurkishPolicy Development Process Infographic Turkish
Policy Development Process Infographic Turkish
 
Policy Development Process Infographic Russian
Policy Development Process Infographic RussianPolicy Development Process Infographic Russian
Policy Development Process Infographic Russian
 
Policy Development Process Infographic Portuguese
Policy Development Process Infographic PortuguesePolicy Development Process Infographic Portuguese
Policy Development Process Infographic Portuguese
 
Policy Development Process Infographic Spanish
Policy Development Process Infographic SpanishPolicy Development Process Infographic Spanish
Policy Development Process Infographic Spanish
 
Policy Development Process Infographic French
Policy Development Process Infographic FrenchPolicy Development Process Infographic French
Policy Development Process Infographic French
 
Policy Development Process Infographic English
Policy Development Process Infographic EnglishPolicy Development Process Infographic English
Policy Development Process Infographic English
 
Policy Development Process Infographic Chinese
Policy Development Process Infographic ChinesePolicy Development Process Infographic Chinese
Policy Development Process Infographic Chinese
 

Recently uploaded

Recently uploaded (20)

Behind the Scenes From the Manager's Chair: Decoding the Secrets of Successfu...
Behind the Scenes From the Manager's Chair: Decoding the Secrets of Successfu...Behind the Scenes From the Manager's Chair: Decoding the Secrets of Successfu...
Behind the Scenes From the Manager's Chair: Decoding the Secrets of Successfu...
 
IOS-PENTESTING-BEGINNERS-PRACTICAL-GUIDE-.pptx
IOS-PENTESTING-BEGINNERS-PRACTICAL-GUIDE-.pptxIOS-PENTESTING-BEGINNERS-PRACTICAL-GUIDE-.pptx
IOS-PENTESTING-BEGINNERS-PRACTICAL-GUIDE-.pptx
 
Designing for Hardware Accessibility at Comcast
Designing for Hardware Accessibility at ComcastDesigning for Hardware Accessibility at Comcast
Designing for Hardware Accessibility at Comcast
 
10 Differences between Sales Cloud and CPQ, Blanka Doktorová
10 Differences between Sales Cloud and CPQ, Blanka Doktorová10 Differences between Sales Cloud and CPQ, Blanka Doktorová
10 Differences between Sales Cloud and CPQ, Blanka Doktorová
 
IESVE for Early Stage Design and Planning
IESVE for Early Stage Design and PlanningIESVE for Early Stage Design and Planning
IESVE for Early Stage Design and Planning
 
IoT Analytics Company Presentation May 2024
IoT Analytics Company Presentation May 2024IoT Analytics Company Presentation May 2024
IoT Analytics Company Presentation May 2024
 
Connector Corner: Automate dynamic content and events by pushing a button
Connector Corner: Automate dynamic content and events by pushing a buttonConnector Corner: Automate dynamic content and events by pushing a button
Connector Corner: Automate dynamic content and events by pushing a button
 
Agentic RAG What it is its types applications and implementation.pdf
Agentic RAG What it is its types applications and implementation.pdfAgentic RAG What it is its types applications and implementation.pdf
Agentic RAG What it is its types applications and implementation.pdf
 
Demystifying gRPC in .Net by John Staveley
Demystifying gRPC in .Net by John StaveleyDemystifying gRPC in .Net by John Staveley
Demystifying gRPC in .Net by John Staveley
 
Motion for AI: Creating Empathy in Technology
Motion for AI: Creating Empathy in TechnologyMotion for AI: Creating Empathy in Technology
Motion for AI: Creating Empathy in Technology
 
Powerful Start- the Key to Project Success, Barbara Laskowska
Powerful Start- the Key to Project Success, Barbara LaskowskaPowerful Start- the Key to Project Success, Barbara Laskowska
Powerful Start- the Key to Project Success, Barbara Laskowska
 
AI presentation and introduction - Retrieval Augmented Generation RAG 101
AI presentation and introduction - Retrieval Augmented Generation RAG 101AI presentation and introduction - Retrieval Augmented Generation RAG 101
AI presentation and introduction - Retrieval Augmented Generation RAG 101
 
Salesforce Adoption – Metrics, Methods, and Motivation, Antone Kom
Salesforce Adoption – Metrics, Methods, and Motivation, Antone KomSalesforce Adoption – Metrics, Methods, and Motivation, Antone Kom
Salesforce Adoption – Metrics, Methods, and Motivation, Antone Kom
 
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...
 
In-Depth Performance Testing Guide for IT Professionals
In-Depth Performance Testing Guide for IT ProfessionalsIn-Depth Performance Testing Guide for IT Professionals
In-Depth Performance Testing Guide for IT Professionals
 
Custom Approval Process: A New Perspective, Pavel Hrbacek & Anindya Halder
Custom Approval Process: A New Perspective, Pavel Hrbacek & Anindya HalderCustom Approval Process: A New Perspective, Pavel Hrbacek & Anindya Halder
Custom Approval Process: A New Perspective, Pavel Hrbacek & Anindya Halder
 
Optimizing NoSQL Performance Through Observability
Optimizing NoSQL Performance Through ObservabilityOptimizing NoSQL Performance Through Observability
Optimizing NoSQL Performance Through Observability
 
SOQL 201 for Admins & Developers: Slice & Dice Your Org’s Data With Aggregate...
SOQL 201 for Admins & Developers: Slice & Dice Your Org’s Data With Aggregate...SOQL 201 for Admins & Developers: Slice & Dice Your Org’s Data With Aggregate...
SOQL 201 for Admins & Developers: Slice & Dice Your Org’s Data With Aggregate...
 
AI revolution and Salesforce, Jiří Karpíšek
AI revolution and Salesforce, Jiří KarpíšekAI revolution and Salesforce, Jiří Karpíšek
AI revolution and Salesforce, Jiří Karpíšek
 
PLAI - Acceleration Program for Generative A.I. Startups
PLAI - Acceleration Program for Generative A.I. StartupsPLAI - Acceleration Program for Generative A.I. Startups
PLAI - Acceleration Program for Generative A.I. Startups
 

2013 Registrar Accreditation Agreement FAQs from ICANN 49

  • 3. Text #ICANN49 26 March 2014 • Caitlin Tubergen o Registrar Relations and Contracts Manager • Owen Smigelski o Senior Manager, Contractual Compliance
  • 4. Text #ICANN49 Agenda • 2013 RAA Statistics • How to Request 2013 RAA and Process Time • New Website Posting Requirements • Whois Accuracy + RDDS Specification • Dealings with Resellers • Transfer of Accreditation to Wholly-owned Subsidiaries • Compliance
  • 5. Text #ICANN49  2013 RAA Statistics  Adopting the 2013 RAA
  • 6. Text #ICANN49 2013 RAA Statistics * As of 21 March 2014 Total Registrar Count – 1008 335 (33.17%) 675 (66.83%) Domains Under Management 125,299,774 (82.88%) 25,878,274 (17.12%) 2013 RAA 2009 RAA
  • 7. Text #ICANN49 7 Adopting the 2013 RAA • To request the 2013 RAA, fill out the early adoption form on ICANN website • Process: o Submit Form o ICANN acknowledges receipt o ICANN runs preliminary compliance check o If approved, ICANN sends Registrar Information Specification and 2013 RAA to the Registrar via DocuSign
  • 9. Text #ICANN49 Website Requirements • Provide links to the following: o 3.7.10 Registrants’ Benefits and Responsibilities Specification o https://www.icann.org/en/resources/registrars/registrant-rights/benefits o 3.16 Link to Registrant Educational Information o https://www.icann.org/en/resources/registrars/registrant-rights/educational
  • 10. Text #ICANN49 Website Requirements (cont.) • 3.17 Registrar Information Specification o Defines items that a Registrar must publish on its website:  Item 7. Correspondence Address for the Registrar  Must be able to accept notice of legal process  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. Full name, contact information and position of all officers of the Registrar  Item 22. The ultimate parent entity of Registrar (if applicable) i
  • 11. Text #ICANN49 Website Requirements (cont.) • 3.18.1 Abuse Contact o Publish an email address to receive such reports on the homepage of Registrar’s website • 3.18.3 Tracking Abuse o Supply a description of registrar’s procedures for the receipt, handling and tracking of abuse reports
  • 12. Text #ICANN49  Whois Accuracy  RDDS (Whois) Specification
  • 13. Text #ICANN49 13 Whois Accuracy Specification • Required as of 1 January 2014 • Requires validation and verification of registrant and account holder data • Deletion or suspension of registrations now explicitly required in cases of: o Willful provision of inaccurate / unreliable data (RAA 3.7.7.2) o Willful failure to update data promptly (RAA 3.7.7.2) o Failure to respond to registrar data accuracy inquiry within 15 days (Section 4 of Whois Accuracy Spec)
  • 14. Text #ICANN49 Whois Validation • Registrant and account holder “validation” required within 15 days of: o Registration o Transfer o Registrant or account holder data change  Required fields must be filled (RAA 3.3.1)  Email addresses format specified (RFC 5322)  Telephone numbers format specified (ITU-T E.164)  Postal addresses format specified (UPU S42)  Cross-field validation (not required until mutual agreement between ICANN and WG) (Transition Addendum)
  • 15. Text #ICANN49 Whois Verification • Registrant & account holder “verification” required: o Within 15 days of registration, transfer, or registrant or account holder data change, email address or telephone number verification is required (1(f) of Whois Accuracy Spec) o Within 15 days of bounce or other evidence of inaccuracy – email verification required (4 of Whois Accuracy Spec) • Verification process requires affirmative response o Non-response by registrant requires either manual verification by registrar or suspension o Non-response by account holder requires registrar to perform manual verification only
  • 16. Text #ICANN49 Whois Accuracy Specification Exceptions • Verification / validation not required if: o Previously performed by registrar on identical data o Registrar has no reason to believe the data has become inaccurate or invalid  Example: Whois inaccuracy complaint or email bounce back
  • 18. Text #ICANN49 Example 1: Updated Postal Address • Registered Name Holder updates its postal address • Registrar must:  Validate that the postal address is the proper format (Section 1(d) of Whois Accuracy Spec) • Registrar is not required to:  Re-verify the email address or the telephone number (Section 1(f))
  • 19. Text #ICANN49 Example 2: Updated Email Address • Registered Name Holder updates its email address • Registrar must: o Validate that the email address is the proper format (Section 1(d) of Whois Accuracy Spec) o Verify the email address if registrar previously verified the email address pursuant to 1(f)(i). If registrar verified this registered name holder through a telephone number 1(f)(ii), registrar does not have to verify the email address. (unless reason to believe it is inaccurate)
  • 20. Text #ICANN49 Example 3: Updated Telephone Number • Registered Name Holder updates its telephone number • Registrar must: o Validate that the telephone number is the proper format (Section 1(c) of Whois Accuracy Spec) o Verify the telephone number if registrar verified tel. numbers pursuant to 1(f)(ii). If registrar verified this registered name holder through an email address 1(f)(i), registrar does not have to verify the telephone number.
  • 21. Text #ICANN49  New Requirements: RDDS (“Whois”) Specification
  • 22. Text #ICANN49 New Whois Requirements • Requirements in RDDS Specification • Additional Whois fields required • Uniform Whois query and output formats • EPP status values required exclusively • SLA for Whois service (Section 2.2 of RDDS Spec) • IPv6 accessibility required • Port 43 Whois only required for “thin” registries (RAA 3.3.1)
  • 23. Text #ICANN49 New Whois Fields • As of 1 January 2014 • Registry Domain ID • Registrar Abuse Contact Email • Registrar Abuse Contact Phone • Domain Status • Registry Registrant ID • Registrant Phone • Registrant Phone Ext • Registrant Fax • Registrant Fax Ext • Registrant Email • Registry Admin ID • Registry Tech ID • DNSSEC • Last update of WHOIS database i
  • 24. Text #ICANN49 Output Field Details • Registry Domain ID o Does not change for length of registration • Registrar Abuse Contact Email and Phone o Registrar discretion, separate from LEA contact in RAA 3.18.2 • Domain Status – EPP status codes • IDs: Registry Registrant, Registry Admin, Registry Tech o May be left blank if not available from registry • DNSSEC: o Two options:  DNSSEC: signedDelegation  DNSSEC: unsigned i
  • 25. Text #ICANN49  Relationship with Resellers  Compliance Certificate  Transfer of Accreditation to Wholly-owned Subsidiary
  • 26. Text #ICANN49 How Registrars Can “Ensure” • Examples: o Include all of reseller obligations in the agreement between your registrar and its resellers and attach consequences for contract non-compliance o Implement monitoring processes whereby your registrar periodically looks at its resellers' websites to ensure compliance with certain RAA obligations (such as website posting requirements) o 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
  • 27. Text #ICANN49 Compliance Certificate • Section 3.15 of RAA o Registrar shall complete and deliver to ICANN within twenty (20) days following the end of each calendar year, a certificate executed by the president, chief executive officer, chief financial officer or chief operating officer (or their equivalents) of Registrar certifying compliance with the terms and conditions of this Agreement. • Form is Compliance Certificate (Table of Contents – 11)
  • 28. Text #ICANN49 Transfer of Accreditation to Wholly-owned Subsidiary • Section 7.3.1 of RAA • Required documentation: o Documentation proving that the transferee entity is, in fact, a wholly-owned subsidiary of the ICANN-accredited registrar. o A letter, on company letterhead, from the ICANN-accredited registrar (the transferor) acknowledging that it would like to transfer its accreditation to the transferee o A letter, on company letterhead, from the transferee, acknowledging that it assumes and will be responsible for all the existing obligations and liabilities of the Transferer o Primary Contact Update (if applicable)
  • 30. Text #ICANN49 WHOIS Inaccuracy Verification & Validation Summary o Registrar must verify or re-verify email address of the Registered Name Holder (“RNH”) and if different, the Account Holder (“AH”). o The domain must be suspended or the registrar must provide proof of manual verification. o 1st notice response deadline will remain 15 business days. o Beginning with the second notice, ICANN will inquire why registrars did not suspend or delete registrations. o 2 concurrent parallel tracks (next 2 slides)
  • 31. Text #ICANN49 Whois Inaccuracy • Section 3.7.8 RAA & Section 5 of WHOIS Accuracy Specification o Registrar sends inquiry to RNH- starts 15-calendar day timeline. o ICANN looking for three results  1. WHOIS updated (within 15 days of inquiry sent to RNH)  Registrar provides validation (and verified updates, including affirmative responses if previously verified email or phone was updated).  2. No Response from RNH within 15 calendar days- Domain suspended/terminated until Registrar has validated information  3. Registrar verified WHOIS information correct (within 15 days of inquiry sent to RNH) and Registrar has provided documentation of verification
  • 32. Text #ICANN49 Whois Inaccuracy Requirements • Section 4 of WHOIS Accuracy Specification o Receipt of Notice starts 15-calendar day timeline. o Registrar must verify or re-verify email address of the Registered Name Holder (“RNH”) and if different, the Account Holder (“AH”). o Registrar must demonstrate an affirmative response from the RNH to verify. o If Registrar does not receive affirmative response from the RNH within 15 days, the domain must be suspended or the registrar must provide proof of manual verification. o If Registrar does not receive affirmative response from AH, must provide proof of manual verification. Suspension not required.
  • 33. Text #ICANN49 Registrar must verify email & investigate complaint WHOIS Inaccuracy Complaint 1- WHOIS updated & validated - OR - 2-Suspend if no response - OR - 3- Verified correct & validated (RAA Section 3.7.8 & 2013 Whois Accuracy Program Spec. 5) Affirmative response to email verification (2013 Whois Accuracy Program Spec. 4) Whois Inaccuracy Example 2013 RAA
  • 34. Text #ICANN49 Abuse Reports Requirements • Section 3.18 of the 2013 RAA o Registrars must take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse o Law enforcement reports: can be from any applicable jurisdiction o Registrars must include abuse email & phone number in Whois output o Abuse email address must be conspicuously on website, and cannot be a web form o Registrars cannot require a court order to investigate reports of abuse, unless they inform ICANN of a specific local law or regulation
  • 35. Text #ICANN49  Question & Answer Session  You can submit further questions to RAAquestions@icann.org

Editor's Notes

  1. When filling out form, if you want to update primary contact information form, please do so. Initial Compliance Review – 7 -14 days from submission
  2. Educational materials must appear on any page that customers can register domain names.