Concur Sent from my Pixel 3XL John Laprise, Ph.D. On Sun, May 5, 2019, 9:36 AM DANIEL NANGHAKA <dndannang@gmail.com> wrote:

Hi Maureen,

Thanks for your email.

I agreement to vanda, ATRT3 has just kicked off and we are gathering respective data.

I appreciate Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures as it is partinent to policy discussion and update. Since the EPDP phase 2 has not yet started i think it would not be necessary at the moment.

Otherwise I am in agreement with the listing as is in the discussion email sent.

Daniel K.Nanghaka

ᐧ

On Sun, 5 May 2019 at 06:34, Maureen Hilyard <maureen.hilyard@gmail.com> wrote:

...

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)

1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures. Combine 1.1, 1.2 and 1.3 into one session 1.1 Combatting Abuse with GDPR 1.2 Privacy-Proxy Implementation 1.3 Across Field Validation 2 EPDP Phase 2 / Uniform Access Model REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal

3 Sessions that are merely updates can be provided as a pre-meeting webinar. 3.1 ATRT3 3.2 SSR-2 3.3 NomCom Review 4 Future of Multistakeholder Model Governance Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included. 5 Enhance Effectiveness of Specific Review Recommedations and their Implementation This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included 6 Universal Acceptance There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues. 7 DNS over HTTPS (DoH) Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE. 8 GNSO proposing these topics for one CC session 8.1 Rules for Uniform Domain Name Dispute Resolution Policy 8.2 Uniform Rapid Suspension system (URS) rules 8.3 WHOIS Data Reminder Policy 8.4 Transfer Policy 8.5 Transfer Dispute Resolution Policy 8.6 Across Field Validation 8.7 Process for handing RAA Data Retention Waiver Requests 8.8 Registration Data Access Protocol (RDAP) 8.9 WHOIS Accuracy Reporting System (ARS) 8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Nanghaka Daniel K. Executive Director - ILICIT Africa/ Chair - Outreach and Engagement WG (ICANN At-Large)/ former Chair - FOSSFA / Geo4Africa Lead / Organising Team - FOSS4G2018 Mobile +256 772 898298 (Uganda) Skype: daniel.nanghaka

----------------------------------------- *"Working for Africa" * -----------------------------------------

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

Concur too. -ed On Sun, May 5, 2019 at 10:36 AM DANIEL NANGHAKA <dndannang@gmail.com> wrote:

Hi Maureen,

Thanks for your email.

I agreement to vanda, ATRT3 has just kicked off and we are gathering respective data.

I appreciate Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures as it is partinent to policy discussion and update. Since the EPDP phase 2 has not yet started i think it would not be necessary at the moment.

Otherwise I am in agreement with the listing as is in the discussion email sent.

Daniel K.Nanghaka

ᐧ

On Sun, 5 May 2019 at 06:34, Maureen Hilyard <maureen.hilyard@gmail.com> wrote:

...

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)

1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures. Combine 1.1, 1.2 and 1.3 into one session 1.1 Combatting Abuse with GDPR 1.2 Privacy-Proxy Implementation 1.3 Across Field Validation 2 EPDP Phase 2 / Uniform Access Model REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal

3 Sessions that are merely updates can be provided as a pre-meeting webinar. 3.1 ATRT3 3.2 SSR-2 3.3 NomCom Review 4 Future of Multistakeholder Model Governance Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included. 5 Enhance Effectiveness of Specific Review Recommedations and their Implementation This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included 6 Universal Acceptance There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues. 7 DNS over HTTPS (DoH) Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE. 8 GNSO proposing these topics for one CC session 8.1 Rules for Uniform Domain Name Dispute Resolution Policy 8.2 Uniform Rapid Suspension system (URS) rules 8.3 WHOIS Data Reminder Policy 8.4 Transfer Policy 8.5 Transfer Dispute Resolution Policy 8.6 Across Field Validation 8.7 Process for handing RAA Data Retention Waiver Requests 8.8 Registration Data Access Protocol (RDAP) 8.9 WHOIS Accuracy Reporting System (ARS) 8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Nanghaka Daniel K. Executive Director - ILICIT Africa/ Chair - Outreach and Engagement WG (ICANN At-Large)/ former Chair - FOSSFA / Geo4Africa Lead / Organising Team - FOSS4G2018 Mobile +256 772 898298 (Uganda) Skype: daniel.nanghaka

----------------------------------------- *"Working for Africa" * -----------------------------------------

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- *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.

