Skip to main content

Call for RSVPs | Privacy & Proxy Services Accreditation Issues Working Group Webinar | 28 May 2015 at 14:00 UTC

Please RSVP to nathalie.peregrine@icann.org. Remote participation details will be sent the week of 25 May 2015.

Please join the interim co-chairs of the Privacy & Proxy Services Accreditation Issues Working Group for a one-hour webinar on Thursday 28 May 2015 at 1400 UTC, to hear about the preliminary recommendations that have now been published for public comment by the Working Group.

This Working Group (WG) was chartered [PDF, 463 KB] by the GNSO Council in October 2013 to conduct a Policy Development Process (PDP) with the aim of developing policy recommendations to guide ICANN's implementation of an Accreditation Program for privacy and proxy service providers. The topic of privacy and proxy registrations had been identified upon the conclusion of ICANN's negotiations with the Registrars Stakeholder Group for a new Registrar Accreditation Agreement (RAA) as an issue that remained unresolved and that would be suited for a PDP. The 2013 RAA contains an interim Specification on Privacy & Proxy Registrations that is due to expire on 1 January 2017.

The WG's Initial Report, containing a number of detailed preliminary recommendations and several open questions for which it is seeking community input, was published for public comment on 5 May 2015. The announcement, forum for submitting comments, and a copy of the WG's Initial Report can be found here: https://www.icann.org/public-comments/ppsai-initial-2015-05-05-en. The WG's preliminary recommendations include: (i) requiring that accredited providers expressly include certain mandatory provisions in their customer terms of service; (ii) an obligation to relay initial electronic requests seeking to contact a customer; (iii) an illustrative framework for the handling of requests from trademark and copyright owners for the disclosure of customer contact information; and (iv) steps regarding provider de-accreditation. Open questions on which the WG has yet to reach consensus include the escalation of relay requests, how to deal with disclosure requests received from law enforcement and other third parties other than intellectual property rights-holders, and whether domain names associated with online financial transactions should be able to use privacy or proxy registrations.

This webinar will highlight the WG's preliminary recommendations and open questions, including an opportunity to ask questions of the interim co-chairs. All are welcome; please reply to nathalie.peregrine@icann.org if you wish to attend and to receive details about logging on to the webinar.


More Announcements
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."