April 2019 - CPWG - lists.icann.org

Further Revised Draft Statement on .ORG Renewal
by Greg Shatan May 3, 2019

May 3, 2019

All, I am attaching another, further revised draft public comment on the .ORG renewal, after sifting through the various recent conversations on the list. I will try to circulate a redline in the morning, New York time, but can't right now. I thought about including something on UA, but for .ORG and in the absence of proposed language, I did not see the obvious hook in this statement to bring that concept in. Best regards, Greg Greg Shatan greg(a)isoc-ny.org President, ISOC-NY *"The Internet is for everyone"*

20 38

Final chance for choices for the HIT sessions in Marrakech
by Maureen Hilyard May 2, 2019

May 2, 2019

https://icann.wufoo.com/reports/icann65-proposed-topics It would be good to get some priorities from At-Large, from this final list of proposals for the High Interest and Cross Community Discussions. Gisella must have our list of priorities by Friday week - perhaps 4-5 sessions acceptable to At-Large and for which we could create talking points for the key discussions at Marrakech Maureen

5 5

Fwd: [SOAC-Leaders-ICANNMeeting-Planning] ICANN55 Topic Review Form
by Maureen Hilyard April 30, 2019

April 30, 2019

Proposals from the GNSO for consideration by the team during the discussion on what At-Large would like to support for the HIT sessions. ---------- Forwarded message --------- From: Drazek, Keith via SOAC-Leaders-ICANNMeeting-Planning < soac-leaders-icannmeeting-planning(a)icann.org> Date: Tue, Apr 30, 2019 at 6:15 AM Subject: Re: [SOAC-Leaders-ICANNMeeting-Planning] ICANN55 Topic Review Form To: tanzanica.king(a)icann.org <tanzanica.king(a)icann.org>, soac-leaders-icannmeeting-planning(a)icann.org < soac-leaders-icannmeeting-planning(a)icann.org> Hi all, Following our good discussion last Thursday, here are my summarized views and a proposed approach to the HIT/CC sessions for Marrakech: 1. The GNSO Council recommends consolidating several of the currently proposed sessions under a new session titled “Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures.” This is consistent with Recommendation #27 from the EPDP Phase 1 report, and it will provide an opportunity for groups to air concerns about impacts while helping to identify and prioritize the universe of policies and procedures that will need review and possible updating. I believe the current items: Combatting Abuse with GDPR, Privacy-Proxy Implementation, and Across Field Validation would fit under this consolidated approach. I have attached the consolidated proposal for your reference. (This brings three proposed sessions down to one.) 1. Regarding the two proposals for a session on EPDP Phase 2 / Uniform Access Model, the EPDP Phase 2 work will have only been under way for 6 weeks when we arrive in Marrakech. The first substantive meeting of the EPDP Phase 2 Team will be May 16. As such, I think it’s premature to schedule a HIT/CC session and recommend we defer it to ICANN 66 in Montreal. The EPDP Phase 2 work will be mid-stream and progressing in Marrakech, so I do not see the value of a HIT/CC session at the end of June. It will absolutely be critical in Montreal, as the group should be closer to producing a concrete work product for the community to consider and to provide feedback. (This removes two proposed sessions.) 1. We discussed the possibility of moving sessions that are described as “updates” to a pre-meeting webinar, but we need to ensure community engagement is not stifled. It appears that ATRT3, SSR-2 and NomCom Review Implementation are all on track to produce reports prior to ICANN 66, and have stated this is an opportunity for in-person community education and input. That said, I believe these groups have also extended invitations to our respective community groups, so I’m wondering if these are duplicative. We have identified duplication as a real issue with ICANN scheduling, so I’d be interested in exploring whether these can be moved to interactive webinars in June, prior to Marrakech. (This could remove 1-3 sessions.) 1. The “Future of Multistakeholder Model Governance” session is necessary to complete the project kicked off in Kobe by years’ end. This is clearly a topic of interest to the entire community. (This session should be included.) 1. The “Enhance Effectiveness of Specific Review Recommendations and their Implementation” session is timely, particularly with the developments around the Board’s actions on the CCT-RT recommendations. (This session should be included.) 1. There was a good bit of discussion in Kobe around Universal Acceptance and it’s an issue that appears to be generating increased interests. With the meeting being held in Marrakech, it seems this is a good opportunity to continue discussions on the UA and IDN-related issues. (I’m ok with this session.) 1. Speaking personally, I don’t see the DNS over HTTPS (DoH) session as having broad community interest at this time. Perhaps this could be a regular session, but I don’t think it needs to be a HIT/CC session in Marrakech. (This would remove one session.) So, I think that would get us to a more manageable number of sessions while ensuring we are prioritizing subject matter, meeting space and time appropriately. To summarize, this would result in four HIT/CC sessions with the possibility of ATRT3, SSR-2 and/or NomCom getting added back in if they really need the F2F engagement outside of a webinar. Any other sessions could still be held in Marrakech, but not necessarily as a HIT/CC. Thoughts? I will complete the online forms as well. Regards, Keith *From:* SOAC-Leaders-ICANNMeeting-Planning < soac-leaders-icannmeeting-planning-bounces(a)icann.org> *On Behalf Of *Tanzanica S. King *Sent:* Monday, April 29, 2019 9:17 PM *To:* SOAC-Leaders-ICANNMeeting-Planning < soac-leaders-icannmeeting-planning(a)icann.org> *Subject:* [EXTERNAL] [SOAC-Leaders-ICANNMeeting-Planning] ICANN55 Topic Review Form Dear Community Leaders: Thank you for a productive call last week and apologies for the delay in getting this review form out to the group. Several topic proposals have been updated in the report at https://icann.wufoo.com/reports/icann65-proposed-topics. Updates are also included below for your quick reference. Please use the* online topic review form <https://www.surveymonkey.com/r/ICANN65topics>* to indicate which topics you’d like to see at the meeting as soon as possible, and no later than *Wednesday, 1 May.* *Links:* *Topic Review Form* https://www.surveymonkey.com/r/ICANN65topics *Topic Proposals* https://icann.wufoo.com/reports/icann65-proposed-topics *Current Block Schedule* https://meetings.icann.org/sites/default/files/65-blockschedule._v1.2.pdf *Updated Topic Proposals:* *#1.* *Across Field Address Validation - WHOIS Accuracy (RAA) * *Background:* The IPC needs to understand the criteria associated with the AFAV RAA obligation that ICANN has set forth. This is a 6-year old RAA contractual obligation that is being ignored by ICANN. *Session Goals:* ICANN needs to provide an update on this project, including recent activities and well as the strategy to ensure the obligation will be enforced on the Registrars and associated timelines. *Format:* Open Session *#6. EPDP Phase 2 * *Background:* ICANN Board mandate. Extremely important given the UAM component and need to ensure proper timelines are enforced. *Session Goals:* Need to ensure proper ICANN resources, budget and timelines are assigned to Phase 2. *Format:* Open Session *#8. ICANN - combating domain abuse with GDPR* *Background:* RA and RAA obligations to ensure ICANN compliance is enforcement the contractual obligations as well as what is ICANN Compliance strategy given GDPR *Session Goals:* Need to understand ICANN's plan *Format:* Open session *#11. Privacy and Proxy Implementation * *Background:* PDP, Board Mandated *Session Goals:* The IPC needs to understand why this program remains on hold due to GDPR and what specifically is the overlap or conflict between GDPR and PPP? *Format:* Open Session Best regards, Tanzanica _______________________________________________ Tanzanica S. King Sr. Manager, Meeting Strategy and Design ICANN Office +1 310 301 5800 Mobile +1 310 995 3038 www.icann.org _______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list SOAC-Leaders-ICANNMeeting-Planning(a)icann.org https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning

1 0

Fwd: FW: Draft Comment on RA Renewals
by Greg Shatan April 30, 2019

April 30, 2019

*Please see attached.* -- Greg Shatan greg(a)isoc-ny.org President, ISOC-NY *"The Internet is for everyone"*

14 24

Google public DNS breaks DNS resolution
by Lutz Donnerhacke April 30, 2019

April 30, 2019

I recently came across this really mad idea by Google engineers: https://developers.google.com/speed/public-dns/docs/security#nonce_prefixes They try to protect against DNS spoofing by adding entropy in queries to root/TLD name servers. That's a braindead idea, because they can query all those servers using DNSSEC, which invalidates the reasoning itself. But the more important point is, that this solution is based on a misguided understanding of DNS itself. Let's take for instance "www.uit.int" as an example. ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37704 ;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 1;; QUESTION SECTION: ;www.uit.int. IN A ;; ANSWER SECTION: www.uit.int. CNAME www.itu.int. www.uit.int. RRSIG CNAME 7 3 86400 2019... ;; AUTHORITY SECTION: itu.int. NS ns.itu.ch. itu.int. NS ns2.itu.ch. itu.int. NS ns3.itu.ch. [DNSSEC stuff] So we do get a resolution and a delegation. ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48110 ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 8, ADDITIONAL: 1 ;; QUESTION SECTION: ;nonce-for-dummies.www.uit.int. IN A ;; AUTHORITY SECTION: int. SOA sns.dns.icann.org. ... [lot of DNSSEC NSEC3 non-existence proofs] But the modified request does not reveal even a hint, that the original query might be successful. If necessary, I'm happy to discuss the basics of DNS directly to the engineer, if somebody makes a contact. This discussion will include "non empty non-terminals" and the difference between DS and DNSKEY, both issues where Google public DNS fails.

