Top 10 Questions About the Next-Generation Registration Directory Service (RDS)

Transcription

1 Tp 10 Questins Abut the Next-Generatin Registratin Directry Service (RDS) Expert Wrking Grup n gtld Directry Services (EWG) September, 2014

2 Webinar Agenda Intrductin Tp 10 Questins abut the RDS prpsed by the EWG s Final Reprt Resurces and Next Steps Q&A Dwnlad These Slides: annuncement en Page 2

3 Abut the EWG Frmed t break decade-lng impasse Members brught diverse expertise and experiences t bear n this cmplex prblem Discussed issues frankly, participated individually, and sught cmprmises Wrking tgether t find an answer t the ICANN Bard s questin Is there an alternative t tday s WHOIS t better serve the glbal Internet cmmunity? Page 3

4 EWG s Final Reprt Details a prpsed next-generatin Registratin Directry Service (RDS) Strikes a balance between Accuracy Access Privacy Accuntability Cllects, validates and disclses gtld data fr permissible purpses nly Safeguarded thrugh a new paradigm f purpse-driven gated access Dwnlad Reprt: viewpage.actin?pageid= Page 4

5 Tp 10 Questins Abut the RDS Based n FAQs: display/wg/ewg+faqs Page 5

6 1) What makes the RDS different? WHOIS prvides ne-size-fits-all public access t annymus users Little accuntability r abuse remedies Limited individual privacy prtectin r ability t cnfrm t differing laws Limited ability t ensure data integrity Lack f security and auditing capabilities Cumbersme cntact management Inefficient cmmunicatin The prpsed RDS was designed t address these WHOIS shrtcmings Page 6

7 2) Did the EWG chse a centralized mdel fr the RDS? The EWG evaluated several pssible mdels against defined criteria POSSIBLE MODELS Cllectin Strage Cpy Access Current WHOIS RR RR/Ry n/a RR/Ry Federated RR & V RR/Ry & V n/a RDS Synchrnized * RR & V RR/Ry & V RDS RDS Reginal RR & V RR/Ry & V Reginal RDS Opt-Out RR & V RR/Ry & V Optinal RDS Bypass RR & V RR & V RDS RDS After rigrus analysis f factrs including cst the EWG chse the Synchrnized RDS (SRDS) * Frmerly knwn as the Aggregated RDS (ARDS) Page 7

8 3) Des the RDS eliminate free public access t data? Sme registratin data wuld remain public t prmte Internet stability and meet basic DNS needs This minimum public data wuld still be accessible by anyne, fr any permissible purpse, withut authenticatin Any Requestr RDS Query (Unauthenticated, DN) RDS Respnse (Public Data Only) prtal RDS Returns nly public data available t anyne, fr any purpse. Registries Registries Registries Registries Registries Validatrs Page 8

9 4) What wuld I need t d t access gated RDS data? In the RDS, data is cllected and disclsed fr permissible purpses Requestrs and their data needs vary; s wuld gated access plicies Prir t 1 st GATED query: Requestr must be accredited and btain a Requestr ID Authenticated Requestr RDS Query (Requestr ID,Purpse,DN) RDS Respnse (Public + Gated Data) methds RDS Returns nly requested data available and accessible t authenticated requestr fr declared purpse. Registries Registries Registries Registries Registries Validatrs Page 9

10 5) What new data will the RDS cllect? WHOIS Existing Dmain Name Data Supplied by Registrar and Registry Existing Registrant Cntact Data Cllected frm Registrant Existing Admin, Tech Cntact Data Cllected frm Registrant Tday s WHOIS Entirely Public Data Entirely Annymus Access Registrants Cannt Prvide Cntemprary/Alternate Data Cntacts Cannt Prevent Inaccurate r Fraudulent Use RDS Existing Dmain Name Data Registrant ID Existing Registrant Cntact Data New Optinal Data Elements PBC IDs Admin, Tech Cntact Data Abuse, Legal, Prxy & Business Cntact Data Cllected frm each Cntact Purpse-Driven RDS Minimum Public Data Mst Data Gated By Default! Cntact Data is Validated IDs link Cntact Data t Registered Dmain Names Purpse-Based Cntacts (PBCs) Manage Own Data Page 10