Agree this is of increasing interest to the group ________________________________ From: ALAC <alac-bounces@atlarge-lists.icann.org> on behalf of Sebastien Bachollet <sebicann@bachollet.fr> Sent: Sunday, May 5, 2019 2:35 PM To: ALAC; Maureen Hilyard Subject: Re: [ALAC] The consolidated approach proposed by Keith Drazek Dear ALAC Members and Maureen, I think it is very important to have a session in Marrakech about DoH. It is important for end-users and important to keep Internet open to all. All the best SeB Le 5 mai 2019 à 18:16, Eduardo Diaz <eduardodiazrivera@gmail.com<mailto:eduardodiazrivera@gmail.com>> a écrit : Concur too. -ed On Sun, May 5, 2019 at 10:36 AM DANIEL NANGHAKA <dndannang@gmail.com<mailto:dndannang@gmail.com>> wrote: Hi Maureen, Thanks for your email. I agreement to vanda, ATRT3 has just kicked off and we are gathering respective data. I appreciate Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures as it is partinent to policy discussion and update. Since the EPDP phase 2 has not yet started i think it would not be necessary at the moment. Otherwise I am in agreement with the listing as is in the discussion email sent. Daniel K.Nanghaka [https://mailfoogae.appspot.com/t?sender=aZG5kYW5uYW5nQGdtYWlsLmNvbQ%3D%3D&type=zerocontent&guid=0fdf83af-0ee6-4a2c-bac1-ae9787104bec]ᐧ On Sun, 5 May 2019 at 06:34, Maureen Hilyard <maureen.hilyard@gmail.com<mailto:maureen.hilyard@gmail.com>> wrote: Hi all I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech) 1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures. Combine 1.1, 1.2 and 1.3 into one session 1.1 Combatting Abuse with GDPR 1.2 Privacy-Proxy Implementation 1.3 Across Field Validation 2 EPDP Phase 2 / Uniform Access Model REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal 3 Sessions that are merely updates can be provided as a pre-meeting webinar. 3.1 ATRT3 3.2 SSR-2 3.3 NomCom Review 4 Future of Multistakeholder Model Governance Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included. 5 Enhance Effectiveness of Specific Review Recommedations and their Implementation This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included 6 Universal Acceptance There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues. 7 DNS over HTTPS (DoH) Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE. 8 GNSO proposing these topics for one CC session 8.1 Rules for Uniform Domain Name Dispute Resolution Policy 8.2 Uniform Rapid Suspension system (URS) rules 8.3 WHOIS Data Reminder Policy 8.4 Transfer Policy 8.5 Transfer Dispute Resolution Policy 8.6 Across Field Validation 8.7 Process for handing RAA Data Retention Waiver Requests 8.8 Registration Data Access Protocol (RDAP) 8.9 WHOIS Accuracy Reporting System (ARS) 8.10 Thick WHOIS Transition policy for .com, .net, .jobs Comments please Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org<mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org<http://www.atlarge.icann.org/> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) -- Nanghaka Daniel K. Executive Director - ILICIT Africa/ Chair - Outreach and Engagement WG (ICANN At-Large)/ former Chair - FOSSFA / Geo4Africa Lead / Organising Team - FOSS4G2018 Mobile +256 772 898298 (Uganda) Skype: daniel.nanghaka ----------------------------------------- "Working for Africa" ----------------------------------------- _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org<mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org<http://www.atlarge.icann.org/> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) -- 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. _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org<mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

Hi Maureen, Thank you for your email. I do agree with all the suggestions, however I tend to find DoH as an upcoming topic that had not been discussed yet specially from a policy point of view, I would keep it. Also I tend to find the proposed topics by the GNSO as too many for one session. Some of the proposed topics could be a topic for a whole session like ARS and RDAP. Kindest Regards Hadia From: ALAC [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Maureen Hilyard Sent: Monday, May 06, 2019 12:51 PM To: ALAC Subject: Re: [ALAC] The consolidated approach proposed by Keith Drazek Thank you for those who have given some initial feedback. Following a final decision at our next CPWG meeting I'd like to pass this on. While noting that Keith's suggested consolidated sessions were a means of covering what was considered important to the GNSO community, if we think that something else needs to be added or deleted, then we can pass this onto the SO-AC decision-makers. Vanda - I think that adding Auction Proceeds is an important update that people should hear about. UA got the go ahead in Keith's model Sebastian and Jonathan - DoH - an interesting technical topic (and way over my head) but happy to pass it on as an important session if given consensus. If other groups aren't interested, then could we hold a session on it of our own to give us all some understanding of what it means to us as end-users? Thanks to Dan, John and Eduardo for their prompt agreements. More suggestions or agreements welcome. Maureen On Sat, May 4, 2019 at 5:33 PM Maureen Hilyard <maureen.hilyard@gmail.com<mailto:maureen.hilyard@gmail.com>> wrote: Hi all I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech) 1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures. Combine 1.1, 1.2 and 1.3 into one session 1.1 Combatting Abuse with GDPR 1.2 Privacy-Proxy Implementation 1.3 Across Field Validation 2 EPDP Phase 2 / Uniform Access Model REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal 3 Sessions that are merely updates can be provided as a pre-meeting webinar. 3.1 ATRT3 3.2 SSR-2 3.3 NomCom Review 4 Future of Multistakeholder Model Governance Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included. 5 Enhance Effectiveness of Specific Review Recommedations and their Implementation This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included 6 Universal Acceptance There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues. 7 DNS over HTTPS (DoH) Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE. 8 GNSO proposing these topics for one CC session 8.1 Rules for Uniform Domain Name Dispute Resolution Policy 8.2 Uniform Rapid Suspension system (URS) rules 8.3 WHOIS Data Reminder Policy 8.4 Transfer Policy 8.5 Transfer Dispute Resolution Policy 8.6 Across Field Validation 8.7 Process for handing RAA Data Retention Waiver Requests 8.8 Registration Data Access Protocol (RDAP) 8.9 WHOIS Accuracy Reporting System (ARS) 8.10 Thick WHOIS Transition policy for .com, .net, .jobs Comments please Maureen

DoH is not at all today a technical question (even if we need to understand the technology). It is a huge political issues particularly to all Internet users. SeB Envoyé de mon iPhone

Le 6 mai 2019 à 13:13, Seun Ojedeji <seun.ojedeji@gmail.com> a écrit :

Hello Maureen,

I assume the text in blue are your recommendations? if yes then am fine with the suggestion, if there is an intention to further reduce the list, my preference of item that I think should be retained are 4, 1, 5 in that order before others can then follow. The DoH may be better suited for the techday.

Regards

...

On Sun, May 5, 2019 at 4:34 AM Maureen Hilyard <maureen.hilyard@gmail.com> wrote: Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)

1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures. Combine 1.1, 1.2 and 1.3 into one session 1.1 Combatting Abuse with GDPR 1.2 Privacy-Proxy Implementation 1.3 Across Field Validation 2 EPDP Phase 2 / Uniform Access Model REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal

