August 2019 - CPWG - lists.icann.org

Re: [CPWG] [registration-issues-wg] NARALO Insight: DNS Over HTTPS
by Eduardo Diaz 24 Sep '19

24 Sep '19

My recommendation to the CPWG is to take this and create an advice to the Board by presenting our opinions about this technology, indicate how the end-user is affected, possible way of implementing this technology from the ICANN perspective and point out posible ICANN policies or ICANN structural changes needed to cope with its implementation. The topic is very hot and we should take the opportunity to steer this discussion within ICANN since for I have seen it can split the DNS system in many ways and capture the end-user at the application level . -ed On Wed, Jun 19, 2019 at 4:18 AM Hadia Abdelsalam Mokhtar EL miniawi < Hadia(a)tra.gov.eg> wrote: > Hi All, > > > > Going through the paper published by CENTR, depending on the means of > implementation of DoH it could directly affect end users by limiting > consumers choice and competition. Currently the users, if they wish could > change the resolvers they are using. Again depending on the means of > implementation, the browser companies, which are mainly 2-4 companies could > have control over the traffic of the users and choose which resolvers they > use. The paper raises many different questions and issues, like the > possible impact on the multistakeholder model. In my opinion it is worth > reading. > > > > Kind regards > > Hadia > > > > *From:* CPWG [mailto:cpwg-bounces@icann.org] *On Behalf Of *Hadia El > Miniawi via CPWG > *Sent:* Tuesday, June 18, 2019 2:59 PM > *To:* Eduardo Diaz; Humberto Carrasco > *Cc:* CPWG > *Subject:* Re: [CPWG] [registration-issues-wg] NARALO Insight: DNS Over > HTTPS > > > > Thank you Eduardo and Glenn. > > > > CENTR published yesterday a paper on DoH, the link is herewith > > > > CENTR Issue Paper on DNS over HTTPs > <https://centr.org/library/library/policy-document/centr-issue-paper-on-dns-…> > > > > > CENTR Issue Paper on DNS over HTTPs > > CENTR is the association of European coutry code top-level domain name > registries. CENTR’s main purpose is to pr... > > > > > > Kind regards > > Hadia > > > > On Monday, June 17, 2019, 3:37:05 PM GMT+2, Humberto Carrasco < > hcarrascob(a)gmail.com> wrote: > > > > > > Thanks a lot Eduardo!!! > > Enviado desde mi iPhone > > > El 14-06-2019, a la(s) 13:25, Eduardo Diaz <eduardodiazrivera(a)gmail.com> > escribió: > > All: > > > > Our region believes that this will become a hot topic within ICANN in the > near future. > > > > We invited Dan York from ISOC to explain this technology in layman's terms > and to answer the following questions: [1] Will this affect the end-user? > [2] Will this impact ICANN's remit?. Link to the video: > https://youtu.be/c5CXaphNxU0 (Note: there is an approximate 1 minute gap > around 9 minutes into the video. The rest of the video is OK after that). > > > > NARALO Insights are a dedicated video series on Internet Governance > concerns with a special onus on relevant and topical discussion at ICANN. > Our goal is to have community experts exchange ideas and regional > perspectives on current hot topics to augment policy discussions within > ALAC. > > > > -ed > > > > > > -- > > *NOTICE:* This email may contain information which is confidential and/or > subject to legal privilege, and is intended for the use of the named > addressee only. If you are not the intended recipient, you must not use, > disclose or copy any part of this email. If you have received this email by > mistake, please notify the sender and delete this message immediately. > > _______________________________________________ > CPWG mailing list > CPWG(a)icann.org > https://mm.icann.org/mailman/listinfo/cpwg > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos). You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. > > _______________________________________________ > CPWG mailing list > CPWG(a)icann.org > https://mm.icann.org/mailman/listinfo/cpwg > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos). You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. > > _______________________________________________ > registration-issues-wg mailing list > registration-issues-wg(a)atlarge-lists.icann.org > https://mm.icann.org/mailman/listinfo/registration-issues-wg > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos). You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. > -- *NOTICE:* This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately.

18 44

At-Large Consolidated Policy Working Group (CPWG) Call
by ICANN Policy Calendar 04 Sep '19

04 Sep '19

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 04 September 2019 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/yyz66y4y The agenda (to be updated) and call details can be found at: https://community.icann.org/x/d5DkBg Zoom Room: https://icann.zoom.us/j/410302311 / Meeting ID: 410-302-311 Real time transcription (RTT) available at: https://www.streamtext.net/player?event=ICANN [streamtext.net] [streamtext.net]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.streamtext.net_pla…> 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 [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.adigo.com_icann&d=…> 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 [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…>atlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @ [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>

3 2

