August 2016 - rssac-caucus - lists.icann.org

[rssac-caucus] Tweaks to RSSAC-002
by Shane Kerr Sept. 21, 2016

Sept. 21, 2016

Hello all, I love RSSAC-002, but have had a few small pain points consuming the data that some of the root operators provide. I suggest that it might be good to make RSSAC-002bis to improve things. 1. It would be helpful if there was a standard starting URL for these. I know section 4.7 defines the standard, but the starting point is different with 5 different styles for 8 operators. 'a': 'http://a.root-servers.org/rssac-metrics/raw/', 'b': 'http://b.root-servers.org/rssac/', 'c': 'http://c.root-servers.org/rssac002-metrics/', 'd': 'http://droot-web.maxgigapop.net/rssac002/', 'h': 'http://h.root-servers.org/rssac002-metrics/', 'j': 'http://j.root-servers.org/rssac-metrics/raw/', 'k': 'https://www-static.ripe.net/dynamic/rssac002-metrics/', 'l': 'http://stats.dns.icann.org/rssac/', 'm': 'https://rssac.wide.ad.jp/rssac002-metrics/', 2. It would be nice if there was an SSL way to get the data everywhere. I know it may be hard for Verisign to get a certificate since they left the CA business, but we all have Lets Encrypt now. ;) 3. Some operators seem to have stuff not defined by RSSAC-002 in their directories. For example, several have PNG files in them, others seem to have debugging or additional directories. It's not a big deal, but naive scripts have to filter stuff out. 4. While RSSAC-002 says that frequency that reports are generated is out of scope, everyone but L does it daily so maybe it could just define that? Surely we can convince L to also generate daily? 5. Most importantly, every page says "Measurements of the Root Sever System" at the top (s/Sever/Server/). Once seen, cannot be unseen. As a related issue, it sure would be nice if the remaining root operators provided this information. Currently E, F, G, and I don't have links on the http://www.root-servers.org site to this information (I was surprised to see F and I missing, I admit). Maybe they have this somewhere else? How would I know? Also, the web H site with statistics seems down right now. Maybe it would be helpful if ICANN mirrored the data? (That might actually solve my problem of inconsistent directories.) Cheers, -- Shane

8 14

[rssac-caucus] RSSAC Caucus Meetings 2016-2019
by Carlos Reyes Aug. 16, 2016

Aug. 16, 2016

Dear all, At the RSSAC Caucus meeting on 17 July at IETF96 in Berlin, Germany, there was a discussion about the schedule of RSSAC Caucus meetings. The RSSAC Caucus currently meets at every other/every even-numbered IETF meeting. There was general consensus that the RSSAC Caucus should also meet at ICANN meetings (but not Policy Forum/B format). The RSSAC Co-Chairs would like to propose the following framework for RSSAC Caucus meetings: · Keep the every other/every even-numbered IETF meeting cycle · Add ICANN Annual General Meetings/C format The proposed schedule for 2016-2019 is attached. All feedback is welcome. The next RSSAC Caucus meeting will be at ICANN57 in Hyderabad, India—exact date, time, and location will be confirmed soon. Thank you, Carlos (on behalf of Tripti Sinha and Brad Verd, RSSAC Co-Chairs) 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] Welcome Two New Members!
by Carlos Reyes Aug. 12, 2016

Aug. 12, 2016

Dear RSSAC Caucus, I hope you are well. At the recommendation of the RSSAC Caucus Membership Committee, the RSSAC approved two new members of the RSSAC Caucus: · Shane Kerr · Ryan Stephenson The statements of interest can be found here, and they have been added to this distribution list. Please join me in welcoming them! 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] 30 June minutes
by Carlos Reyes Aug. 8, 2016

Aug. 8, 2016

Hello, all. The RSSAC has approved the minutes from the 30 June RSSAC meeting/teleconference. They have been published on the RSSAC meetings page: https://www.icann.org/resources/pages/rssac-meetings-2014-05-06-en 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] RSSAC Liaison to the ICANN Nominating Committee
by Tripti Sinha Aug. 5, 2016

Aug. 5, 2016

Dear RSSAC Caucus, Yesterday, the RSSAC reappointed Alejandro Acosta as its liaison to the ICANN Nominating Committee for 2017. This will be the second one-year term for Alejandro. In July 2017, we will conduct the annual nomination and selection process for this role. Alejandro will be eligible for one more one-year term per RSSAC Operational Procedures. We would like to acknowledge Alejandro for representing RSSAC this past year and for volunteering to continue in this role for another year. Thank you to everyone who participated in the nomination process this year as well. Best regards, Tripti Sinha and Brad Verd RSSAC Co-Chairs

1 0

[rssac-caucus] RSSAC Liaison to the Nominating Committee
by Carlos Reyes Aug. 4, 2016

Aug. 4, 2016

Hello, RSSAC Caucus. Last week, the RSSAC Co-Chairs received a request from the ICANN Nominating Committee support staff to appoint a liaison for 2017. To learn more about the role, please refer to the attachment. The ICANN Nominating Committee support staff asked for a name by 5 August. The RSSAC Co-Chairs would like to acknowledge the request and still honor the established process. Therefore, the compressed timeline will require a shorter than preferred nomination period. (The relevant sections from “RSSAC000v2: Operational Procedures” are below for your reference.) With this notice, a one-week nomination period via this distribution list is now open. Nominations or self-nominations 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 3 August. The RSSAC will then consider the slate of candidates on its 4 August teleconference. As you may recall, the RSSAC elected Alejandro Acosta to this role for 2016. Per the RSSAC Operational Procedures, Alejandro is eligible for re-election by the RSSAC. The RSSAC Co-Chairs appreciate your flexibility and consideration. Please do not hesitate to contact the RSSAC Co-Chairs or support staff with any questions or concerns. Best, Carlos 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

6 8