3 Sessions that are merely updates can be provided as a pre-meeting webinar. 3.1 ATRT3 3.2 SSR-2 3.3 NomCom Review 4 Future of Multistakeholder Model Governance Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included. 5 Enhance Effectiveness of Specific Review Recommedations and their Implementation This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included 6 Universal Acceptance There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues. 7 DNS over HTTPS (DoH) Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE. 8 GNSO proposing these topics for one CC session 8.1 Rules for Uniform Domain Name Dispute Resolution Policy 8.2 Uniform Rapid Suspension system (URS) rules 8.3 WHOIS Data Reminder Policy 8.4 Transfer Policy 8.5 Transfer Dispute Resolution Policy 8.6 Across Field Validation 8.7 Process for handing RAA Data Retention Waiver Requests 8.8 Registration Data Access Protocol (RDAP) 8.9 WHOIS Accuracy Reporting System (ARS) 8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- ------------------------------------------------------------------------ Seun Ojedeji, Federal University Oye-Ekiti web: http://www.fuoye.edu.ng Mobile: +2348035233535 alt email: seun.ojedeji@fuoye.edu.ng

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

Hello Olivier, I hear you and am looking forward to more details on how that relegation of ICANN could happen in practice.....am sure not against having DoH on HIT but I hope we will first ensure to give end-users the technological details of DoH(in a layman way) before we move on to its political implications as I certainly don't think DoH threatens ICANN's root management role as you seem to suggest; perhaps for now one can say it could move the direction of a few USDs ;-) Regards On Mon, May 6, 2019 at 1:18 PM Olivier MJ Crépin-Leblond <ocl@gih.com> wrote:

Yup -- in DoH think about a naming system solely run and controlled by the cloud providers that have signed up for DoH. That can easily replace the DNS altogether and relegate ICANN to a glitch in history. Kindest regards,

Olivier

On 06/05/2019 13:39, Sebastien Bachollet wrote:

DoH is not at all today a technical question (even if we need to understand the technology). It is a huge political issues particularly to all Internet users. SeB

Envoyé de mon iPhone

Le 6 mai 2019 à 13:13, Seun Ojedeji <seun.ojedeji@gmail.com> a écrit :

Hello Maureen,

I assume the text in blue are your recommendations? if yes then am fine with the suggestion, if there is an intention to further reduce the list, my preference of item that I think should be retained are 4, 1, 5 in that order before others can then follow. The DoH may be better suited for the techday.

Regards

On Sun, May 5, 2019 at 4:34 AM Maureen Hilyard <maureen.hilyard@gmail.com> wrote:

...

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)

1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures.

Combine 1.1, 1.2 and 1.3 into one session

1.1 Combatting Abuse with GDPR

1.2 Privacy-Proxy Implementation

1.3 Across Field Validation

2 EPDP Phase 2 / Uniform Access Model

REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal

3 Sessions that are merely updates can be provided as a pre-meeting webinar.

3.1 ATRT3

3.2 SSR-2

3.3 NomCom Review

4 Future of Multistakeholder Model Governance

Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included.

5 Enhance Effectiveness of Specific Review Recommedations and their Implementation

This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included

6 Universal Acceptance

There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues.

7 DNS over HTTPS (DoH)

Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE.

8 GNSO proposing these topics for one CC session

8.1 Rules for Uniform Domain Name Dispute Resolution Policy

8.2 Uniform Rapid Suspension system (URS) rules

8.3 WHOIS Data Reminder Policy

8.4 Transfer Policy

8.5 Transfer Dispute Resolution Policy

8.6 Across Field Validation

8.7 Process for handing RAA Data Retention Waiver Requests

8.8 Registration Data Access Protocol (RDAP)

8.9 WHOIS Accuracy Reporting System (ARS)

8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- ------------------------------------------------------------------------

*Seun Ojedeji, Federal University Oye-Ekiti web: http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile: +2348035233535 **alt email: <http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <seun.ojedeji@fuoye.edu.ng>*

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

_______________________________________________ ALAC mailing listALAC@atlarge-lists.icann.orghttps://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html

-- ------------------------------------------------------------------------ *Seun Ojedeji,Federal University Oye-Ekitiweb: http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile: +2348035233535**alt email: <http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <seun.ojedeji@fuoye.edu.ng>* Bringing another down does not take you up - think about your action!

DOH is multi faceted. First of all, it has direct impact on end users. Today it is not default, but available option and we don't know how it evolves. There are pros and cons. Super concentration of DNS control and data in the hands of internet behemoths from one side. Also this technology bypasses DNS proxies sometimes assigned by state regulators in order to control and limit access to some resources. It is definitely interesting topic. Related article: https://www.forbes.com/sites/zakdoffman/2019/04/22/crisis-as-changes-to-goog... --andrei пн, 6 мая 2019 г. в 16:55, Satish Babu via ALAC < alac@atlarge-lists.icann.org>:

I'd be curious to know what makes DoH more attractive in comparison with the existing DNS service in order for it to completely displace DNS.

The key question is if DoH will remain a niche technology (similar to first- and second-generation DNS substitutes ranging from TOR, FreeNet, and I2P to the very new Ethereum Name Service, all of which are likely to remain niche), or if it's likely to scale up as a direct (and effective) substitute to the generic DNS, noting that it does avoid several security pitfalls (including eavesdropping/tracking, man-in-the-middle etc).

Also, from an Internet Consolidation perspective, DoH appears to make things even more centralized...not necessarily a good thing for end-users.

satish

On Mon, May 6, 2019 at 6:51 PM Seun Ojedeji <seun.ojedeji@gmail.com> wrote:

...

Hello Olivier,

I hear you and am looking forward to more details on how that relegation of ICANN could happen in practice.....am sure not against having DoH on HIT but I hope we will first ensure to give end-users the technological details of DoH(in a layman way) before we move on to its political implications as I certainly don't think DoH threatens ICANN's root management role as you seem to suggest; perhaps for now one can say it could move the direction of a few USDs ;-)

