- rssac-caucus - lists.icann.org

Re: [rssac-caucus] Nomination Period: RSSAC Outgoing Liaison to the ICANN Nominating Committee
by Robert Martin-Legene June 27, 2017

June 27, 2017

I would like to state my support for Alejandro in his candidacy. I know Alejandro to be competent and dedicated. --- Hello Carlos / List, I'm willing to server for a third and final period if necessary. The first year was a tough one, I probably did not feel comfortable. I mean, the daily basis is very different than what I usually did. However, this year I think I have contributed a lot, I have given a lot of feedback, shared new ideas, participated more active in calls and conversations. In some how I can say that I have had some "fights" to make things happen & better. Nowadays I can say I feel much better than a year ago. Thanks, Alejandro,

1 0

[rssac-caucus] Nomination Period: RSSAC Outgoing Liaison to the ICANN Nominating Committee
by Carlos Reyes June 24, 2017

June 24, 2017

Hello, RSSAC Caucus. It is time to begin the selection process for the Outgoing RSSAC Liaison to the ICANN Nominating Committee. Please refer to this page for more information about the Nominating Committee. I have also copied below the relevant sections from “RSSAC000v2: Operational Procedures” for your reference. With this notice, a one-month nomination period via this distribution list is now open. Nominations or self-nominations will be accepted and require a second. Nominees must then accept or decline their nomination and may provide more context for their decision. The nomination period will close at 23:59 UTC on 20 July. The RSSAC will then consider the slate of candidates on its August teleconference. As you may recall, the RSSAC elected Alejandro Acosta to this role in 2015 and re-elected him in 2016. Per RSSAC Operational Procedures, Alejandro is eligible for re-election by the RSSAC for one more one-year term. The RSSAC Co-Chairs appreciate your consideration. Please do not hesitate to contact the RSSAC Co-Chairs or support staff with any questions or concerns. Best, Carlos Reyes on behalf of Tripti Sinha and Brad Verd, RSSAC Co-Chairs 1.2.6.3 Outgoing RSSAC Liaison to the ICANN Nominating Committee The outgoing RSSAC Liaison to the ICANN Nominating Committee is specified in the ICANN Bylaws. The term for the outgoing RSSAC Liaison to the ICANN Nominating Committee shall be one year. A person may only serve for three consecutive terms. The eligibility status for a previous liaison is reset one year after having stepped down. The RSSAC must elect the outgoing RSSAC Liaison to the ICANN Nominating Committee according to the Outgoing RSSAC Liaisons Election Procedure (Section 1.2.6.6) from the members of the RSSAC Caucus. The outgoing RSSAC Liaison to the ICANN Nominating Committee acts as a conduit between the RSSAC and the ICANN Nominating Committee reporting on matters that need to be coordinated or communicated between the two bodies. The role requires discretion, management skills, and considerable time commitment. 1.2.6.6 Outgoing Liaisons Election Procedure One month prior to each election, qualified nominees will be accepted for the outgoing liaison position and announced on the RSSAC distribution list. During the meeting that includes election of an outgoing liaison position on its announced agenda, additional nominations will be accepted, and all nominees will indicate their intentions: to accept or to decline their nomination. In the event that only one candidate is standing for election, the RSSAC may elect the new outgoing liaison by acclimation. In the event that two or more candidates are standing for election, the presiding Co-Chair will call for a vote. Members will indicate their selection. A simple majority (half plus one) of the voting members will establish the new liaison. In the event a simple majority is not achieved due to having more than two nominees, the nominee with the least number of votes is eliminated and the voting is repeated with the reduced slate of names. The process is repeated until a nominee achieves a simple majority. In the event of a tie, a run-off election will occur with members indicating their selection. In the event of a second tie, the floor will be opened for discussion followed by a new vote with the simple majority designating the new liaison. The Co-Chairs will forward the name of the outgoing liaison-elect to the reciprocating body. If a vacancy exists in an outgoing liaison role, the RSSAC will elect a new outgoing liaison through this process. Carlos Reyes | Policy and Community Engagement Manager carlos.reyes(a)icann.org | +1 (202) 802-8019 ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006

2 1

[rssac-caucus] RSSAC027
by Carlos Reyes June 20, 2017

June 20, 2017

Dear RSSAC Caucus, The RSSAC has published RSSAC027: May 2017 Workshop Report (see RSSAC Publications page). The document provides a high-level summary of the outcomes from the fourth RSSAC workshop held in Reston, Virginia in early May. The RSSAC welcomes comments. Best, Carlos Carlos Reyes | Policy and Community Engagement Manager carlos.reyes(a)icann.org | +1 (202) 802-8019 ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006

1 0

[rssac-caucus] Monthly Update
by Carlos Reyes June 13, 2017

June 13, 2017

