- rssac-caucus - lists.icann.org

Re: [RSSAC Caucus] [SOAC-Leaders-ICANNMeeting-Planning] At-Large Submission to the HIT Plenary Programme
by Fred Baker Dec. 19, 2019

Dec. 19, 2019

I'm changing the CC to the RSSAC Caucus, which, in addition to my vice-chair and relevant staff, includes the RSSAC and a number of DNS experts in other locations. I have not solicited their opinions, in large part due to temporal issues - you need an answer in less than 48 hours. I therefore speak for myself, and for the perspective that the RSS is and has since the 1980's been predicated on the concepts you will find in RFC RFC 2826, the IAB's Technical Comment on the Unique DNS Root. I think that splintering the Internet into three shards - or a great many more, which I suspect will happen if current BRIC forces hold sway - will make the conceptual basis for the RSS very tenuous indeed, and will economically hurt those countries that pursue the path. This is far beyond slogans. The Internet has empowered the economies of 60 countries or more, and is being promoted to enhance the economies of about 140 more. By destroying the markets the Internet has created or facilitated, the BRICI countries threaten to undermine world markets - and especially their own. What is proposed by Russia and others is one of two things - either a wresting of Internet governance away from those who have done it to date to the BRIC countries, or a return to many of the concepts behind the PSTN, including the creation of national DNS roots, or possibly other divisions. We once worried that having more than a few common generic TLDs would mean that IPR-holders would have to register each name in each of them, which is something that was eventually formally set aside. Now, I worry that each name-holder will be forced to register a name in each of 200-or-so name service systems (whether DNS, DoH, or something else entirely), or forfeit whatever business they normally get from them. Those countries that follow that route also forfeit whatever business they might have gotten via those same companies. Russia has already formalized this, as I understand it; names used in Russia pretty much have to be Russian names served by Russian servers. So, from my perspective, both as chair of RSSAC and a contributor to Internet technology for rather a while, I think this is a very valid topic, and expect that RSSAC people will find it interesting. > On Dec 18, 2019, at 4:53 PM, Tanzanica S. King <tanzanica.king(a)icann.org> wrote: > > All, > > We have two confirmed plenary session topics for ICANN67: > > The Domain Name Services Marketplace - Market Dynamics, Business Models and Commercial Drivers > Monday, 09 March 2020, 17:00-18:30 > > The DNS and the IoT: Opportunities, Risks, and Challenges > Thursday, 12 March 2020, 09:00-10:30 > > The 3rd proposed session on "Building Greater Trust in the ICANN Multi-stakeholder Process among Policymakers in Government" was withdrawn. However, At-Large has an alternate session proposal for your consideration to fill the remaining slot on Wednesday, 11 March 2020, 09:00-10:30. > > Please see the session details outlined by Maureen below and let us know how you would like to proceed. We must finalize the block schedule by this Friday, 20 December, so time is of the essence. > > Best, > > Tanzanica > > _______________________________________________ > Tanzanica S. King > Sr. Manager, Meeting Strategy and Design > ICANN > > Office +1 310 301 5800 > Mobile +1 310 995 3038 > www.icann.org > > From: Maureen Hilyard <maureen.hilyard(a)gmail.com> > Date: Wednesday , 18 December 2019 at 15:28 > To: Tanzanica King <tanzanica.king(a)icann.org>, "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> > Subject: [Ext] At-Large Submission to the HIT Plenary Programme > > Dear SOAC Colleagues and Tanzanica > > I hope that you have excused the slip that was made earlier when one of our members submitted a proposal without going through the proper processes. However, we do have a proposal that, although I know it is a little late, our CPWG team hope you will seriously consider for inclusion into the ICANN67 HIT programme. The proposal is as follows. Sorry it is not in the formal template (in my haste to get it to you all before you go on holiday!) > > Title: “One world - one internet?” Cybersecurity and geopolitics in a multistakeholder environment > > This session/roundtable seeks to explore the modern day rationale for ICANN's policy of "One World. One Internet." In time of enhancing splinternet, prevailing cybersovereignity trends and states taking forever more effective measures to ensure their jurisdiction over what they consider to be "their" part of cyberspace. It is in this context that ICANN's global stewardship role has grown more significant than ever. This session seeks to explore how to best justify ICANN's "One world. One Internet" policy in the face of global disruptive trends. It specifically looks at national and regional security and privacy laws as well as new communication protocols, seeking to find how they attend or add to this challenge. > > The point of departure for this panel will be the perspective onto global IG as presented in his 2018 IGF speech by President Macron, referring to three different options for global Internet: the California based one, the EU focused one and the Chinese one (https://www.intgovforum.org/multilingual/content/igf-2018-speech-by-french-… [intgovforum.org] ). We will seek to jointly explore whether current and upcoming global trends actually do indicate Internet fragmentation or whether ICANN can legitimately sustain its “One World. One Internet” narrative. If so, what is the modern day rationale behind it? > > The desired outcome of this session is to identify and present to the ICANN community a coherent, comprehensive narrative on why "One world. One internet" remains a valid policy narrative in the time of disruptive global trends and how to best communicate it to the different stakeholders outside ICANN. > > Panelists (TBC): Patrik Fältström, Rod Rasmussen/Merike Kaeo, Peter Micek (AccessNow)/Thomas Rickert (EPDP), Lousewies van der Laan (?)/GAC Rep (Manal Ismail?), León Sanchez, ISOC Rep? > > Keywords: cybersecurity, privacy, GDPR, splinternet, sovereignty, jurisdiction > > > Best regards, > > Joanna Kulesza, PhD > assistant professor of international law and Internet governance > Faculty of Law and Administration, University of Lodz > Kopcinskiego Street 8/12, 90-232 Lodz, Poland > publications: https://unilodz.academia.edu/JoannaKulesza/ [unilodz.academia.edu] > website: https://pl.linkedin.com/in/kuleszajoanna [pl.linkedin.com] > > > _______________________________________________ > SOAC-Leaders-ICANNMeeting-Planning mailing list > SOAC-Leaders-ICANNMeeting-Planning(a)icann.org > https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning > > _______________________________________________ > 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.

2 2

INPUT REQUESTED: Proposal for Future Root Zone KSK Rollovers
by Andrew McConachie Dec. 18, 2019

Dec. 18, 2019

Dear RSSAC Caucus, The IANA has published a Proposal for Future Root Zone KSK Rollovers and is soliciting public comments on it. <https://www.icann.org/public-comments/proposal-future-rz-ksk-rollovers-2019…> The RSSAC wishes to solicit feedback from the Caucus to determine its response. Please review the proposal and if you have comments please send them to this list by December 15th. Depending on the comments and discussion generated on this list the RSSAC may kick off a quick work party to draft input, or we may just continue using this list for development of the document. The final deadline for input is January 31, 2020. So we don’t have too much time to get something ready. Thanks, Andrew

10 14

Collected KSK comments
by Fred Baker Dec. 16, 2019

Dec. 16, 2019

I'm pulling together comments that we might make. I am including who said them, because we said that Caucus contributions would be attributable to their source. Speaking for myself, I would rather have the comments be considered to have been made by the committee, which is to say without attribution. If that's a general viewpoint, let me know. George Michaelson: The proposal should address algorithm rollover. As that is considered out of scope for this version, propose for the next change. The proposal should include measurement. (George: specifically what would you like to measure?) The alternate/replacement key pre-gen stuff is forward-thinking, and good. Paul Muchene: Phase D, the KSK standby state, it potentially invites an attacker to exploit possible vulnerabilities with either the properties of the key or key generation algorithm. If phase D could be reduced a reasonably shorter duration (1-1.5 years) this problem could be mitigated. However, if this duration is pretty short and will inconvenience the dissemination of the KSK to OS and DNS software vendors, then considerations should be proposed for using a longer KSK key length of 3072-bit RSA. Dessalegn Yehuala Section 2.4 seems to give a soft rationale for the rollover frequency. Arguments exist for a longer or a shorter interval, and these arguments don't seem to be strong enough to make a firm choice. Section 2.6 assumes current state of the strength of the current cryptographic algorithm employed for the KSK (2048-bit RSA), there is no risk mitigation identified in the event the current cryptographic algorithm discovered to have some exploitable vulnerabilities. Fred Baker: in that context, researchers from KeyFactor presented a paper at First IEEE Conference on Trust, Privacy, and Security that reported that one in 172 RSA certificates certified keys for which the private key could be derived from the public key. Davey Song: Suggests changing to an ECC algorithm rather than changing to a 3072 bit key. There should be a predictable timeline for algorithm rollover and as a result a advance timeline for study, review, and testing work on this.

4 3

Fwd: INPUT REQUESTED: Proposal for Future Root Zone KSK Rollovers
by Dessalegn Yehuala Dec. 15, 2019

Dec. 15, 2019

I agree with Paul's comment. I forgot to share my comments on this to the RSSAC mailing list. It was sent a couple of days back. My comments are described below. ---------- Forwarded message --------- From: Dessalegn Yehuala <mequanint.yehuala(a)gmail.com> Date: Thu, 12 Dec 2019, 16:54 Subject: Re: [RSSAC Caucus] INPUT REQUESTED: Proposal for Future Root Zone KSK Rollovers To: Andrew McConachie <andrew.mcconachie(a)icann.org> Hi Andrew, I have two comments to forward on the proposed future root zone KSK rollovers: 1. Section 2.4 (Rationale for rollover frequency)- the rationale given is vague or at best subjective, no cost model or any other parameters (based on challenges faced in previous KSK rollovers) have been used to justify the tradeoffs that come along with making the rollover frequency to 3 years. Why not for a longer rollover frequency like 4 years or 5 years? 2. Section 2.6 (Changes to key algorithm and strength)- it only assumes on the current state of the strength of the current cryptographic algorithm employed for the KSK (2048-bit RSA), there is no risk mitigation identified in the event the current cryptographic algorithm discovered to have some exploitable vulnerabilities. Kind regards, Dessalegn On Wed, Dec 11, 2019 at 7:06 PM Andrew McConachie < andrew.mcconachie(a)icann.org> wrote: > Dear RSSAC Caucus, > > A friendly reminder to send in any feedback by *December 15th*. > > Thanks, > Andrew > > On Dec 3, 2019, at 22:49, Andrew McConachie <andrew.mcconachie(a)icann.org> > wrote: > > Dear RSSAC Caucus, > > The IANA has published a Proposal for Future Root Zone KSK Rollovers and > is soliciting public comments on it. > <https://www.icann.org/public-comments/proposal-future-rz-ksk-rollovers-2019… > [icann.org] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> > > > > The RSSAC wishes to solicit feedback from the Caucus to determine its > response. Please review the proposal and if you have comments please send > them to this list by *December 15th*. Depending on the comments and > discussion generated on this list the RSSAC may kick off a quick work party > to draft input, or we may just continue using this list for development of > the document. > > The final deadline for input is January 31, 2020. So we don’t have too > much time to get something ready. > > Thanks, > Andrew > _______________________________________________ > rssac-caucus mailing list > rssac-caucus(a)icann.org > https://mm.icann.org/mailman/listinfo/rssac-caucus > > _______________________________________________ > 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_… > ) and the website Terms of Service ( > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_… > ). 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. > > > _______________________________________________ > rssac-caucus mailing list > rssac-caucus(a)icann.org > https://mm.icann.org/mailman/listinfo/rssac-caucus > > _______________________________________________ > 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.

1 0

REMINDER: Doodle | Calls to Update RSSAC002v4 and RSSAC023v2
by Ozan Sahin Dec. 13, 2019

Dec. 13, 2019

Hello, all. This is a reminder on the doodle poll to schedule two calls in order to update RSSAC002v4 and RSSAC023v2. Please confirm your availability via the doodle poll<https://doodle.com/poll/euhbph2fwyuu7m7x> by Monday, 16 December if you have not done so yet. Best, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org> From: Ozan Sahin <ozan.sahin(a)icann.org> Date: Monday, December 9, 2019 at 10:03 PM To: "rssac-caucus(a)icann.org" <rssac-caucus(a)icann.org> Subject: Doodle | Calls to Update RSSAC002v4 and RSSAC023v2 Dear all, Please confirm, via Doodle link below, your availability to join two one-hour calls on the week of 6 January 2020 in order to update the following two documents: * RSSAC002v4: RSSAC Advisory on Measurements of the Root Server System<https://docs.google.com/document/d/1na7VpPYfo4VEBfQMHwix6I2Puohvc1hvwRh0aW1…> * RSSAC023v2: History of the Root Server System<https://docs.google.com/document/d/16FaQzGJnqBsy5zk4xmLPU2v7FUqLQT8readmSYI…> Doodle poll: https://doodle.com/poll/euhbph2fwyuu7m7x We appreciate your confirmation no later than close of business on Monday, 16 December 2019. Best, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

1 0

REMINDER: Call for Volunteer | Fellowship Program Mentor
by Ozan Sahin Dec. 13, 2019

Dec. 13, 2019

Hello, all. This is a reminder on the deadline to indicate your interest to serve as a Fellowship Program Mentor. Please e-mail ozan.sahin(a)icann.org<mailto:ozan.sahin@icann.org> by 23:59 UTC on Tuesday, 17 December if you would like to be considered for this role. Best, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org> From: rssac-caucus <rssac-caucus-bounces(a)icann.org> on behalf of Ozan Sahin <ozan.sahin(a)icann.org> Date: Thursday, December 5, 2019 at 2:13 PM To: "rssac-caucus(a)icann.org" <rssac-caucus(a)icann.org> Subject: [RSSAC Caucus] Call for Volunteer | Fellowship Program Mentor Dear RSSAC Caucus Members, ICANN’s Supporting Organizations and Advisory Committees are invited to nominate one individual each to serve as a mentor in the ICANN Fellowship Program. Learn more here: https://www.icann.org/news/announcement-2019-11-13-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> The mentor would serve for three consecutive ICANN Public Meetings starting with ICANN68 in June 2020. More information can be found here: https://www.icann.org/resources/pages/fellowship-mentoring-2018-10-15-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> By 23:59 UTC on Tuesday, 17 December please e-mail ozan.sahin(a)icann.org<mailto:ozan.sahin@icann.org> if you would like to be considered for this role. Please let me know if you have any questions. Best, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

1 0

Doodle | Calls to Update RSSAC002v4 and RSSAC023v2
by Ozan Sahin Dec. 9, 2019

Dec. 9, 2019

Dear all, Please confirm, via Doodle link below, your availability to join two one-hour calls on the week of 6 January 2020 in order to update the following two documents: * RSSAC002v4: RSSAC Advisory on Measurements of the Root Server System<https://docs.google.com/document/d/1na7VpPYfo4VEBfQMHwix6I2Puohvc1hvwRh0aW1…> * RSSAC023v2: History of the Root Server System<https://docs.google.com/document/d/16FaQzGJnqBsy5zk4xmLPU2v7FUqLQT8readmSYI…> Doodle poll: https://doodle.com/poll/euhbph2fwyuu7m7x We appreciate your confirmation no later than close of business on Monday, 16 December 2019. Best, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

1 0

Publication of RSSAC045
by Andrew McConachie Dec. 9, 2019

Dec. 9, 2019

Dear RSSAC Caucus Members, The RSSAC has recently published “RSSAC045: RSSAC Statement on Threat Mitigation for the Root Server System." RSSAC045 can be found here. <https://www.icann.org/en/system/files/files/rssac-045-03dec19-en.pdf> Thanks, Andrew

1 0

Call for Volunteer | Fellowship Program Mentor
by Ozan Sahin Dec. 5, 2019

Dec. 5, 2019

Dear RSSAC Caucus Members, ICANN’s Supporting Organizations and Advisory Committees are invited to nominate one individual each to serve as a mentor in the ICANN Fellowship Program. Learn more here: https://www.icann.org/news/announcement-2019-11-13-en The mentor would serve for three consecutive ICANN Public Meetings starting with ICANN68 in June 2020. More information can be found here: https://www.icann.org/resources/pages/fellowship-mentoring-2018-10-15-en By 23:59 UTC on Tuesday, 17 December please e-mail ozan.sahin(a)icann.org<mailto:ozan.sahin@icann.org> if you would like to be considered for this role. Please let me know if you have any questions. Best, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

1 0

[RSS Metrics] Update on the RSS Metrics document
by Steve Sheng Dec. 4, 2019

Dec. 4, 2019

Dear RSS Metrics WP, Following the RSS metrics discussions at ICANN66 and IETF106, the work party co-chair and staff worked on the document to address your comments. We have identified a few outstanding comments to be discussed at the upcoming WP call. But otherwise, the document is stable. Therefore, the staff has put the document into view only mode. If you have any substantial comments please submit them directly to the mailing list with alternative wording. If you have copy-edit comments, please submit them to Steve Sheng (steve.sheng(a)icann.org<mailto:steve.sheng@icann.org>). Best Steve

6 8