Regards

On Mon, May 6, 2019 at 1:18 PM Olivier MJ Crépin-Leblond <ocl@gih.com> wrote:

...

Yup -- in DoH think about a naming system solely run and controlled by the cloud providers that have signed up for DoH. That can easily replace the DNS altogether and relegate ICANN to a glitch in history. Kindest regards,

Olivier

On 06/05/2019 13:39, Sebastien Bachollet wrote:

DoH is not at all today a technical question (even if we need to understand the technology). It is a huge political issues particularly to all Internet users. SeB

Envoyé de mon iPhone

Le 6 mai 2019 à 13:13, Seun Ojedeji <seun.ojedeji@gmail.com> a écrit :

Hello Maureen,

I assume the text in blue are your recommendations? if yes then am fine with the suggestion, if there is an intention to further reduce the list, my preference of item that I think should be retained are 4, 1, 5 in that order before others can then follow. The DoH may be better suited for the techday.

Regards

On Sun, May 5, 2019 at 4:34 AM Maureen Hilyard < maureen.hilyard@gmail.com> wrote:

...

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)

1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures.

Combine 1.1, 1.2 and 1.3 into one session

1.1 Combatting Abuse with GDPR

1.2 Privacy-Proxy Implementation

1.3 Across Field Validation

2 EPDP Phase 2 / Uniform Access Model

REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal

3 Sessions that are merely updates can be provided as a pre-meeting webinar.

3.1 ATRT3

3.2 SSR-2

3.3 NomCom Review

4 Future of Multistakeholder Model Governance

Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included.

5 Enhance Effectiveness of Specific Review Recommedations and their Implementation

This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included

6 Universal Acceptance

There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues.

7 DNS over HTTPS (DoH)

Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE.

8 GNSO proposing these topics for one CC session

8.1 Rules for Uniform Domain Name Dispute Resolution Policy

8.2 Uniform Rapid Suspension system (URS) rules

8.3 WHOIS Data Reminder Policy

8.4 Transfer Policy

8.5 Transfer Dispute Resolution Policy

8.6 Across Field Validation

8.7 Process for handing RAA Data Retention Waiver Requests

8.8 Registration Data Access Protocol (RDAP)

8.9 WHOIS Accuracy Reporting System (ARS)

8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- ------------------------------------------------------------------------

*Seun Ojedeji, Federal University Oye-Ekiti web: http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile: +2348035233535 **alt email: <http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <seun.ojedeji@fuoye.edu.ng>*

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

_______________________________________________ ALAC mailing listALAC@atlarge-lists.icann.orghttps://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html

-- ------------------------------------------------------------------------

*Seun Ojedeji,Federal University Oye-Ekitiweb: http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile: +2348035233535**alt email: <http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <seun.ojedeji@fuoye.edu.ng>*

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Andrey Kolesnikov RIPN.NET

Thanks very much, Olivier and Andrei, for the technical details. A follow-up comment: Many regulators and Governments are not likely to be happy with DoH/DoT, as these will undermine DNS-based site blocking that many Governments currently use. I wonder how they will respond, and if this is likely to impede scaling of these technologies (or if they can legally block these). satish On Mon, May 6, 2019 at 9:17 PM Olivier MJ Crépin-Leblond <ocl@gih.com> wrote:

Dear Satish,

DoH is attractive to some organisations because it is the missing piece of the puzzle that algorithms could use to learn more about you. Yes, it is a niche technology, but today the "owners" of the metadata of all of the addresses that you go to, derived from DNS queries, is actually distributed. The Root operators know what TLDs you use most. An ISP that runs the local resolver knows what addresses you access. In fact, anyone can scan and eavesdrop on your DNS queries to derive meta-information about your browsing habits. DoH closes the door to this third party meta-information gathering, to bring it to a closed group of players that already have cookies, IP addresses, your log-in account, email, and any other services which you use on the cloud with the meta-data of all of your DNS enquiries. It is one more piece of the puzzle towards tracking you. In the future it would also be possible to, by the flick of a switch, switch off the DNS queries and keep solely to the DoH queries based on a snapshot of the Internet's addresses. The difference between this and other systems is that alternative roots required an intervention from the user to switch to an alternative root, which was a less stable system than the DNS's 13 roots. Plus, alternative DNSes did not have that essential element of providing so much data for a single entity thus there was no commercial drive to go that way. DoH has all the elements for a perfect storm, from industry consolidation to generation of more meta-data in-house, value creation through better tracking and big players already really interested in implementing it. That's the threat and that's why it is important. Kindest regards,

Olivier

On 06/05/2019 15:54, Satish Babu wrote:

I'd be curious to know what makes DoH more attractive in comparison with the existing DNS service in order for it to completely displace DNS.

The key question is if DoH will remain a niche technology (similar to first- and second-generation DNS substitutes ranging from TOR, FreeNet, and I2P to the very new Ethereum Name Service, all of which are likely to remain niche), or if it's likely to scale up as a direct (and effective) substitute to the generic DNS, noting that it does avoid several security pitfalls (including eavesdropping/tracking, man-in-the-middle etc).

Also, from an Internet Consolidation perspective, DoH appears to make things even more centralized...not necessarily a good thing for end-users.

satish

On Mon, May 6, 2019 at 6:51 PM Seun Ojedeji <seun.ojedeji@gmail.com> wrote:

...

Hello Olivier,

I hear you and am looking forward to more details on how that relegation of ICANN could happen in practice.....am sure not against having DoH on HIT but I hope we will first ensure to give end-users the technological details of DoH(in a layman way) before we move on to its political implications as I certainly don't think DoH threatens ICANN's root management role as you seem to suggest; perhaps for now one can say it could move the direction of a few USDs ;-)

