Skip to main content
Resources

ICANN's Technical Study Group on Access to Non-Public Registration Data

This group will explore technical solutions for authenticating, authorizing, and providing access to non-public registration data for third parties with legitimate interests. The work is focused on examining technical implementation solutions built on the Registration Data Access Protocol (RDAP). In parallel with community efforts to develop an RDAP profile prior to deployment of the protocol, this Technical Study Group will focus its efforts on developing technical solutions for providing access to non-public data.

Click here to return to ICANN's Data Protection/Privacy Issues webpage.

About the Group

Supporting Documents

Announcements/Blogs

5 April 2019 Blog: Next Steps for the Technical Study Group & EPDP
27 March 2019 Blog: Technical Study Group Engages with Community in Kobe
7 March 2019 Blog: Technical Study Group publishes draft model for review and input
21 February 2019 Blog: Technical Study Group Advances Draft Model
4 February 2019 Blog: Technical Study Group Makes Progress at First Face-to-Face Meeting
21 December 2018 Blog: Technical Study Group Publishes Charter
14 December 2018 Announcement: Technical Study Group on Access to Non-Public Registration Data Begins Work
8 November 2018 Blog: Data protection/privacy issues: ICANN63 wrap-up and next steps

Meetings/Work Sessions

15 – 16 April 2019

TSG on Access to Non-Public Registration Data – Face-to-Face Meeting #4 – Washington D.C.

 

9 April 2019

TSG on Access to Non-Public Registration Data – Meeting #14

4 April 2019

TSG on Access to Non-Public Registration Data – Meeting #13

2 April 2019

TSG on Access to Non-Public Registration Data – Meeting #12

13 March 2019

TSG on Access to Non-Public Registration Data – Face-to-Face Meeting #3 – Kobe, Japan (ICANN64)

12 March 2019

ICANN64 – Community Outreach with the Non Commercial Stakeholder Group (NCSG)

12 March 2019

ICANN64 – Community Outreach with the Governmental Advisory Committee (GAC) Public Safety Working Group (PSWG)

12 March 2019

ICANN64 – Community Outreach with the Registrar Stakeholder Group (RrSG)

11 March 2019

ICANN64 – Community Engagement Session: TSG on Access to Non-Public Registration Data

10 March 2019

ICANN64 - Community Outreach with the Expedited Policy Development Process (EPDP) Team on the Temporary Specification for gTLD Registration Data

5 March 2019

TSG on Access to Non-Public Registration Data – Meeting #11

27 February 2019

TSG on Access to Non-Public Registration Data – Meeting #10

26 February 2019

TSG on Access to Non-Public Registration Data – Meeting #9

21 February 2019

TSG on Access to Non-Public Registration Data – Meeting #8

19 February 2019

TSG on Access to Non-Public Registration Data – Meeting #7

11-13 February 2019

TSG on Access to Non-Public Registration Data – Face-to-Face Meeting #2 – Washington D.C.

 

5 February 2019

TSG on Access to Non-Public Registration Data – Meeting #6

29 January 2019

TSG on Access to Non-Public Registration Data – Meeting #5

22 January 2019

TSG on Access to Non-Public Registration Data – Meeting #4

14 & 15 January 2019

TSG on Access to Non-Public Registration Data – Face-to-Face Meeting #1 – Washington D.C. – Day 2

 

8 January 2019

TSG on Access to Non-Public Registration Data – Meeting #3

18 December 2018

TSG on Access to Non-Public Registration Data – Meeting #2

11 December 2018

TSG on Access to Non-Public Registration Data – Meeting #1

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."