- CPWG - lists.icann.org

Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 14 November 2018 at 13:00 UTC
by ICANN At-Large Staff Nov. 7, 2018

Nov. 7, 2018

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 14 November 2018 at 13:00 UTC for 60 mins. For other times: https://tinyurl.com/y7rgxhz6 The agenda (to be updated) and call details can be found at: https://community.icann.org/x/RgTVBQ AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: http://adigo.com/icann/ At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

EPDP Update - Week of 29 October
by Hadia Abdelsalam Mokhtar EL miniawi Nov. 7, 2018

Nov. 7, 2018

Dear All, Kindly find herewith the update of week 29 October Hadia From: ICANN Policy Staff [mailto:policy-staff@icann.org] Sent: Tuesday, November 06, 2018 10:15 PM To: Hadia Abdelsalam Mokhtar EL miniawi Subject: Read the EPDP Update - Week of 29 October [http://r20.rs6.net/on.jsp?ca=a4696896-200d-4302-934e-a82c4be703e5&a=1122025…] [http://files.constantcontact.com/304b3fd3501/56a69255-40e1-45ae-92f9-4e332f…] EPDP on the Temporary Specification for gTLD Registration Data Update for Week of 29 October 2018 [http://files.constantcontact.com/304b3fd3501/bb70d337-f273-4102-bcd0-89b2b1…] WHAT HAPPENED THIS WEEK? Overview As a recap, The EPDP Team met four times during ICANN63, and pursuant to the EPDP Team’s draft work plan<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…>, the primary goal of the meetings was to finalize the EPDP Team’s recommendations for its Initial Report. In working through its charter questions<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…>, the EPDP Team continued to discuss purposes for processing registration data, related processing activities, lawful bases of processing activities, et.al. The EPDP Team also presented during a High Interest Topic Session<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…>, during which representatives from the EPDP Team presented an overview of the EPDP Team’s composition, scope, progress, working methodology, and expected next steps in relation to the publication of its Initial Report. The EPDP Team will be publishing its Initial Report shortly and following the publication, the EPDP Team will welcome the community’s submission of public comments. [http://files.constantcontact.com/304b3fd3501/0fd873dd-efe0-44c9-885b-2f2bb1…] The Team continued working through the data elements workbooks<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…>; this week, we focused on: · Purpose E (registry): 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 M: Coordinate, operationalize and facilitate policies for resolution of disputes regarding or relating to the registration of domain names (as opposed to the use of such domain names), namely, the UDRP, URS, PDDRP, RDDRP and future-developed domain name registration-related dispute procedures for which it is established that the processing of personal data is necessary; and · Purpose N: Enabling validation of Registered Name Holder satisfaction (fulfillment) of gTLD registration policy eligibility criteria. The Leadership Team led the Team through the first iteration of the draft Initial Report<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…>. There is highlighting and color-coding within the draft report to emphasize outstanding issues. · Items highlighted in yellow are flags for staff to populate supporting documentation (such as completed data elements workbooks, once reviewed by the EPDP Team). · Items highlighted in blue reflect documents still under discussion, e.g., Small Team 1 and 2 language that is not yet finalized. Blue highlights also denote areas where ICANN Support Staff has suggested language for the Team to review. Staff-suggested language appears in brackets. · Items highlighted in red have not been discussed in detail, and it would be helpful if EPDP Team members volunteer to provide draft responses to red items. Risk The EPDP team is working toward issuing the Initial Report by 19 November based on the newly-adjusted timeline shared during ICANN63 (with a delay of 2 weeks to the previous timeline and milestone of 5 November). Leadership and support team set a tight schedule post-ICANN63 to get EPDP team members feedback and comments to finalize the Initial Report. Depending the groups comments and feedback on several outstanding items or requests to revisit previous deliberations, there is a risk of delay for finalizing the report by the deadline. [http://files.constantcontact.com/304b3fd3501/94e4d20f-a89e-4b9e-9bbf-4bd435…] WHAT IS ON NEXT WEEK'S AGENDA? The Leadership Team will present the review and editing methodology to the EPDP Team, and the EPDP Team will address any outstanding issues flagged within the draft Initial Report. [http://files.constantcontact.com/304b3fd3501/e36580aa-b435-4cc6-a1ad-2d6910…] STATUS REPORT RED Serious Delay/Issues AMBER Manageable Delay/Issues GREEN No Delay/Issues Meeting # & Date Topic 1 Topic 2 Planned Deliverable(s) Status (#1) 1-Aug Orientation, Background, Operating Mode ‌ ‌ COMPLETE (#2) 7-Aug Temp Sepc Triage - Part 1 ‌ ‌ COMPLETE (#3) 9-Aug Temp Sepc Triage - Part 1 ‌ ‌ COMPLETE (#4) 14-Aug Temp Sepc Triage - Part 2 ‌ ‌ COMPLETE (#5) 16-Aug Temp Sepc Triage - Part 3 ‌ ‌ COMPLETE (#6) 21-Aug Temp Sepc Triage - Part 4 ‌ ‌ COMPLETE (#7) 28-Aug Proposed Approach to Deliberations ‌ ‌ COMPLETE (#8) 28-Aug Section 4.4 - Purposes for processing Triage report*; Appendix D, E, G - URS, UDRP, Transfers* ‌ COMPLETE (#9) 30-Aug Section 4.4 - Purposes for processing Appendix C - Data Processing Requirements - Activity & Role Chart ‌ COMPLETE (#10) 4-Sep Section 4.4 - Purposes for processing Appendix C - Data Processing Requirements - Activity & Role Chart Triage Report submitted to the Council on 13 Sep COMPLETE (#11) 6-Sep Appendix C.3 - Processor Requirements Appendix C - Data Processing Requirements - Activity & Role Chart ‌ COMPLETE (#12) 11-Sep Appendix C.3 - Processor Requirements Appendix A 2.1 & 3.0 - European Economic Area Redline 4.4 - deliverable terminated COMPLETE (#13) 13-Sep Appendix A 2.2-2.4 - Redacted data set* Appendix A 2.1 & 3.0 - European Economic Area Data Elements Survey to be used during F2F meeting COMPLETE (#14) 18-Sep Appendix A 2.2-2.4 - Redacted data set* Sections 5,6,7 Registry / Registrar Requirements Redline Appendix C - deliverable terminated COMPLETE (#15) 20-Sep Section 7.2 Consent Sections 5,6,7 Registry / Registrar Requirements Redline Appendix A 2.1, 2.2-2.4, 3.0 - deliverable terminated COMPLETE (--) 24-Sep LA - Roadmap, Purposes, Data Elements for Processing ‌ ‌ COMPLETE (--) 25-Sep LA - Roadmap, Purposes, Data Elements for Processing ‌ Short list of ICANN purposes COMPLETE (--) 26-Sep LA - Roadmap, Purposes, Data Elements for Processing ‌ Data elements matrix per discussed ICANN purposes COMPLETE (#16) 2-Oct Legal Basis for Purposes and related processing activities Review Data Elements Workbook C Next version of Workbook C COMPLETE (#17) 4-Oct Review Data Elements Workbook F - Compliance Review Data Elements Workbook N - Ry Eligibility Requirements Next versions of Workbooks F, N COMPLETE (#18) 9-Oct Review Data Elements Workbook A - Rt Rights Review Data Elements Workbook M & N Next versions of Workbooks A, M, N COMPLETE (#19) 11-Oct Review Data Elements Workbook B - lawful disclosure Prepare for ICANN meeting Next versions of Workbook B COMPLETE (#20) 16-Oct Prepare for ICANN meeting ‌ ICANN63 meeting materials, ICANN Purposes and lawful basis, Data Elements Workbooks COMPLETE (--) 20-Oct ICANN63 Barcelona - EPDP Team ‌ Purpose A & B COMPLETE (--) 21-Oct ICANN63 Barcelona - HIT ‌ ‌ COMPLETE (--) 24-Oct ICANN63 Barcelona - EPDP Team ‌ Legal vs. Natural; Geographic Basis; Reasonable Access agreements COMPLETE (--) 25-Oct ICANN63 Barcelona - EPDP Team ‌ Redaction agreement COMPLETE (#21) 30-Oct Review Workbooks M & N ‌ Confirm Workbooks M & N COMPLETE (#22) 1-Nov Review Workbooks E-Ry & E-Rr, Initial Report ‌ Confirm Workbooks E-Rr & E-Ry; review 1st draft Initial Report ‌ (#23) 6-Nov Review Initial Report & Workbooks ‌ ‌ ‌ (#24) 8-Nov Review Initial Report & Workbooks ‌ ‌ ‌ (#25) 13-Nov Review Initial Report & Workbooks ‌ ‌ ‌ (#26) 15-Nov Review Initial Report & Workbooks ‌ ‌ ‌ (--) 19-Nov Publish Initial Report & Public Comment (30 days) ‌ Initial Report ‌ (--) 19-Dec Public Comment period close on the Initial Report ‌ Public Comment period close ‌ (--) 1-Feb Submission of Final Report to the GNSO Council ‌ Final Report ‌ (--) 15-Feb Approval of Final Report and Recommendations by the GNSO Council ‌ ‌ ‌ (--) 22-Feb Report to the Board ‌ ‌ ‌ (--) 23-Feb Publish Recommendations for Public Comment (30 days) ‌ ‌ ‌ Optional Public Forum Discussion ‌ ‌ ‌ (--) 23-Feb Inform GAC if Recommendations affect public policy ‌ ‌ ‌ (--) 25-Mar Recommendations for Public Comment close (30 days) ‌ ‌ ‌ (--) 15-Apr Board Paper ‌ ‌ ‌ (--) 14-May Board consideration / approval ‌ ‌ ‌ [http://files.constantcontact.com/304b3fd3501/a811f585-9f57-440e-a06b-8e8ab9…] MULTIMEDIA Update on EPDP Team Progress in ICANN63 The EPDP Leadership Team discussed what the team accomplished during ICANN63. Watch the video interview HERE<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…> [http://files.constantcontact.com/304b3fd3501/8a689d7c-fc76-40e8-b8e7-2aa608…]<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…> Photos of the EPDP Team in ICANN63, including during working sessions and the High Interest Topic session, can be found on ICANN Flickr<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…> [http://files.constantcontact.com/304b3fd3501/dd9c0397-65f5-4ee9-aefe-e8a922…] [http://files.constantcontact.com/304b3fd3501/8a00e788-ae26-42bf-bc95-2a0c9f…] [http://files.constantcontact.com/304b3fd3501/09e6b505-0131-41fa-bbf4-b3160d…] [http://files.constantcontact.com/304b3fd3501/9b202037-926a-48d3-bb7f-13720a…] More Information · Workspace Wiki<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…> · Charter<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…> · Timeline/Work Plan/Project Plan/Budget Fact Sheet<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…> · GNSO Website<http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…> If you would like to follow this effort as an observer, please email the GNSO Secretariat<mailto:gnso-secs@icann.org> Follow the GNSO on Twitter [Twitter]‌ <http://r20.rs6.net/tn.jsp?f=001ZWW0BnMjk9ilojpdPi_FHuN9oNsd9SPV3t6EbMIru2iT…> ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe hadia(a)tra.gov.eg<https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Update Profile<https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> | About our service provider<http://www.constantcontact.com/legal/service-provider?cc=about-service-prov…> Sent by policy-staff(a)icann.org<mailto:policy-staff@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.]<http://www.constantcontact.com/index.jsp?cc=nge> Try it free today<http://www.constantcontact.com/index.jsp?cc=nge>

1 0

Call for Comments: ICANN Seeking Community Feedback on Proposed Unified Access Model
by ICANN At-Large Staff Nov. 7, 2018

Nov. 7, 2018

Dear All, Please note the first draft ALAC Statement on ICANN Seeking Community Feedback on Proposed Unified Access Model<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+ICA…> is ready for your review. The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/wwA5BQ. The At-Large website page for the Statement is here: https://atlarge.icann.org/advice_statements/12105. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function. You will need to log in to the wiki to use the comment function. If you don’t have a login or have other issue using the wiki, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

2 2

Revised Draft Statement on Unified Access Model
by Greg Shatan Nov. 6, 2018

Nov. 6, 2018

All, I have attached a further revised version of the draft ALAC Statement on the the Unified Access Model. This version reflects the discussions in Barcelona. In addition, I’ve tried to make changes so that it is shorter and more straightforward. I will be on audio only for tomorrow’s call, as I’ll be in transit, but I hope that we can (finally) wrap this up so that the ALAC can do their thing. Best regards, Greg

1 0

REMINDER / Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 07 November 2018 at 13:00 UTC for 90mins
by ICANN At-Large Staff Nov. 6, 2018

Nov. 6, 2018

If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> with your preferred number. Please remember that it is now possible to connect your audio via the AC room, without using your telephone. You need a stable internet connection. If you would like a reminder of how to connect please let staff know. Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 07 November 2018 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/ydgv8fcs The agenda (to be updated) and call details can be found at: https://community.icann.org/x/eADVBQ AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: http://adigo.com/icann/ At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Re: [CPWG] [registration-issues-wg] [GTLD-WG] Verisign Dissing Domainers?
by Alan Greenberg Nov. 6, 2018

Nov. 6, 2018

The RAA has always had a provision allowing ICANN to have a Consensus Policy prohibiting reistrars from warehousing or speculation. We have never taken action on this and I cannot see the GNSO ever doing so. The Verisign blog is interesting. Rare that a large company publicly disses its largest customers. Alan At 02/11/2018 03:43 PM, Greg Shatan wrote: This post is actually taking aim primarily at REGISTRARS who buy huge numbers of .com domains at wholesale ($7.85 per domain) and then hold them, in order to try and sell them later for a premium price. That’s not really dissing domainers in the general sense, just these registrar-domainers. The writing is a bit sloppy on this point, and the blog pivots to ICA toward the end, but even there, the focus is on the registrar-domainers, not on the general domaining public. Look again at the post, and you will see references to “speculators” who buy at a “regulated price.” That’s the Verisign price they are talking about. Regular registrants don’t have that opportunity � onlly registrars. The “Domainer Name Wire” article largely misses this point � partly because the post is vague and partly becausse of a tendency to “rush to judgment” in the domaining press. As Jonathan notes, ICA argues it’s protecting the little guy, when they are actually providing loads of protection for some very “big guy” registrar-domainers. While this is not “insider trading,” it is really a form of diversion based on insider access � the registrars abuse their privileged position to bbuy cheap and to buy before any “regular” registrant (even a domainer) can, and then they hold this portfolio and charge secondary-market prices for domains that are not really in the secondary market. Registrars’ unique ability to buy domain names directly from the registries was never meant to produce this result. This is a bug, not a feature. The end user domainers should really be pissed off at the registrar-domainers, not at Verisign. (Of course, they are permanently pissed off at Verisign, especially with a price increase in their “commodity.”) Maybe registrars should be prohibited from buying for their own account for investment purposes. GoDaddy apparently has 2.5 billion reasons to oppose that idea. I don’t know if I would call them scalpers (though it’s a fair comparison). I see domainers more like the folks in Boston who get up in the morning, sit down in a lawn chair in a prime parking spot near the Fenway Park baseball stadium, and then sit there until game time approaches. Then they charge you $20 or more to get out of the way so you can park there. This is not entirely accurate either since this is a lot more work than a domainer would put in (at least for a single domain name. Greg On Fri, Nov 2, 2018 at 3:10 PM Jonathan Zuck < JZuck(a)innovatorsnetwork.org<mailto:JZuck@innovatorsnetwork.org>> wrote: We'll, it's not particularly easy to take them back. Blog raises some good points about where the money goes. The ICA rhetoric about small business is pretty silly. Jonathan Zuck Executive Director Innovators Network Foundation www.Innovatorsnetwork.org<http://www.Innovatorsnetwork.org> ________________________________ From: GTLD-WG < gtld-wg-bounces(a)atlarge-lists.icann.org<mailto:gtld-wg-bounces@atlarge-lists.icann.org>> on behalf of Carlton Samuels < carlton.samuels(a)gmail.com<mailto:carlton.samuels@gmail.com>> Sent: Friday, November 2, 2018 2:59:12 PM To: cpwg(a)icann.org<mailto:cpwg@icann.org>; lac-discuss-en(a)atlarge-lists.icann.org<mailto:lac-discuss-en@atlarge-lists.icann.org> Subject: [GTLD-WG] [CPWG] Verisign Dissing Domainers? Um,.......hmmmm, a flag up the pole to see who salute you think? Assuming the posting it is sanctioned as official view, what is the end game here? Afterall, they are gifted ownership of every name, known and hitherto unknown, in the .com space! The domainers merely 'rent' them! Hmmm....we have a saying in my corner of empire, 'one hand alone can't clap'. Gotta follow the money. https://domainnamewire.com/2018/11/02/holy-sht-verisign-just-called-out-dom… ============================== Carlton A Samuels Mobile: 876-818-1799 Strategy, Process, Governance, Assessment & Turnaround ============================= _______________________________________________ CPWG mailing list CPWG(a)icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ registration-issues-wg mailing list registration-issues-wg(a)atlarge-lists.icann.org<mailto:registration-issues-wg@atlarge-lists.icann.org> https://mm.icann.org/mailman/listinfo/registration-issues-wg _______________________________________________ CPWG mailing list CPWG(a)icann.org https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ registration-issues-wg mailing list registration-issues-wg(a)atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/registration-issues-wg

6 9

FW: **REMINDER** Meeting Invitation: Alternates & Observers / GNSO Temp Spec gTLD RD EPDP call / Tuesday, 06 November 2018 at 14:00 UTC
by Hadia Abdelsalam Mokhtar EL miniawi Nov. 6, 2018

Nov. 6, 2018

In case you are interested to follow the call Hadia From: Gnso-epdp-team [mailto:gnso-epdp-team-bounces@icann.org] On Behalf Of Julie Bisland Sent: Monday, November 05, 2018 5:06 PM To: gnso-epdp-team(a)icann.org Cc: gnso-secs(a)icann.org Subject: [Gnso-epdp-team] **REMINDER** Meeting Invitation: Alternates & Observers / GNSO Temp Spec gTLD RD EPDP call / Tuesday, 06 November 2018 at 14:00 UTC Dear all, Non-members can follow the EPDP call taking place on Tuesdays and Thursdays at 14:00 UTC via the audio cast or view only Adobe Connect room. As requested and discussed on Tuesday's (14 August 2018) meeting, please note that an additional Adobe Connect room has been created for use by interested alternates and observers to be able to view-only the main EPDP Team Adobe Connect room. The view-only room will also broadcast the audio of the EPDP Team AC room, however, those in the view-only room will not be heard. Note that the audio cast stream will also remain available for now for those that prefer to use that option to listen live to the EPDP Team meeting. View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers Meeting Audio Cast (for alternates and observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Agenda wiki page: https://community.icann.org/x/qA68BQ Thank you. Kind Regards, Julie

1 0

Verisign Dissing Domainers?
by Carlton Samuels Nov. 6, 2018

Nov. 6, 2018

Um,.......hmmmm, a flag up the pole to see who salute you think? Assuming the posting it is sanctioned as official view, what is the end game here? Afterall, they are gifted ownership of every name, known and hitherto unknown, in the .com space! The domainers merely 'rent' them! Hmmm....we have a saying in my corner of empire, 'o*ne hand alone can't clap*'. Gotta follow the money. https://domainnamewire.com/2018/11/02/holy-sht-verisign-just-called-out-dom… ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

5 7

Fwd: A conceptual view of TempSpec/EPDP and the Unified Access Model
by Jonathan Zuck Nov. 4, 2018

Nov. 4, 2018

DelBianco tried to incorporate the feedback. Feels like a useful tool to descalate so let's see if we can support. Jonathan Zuck Executive Director Innovators Network Foundation www.Innovatorsnetwork.org<http://www.Innovatorsnetwork.org> ________________________________ From: Steve DelBianco Sent: Sunday, November 4, 2018 11:31:42 AM To: Jonathan Zuck Subject: Re: A conceptual view of TempSpec/EPDP and the Unified Access Model Jonathan, Attached is a v2, reflecting these changes: Per suggestion from ALAC, added qualified under UAM "(if DPAs recognize ICANN as the responsible party)" I changed the title to reflect the narrow focus on "Publication and Disclosure of Registrant Data, under the EPDP and UAM". Per suggestion from BC and IPC, changed "TM protection" to IP protection" and changed "May disclose on request" to "Must disclose on request, if GDPR 6(1)(f) balance is met". Registrars and registries use their discretion to determine if 61f balance is met, so that’s why I had “May disclose” in prior version. --Steve On 10/30/18, 5:46 PM, "Steve DelBianco" <sdelbianco(a)netchoice.org> wrote: Jonathan, Could you please think about sharing this with ALAC policy folks who are working on the EPDP? Attached please find a conceptual view of EPDP and the Unified Access Model. This started with a napkin sketch while Keith Drazek and I were talking at the Barcelona airport on Friday morning, as a follow-up to the very positive CSG-CPH meeting on Wednesday. We saw the need to help the ICANN community distinguish between Published data, Disclosure under “reasonable access”, and Unified Access operated by ICANN. This diagram attempts to make those distinctions. Another purpose of the diagram is to focus the EPDP (at this stage) on collection, publication, and discretionary disclosure under (what the TempSpec calls “reasonable access”). With that focus, the EPDP can move more smoothly to an initial report on its first charter task to develop policy to replace the TempSpec. We understand that phase 2 of EPDP can address policy for the UAM, including accreditation process, verifying credentials, logging, and disclosure. But first, the community and Data Protection Authorities need to endorse the conceptual approach that a UAM operated by ICANN can position ICANN as the responsible party. That's a "gating question". --Steve DelBianco

1 0

Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 07 November 2018 at 13:00 UTC for 90mins
by ICANN At-Large Staff Nov. 3, 2018

Nov. 3, 2018

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 07 November 2018 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/ydgv8fcs The agenda (to be updated) and call details can be found at: https://community.icann.org/x/eADVBQ AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: http://adigo.com/icann/ At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

4 3