Regards

On Mon, May 6, 2019 at 1:18 PM Olivier MJ Crépin-Leblond <ocl@gih.com> wrote:

...

Yup -- in DoH think about a naming system solely run and controlled by the cloud providers that have signed up for DoH. That can easily replace the DNS altogether and relegate ICANN to a glitch in history. Kindest regards,

Olivier

On 06/05/2019 13:39, Sebastien Bachollet wrote:

DoH is not at all today a technical question (even if we need to understand the technology). It is a huge political issues particularly to all Internet users. SeB

Envoyé de mon iPhone

Le 6 mai 2019 à 13:13, Seun Ojedeji <seun.ojedeji@gmail.com> a écrit :

Hello Maureen,

I assume the text in blue are your recommendations? if yes then am fine with the suggestion, if there is an intention to further reduce the list, my preference of item that I think should be retained are 4, 1, 5 in that order before others can then follow. The DoH may be better suited for the techday.

Regards

On Sun, May 5, 2019 at 4:34 AM Maureen Hilyard < maureen.hilyard@gmail.com> wrote:

...

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)

1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures.

Combine 1.1, 1.2 and 1.3 into one session

1.1 Combatting Abuse with GDPR

1.2 Privacy-Proxy Implementation

1.3 Across Field Validation

2 EPDP Phase 2 / Uniform Access Model

REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal

3 Sessions that are merely updates can be provided as a pre-meeting webinar.

3.1 ATRT3

3.2 SSR-2

3.3 NomCom Review

4 Future of Multistakeholder Model Governance

Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included.

5 Enhance Effectiveness of Specific Review Recommedations and their Implementation

This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included

6 Universal Acceptance

There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues.

7 DNS over HTTPS (DoH)

Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE.

8 GNSO proposing these topics for one CC session

8.1 Rules for Uniform Domain Name Dispute Resolution Policy

8.2 Uniform Rapid Suspension system (URS) rules

8.3 WHOIS Data Reminder Policy

8.4 Transfer Policy

8.5 Transfer Dispute Resolution Policy

8.6 Across Field Validation

8.7 Process for handing RAA Data Retention Waiver Requests

8.8 Registration Data Access Protocol (RDAP)

8.9 WHOIS Accuracy Reporting System (ARS)

8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- ------------------------------------------------------------------------

*Seun Ojedeji, Federal University Oye-Ekiti web: http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile: +2348035233535 **alt email: <http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <seun.ojedeji@fuoye.edu.ng>*

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

_______________________________________________ ALAC mailing listALAC@atlarge-lists.icann.orghttps://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html

-- ------------------------------------------------------------------------

*Seun Ojedeji, Federal University Oye-Ekiti web: http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile: +2348035233535 **alt email: <http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <seun.ojedeji@fuoye.edu.ng>*

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html

Dear All, I can understand the cloud aspect - due to the architectural landscape of the software-defined networking (SDN), the private entities like the cloud infrastructure providers would try to sell or offer their clients DoH/DoT as an option-based solutions; whether to choose 1) encrypted 2) unencrypted traffic to the internal or external HTTPS endpoints. That said, the big players might come out to say to the governments that, with DoH/DoT there is a guarantee of a better percentage of end-to-end information assurance over the mechanism offers by the DNSSEC. Regards, Wale On Mon, May 6, 2019 at 7:04 PM Olivier MJ Crépin-Leblond <ocl@gih.com> wrote:

Dear Satish,

you've hit the nail right on the head. This is likely to turn into another round of private sector vs. government. The trouble is that one of the ways that this could be accepted by these governments is by having these companies act as the censor. History is showing us that the Private sector is happy to oblige under certain conditions. Kindest regards,

Olivier

On 06/05/2019 18:04, Satish Babu wrote:

Thanks very much, Olivier and Andrei, for the technical details.

A follow-up comment: Many regulators and Governments are not likely to be happy with DoH/DoT, as these will undermine DNS-based site blocking that many Governments currently use. I wonder how they will respond, and if this is likely to impede scaling of these technologies (or if they can legally block these).

satish

On Mon, May 6, 2019 at 9:17 PM Olivier MJ Crépin-Leblond <ocl@gih.com> wrote:

...

Dear Satish,

DoH is attractive to some organisations because it is the missing piece of the puzzle that algorithms could use to learn more about you. Yes, it is a niche technology, but today the "owners" of the metadata of all of the addresses that you go to, derived from DNS queries, is actually distributed. The Root operators know what TLDs you use most. An ISP that runs the local resolver knows what addresses you access. In fact, anyone can scan and eavesdrop on your DNS queries to derive meta-information about your browsing habits. DoH closes the door to this third party meta-information gathering, to bring it to a closed group of players that already have cookies, IP addresses, your log-in account, email, and any other services which you use on the cloud with the meta-data of all of your DNS enquiries. It is one more piece of the puzzle towards tracking you. In the future it would also be possible to, by the flick of a switch, switch off the DNS queries and keep solely to the DoH queries based on a snapshot of the Internet's addresses. The difference between this and other systems is that alternative roots required an intervention from the user to switch to an alternative root, which was a less stable system than the DNS's 13 roots. Plus, alternative DNSes did not have that essential element of providing so much data for a single entity thus there was no commercial drive to go that way. DoH has all the elements for a perfect storm, from industry consolidation to generation of more meta-data in-house, value creation through better tracking and big players already really interested in implementing it. That's the threat and that's why it is important. Kindest regards,

Olivier

On 06/05/2019 15:54, Satish Babu wrote:

I'd be curious to know what makes DoH more attractive in comparison with the existing DNS service in order for it to completely displace DNS.

