ISSUE CHART FOR THE GNSO RAA REMAINING ISSUES PDP ON PRIVACY/PROXY SERVICES

Similar documents
Topic LE /GAC position Registrar Position Agreement in Principle 1. Privacy and Proxy services

Whois Study Table Updated 18 February 2009

Progress Report Negotiations on the Registrar Accreditation Agreement Status as of 1 March 2012

Law Enforcement Recommended RAA Amendments and ICANN Due Diligence Detailed Version

Privacy and Proxy Service Provider Accreditation. ICANN58 Working Meeting 11 March 2017

Final Report on the Privacy & Proxy Services Accreditation Issues Policy Development Process

Summary of Public Suggestions on Further Studies of WHOIS including the GAC recommendations of 16 April Updated 10 May 2008

PURPOSE STATEMENT FOR THE COLLECTION AND PROCESSING OF WHOIS DATA

Final Outcomes Report of the WHOIS Working Group 2007

.LATROBE TLD REGISTRATION POLICY

ICANN GDPR Proposed Models Redaction Proposal EXECUTIVE SUMMARY:

The registration of Domain Names will be centralized and managed through all DOT accredited Registrars selected by the Registry.

ICANN Contractual Compliance. ALAC Mee(ng. Sunday, 23 March 2014 #ICANN49

TERMS AND CONDITIONIONS FOR WHOIS DATA COLLECTION AND DISPLAY

Summary of Expert Working Group on gtld Directory Services June 2014 Final Report

INTELLECTUAL PROPERTY CONSTITUENCY COMMENTS ON PROPOSED INTERIM MODELS FOR ICANN COMPLIANCE WITH EU GENERAL DATA PROTECTION REGULATION

GDPR. The new landscape for enforcing and acquiring domains. You ve built your business and your brand. Now how do you secure and protect it?

Registration Abuse Policies Final Report. Greg Aaron, RAPWG Chair Sunday, 20 June 2010

Privacy and WHOIS Data Policy

Post-Expiration Domain Name Recovery PDP Initial Report Update to the GNSO Council. Saturday, 19 June 2010

ICANN Contractual Compliance. IPC Mee(ng. Tuesday, 25 March 2014 #ICANN49

Advisory Concerning Inter-Registrar Transfer Policy. 23 August 2007

Proposed Final Report on the Post-Expiration Domain Name Recovery Policy Development Process Executive Summary

Contractual Compliance Semi Annual Report February 2009

GNSO Council Report to the ICANN Board Locking of a Domain Name subject to UDRP Proceedings PDP

USER CORPORATE RULES. These User Corporate Rules are available to Users at any time via a link accessible in the applicable Service Privacy Policy.

You may contact The Translation Network by at You may also call The Translation Network at

Update on Whois Studies

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

WHOIS Accuracy Study Findings, Public Comments, and Discussion

Proposal for a model to address the General Data Protection Regulation (GDPR)

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

Post-Expiration Domain Name Recovery PDP. Presentation of Final Report

Registry Internet Safety Group (RISG)

Final Report from the Expert Working Group on gtld Directory Services: A Next-Generation Registration Directory Service (RDS)

Improving WHOIS- An Update. 20 November, 2013

Expert Working Group on gtld Directory Services (EWG) Frequently Asked Questions (FAQs) 2014 Final Report Update

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

Post- Expira,on Domain Name Recovery PDP WG. ICANN San Francisco March 2011

This descriptive document is intended as the basis for creation of a functional specification for 2

Registration Policy for. 大众汽车

Report on Registrar Whois Data Reminder Policy Survey

Contractual Compliance. Text. IPC Meeting. Tuesday, 24 June 2014 #ICANN50

2011 Whois Data Reminder Policy Audit Report

Fast Flux Hosting Final Report. GNSO Council Meeting 13 August 2009

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

DRAFT: gtld Registration Dataflow Matrix and Information

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

Registrar Stakeholder Mee2ng Tuesday, 25 March 2014

Internet Corporation for Assigned Names & Numbers Contractual Compliance Update

Contractual Compliance Update ICANN 52 February 2015

General Update Contractual Compliance Initiatives and Improvements Audit Program Update Complaints Handling and Enforcement Summary

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

GAC PRINCIPLES REGARDING gtld WHOIS SERVICES. Presented by the Governmental Advisory Committee March 28, 2007

1. Anti-Piracy Services. 2. Brand Protection (SAAS) 3. Brand Protection Services. Data Protection and Permitted Purpose. Services

ICANN Contractual Compliance Proforma DNS Infrastructure Abuse November 2018 Registry Audit Request For Information (RFI)*

The Internet Big Bang: Implications for Financial Services Brand Owners

Draft Thick RDDS (Whois) Consensus Policy and Implementation Notes

ACCEPTABLE USE POLICY

Attachment 3..Brand TLD Designation Application

Matters Related to WHOIS

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

Act CXII of 2011 on the right to information self-determination and freedom of information. Act ;

Summary. January 31, Jo Lim. Chief Operations and Policy Officer. Dear Jo,

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

General Update Contractual Compliance Initiatives and Improvements Audit Program Update Complaints Handling and Enforcement Summary

Contractual ICANN. An Overview for Newcomers 11 March 2012

Intellectual Property Constituency (IPC)

Registrar Session ICANN Contractual Compliance

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

Attachment 3..Brand TLD Designation Application

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

Proposed Interim Model for GDPR Compliance-- Summary Description

WHOIS Access and the EU General Data Protection Regulation. Part 2

Initial Report on the Locking of a Domain Name Subject to UDRP Proceedings Policy Development Process

Summary of feedback on the proposed changes to.uk policy arising from GDPR

Final Report on the Locking of a Domain Name Subject to. UDRP Proceedings. Policy Development Process

Initial Report from the Expert Working Group on gtld Directory Services: A Next Generation Registration Directory Service

WHOIS Proxy/Privacy Abuse

Review of Law Applicable to the Transition of Data from a Thin to Thick. In March 2014, the ICANN Board adopted GNSO consensus policy

OnlineNIC PRIVACY Policy

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

en.pdf

Orion Registrar, Inc. Certification Regulations Revision J Effective Date January 23, 2018

THE CAN-SPAM ACT OF 2003: FREQUENTLY ASKED QUESTIONS EFFECTIVE JANUARY 1, December 29, 2003

Contractual Compliance Semi-Annual Report July Table of Contents

With this vital goal in mind, MarkMonitor believes that the optimal WHOIS model should have, at minimum, these five important characteristics:

EVALUATION OF INTERNET CORPORATION OF ASSIGNED NAMES AND NUMBERS (ICANN) COMPLIANCE PROCESSES. Garth Bruen

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

GNSO-APPROVED WHOIS STUDIES COMPILATION OF EXECUTIVE SUMMARIES (IN ORDER OF COMPLETION) I. WHOIS PRIVACY & PROXY RELAY & REVEAL FEASIBILITY SURVEY

Office Properties Income Trust Privacy Notice Last Updated: February 1, 2019

SCHOOL SUPPLIERS. What schools should be asking!

DATA PUBLICATION AND ACCESS POLICY ON AF NIC REGISTRATIONS

BKK CENTRE FOR BUDAPEST TRANSPORT PRIVATE LIMITED COMPANY. PRIVACY POLICY on the BKK Online Shop sales

Acceptable Use Policy

Temporary Specification for gtld Registration Data

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

Transcription:

ISSUE CHART FOR THE GNSO RAA REMAINING ISSUES PDP ON PRIVACY/PROXY SERVICES Issue Explanation/Prior Recommendation 1 Practices & Procedures 1.1 Standard Service Practices These should be clearly published, and pro-actively advised to potential users of these services so they can make informed choices based on their individual circumstances Source 1 Policy Question to Be Explored What are the types of Standard Service Practices that should be adopted and published by 1.2 Standardized Relay and Reveal Procedures 1.3 Revealing identity for service of cease & desist letters in a timely manner 1.4 Obligation to forward correspondence Adopting agreed standardized relay and reveal processes and timeframes Need to enable service of process in a timely manner in order to avoid flight risk (transfer to another provider to evade service) Requirement to forward allegations of malicious conduct, cybersquatting, and other illegal activities to privacy or proxy service customers GNSO-ALAC RAA DT What are the baseline minimum standardized relay and reveal processes that should be adopted by ICANNaccredited privacy/proxy service Should to reveal customer identities for this specific purpose? Should to forward on to the customer all allegations they receive of illegal activities relating to specific domain names of the customer? 1 Excerpts from the source materials and relevant documents are included in Annex 1.

1.5 Revealing in instances of illegal malicious conduct 1.6 Publication in WHOIS in instances of illegal conduct In instances of presentation of evidence of illegal malicious conduct should result in a requirement to reveal the contact information of customers of privacy or proxy services, consistent with procedures designed to respect any applicable protections for privacy and freedom of expression Registrants using privacy/proxy registration services will have the contact information of the customer immediately published by the Registrar when registrant is found to be violating terms of service, including but not limited to the use of false data, fraudulent use, spamming and/or criminal activity GNSO-ALAC RAA DT LEA Request What forms of malicious conduct and what evidentiary standard would be sufficient to trigger such disclosure? What safeguards must be put in place to ensure adequate protections for privacy and freedom of expression? What specific violations would be sufficient to trigger such publication? What safeguards or remedies should there be for cases where publication is found to have been unwarranted? Relationship with Customer 2.1 Due Diligence Conducting periodic due diligence checks on customer contact information (such as validation or verification of the same fields that are subject to validation or verification in WHOIS) 2.2 Terminating a Customer's access Cancel registrations of proxy services that do not fulfill their contractual obligations to conduct periodic checks to ensure accuracy of customer contact information; and if so, how? What are the contractual obligations that, if unfulfilled, would justify termination of customer access by

2.3 Rights of Customers Providing clear and unambiguous guidance on the rights and responsibilities of registered name holders, and how those should be managed in the privacy/proxy environment 3 Disclosure 3.1 WHOIS Labels Clearly labeling WHOIS entries to indicate that registrations have been made by a privacy or proxy service 3.2 WHOIS Provider Contacts Providing full WHOIS contact details for the provider, which are contactable and responsive What rights and responsibilities should customers of s have? What obligations should providers have in managing these rights and responsibilities? Clarify how transfers, renewals, and PEDNR policies should apply. to label WHOIS entries to clearly show when a registration is made through a? Should full WHOIS contact details for providers be required? What measures should be taken to ensure contactability and responsiveness of the 4 Abuse Point of Contact 4.1 Maintain Abuse Point of Contact Maintaining dedicated abuse points of contact for each provider to maintain dedicated points of contact for reporting abuse? If

4.2 Publication of Abuse Point of Contact Designation and publication of technically competent point of contact on malicious conduct issues, available on 24/7 basis GNSO-ALAC RAA DT so, should the terms be consistent with the requirements applicable to registrars under Section 3.18 of the RAA? What are the forms of malicious conduct that would be covered by a designated published point of contact at an provider? 5 Law Enforcement 5.1 Access for Law Enforcement The ability to hide ones identity in the global e- commerce marketplace creates and environment that allows illegal activities to flourish. It is imperative that law enforcement is able to identify the who, what, where of domain name operators immediately in order to effectively investigate. There should be development of clear, workable, enforceable, and standardized processes to regulate access to registrant data when requested by law enforcement. What circumstances would warrant access to registrant data by law enforcement agencies? What clear, workable, enforceable and standardized processes should be adopted by ICANNaccredited s in order to regulate such access? 6 Privacy Considerations 6.1 Balancing Privacy and Public Access Consideration of use of domain name -- commercial v. personal, and whether the use of privacy or proxy services is providers distinguish between domain

6.2 Restrict Proxy/Privacy Services to only noncommercial purposes appropriate when a domain name is used for commercial purposes If proxy/privacy registrations are allowed, the proxy/privacy registrant is a private individual using the domain name for noncommercial purposes only LEA Request names used for commercial vs. personal purposes? Specifically, is the use of privacy/proxy services appropriate when a domain name is registered for commercial purposes? Should there be a difference in the data fields to be displayed if the domain name is registered/ used for a commercial purpose or by a commercial entity instead of to a natural person? Should the use of s be restricted only to registrants who are private individuals using the domain name for noncommercial purposes? 7 Enforcement 7.1 Registrar to cancel Registrations Registrar responsibility for cancellation under appropriate circumstances of registrations made by s offered by others for noncompliance with Relay and Reveal GNSO-ALAC RAA DT What types of services should be covered, and what would be the forms of noncompliance that would trigger cancellation or suspension of registrations? 8 General 8.1 Distinction between Privacy and Proxy Services In considering Accreditation Program, take into account whether to distinguish between s Should ICANN distinguish between privacy and proxy services for the purpose of the accreditation process?