Developing a Work Plan for the Evolution of ICANN’s Multistakeholder Model Webinar
by Evin Erdogdu 29 Aug '19

29 Aug '19

Dear CPWG Members, Please note the community has been invited to participate in a webinar on 11 September 2019 at 23:00 UTC or 12 September 2019 at 16:00 UTC regarding the ICANN Public Comment, "Next Steps to Improve the Effectiveness of ICANN's Multistakeholder Model". Please view details of the announcement here: https://www.icann.org/news/announcement-2-2019-08-27-en Please view the related At-Large workspace here: https://community.icann.org/x/G5DkBg? Kind Regards, Evin

1 0

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 04 September 2019 at 13:00 UTC
by ICANN At-Large Staff 28 Aug '19

28 Aug '19

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 04 September 2019 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/yyz66y4y The agenda (to be updated) and call details can be found at: https://community.icann.org/x/d5DkBg Zoom Room: https://icann.zoom.us/j/410302311 / Meeting ID: 410-302-311 Real time transcription (RTT) available at: https://www.streamtext.net/player?event=ICANN [streamtext.net] [streamtext.net]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.streamtext.net_pla…> 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 [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.adigo.com_icann&d=…> 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 [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…>atlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @ [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>

1 0

At-Large CPWG Pro... - This a process for everything we do, ...
by Nadira Al Araj (Google Docs) 27 Aug '19

27 Aug '19