The key question is if DoH will remain a niche technology (similar to first- and second-generation DNS substitutes ranging from TOR, FreeNet, and I2P to the very new Ethereum Name Service, all of which are likely to remain niche), or if it's likely to scale up as a direct (and effective) substitute to the generic DNS, noting that it does avoid several security pitfalls (including eavesdropping/tracking, man-in-the-middle etc).

Also, from an Internet Consolidation perspective, DoH appears to make things even more centralized...not necessarily a good thing for end-users.

satish

On Mon, May 6, 2019 at 6:51 PM Seun Ojedeji <seun.ojedeji@gmail.com> wrote:

...

Hello Olivier,

I hear you and am looking forward to more details on how that relegation of ICANN could happen in practice.....am sure not against having DoH on HIT but I hope we will first ensure to give end-users the technological details of DoH(in a layman way) before we move on to its political implications as I certainly don't think DoH threatens ICANN's root management role as you seem to suggest; perhaps for now one can say it could move the direction of a few USDs ;-)

Regards

On Mon, May 6, 2019 at 1:18 PM Olivier MJ Crépin-Leblond <ocl@gih.com> wrote:

...

Yup -- in DoH think about a naming system solely run and controlled by the cloud providers that have signed up for DoH. That can easily replace the DNS altogether and relegate ICANN to a glitch in history. Kindest regards,

Olivier

On 06/05/2019 13:39, Sebastien Bachollet wrote:

DoH is not at all today a technical question (even if we need to understand the technology). It is a huge political issues particularly to all Internet users. SeB

Envoyé de mon iPhone

Le 6 mai 2019 à 13:13, Seun Ojedeji <seun.ojedeji@gmail.com> a écrit :

Hello Maureen,

I assume the text in blue are your recommendations? if yes then am fine with the suggestion, if there is an intention to further reduce the list, my preference of item that I think should be retained are 4, 1, 5 in that order before others can then follow. The DoH may be better suited for the techday.

Regards

On Sun, May 5, 2019 at 4:34 AM Maureen Hilyard < maureen.hilyard@gmail.com> wrote:

...

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)

1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures.

Combine 1.1, 1.2 and 1.3 into one session

1.1 Combatting Abuse with GDPR

1.2 Privacy-Proxy Implementation

1.3 Across Field Validation

2 EPDP Phase 2 / Uniform Access Model

REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal

3 Sessions that are merely updates can be provided as a pre-meeting webinar.

3.1 ATRT3

3.2 SSR-2

3.3 NomCom Review

4 Future of Multistakeholder Model Governance

Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included.

5 Enhance Effectiveness of Specific Review Recommedations and their Implementation

This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included

6 Universal Acceptance

There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues.

7 DNS over HTTPS (DoH)

Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE.

8 GNSO proposing these topics for one CC session

8.1 Rules for Uniform Domain Name Dispute Resolution Policy

8.2 Uniform Rapid Suspension system (URS) rules

8.3 WHOIS Data Reminder Policy

8.4 Transfer Policy

8.5 Transfer Dispute Resolution Policy

8.6 Across Field Validation

8.7 Process for handing RAA Data Retention Waiver Requests

8.8 Registration Data Access Protocol (RDAP)

8.9 WHOIS Accuracy Reporting System (ARS)

8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- ------------------------------------------------------------------------

*Seun Ojedeji, Federal University Oye-Ekiti web: http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile: +2348035233535 **alt email: <http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <seun.ojedeji@fuoye.edu.ng>*

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

_______________________________________________ ALAC mailing listALAC@atlarge-lists.icann.orghttps://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html

-- ------------------------------------------------------------------------

*Seun Ojedeji, Federal University Oye-Ekiti web: http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile: +2348035233535 **alt email: <http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <seun.ojedeji@fuoye.edu.ng>*

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html

-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

Dear Seun, DoH does not threaten ICANN's root management role, but since it looks likely to be supported by a number of very powerful players and provides for a filter to the standard addressing scheme, the consortium of vendors that will join DoH from cloud providers to browser manufacturers will be in a position where they could add/remove to the official root, for example filtering out any TLD that's seen to convey malware or even going as far as adding more TLDs that are not in the root itself. A fragmentation between Web addresses and DNS addresses is possible. That, in itself is a terrible thing. Kindest regards, Olivier On 06/05/2019 15:20, Seun Ojedeji wrote:

Hello Olivier,

I hear you and am looking forward to more details on how that relegation of ICANN could happen in practice.....am sure not against having DoH on HIT but I hope we will first ensure to give end-users the technological details of DoH(in a layman way) before we move on to its political implications as I certainly don't think DoH threatens ICANN's root management role as you seem to suggest; perhaps for now one can say it could move the direction of a few USDs ;-)

Regards

On Mon, May 6, 2019 at 1:18 PM Olivier MJ Crépin-Leblond <ocl@gih.com <mailto:ocl@gih.com>> wrote:

Yup -- in DoH think about a naming system solely run and controlled by the cloud providers that have signed up for DoH. That can easily replace the DNS altogether and relegate ICANN to a glitch in history. Kindest regards,

Olivier

On 06/05/2019 13:39, Sebastien Bachollet wrote:

...

DoH is not at all today a technical question (even if we need to understand the technology). It is a huge political issues particularly to all Internet users. SeB 

Envoyé de mon iPhone

Le 6 mai 2019 à 13:13, Seun Ojedeji <seun.ojedeji@gmail.com <mailto:seun.ojedeji@gmail.com>> a écrit :

...

Hello Maureen,

I assume the text in blue are your recommendations? if yes then am fine with the suggestion, if there is an intention to further reduce the list, my preference of item that I think should be retained are 4, 1, 5 in that order before others can then follow. The DoH may be better suited for the techday.

Regards

On Sun, May 5, 2019 at 4:34 AM Maureen Hilyard <maureen.hilyard@gmail.com <mailto:maureen.hilyard@gmail.com>> wrote:

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)   1  Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures.

