August 2018 - CPWG - lists.icann.org

Unified Access Model published for community input
by Greg Shatan Sept. 4, 2018

Sept. 4, 2018

All, As mentioned on today's CPWG call, ICANN org published a blog earlier this week releasing the proposed Unified Access Model for community input. https://www.icann.org/news/blog/possible-unified-access-model -published-for-community-input The proposal itself can be found here: Draft Framework for a Possible Unified Access Model for Continued Access to Full WHOIS Data – For Discussion <https://www.icann.org/en/system/files/files/framework-elements-unified-acce…> I am the penholder on this comment. Please reply to this email if your are interested in commenting. Thanks! Greg -- Greg Shatan greg(a)isoc-ny.org "The Internet is for everyone"

5 7

WIPO FAQ page on GDPR and its impact on the UDRP.
by Dev Anand Teelucksingh Sept. 3, 2018

Sept. 3, 2018

the WIPO Center has produced the present Q&A on the GDPR’s relation to the UDRP. http://www.wipo.int/amc/en/domains/gdpr/

3 4

Next possible move related to GDPR
by Alan Greenberg Sept. 3, 2018

Sept. 3, 2018

Not of direct relevance to our work, but perhaps interesting. Alan

9 11

New gTLD SubPro IR section 2.8.1 Objections
by Justine Chew Aug. 30, 2018

Aug. 30, 2018

Dear colleagues, I am providing an update, ahead of the CPWG call later today, on inputs to the New gTLD Subsequent Procedures Initial Report (IR) call for comments. For those attending the call later, this is agenda item 3g Objections <https://community.icann.org/display/atlarge/2018-08-29+Consolidated+Policy+…> . For starters, I do not know if consensus has been established for At-Large/ALAC to comment on section 2.8.1 Objections of the IR. However I flagged this section about 2 CPWG calls ago because, being somewhat familiar with the IR, I knew *there were questions relating to ALAC in this section which I suggest ALAC should respond to*. So, while working towards completing my inputs to section 2.8.1 Objections of the IR, I wanted to draw your attention to the inputs submitted by Alan Greenberg and myself thus far. And this is quite a long section I might add. These can be found at (my) googledoc (*link here <https://drive.google.com/open?id=1rlGb86PXT50tYN33WHtwi94trFpoAoB6r63O_v6AT…>*). Please scroll down the left table of contents menu and click on 2.8.1 Objections. Questions in this section 2.8.1 include: - Q 2.8.1.e.10 Whether ICANN should continue to fund objections filed by ALAC? And if yes, should any limits be placed on such funding and if so, what limits? - Q 2.8.1.e.1 et al Role of GAC Advice - Q 2.8.1.e.4 et al Role of Independent Objector - Q 2.8.1.e.13 et al Community Objections (input pending) - Q 2.8.1.e.15 Can a Community Objection be resolved by applying a mandatory PIC? (input pending) I invite you to add to or rebut posted inputs. In particular, I wanted to ask if any of you were involved in the ALAC Objection procedures (and attempted objection filing) for the 2012 round, and if you were to please provide comments on what weaknesses we would like to address in respect of the Objection procedure for ALAC. (I will find some time to post the inputs on the designated wiki asap) Regards, Justine ----

1 1

Meeting Invitation: Consolidated Policy Working Group (CPWG) Call on Wednesday, 05 September 2018 at 13:00 UTC for 90mins
by ICANN At-Large Staff Aug. 29, 2018

Aug. 29, 2018

*** This call is scheduled at 13:00 UTC, instead of 19:00 UTC, due to trying to avoid conflict with AFRALO Monthly Call. *** Please note: Working Group will be meeting at rotating times of 19:00 UTC and 13:00 UTC, alternating weekly. Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 05 September 2018 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/ya6223xk The agenda (to be updated) and call details can be found at: https://community.icann.org/x/UAONBQ 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<applewebdata://D0C9D8AD-F5F9-47D1-8000-12B5977AB503/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

At-Large Workspace: Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4)
by Olivier MJ Crépin-Leblond Aug. 29, 2018

Aug. 29, 2018

Dear colleagues, on this week's forthcoming CPWG call, we'll have an item that will focus on the "Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4)" This is a very important track, which we risk missing out altogether due to our focus on the EPDP - hence the reason why we'll spend some time on this, specifically with a goal to respond to the Public Consultation on this topic. This can be found on: https://community.icann.org/x/dYdHBQ Between now and the call, please take some time to acquaint yourself with the public consultation and read the Working Group's Initial Report which you'll find referenced on that WIKI page. Also - would any participants in the PDP on New gTLD Subsequent Procedures please be so kind to identify themselves by email to Jonathan and me so we can call upon you to make suggestions as to what we should particularly look out for. Kindest regards, Olivier

19 46

Example of Voluntary PIC
by Alan Greenberg Aug. 29, 2018

Aug. 29, 2018

