[Gnso-epdp-team] Proposed Agenda - EPDP Team Meeting #34
kurt at kjpritz.com
Wed Dec 12 19:25:19 UTC 2018
I think the agenda is fine but please include a note that we understand that we are likely to not complete all the agenda items but we wished to lay out the order of topics for this, and probably the next meeting.
Something like that.
> On Dec 12, 2018, at 7:23 AM, Caitlin Tubergen <caitlin.tubergen at icann.org> wrote:
> Dear All,
> Below, please find the proposed agenda for tomorrow’s EPDP Team call.
> Best regards,
> Marika, Berry, and Caitlin
> EPDP Meeting #34 Agenda <>
> Thursday, 13 December 2018
> <> <>Roll Call & SOI Updates (5 minutes)
> Welcome and Updates from EPDP Team Chair (5 minutes)
> Review of outstanding action items
> Other updates, if applicable
> Continue review of list of topics for further discussion
> Geographic basis
> Consider EDPB Guideline (see https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-32018-territorial-scope-gdpr-article-3-version_en <https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-32018-territorial-scope-gdpr-article-3-version_en>)
> How does this guideline impact EPDP Team’s position on this topic? What changes, if any, should be considered for the Final Report?
> Policy Change Impact Analysis
> Review current language in Initial Report
> Discuss what other information this section should contain
> Volunteers to work on this section?
> Privacy/Proxy Services - how the P/P records appear in the public WHOIS
> Current Language in Temp Spec - Appendix A, Section 2.6: Notwithstanding Sections 2.2, 2.3, 2.4, and 2.5 of this Appendix, in the case of a domain name registration where a privacy/proxy service used (e.g. where data associated with a natural person is masked), Registrar MUST return in response to any query full WHOIS data, including the existing proxy/proxy pseudonymized email.
> Margie to introduce issue for discussion
> Proposed outcome: confirm requirement [BC/IPC support confirmation.]
> Discuss next steps
> Registrant Consent to Publication – option for registrants to request to have all of their RDS data published
> Current Language in Temp Spec, Section 7.2.1/ Appendix C – Section 2.3: As soon as commercially reasonable, Registrar MUST provide the opportunity for the Registered Name Holder to provide its Consent to publish the additional contact information outlined in Section 2.3 of Appendix A for the Registered Name Holder.
> Margie to introduce issue: Whether registrars should give the registrant the option to opt in to having their WHOIS Contact Data be published rather than be redacted. This is an issue that would be available to both natural persons and legal persons.
> Proposed outcome: confirm this requirement [IPC/BC/SSAC/Some members of RrSG also support confirmation.]
> Consent by the Registrant to Publish and/or Disclose for technical contact
> Current language in Temp Spec, Section 7.2.1/ Appendix C – Section 2.3 contains this requirement: Registrar MAY provide the opportunity for the Admin/Tech and/or other contacts to provide Consent to publish additional contact information outlined in Section 2.4 of Appendix A.
> Margie to introduce issue: Whether registrars should seek consent from those listed as additional contacts (admin/tech) to having their information as reflected in the Contact data be published rather than be redacted. This is an issue that would be available to both natural persons and legal persons.
> Proposed outcome: confirm this requirement [IPC/BC/SSAC support confirmation.]
> Update from Leadership Team regarding approach to external legal counsel
> Wrap and confirm next meeting to be scheduled for Tuesday 18 December 2018 at 14.00 UTC
> Confirm action items
> Confirm questions for ICANN Org, if any
> <Topics for further discussion - upd 12 Dec 2018.docx>_______________________________________________
> Gnso-epdp-team mailing list
> Gnso-epdp-team at icann.org <mailto:Gnso-epdp-team at icann.org>
> https://mm.icann.org/mailman/listinfo/gnso-epdp-team <https://mm.icann.org/mailman/listinfo/gnso-epdp-team>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnso-epdp-team