Nadira Al Araj replied to a comment in the following document At-Large CPWG Process for Comment (https://docs.google.com/document/d/13EjNxqfOvXGToCWLZi9-crsUSKvqnfdW57JF9dr…) Eduardo Diaz This a process for everything we do, however, in the context of the CPWG the process should be narrowed in scope to policy issues only. So, if this graphic is going to be part of the charter I suggest that it shows only that part that pertains to the CPWG scope which is policy. Bastiaan Goslings This whole diagram looks to me like a detailed description of the 'Develop position/action in the '3. CPWG Ingest process' funnel. If so maybe an explicit referral would help to avoid confusion. Maureen Hilyard This provides good guidance for the development of how the CPWG (and its charter) fits into the At-Large PDP process. I like the expectation of involvement of the RALOs Ricardo Holmquist I have a "trouble" with this graphic, for me some of the steps are in parallel, not one after the other. For example, the RALO part does not need to be after the Penholder or the CPWG Discuss, hence narrowing its discussion, when a RALO might have a opposite position or a different view. As for the question of Ed, this graphic needs to be in conjuction with the inverted pyramid where his comment is included. Nadira Al Araj Yes, RALOS 3 boxes can be replaced by one box that says something in this regards: (RALOs are encouraged to respond to surveys developed by CPWG) Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this email because you are a participant in this thread. Change () what Google sends you. You cannot reply to this email. View At-Large CPWG Process for Comment (https://docs.google.com/document/d/13EjNxqfOvXGToCWLZi9-crsUSKvqnfdW57JF9dr…) to reply.

1 0

At-Large CPWG Pro... - This a process for everything we do, ...
by Ricardo Holmquist (Google Docs) 27 Aug '19

27 Aug '19

Ricardo Holmquist replied to a comment in the following document At-Large CPWG Process for Comment (https://docs.google.com/document/d/13EjNxqfOvXGToCWLZi9-crsUSKvqnfdW57JF9dr…) Eduardo Diaz This a process for everything we do, however, in the context of the CPWG the process should be narrowed in scope to policy issues only. So, if this graphic is going to be part of the charter I suggest that it shows only that part that pertains to the CPWG scope which is policy. Bastiaan Goslings This whole diagram looks to me like a detailed description of the 'Develop position/action in the '3. CPWG Ingest process' funnel. If so maybe an explicit referral would help to avoid confusion. Maureen Hilyard This provides good guidance for the development of how the CPWG (and its charter) fits into the At-Large PDP process. I like the expectation of involvement of the RALOs Ricardo Holmquist I have a "trouble" with this graphic, for me some of the steps are in parallel, not one after the other. For example, the RALO part does not need to be after the Penholder or the CPWG Discuss, hence narrowing its discussion, when a RALO might have a opposite position or a different view. As for the question of Ed, this graphic needs to be in conjuction with the inverted pyramid where his comment is included. Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this email because you are a participant in this thread. Change () what Google sends you. You cannot reply to this email. View At-Large CPWG Process for Comment (https://docs.google.com/document/d/13EjNxqfOvXGToCWLZi9-crsUSKvqnfdW57JF9dr…) to reply.

1 0

Subsequent Procedures Update: IDNs, snapshot as at 26 Aug 2019
by Justine Chew 27 Aug '19

27 Aug '19

Dear all, Reference is made to the *SubPro Updates workspace <https://community.icann.org/x/6a_jBg>*. The Subsequent Procedures PDP WG is expected to commence during its call of 27 Aug 3:00 UTC, its deliberation on the public comments received to its Initial Report on the topic of Internationalized Domain Names (IDNs). So, here is a *snapshot on the topic of IDNs as at 26 Aug* <https://community.icann.org/download/attachments/111390697/01.%20SubPro%20I…> . While no CCT recommendation was applied to this topic, I hope colleagues in the *At-Large IDN Policy Working* would be be able to consider and provide feedback to the outstanding items/comments made by other stakeholder groups (if necessary). I wish you all a pleasant week ahead. Thank you, Justine Chew -----

2 2

Fwd: FOLLOWING UP: ICANN66 & DNS Abuse
by Maureen Hilyard 26 Aug '19

26 Aug '19

---------- Forwarded message --------- From: Mary Wong <mary.wong(a)icann.org> Date: Mon, 26 Aug 2019, 1:34 PM Subject: FOLLOWING UP: ICANN66 & DNS Abuse To: jrobinson(a)afilias.info <jrobinson(a)afilias.info>, Manal Ismail < manal(a)tra.gov.eg>, Steve DelBianco <sdelbianco(a)netchoice.org>, Cathrin Bauer-Bulst <Cathrin.BAUER-BULST(a)ec.europa.eu>, Kapin, Laureen < LKAPIN(a)ftc.gov>, Maureen Hilyard <maureen.hilyard(a)gmail.com>, Mark Svancarek (CELA) <marksv(a)microsoft.com>, Romero, Gonzalo < gonzalo(a)cointernet.com.co>, Rod Rasmussen <rod(a)rodrasmussen.com>, Julie Hammer @Bigpond <julie.hammer(a)bigpond.com>, Brian Winterfeldt <Brian(a)winterfeldt.law>, gbunton(a)tucows.com <gbunton(a)tucows.com> Cc: Keith Drazek <kdrazek(a)verisign.com>, Austin, Donna <Donna.Austin(a)team.neustar>, Alejandra Reynoso <alejandra.reynoso(a)cctld.gt>, Carlos Reyes <carlos.reyes(a)icann.org>, Tanzanica S. King < tanzanica.king(a)icann.org>, Zoe Bonython <secretariat(a)icannregistrars.org>, secretariat(a)rysg.info <secretariat(a)rysg.info>, Steve Sheng < steve.sheng(a)icann.org>, Joke Braeken <joke.braeken(a)icann.org>, Chantelle Doerksen <chantelle.doerksen(a)icann.org>, Fabien Betremieux < fabien.betremieux(a)icann.org>, Robert Hoggarth <robert.hoggarth(a)icann.org>, Heidi Ullrich <Heidi.Ullrich(a)icann.org> Dear all, I write in relation to the agreed pre-ICANN66 informational webinar (to be scheduled during Prep Week, which runs from 14-17 October) and the plenary session to be held during the ICANN66 Meeting itself, on DNS Abuse. I’ve included those who staff recalls from the ALAC, BC, ccNSO, GAC, IPC, RrSG, RySG and SSAC had expressed interest in participating in and/or supporting these sessions, but please let me know if I have missed anyone (or added anyone who doesn’t wish to be part of the planning process!) As this is the first time that we will be doing a pre-Meeting informational webinar, followed by the actual plenary session, and as we have multiple community groups involved in planning and executing these sessions, I hope it will be helpful to suggest that this group begin to discuss the following points: 1. *What should the pre-Meeting informational webinar cover, and what should the Montreal plenary session cover?* - You can find the topic descriptions as submitted here: https://docs.google.com/spreadsheets/d/1cVxmAjNoX77RSOg59-rdM4DMjFFwfnIxx3W…. - As submitted by the GAC: *“This session approaches the topic of DNS Abuse by first looking at the key practical issues followed by a facilitated community discussion. DNS Abuse takes a variety of forms, and the session will explore – using definitions and examples – what type of conduct has traditionally been labelled “DNS Abuse”, an important precursor to arriving at a joint definition of DNS Abuse. In a second step, the session will explore how registry and registrar operators mitigate and address DNS Abuse/security threats, by looking at examples of prevention and mitigation measures. Following that, the session will provide a gap analysis of issues left to address – including possible challenges to prevention and mitigation measures. This session will include discussion of how evolving legal and regulatory frameworks put DNS Abuse investigations and mitigations performed by 3rd parties at risk, how aware lawmakers and regulators of these risks, how governments are working together to bring clarity to these issues, and actions the ICANN community can take based on the experience it has accumulated on this matter over time and most recently through several processes including the CCT Review, the Domain Abuse Activity Reporting and the DNS Infrastructure Abuse Audits.*” - As submitted by the RySG: *“This session approaches the currently "hot topic" of DNS Abuse by first looking at the key practical issues followed by a facilitated community discussion. First, we'll take a focused look at ICANN's bylaws and remit and next, explore how registry and registrar operators mitigate and address DNS Abuse/security threats in that context. Third, the community will be invited to discuss issues arising and proposed solutions.”* 1. *Assuming that all the interested groups will wish to be involved in both the webinar and plenary session, how shall we proceed in terms of who will do what for both, and in light of the recent open letter to the ICANN community from the RySG (reattached for your convenience)?* Staff will be happy to organize a call to discuss these preliminary matters; we just thought it may be helpful to kickstart the discussions by connecting everyone via email. For your information, and as has been the practice with previous cross-community and high-interest topics, an ICANN Org Senior Executive will be tasked with assisting you with your planning, with relevant Meetings and Policy team staff to help manage logistics and overall session management (including a proposed date and time for the pre-Meeting webinar). I will get back to you with further details very shortly. Thank you! Cheers Mary

1 0

At-Large CPWG Pro... - This a process for everything we do, ...
by Maureen Hilyard (Google Docs) 26 Aug '19

26 Aug '19

Maureen Hilyard replied to a comment in the following document At-Large CPWG Process for Comment (https://docs.google.com/document/d/13EjNxqfOvXGToCWLZi9-crsUSKvqnfdW57JF9dr…) Eduardo Diaz This a process for everything we do, however, in the context of the CPWG the process should be narrowed in scope to policy issues only. So, if this graphic is going to be part of the charter I suggest that it shows only that part that pertains to the CPWG scope which is policy. Bastiaan Goslings This whole diagram looks to me like a detailed description of the 'Develop position/action in the '3. CPWG Ingest process' funnel. If so maybe an explicit referral would help to avoid confusion. Maureen Hilyard This provides good guidance for the development of how the CPWG (and its charter) fits into the At-Large PDP process. I like the expectation of involvement of the RALOs Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this email because you are a participant in this thread. Change () what Google sends you. You cannot reply to this email. View At-Large CPWG Process for Comment (https://docs.google.com/document/d/13EjNxqfOvXGToCWLZi9-crsUSKvqnfdW57JF9dr…) to reply.

1 0

Fwd: [Gnso-newgtld-wg] SLA Monitoring (SLAM) Statistics
by Carlton Samuels 26 Aug '19

26 Aug '19

Without prejudice to "collective recollection", my only question is why should information on PDT and via a contractor be 'anecdotal'? CAS ---------- Forwarded message --------- From: Steve Chan <steve.chan(a)icann.org> Date: Fri, 23 Aug 2019, 4:26 pm Subject: [Gnso-newgtld-wg] SLA Monitoring (SLAM) Statistics To: gnso-newgtld-wg(a)icann.org <gnso-newgtld-wg(a)icann.org> Dear WG Members, During the course of discussions, particularly as it relates to RSP pre-approval and most recently, registrant protections, WG members have asked for updated statistics on the Service Level Agreement (SLA) Monitoring program within ICANN. Attached, please find the latest report. A few contextual notes that may help your digestion of this information: - The statistics are on a per TLD basis for each month. - In some months, there are spikes in the number of DNS and RDDS failures. Usually, these spikes are a caused by a failure in an RSP that serves a large number of TLDs. - On the 4ht slide, you will see several failures that reached EBERO thresholds but in the vast majority of cases, the failures did not trigger an EBERO event. As has been shared previously, this is likely because ICANN Org worked with the registry to resolve the event and/or there were minimal domains under management. In addition, members asked for information around Pre-Delegation Testing (PDT), which I believe is now an element of the broader Registry System Testing (RST). Please see the below response from GDD: “Additionally, on the PDT/RST side - ICANN org has neither compiled nor published summary data regarding Pre-Delegation Test results from the 2012 round. Testing data was tracked and managed by IIS, the pre-delegation testing vendor. Such testing data, was not provided to ICANN org as part of the service delivery efforts. However, based on ICANN org management of the Pre-Delegation testing processing since 2012, we can share anecdotal information based on the collective recollection of org and vendor staff. These anecdotal results includes: 1. Most TLDs received follow-up questions regarding their PDT testing submission (similar to initial evaluation Clarifying Questions) 2. Approximately one quarter of TLDs tested required extended testing beyond the standard 2 to 3 week testing cycle. Some of these tests extended up to 12 weeks. 3. Based on the flexibility of extended testing and the assistance provided by the PDT vendor to TLD operators, fewer than 10 TLDs required a second full PDT testing cycle.“ Hopefully you all find this information helpful. If you have questions or concerns, especially for GDD, please let us know. Best, Steve *Steven Chan* Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410

1 0