On the CPWG call today, there was a discussion of Voluntary PICs and whether they had any meaningful benefit. I mentioned that in the ALAC review of the GAC concern over TLDs using strings representing highly regulated sectors, we found that there were some TLDs in those sectors that used voluntary picks to mitigate possible problems. Two such examples are included. Alan ================ .gmbh (the German term for a Limited Liability Company) Eligibility / Validation - Eligible registrants in the TLD will be limited to those entities designated, or pending designation, as a GmbH (Gesellschaft mit besechränkter Haftung) limited liability entity whose existence can be validated with the respective public authorities in Austria, Germany, Liechtenstein or Switzerland. Registry Operator will include a provision in their Registry-Registrar Agreements that requires registrars to include in their Registration Agreements a provision requiring a representation that the registrant possesses the necessary registration and designation under applicable law for registration in the TLD. ================ .inc Registry Operators will include a provision in their Registry?Registrar Agreements that requires registrars to include in their Registration Agreements a provision requiring a representation that the registrant possesses any necessary authorizations, charters, licenses and/or other related credentials for participation in the sector associated with the TLD. If a Registry Operator receives a complaint expressing doubt with regard to the authenticity of licenses or credentials, Registry Operators should consult with relevant national supervisory authorities, or their equivalents regarding the authenticity.

1 0

REMINDER / Meeting Invitation: Consolidated Policy Working Group (CPWG) Call on Wednesday, 29 August 2018 at 13:00 UTC for 90mins
by ICANN At-Large Staff Aug. 28, 2018

Aug. 28, 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. Please note: Working Group will be meeting at rotating times of 19:00 UTC and 13:00 UTC, alternating weekly. Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 29 August 2018 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/ya4m8vze The agenda (to be updated) and call details can be found at: https://community.icann.org/x/xxxpBQ 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<applewebdata://D0C9D8AD-F5F9-47D1-8000-12B5977AB503/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>

2 1

URGENT - WT5 proposal for 3-letter country codes
by Maureen Hilyard Aug. 28, 2018

Aug. 28, 2018

Hi everyone If you have been following the discussions in WT5 you will see that there has been a lot of controversy over the GNSO consensus process on Country and Territory Names and how best to come to a decision on each of the key issues that are being discussed. With regards to an agreement over 3-letter country codes, Carlos Raul Gutierrez has proposed the following suggestion to help this process move forward, I believe we should consider his proposal as a reasonable compromise considering all the discussion that has taken place and send our support (or otherwise) to our ALAC co-Chair. The ALAC views could be coordinated by the CPWG leads but will be required *by Tuesday??*. *This is urgent, as it appears that consensus calls will be received by the co-Chairs during the week and as they will have to prepare for the next WT5 meeting on the 22nd, it would be good to include an ALAC opinion as well. * “Dear Annebeth, As you have heard me (too) many times before, I admire the track record of preceding, clearly focused public interest 3 letter geo-TLDs, like the ones from Catalonia in Spain, Brittany's in France, and Serbia's 3 letter TLDs Now that I re-stated my rationale for such a clear-cut public interest case in an email to Rosalia (for geo use ONLY, accessible -i.e. cheap- and non-profit), I hereby submit to the WT my final revised language suggestion, which is ONLY applicable for 3-Letter codes. It would substitute the following final paragraph in the relevant section which deals with 3-Letter codes: “*The SubPro may want to consider recommending whether any future application/revision/delegation process to be established (either generic or restricted to the Geographic categories only), should determine if, when, and how specific interested parties, such as relevant public international, national or sub-national public authorities, may apply for country and territory names*" My suggestion for a FORWARD looking option is: “*ICANN may only consider applications of ISO 3166-1 Alpha 3 Letter Codes submitted by relevant governmental authorities, ccTLD managers and public interest/public benefit entities*.” This paragraph is, in my view, a sensible part of a forward-looking recommendation that could go ahead with broader WT consensus. And if it does not, please make sure it is recorded as an objection against a permanent restriction of the delegation of the ISO 3-Letter list. Thanks to all, Carlos Raúl Gutiérrez"

25 52

Reduced SubProc spreadsheet
by Jonathan Zuck Aug. 24, 2018

Aug. 24, 2018

Dear CPWG Members, Please see the addition I made to the Google Doc spreadsheet for our Sub Proc filing. Found here: https<https://docs.google.com/spreadsheets/d/1agNhbXfXLPQIRTGjC-8U-l534SWpbnsiapi…>://<https://docs.google.com/spreadsheets/d/1agNhbXfXLPQIRTGjC-8U-l534SWpbnsiapi…>docs.google.com<https://docs.google.com/spreadsheets/d/1agNhbXfXLPQIRTGjC-8U-l534SWpbnsiapi…>/spreadsheets/d/1agNhbXfXLPQIRTGjC-8U-l534SWpbnsiapi-fi5mzFw/<https://docs.google.com/spreadsheets/d/1agNhbXfXLPQIRTGjC-8U-l534SWpbnsiapi…>edit#gid<https://docs.google.com/spreadsheets/d/1agNhbXfXLPQIRTGjC-8U-l534SWpbnsiapi…>=180358966<https://docs.google.com/spreadsheets/d/1agNhbXfXLPQIRTGjC-8U-l534SWpbnsiapi…>. After clicking the link I provided, you should find that I created a tab at the bottom of the spreadsheet titled “ALAC Comment Sheet.” Once you click on that tab, you will see that I condensed the spreadsheet to subjects that this group has agreed to comment on so as to receive targeted feedback to questions we feel are important to the At-Large. I hope you will find it useful throughout this drafting process and while providing input. As always, please feel free to reach out to me if you have any questions related to this new addition or the comment process more generally. Best, Jonathan Jonathan Zuck | Executive Director | Innovators Network jzuck(a)innovatorsnetwork.org<mailto:jzuck@innovatorsnetwork.org> | O 202.420.7497 | S jvzuck | [INFLogo2]

1 0