11 6) What are Cntacts and Cntact IDs? Cntacts are reusable blcks f cntact data, linked t dmains by Cntact IDs Cntact IDs (numbers) are public Cntact Data (names, addresses) is largely gated Imprves accuntability and reachability while giving everyne mre cntrl ver persnal data Registrant Cntact Required fr all DNs tday Every Dmain Name has 1 Registrant Cntact ID 4 Mandatry PBC ID 2 Optinal PBC IDs Admin Cntact Required fr all DNs tday Technical Cntact Required fr all DNs tday Abuse Cntact Required fr all new DNs Legal Cntact Required fr all new DNs Privacy/Prxy Prvider Cntact Required fr PP registratins Business Cntact Recmmended fr businesses Page 11

12 7) Hw wuld the RDS imprve data quality, privacy, and security? Gives Registrants and Cntact Hlders greater cntrl ver their persnal data Applies standard validatin t all data and ptin t further deter identity theft Uses Gated Access t deliver purpse-based access with greater accuntability & security Uses rules engine t enfrce RDS plicy, harmnized with data prtectin & privacy laws Supprts accredited privacy/prxy services and secure prtected credentials fr at-risk users Page 12

13 8) Hw des the RDS make life simpler fr individual registrants? In the RDS, Registrants will have Mre visibility int what their data is used fr Ability t enter and update their data mre easily Mre flexibility and cntrl ver what data is public Optins t deter fraudulent use f their data One place t see what RDS users can learn abut them And greater assurance that Privacy, data prtectin, security, and auditing plicies will be unifrmly applied Access t data will be limited t thse with a need t knw Requestrs wh access data will be held accuntable Page 13

14 9) Hw wuld the RDS impact registrar and registry csts? RDS shuld perate n a cst-recvery basis gtld Registrars n lnger bligated t cllect r validate WHOIS cntact data Cllect pre-validated Cntact IDs frm registrants Cntact validatin, cmpliance, and data prtectin burdens shift t Validatrs Registrar s bligatins fcus n DNS-related data gtld Registries n lnger bligated t receive r disclse WHOIS cntact data Cntact data strage and prcessing shift t Validatrs Prt 43 WHOIS bligatins shift t the Synchrnized RDS Registries use EPP t supply updates t the SRDS Page 14

15 10) Hw wuld the RDS address WhWas and Reverse WHOIS needs? The Registratin Directry Service (RDS) will handle Ordinary RDS Queries abut every gtld dmain name Reverse Queries that search public and gated data elements acrss all gtld dmains WhWas Queries that return histrical snapshts f bth public and gated data Enfrcing requestr accreditatin, authenticatin, authrizatin, and terms and cnditins f RDS data use The entire RDS data set cannt be exprted in bulk Third party service prviders that use WHOIS bulk data tday will be able t use this new RDS framewrk t Query, prcess and deliver RDS data in innvative ways Supplied nly t accredited requestrs with permissible purpses Subject t terms and cnditins f RDS data use Page 15

16 T learn mre abut the prpsed RDS Dwnlad Our Reprt: viewpage.actin?pageid= Read Our FAQs: display/wg/ewg+faqs Watch Our Vides: EWG+Multimedia+Frequently+Asked+Questins Page 16

17 Next Steps ICANN Bard is nw cnsidering hw t use EWG s Final Reprt as a fundatin fr Bard-requested GNSO Plicy Develpment Prcess (PDP) At ICANN 51, Cmmunity Sessin n all things WHOIS will explre hw t best structure PDP(s) fr success All interested parties are invited t Cntribute ideas abut PDP structure in LA Prvide feedback n RDS as part f PDP(s) Page 17

18 Questins? Page 18