Combine 1.1, 1.2 and 1.3 into one session

1.1 Combatting Abuse with GDPR

1.2 Privacy-Proxy Implementation

1.3 Across Field Validation

2 EPDP Phase 2 / Uniform Access Model

REMOVEthese two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal   3 Sessions that are merely updates can be provided as a pre-meeting webinar.

3.1 ATRT3

3.2 SSR-2

3.3 NomCom Review

4 Future of Multistakeholder Model Governance

Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included.

5 Enhance Effectiveness of Specific Review Recommedations and their Implementation

This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations .This session should be included

6 Universal Acceptance

There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussionson the UA and IDM-related issues. 

7 DNS over HTTPS (DoH)

Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE.

8 GNSO proposing these topics for one CC session

8.1 Rules for Uniform Domain Name Dispute Resolution Policy

8.2 Uniform Rapid Suspension system (URS) rules

8.3 WHOIS Data Reminder Policy

8.4 Transfer Policy

8.5 Transfer Dispute Resolution Policy

8.6 Across Field Validation

8.7 Process for handing RAA Data Retention Waiver Requests

8.8 Registration Data Access Protocol (RDAP)

8.9 WHOIS Accuracy Reporting System (ARS)

8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- ------------------------------------------------------------------------

/Seun Ojedeji, Federal University Oye-Ekiti web:      http://www.fuoye.edu.ng Mobile: +2348035233535 //alt email:<http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <mailto:seun.ojedeji@fuoye.edu.ng>/

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html

-- ------------------------------------------------------------------------

/Seun Ojedeji, Federal University Oye-Ekiti web:      http://www.fuoye.edu.ng Mobile: +2348035233535 //alt email:<http://goog_1872880453>seun.ojedeji@fuoye.edu.ng <mailto:seun.ojedeji@fuoye.edu.ng>/

Bringing another down does not take you up - think about your action!

-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html

Dear Holly, I responded to Sebastien saying "Yup" - and thus in agreement with him. Warmest regards, Olivier On 08/05/2019 01:42, h.raiche@internode.on.net wrote:

HI Olivier

 Is that 'Yup" agreement to simply not discuss DoH (or DoT) or is agreement with Sebastien - it is a huge issue.  If it is a huge issue than I am assuming the suggestion below to remove the topic is not what you are supporting??

Holly

----- Original Message ----- From:

To: "Sebastien Bachollet" <sebicann@bachollet.fr>, "Seun Ojedeji" <seun.ojedeji@gmail.com> Cc: "ALAC" <alac@atlarge-lists.icann.org> Sent: Mon, 6 May 2019 14:18:06 +0200 Subject: Re: [ALAC] The consolidated approach proposed by Keith Drazek

Yup -- in DoH think about a naming system solely run and controlled by the cloud providers that have signed up for DoH. That can easily replace the DNS altogether and relegate ICANN to a glitch in history. Kindest regards,

Olivier

On 06/05/2019 13:39, Sebastien Bachollet wrote:

DoH is not at all today a technical question (even if we need to understand the technology). It is a huge political issues particularly to all Internet users. SeB 

Envoyé de mon iPhone

Le 6 mai 2019 à 13:13, Seun Ojedeji <seun.ojedeji@gmail.com <mailto:seun.ojedeji@gmail.com>> a écrit :

Hello Maureen,

I assume the text in blue are your recommendations? if yes then am fine with the suggestion, if there is an intention to further reduce the list, my preference of item that I think should be retained are 4, 1, 5 in that order before others can then follow. The DoH may be better suited for the techday.

Regards

On Sun, May 5, 2019 at 4:34 AM Maureen Hilyard <maureen.hilyard@gmail.com <mailto:maureenhilyard@gmail.com>> wrote:

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)   1  Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures.

Combine 1.1, 1.2 and 1.3 into one session

1.1 Combatting Abuse with GDPR

1.2 Privacy-Proxy Implementation

1.3 Across Field Validation

2 EPDP Phase 2 / Uniform Access Model

REMOVEthese two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal   3 Sessions that are merely updates can be provided as a pre-meeting webinar.

3.1 ATRT3

3.2 SSR-2

3.3 NomCom Review

4 Future of Multistakeholder Model Governance

Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included.

5 Enhance Effectiveness of Specific Review Recommedations and their Implementation

This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations .This session should be included

6 Universal Acceptance

There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussionson the UA and IDM-related issues. 

7 DNS over HTTPS (DoH)

Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE.

8 GNSO proposing these topics for one CC session

8.1 Rules for Uniform Domain Name Dispute Resolution Policy

8.2 Uniform Rapid Suspension system (URS) rules

8.3 WHOIS Data Reminder Policy

8.4 Transfer Policy

8.5 Transfer Dispute Resolution Policy

8.6 Across Field Validation

8.7 Process for handing RAA Data Retention Waiver Requests

8.8 Registration Data Access Protocol (RDAP)

8.9 WHOIS Accuracy Reporting System (ARS)

8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- ------------------------------------------------------------------------

/Seun Ojedeji, Federal University Oye-Ekiti web:      http://www.fuoye.edu.ng Mobile: +2348035233535 //alt email:seun.ojedeji@fuoye.edu.ng <mailto:seun.ojedeji@fuoye.edu.ng>/

Bringing another down does not take you up - think about your action!

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org <http://www.atlarge.icannorg> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html

DNS over HTTPS (DoH) is a natural topic for the whole At-Large Community & ALAC to discuss & even rally behind. On Mon, May 6, 2019 at 8:46 AM Barrack Otieno <otieno.barrack@gmail.com> wrote:

Hi Maureen,

I concur with Olivier.

Regards

On 5/6/19, Sergio Salinas Porto <presidencia@internauta.org.ar> wrote:

...

Dear Maureen and all, This sounds good, very much in agreement with the topics that are hot topic in LACRALO, Universal acceptance, the future of the government model of the interested parties, DoH, I think this is a good start for our meeting in Marrakesh. The best thing is to focus on what is important!

*Sergio Salinas Porto**Presidente Internauta Argentina - LACRALO/ICANN <https://atlarge.icann.org/ralos/lacralo>**Asociación Argentina de Usuarios de Internet <http://www.internauta.org.ar/>/FeTIA <http://www.fetia.org.ar/>**FUILAC- Federación de Usuarios de Internet de LAC <https://fuilac.org>**facebook: salinasporto <http://www.facebook.com/salinasporto> **twitter: sergiosalinas <http://twitter.com/sergiosalinas>**Mobi:+54 9 223 5 215819**"Ojalá podamos ser desobedientes, cada vez que recibimos órdenes que humillan nuestra *

* conciencia o violan nuestro sentido común" Eduardo Galeano*

El dom., 5 may. 2019 a las 0:34, Maureen Hilyard (<maureen.hilyard@gmail.com>) escribió:

...

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)

1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures. Combine 1.1, 1.2 and 1.3 into one session 1.1 Combatting Abuse with GDPR 1.2 Privacy-Proxy Implementation 1.3 Across Field Validation 2 EPDP Phase 2 / Uniform Access Model REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal

3 Sessions that are merely updates can be provided as a pre-meeting webinar. 3.1 ATRT3 3.2 SSR-2 3.3 NomCom Review 4 Future of Multistakeholder Model Governance Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included. 5 Enhance Effectiveness of Specific Review Recommedations and their Implementation This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included 6 Universal Acceptance There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues. 7 DNS over HTTPS (DoH) Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE. 8 GNSO proposing these topics for one CC session 8.1 Rules for Uniform Domain Name Dispute Resolution Policy 8.2 Uniform Rapid Suspension system (URS) rules 8.3 WHOIS Data Reminder Policy 8.4 Transfer Policy 8.5 Transfer Dispute Resolution Policy 8.6 Across Field Validation 8.7 Process for handing RAA Data Retention Waiver Requests 8.8 Registration Data Access Protocol (RDAP) 8.9 WHOIS Accuracy Reporting System (ARS) 8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki:

https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

-- Barrack O. Otieno +254721325277 +254733206359 Skype: barrack.otieno PGP ID: 0x2611D86A _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)

Some issues should be categorised for webinars and technical issues. What is the endusers role in DoH/DoT? This is where the discussion starts and th drive it towards policy. Are there any current policies that are related to DoH/DoT? If yes, we put it on table for discussion . My opinion is lets build a use case to recommend what ammendments need to be done. On May 8, 2019 2:14 AM, <h.raiche@internode.on.net> wrote:

Thanks Maureen - and sorry for the delay in responding

I like this list and would be happy for it to be followed.

My one reservation: At some point, the implications of DoH and DoT should be discussed. I note Satish's comments - and would point out that his fears are exactly what was said by the presenter in the ALAC session in Kobe. My response - the presenter said that they are NOW being used so, like them or not, they are being used so we should at least acknolwedge that we do/do not support further discussion about issues raised - which can happen in ALAC if not in a more general session

Holly

----- Original Message ----- From: "Maureen Hilyard" <maureen.hilyard@gmail.com>

To: "ALAC" <alac@atlarge-lists.icann.org> Cc:

Sent: Sat, 4 May 2019 17:33:58 -1000 Subject: [ALAC] The consolidated approach proposed by Keith Drazek

Hi all

I finally found what I was looking for. This was Keith's consolidated approach proposed on April 30 for your consideration (to mnimise the number of HIT sessions in Marrakech)

1 Impact of GDPR and EPDP Phase 1 Recommendations on Existing Policies and Procedures. Combine 1.1, 1.2 and 1.3 into one session 1.1 Combatting Abuse with GDPR 1.2 Privacy-Proxy Implementation 1.3 Across Field Validation 2 EPDP Phase 2 / Uniform Access Model REMOVE these two proposed sessions because EPDP Phase 2 work will only have been under way for 6 weeks by the time we arrive in Marrakech. It may be premature to schedule a HIT/CC session - possibly defer this to ICANN66 in Montreal

3 Sessions that are merely updates can be provided as a pre-meeting webinar. 3.1 ATRT3 3.2 SSR-2 3.3 NomCom Review 4 Future of Multistakeholder Model Governance Is necessary to complete the project kicked off in Kobe by the year's end. Clearly a topic of interest to the entire community. This session should be included. 5 Enhance Effectiveness of Specific Review Recommedations and their Implementation This session is timely, particularly with developments around the Board's actions on the CCT-RT recommendations . This session should be included 6 Universal Acceptance There was a good bit of discussion in Kobe and it is an issue that appears to be generating increased interest. With the meeting being held in Marrakech, it is a good opportunity to continue discussions on the UA and IDM-related issues. 7 DNS over HTTPS (DoH) Not seen as having broad community interest at this time. Could possibly be a regular session but would REMOVE. 8 GNSO proposing these topics for one CC session 8.1 Rules for Uniform Domain Name Dispute Resolution Policy 8.2 Uniform Rapid Suspension system (URS) rules 8.3 WHOIS Data Reminder Policy 8.4 Transfer Policy 8.5 Transfer Dispute Resolution Policy 8.6 Across Field Validation 8.7 Process for handing RAA Data Retention Waiver Requests 8.8 Registration Data Access Protocol (RDAP) 8.9 WHOIS Accuracy Reporting System (ARS) 8.10 Thick WHOIS Transition policy for .com, .net, .jobs

Comments please Maureen

_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+ Advisory+Committee+(ALAC)