Dear RSSAC Caucus, This is the Caucus monthly update. As always, we welcome your feedback on the content and format of these updates. Thank you, Carlos WORK UPDATES NEW WORK PARTY: Harmonization of Anonymization Procedures for Data Collecting At its 4 May meeting, the RSSAC approved the statement of scope and work for a new work party and appointed Lars-Johan Liman as the RSSAC Shepherd for this effort. Please review the attachment and respond to this message if you would like to serve on this work party. Root Server Naming Scheme Work Party | John Bond, Work Party Leader The RSSAC received this document on 18 May and plans to review it in detail at ICANN59. ADMINISTRATION Minutes from RSSAC Meetings The minutes from the 6 April RSSAC teleconference and 4 May RSSAC meeting have been published here. Upcoming Caucus Meetings The next Caucus meeting will be held during ICANN60 | Annual General Meeting (28 October-3 November 2017) in Abu Dhabi, UAE. The exact date, time, and location will be confirmed as the meeting approaches. Per the cadence of Caucus meetings at IETF meetings, the Caucus will not convene at IETF99 in Prague, Czech Republic. The next Caucus meeting at an IETF meeting will be held during IETF100 (12-17 November 2017) in Singapore. The exact date, time, and location will be confirmed as the meeting approaches.

3 2

[rssac-caucus] FW: Announcement: Pre-ICANN59 Policy Update Webinar
by Kathy Schnitt May 22, 2017

May 22, 2017

Dear RSSAC Caucus, Please see the following announcement that may be of interest. Best regards, Kathy Kathy Schnitt, Secretariat Services Coordinator for RSSAC and SSAC From: Ozan Sahin <ozan.sahin(a)icann.org<mailto:ozan.sahin@icann.org>> Date: Monday, May 22, 2017 at 8:25 AM To: Policy Staff <policy(a)icann.org<mailto:policy@icann.org>> Subject: Announcement: Pre-ICANN59 Policy Update Webinar Dear Policy Team Members, Please find below the announcement of the "Pre-ICANN59 Policy Update Webinar" published on the ICANN website. Please share it with your groups and mailing lists as appropriate. Kindly let me know if you have any questions. Kind regards, Ozan https://www.icann.org/news/announcement-2017-05-22-en Please RSVP via this form<https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> by 13 June 2017. You will receive remote participation details the week of 12 June 2017. The ICANN Policy Development Support Team will host a Policy Update Webinar on Thursday, 15 June 2017 at 10:00 and 19:00 Coordinated Universal Time (UTC), in preparation for the upcoming ICANN59 Policy Forum in Johannesburg, South Africa. The purpose of the webinar is to summarize policy activities across the ICANN policy development community and to brief the community on the Empowered Community consultation and cross-community sessions taking place in Johannesburg. Briefings on the Empowered Community Consultation and Cross-Community Sessions: · Special session on the Proposed Fundamental Bylaws Amendments · Next-Generation Generic Top-Level Domain (gTLD) Registration Directory Services (RDS) policy requirements · General Data Protection Regulation (GDPR) · Geographic names · Operational side of ICANN's Operating Plan and Budget · Who sets ICANN's priorities? Updates on Supporting Organizations and Advisory Committees: · Address Supporting Organization (ASO) and regional Internet registries (RIR) policy development · Country Code Names Supporting Organization (ccNSO) · Generic Names Supporting Organization (GNSO) · At-Large Advisory Committee (ALAC) and At-Large Community · Governmental Advisory Committee (GAC) · Root Server System Advisory Committee (RSSAC) · Security and Stability Advisory Committee (SSAC) The two sessions are duplicates, scheduled to accommodate different time zones. Each session runs in English for 90 minutes. The webinar will be conducted via Adobe Connect along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, participants may submit questions using the chat function in Adobe Connect. Recordings of the webinars will be made available here<https://www.icann.org/resources/pages/presentations-2012-08-27-en>. The Policy Development Support Team is always available to answer any questions via email at policyinfo(a)icann.org<mailto:policyinfo@icann.org>. Please RSVP via this form<https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> by 13 June 2017. You will receive remote participation details the week of 12 June 2017. Ozan Sahin Community Engagement Support Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6218 Mobile: +90.533.641.0007 Email: ozan.sahin(a)icann.org<mailto:ozan.sahin@icann.org> Skype: ozan.sahin.icann www.icann.org

1 0

Re: [rssac-caucus] ATRT3 Call for Volunteers
by Carlos Reyes May 18, 2017

May 18, 2017

Hello, all. As a reminder, if you would like to be considered for RSSAC endorsement as a member of ATRT3, please apply by tomorrow. Best, Carlos Carlos Reyes | Policy and Community Engagement Manager carlos.reyes(a)icann.org | +1 (202) 802-8019 ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 From: <rssac-caucus-bounces(a)icann.org> on behalf of Carlos Reyes <carlos.reyes(a)icann.org> Date: Monday, May 8, 2017 at 3:09 AM To: "rssac-caucus(a)icann.org" <rssac-caucus(a)icann.org> Subject: [rssac-caucus] ATRT3 Call for Volunteers Hello, all. The RSSAC encourages RSSAC Caucus members to consider applying for the third Accountability and Transparency Review Team. To receive RSSAC endorsement, please apply by 19 May. This will give the RSSAC Co-Chairs time to manage the endorsement process ahead of the RSSAC meeting on 1 June and still meet the deadline. More details about ATRT3, the expected commitment, and the application process can be found here: https://www.icann.org/news/announcement-2017-01-31-en When submitting your statement of interest to reviews(a)icann.org, please also copy me (carlos.reyes(a)icann.org) to ensure proper coordination. Thank you, Carlos Carlos Reyes | Policy and Community Engagement Manager carlos.reyes(a)icann.org | +1 (202) 802-8019 ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006

