You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Purpose (latest wording)LinkNotesOlder versions

ICANN Purpose A - Establish the rights of a Registered Name Holder in a Registered Name and ensuring that the Registered Name Holder may exercise its rights in respect of the Registered Name


Purpose A - Data_Elements_Processing_Workbook_v2.4.4(ct).docx

Updated with proposed legal basis (as per small team)

Updated with response to new question 3 (as per small team)


Registrar / Registry Purpose B - Facilitate lawful access for legitimate 3rd party interests to data that is already collected and identified herein


Purpose B - Data_Elements_Processing_Workbook_v0.4.4(ct) .docx

The tentative agreement on this purpose was subject to the following qualifying statements:

  • This is a registry/registrar purpose
  • We don’t agree if ICANN also as the same purpose – we will analyze that more.
  • We all agree that we want third parties with legitimate interests to be able to have predictable, lawful access, and the EPDP policy must make that clear.
  • We are all going to bring this back to our constituencies. 


Next step: Workbook to be completed from a Rr and Ry perspective.

ICANN Purpose C - Enable communication or notification to the Registered Name Holder and/or their delegated parties of technical and/or administrative issues with a Registered Name

Purpose C - Data_Elements_Processing_Workbook_v0.4.4.docxAs completed by the small team. Not yet reviewed in plenary.

ICANN Purpose E (Registrar Escrow) - Provide mechanisms for safeguarding Registered Name Holders' Registration Data in the event of a business or technical failure, or other unavailability of a Registrar or Registry Operator

Purpose E Rr Data_Elements_Processing_Workbook_v0.4.4_v0.2(ct).docxUpdated with the proposed legal basis (as per the small team). Not yet reviewed in plenary.
ICANN Purpose E (Registry Escrow) - Provide mechanisms for safeguarding Registered Name Holders' Registration Data in the event of a business or technical failure, or other unavailability of a Registrar or Registry Operator
To be developed

ICANN Purpose F - Handle contractual compliance monitoring requests, audits, and complaints submitted by Registry Operators, Registrars, Registered Name Holders, and other Internet users.

Purpose F - Data_Elements_Processing_Workbook_v0.4.4(ct).docxAwaiting input from ICANN Compliance

ICANN Purpose M - Coordinate the development and implementation of policies for resolution of disputes regarding the registration of domain names (as opposed to the use of such domain names). (ICANN bylaws Annex G and 1(1) section I(a)


Purpose M - Data_Elements_Processing_Workbook_v0.4.4_ updated - 25 Sept 2018(ct).docxAwaiting confirmation of EPDP Team of legal basis per discussions / agreement on legal basis for purpose A. If legal basis for UDRP/URS is the same as for RDDRP, PDDRP and PICDRP, consider adding those with a general description to this definition. If not, create a separate worksheet for those. 

ICANN Purpose N - Enabling validation of Registered Name Holder satisfaction (fulfillment) of registration policy eligibility criteria.


Purpose N - Data_Elements_Processing_Workbook_v0.4.4(ct).docxUpdated with legal basis (per small team recommendations for purpose A). To be further fleshed out by RySG reps.
  • No labels