1 0

Google public DNS breaks DNS resolution
by lutz＠fitug.de April 30, 2019

April 30, 2019

I recently came across this really mad idea by Google engineers: https://developers.google.com/speed/public-dns/docs/security#nonce_prefixes They try to protect against DNS spoofing by adding entropy in queries to root/TLD name servers. That's a braindead idea, because they can query all those servers using DNSSEC, which invalidates the reasoning itself. But the more important point is, that this solution is based on a misguided understanding of DNS itself. Let's take for instance "www.uit.int" as an example. ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37704 ;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 1;; QUESTION SECTION: ;www.uit.int. IN A ;; ANSWER SECTION: www.uit.int. CNAME www.itu.int. www.uit.int. RRSIG CNAME 7 3 86400 2019... ;; AUTHORITY SECTION: itu.int. NS ns.itu.ch. itu.int. NS ns2.itu.ch. itu.int. NS ns3.itu.ch. [DNSSEC stuff] So we do get a resolution and a delegation. ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48110 ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 8, ADDITIONAL: 1 ;; QUESTION SECTION: ;nonce-for-dummies.www.uit.int. IN A ;; AUTHORITY SECTION: int. SOA sns.dns.icann.org. ... [lot of DNSSEC NSEC3 non-existence proofs] But the modified request does not reveal even a hint, that the original query might be successful. If necessary, I'm happy to discuss the basics of DNS directly to the engineer, if somebody makes a contact. This discussion will include "non empty non-terminals" and the difference between DS and DNSKEY, both issues where Google public DNS fails.

1 0

NOW THURSDAY - At-Large Consolidated Policy Working Group (CPWG)call on Tuesday, 30 April 2019 at 21:00 UTC
by ICANN At-Large Staff April 30, 2019

April 30, 2019

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. Si necesita una llamada a su telefono, por favor póngase en contacto con el personal de At-Large en staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> con su número preferido. Por favor, recuerde que es posible conectar el audio a través de la Adobe Connect, sin necesidad de utilizar su teléfono. Se necesita una conexión a Internet estable. Si desea un recordatorio de cómo conectar por favor que el personal sepa. Por favor note que esta llamada tendra interpretación en ES. Please note this call will have ES interpretation. Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Thursday 02 May 2019 at 20:00 UTC for 90 mins. For other times: https://tinyurl.com/y5arqd5r The agenda and call details can be found at: https://community.icann.org/x/WIOGBg Zoom Room: https://icann.zoom.us/j/407784499 Zoom Dial-in Numbers: https://zoom.us/u/ayXQGOHVG / Meeting ID: 407 784 499 ADIGO Conference Bridge: EN: 1638 ES: 1738 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.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

renewal of .org registry
by Marita Moll April 29, 2019

April 29, 2019

Further to our discussions this week re: renewal of .org registry with removal of price cap -- it appears that there is a well organized campaign going on out there to scare people about potential rate hikes. That probably accounts for all those opposition letters we saw posted on the site that George Kirikos was referring to. See blog below: https://www.namecheap.com/blog/keep-domain-prices-in-check/?utm_source=Iter… Marita

11 26

At-Large Consolidated Policy Working Group (CPWG) Call
by ICANN Policy Calendar April 29, 2019

April 29, 2019

***** UPDATED: We will be using Zoom for this call ***** REVISED details to follow! Now on Thursday 02 May at 20:00 UTC ************************************************* The agenda (to be updated) and call details can be found at: https://community.icann.org/x/WIOGBg Zoom Room: https://icann.zoom.us/j/407784499 Zoom Dial-in Numbers: https://zoom.us/u/ayXQGOHVG / Meeting ID: 407 784 499 ADIGO Conference Bridge: EN: 1638 ES: 1738 Other toll-free numbers: https://www.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

At-Large Consolidated Policy Working Group (CPWG) Call
by ICANN Policy Calendar April 29, 2019

April 29, 2019

***** UPDATED: We will be using Zoom for this call ***** REVISED details to follow! Now on Thursday 02 May at 20:00 UTC ************************************************* The agenda (to be updated) and call details can be found at: https://community.icann.org/x/WIOGBg Zoom Room: https://icann.zoom.us/j/407784499 Zoom Dial-in Numbers: https://zoom.us/u/ayXQGOHVG / Meeting ID: 407 784 499 ADIGO Conference Bridge: EN: 1638 ES: 1738 Other toll-free numbers: https://www.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