1 0

[rssac-caucus] Closing out the "Technical Analysis of the Naming Scheme Used For Individual Root Servers" document
by Paul Hoffman May 18, 2017

May 18, 2017

Greetings, and thanks for the comments on the third round. I have incorporated most of them, including Davey's suggestion for a further research item. I have also now made the document read-only to indicate that we are done editing. The next step is for Steve Sheng to turn this into a Word document again and pass it to RSSAC for publication. However, while he is doing that, I want the Caucus to review one significant technical change that we made during this round. The definition of "node re-delegation attack" in the Terminology section assumed a definition of the "Kaminsky attack" that is not reflected in the common understanding of the "Kaminsky attack", and didn't give any external reference for "node re-delegation". The new definition is below. I believe it is technically correct, and it directs the reader to Section 7.2 which says that we are going to need to do further study to see if the attacks are feasible. Please review this definition and, if you have any comments, send them to this list (do not try to edit the document) before May 17. That will give Steve enough time to finish his conversion work before he needs to pass the document back to RSSAC. Again, thanks for all the work you all have done on reviewing the document. The recommendations make it clear that further work will need to be done after this gets published, and I hope that there will interest from this group in doing that. --Paul Hoffman Node re-delegation attack – These attacks, if found to be feasible, could possibly allow an attacker to poison the cache of a recursive resolver in a similar fashion to the well-known “Kaminsky attack”. Node re-delegation attacks* might affect the resolution of all zones in resolvers that do not validate, and all unsigned zones in validating resolvers. Section 7.2 recommends further study to determine whether these attacks are feasible and, if so, what the effects might be. *https://www.sec-consult.com/fxdata/seccons/prod/downloads/whitepaper-dns-node-redelegation.pdf

2 1

[rssac-caucus] ATRT3 Call for Volunteers
by Carlos Reyes May 8, 2017

May 8, 2017

Hello, all. The RSSAC encourages RSSAC Caucus members to consider applying for the third Accountability and Transparency Review Team. To receive RSSAC endorsement, please apply by 19 May. This will give the RSSAC Co-Chairs time to manage the endorsement process ahead of the RSSAC meeting on 1 June and still meet the deadline. More details about ATRT3, the expected commitment, and the application process can be found here: https://www.icann.org/news/announcement-2017-01-31-en When submitting your statement of interest to reviews(a)icann.org, please also copy me (carlos.reyes(a)icann.org) to ensure proper coordination. Thank you, Carlos Carlos Reyes | Policy and Community Engagement Manager carlos.reyes(a)icann.org | +1 (202) 802-8019 ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006

1 0

[rssac-caucus] Second round review on "Technical Analysis of the Naming Scheme Used For Individual Root Servers"
by Paul Hoffman May 8, 2017

May 8, 2017

Greetings. The Work Party has made some significant changes to the document at the request of a few folks from RSSAC. The new edition is at: https://docs.google.com/document/d/17eGSbMMo6GbyG8gE4l1uK1LW8Q1iCIouN4PATcV… The major changes from the last version that Caucus saw are are: - Tightening of the introduction, talking only about what the RSSAC asked the Caucus to look at - Huge changes to the recommendations in Section 7, aiming more on the need for future work - More focused tables in Appendix A Please check all of these carefully and make tracked changes or comments in the document, plus let the list know. We would like this finished in about ten days, by May 5. --Paul Hoffman

6 8

[rssac-caucus] Third round review on "Technical Analysis of the Naming Scheme Used For Individual Root Servers"
by Paul Hoffman May 5, 2017

May 5, 2017

Greetings, and thanks for the comments so far. I have incorporated as many as I could given the current scope of the document. The current edition is at: https://docs.google.com/document/d/17eGSbMMo6GbyG8gE4l1uK1LW8Q1iCIouN4PATcV… There are still some outstanding comments, and we need to clear these before we send this back to RSSAC. Please review: - Definition of "node re-delegation attack" in section 2. I have suggested text that gives more space for the possibility that the attacks, while possible, might not be feasible. Terry also suggests adding an actual reference. - The first drawback bullet in 5.6 mistakes configuration information for priming with the first responses. I have suggested alternative text. - In Section 6, Duane points out that "dependency" is too strong, and I propose removing the sentence. - Terry and Duane have a suggested replacement for Recommendation 3 in Section 7.2 Please check all of these carefully and make tracked changes or comments in the document, plus let the list know. We would like this finished by Wednesday May 10 in order to work with RSSAC's schedule. --Paul Hoffman

1 0