SLIDE 1
| 1
| 2
| 1 Agenda GDD Summit 2019 CZDS 2.0 Update Data Escrow Data - - PowerPoint PPT Presentation
| 1 Agenda GDD Summit 2019 CZDS 2.0 Update Data Escrow Data - - PowerPoint PPT Presentation
| 1 Agenda GDD Summit 2019 CZDS 2.0 Update Data Escrow Data Processing Agreements RDAP Update IDN Implementation Guidelines 4.0 PICDRP Improvements RSEP Improvements Compliance Audits RySG Priorities / What can we work on
SLIDE 2
SLIDE 3
| 3
2019 GDD Summit – Bangkok Thailand
¤ https://www.icann.org/gddsummit ¤ Fun Filled week: GDD Summit + ROW +DNS Symposium + DNS OARC ¤ We need your help, join the planning committee!
SLIDE 4
| 4
CZDS 2.0 Coming January 2019
¤ New platform will enable future enhancements ¤ Refreshed user experience for community users ¤ Migrating Registry functionality into NSp ¡ Not migrating registry CZDS users ¡ RPC’s will be given initial access within NSP ¡ Option to delegate or add additional CZDS only users ¤ Existing access to zone files will be migrated ¤ More info and training materials will be published before year end
SLIDE 5
| 5
Update: Data Escrow Data Processing Agreement
¤ Per the Temp Spec – Registries & Registrars were expected to ensure
their data escrow agreements included data processing requirements consistent with GDPR
¤ Similar to RRAs we had agreed to work together (ICANN +CPH) to
develop a consistent approach – progress has been slow
¤ There are differing views on controller / processor relationship for each
- f the parties (CP, ICANN, DEA) and what agreements are needed
¤ Suggested Approach ¡ ICANN work with Data Escrow Agents to develop approved
template data processing agreement that can be added as addendums to the existing data escrow agreements when a RO or RR believes it is necessary
SLIDE 6
| 6
RDAP Implementation Status
¤ The Temporary Specification for gTLD Registration Data calls for
gTLD registries and registrars to implement RDAP following a common profile, SLA, and registry reporting requirements
¤ A proposal for a gTLD RDAP Profile ended its public comment
period on 13 October 2018
¤ ICANN org and the contracted parties continue to negotiate an
RDAP SLA and registry reporting requirements
SLIDE 7
| 7
13 Oct 2018 Oct 2018 Nov-Dec 2018 Dec 2018
Draft gTLD RDAP profile ended Public Comment Publish draft gTLD RDAP SLA, and registry reporting requirements for Public Comment Publish Final gTLD RDAP profile
1H 2019
RDAP service becomes generally available Publish Final gTLD RDAP SLA, and registry reporting requirements
135-day Implementation Public Comment Period
Expected RDAP Implementation Timeline
SLIDE 8
| 8
IDN Implementation Guidelines
Background
¡ For second-level
IDN registration policies and practices
¡ To minimize the risk
- f cybersquatting
and consumer confusion
¤ gTLD – registries and registrars offering IDNs
contractually bound
¡
Required by most Registry Agreements
- For example, new gTLD Registry
Agreement: Specification 6 Section 1.4
¡
Required by many Registrar Agreements
- For example, 2013 Registrar
Accreditation Agreement: Additional Registrar Operation Specification Clause 3
¤ IDN ccTLDs – “expected” by the Fast Track
Process and the proposed IDN ccTLD Policy
SLIDE 9
| 9
History and Status of Update
Jul 2015 Oct 2015
Working Group formed Initial issues list presented Call for Community Experts Interim draft presented First draft for Public Comment presented Final draft for Second Public Comment presented Final Proposed
- Ver. 4.0
published
May 2018
Final Draft Presented to ICANN Board + Second Public Comment response presented
¤ Last updated in 2011
SLIDE 10
| 10
Topics Covered and Next Steps
¤ https://www.icann.org/news/announcement-2018-05-10-en ¤ Total of 7 topics and 19 guidelines with additional notes:
Transition (4) Format of IDN Tables (2) Consistency of IDN Tables and Practices (4) IDN Variant Labels (3) Similarity and Confusability
- f Labels
(4) Publishing IDN Registration Policy and Rules (1) Terminology (1) Additional Notes I - VII
¤ ICANN org currently analysing the requirements posed by IDN
Guidelines 4.0
¤ Targeting for ICANN Board consideration in Jan. 2019; Implementation
Required as early as August 2019
¤ Contracted Parties should be reviewing and preparing now
SLIDE 11
| 11