- rssac-caucus - lists.icann.org

Publication of RSSAC052
by Andrew McConachie Dec. 7, 2020

Dec. 7, 2020

Dear RSSAC Caucus Members, The RSSAC has recently published RSSAC0052: Statement on Recommendations for an Early Warning System for Root Zone Scaling. RSSAC052 can be found here. <https://www.icann.org/en/system/files/files/rssac-052-25nov20-en.pdf <https://www.icann.org/en/system/files/files/rssac-052-25nov20-en.pdf>> RSSAC052 was also submitted to the ICANN Public Comment Proceeding on the same topic. Thanks, Andrew

1 1

Local Perspective Working Party
by ABDULKARIM OLOYEDE Dec. 4, 2020

Dec. 4, 2020

Dear RSSAC Caucus Members, The Local Perspective Working Party (WP) has had a monthly meeting since our inaugural meeting in April 2020. The aim of the WP is to develop metrics needed in measuring the local perspective to help improve internet services in general and RSS systems in particular. The WP hope to help identify inadequate infrastructure and identify locations for new RSS instance. This could also help give the end-user a measurement of their perspective of the RSS. The WP came up with a number of user narratives which has so far been reduced to 5 (This can be found at https://docs.google.com/document/d/1enH6LjICyAbKVr7ssps_4KapecRAROK0nZrw2ih… https://docs.google.com/document/d/1enH6LjICyAbKVr7ssps_4KapecRAROK0nZrw2ih… ). The user narratives are 1. Evaluating proposed locations for new root server instances 2. Identify currently underserved areas 3. Recursive resolver operators wanting to better understand the RSS 4. RSS data in support of research (*We are considering dropping this because we think it might be out of scope for the WP*) 5. Improve General Internet Connectivity/Access Please we would like you to go though the document and let us know if you agree with these narratives or not and if you have any suggestion. Also we would like to have your comments on the scope of this work in general especially if you think the WP is going beyond what is expected. The scope can be found at https://docs.google.com/document/d/1DVtC3DA-oxAvERGYsSdOAcBdmCsDEOwuNU1v5TA… .We are getting to a stage where we need to have the opinion of the member of RSSAC caucus. The recording and agenda for previous meeting can be found at https://community.icann.org/display/RSSAC/RSSAC+Caucus+Local+Perspective+To… Please more impotantly, we need more people to volunteer and help in contributing and writing up the report of the WP. The proposed outline of the repot can be found at https://docs.google.com/document/d/11slZDTqrcwTwywpbi3JwHuU_FoaoN54u0f3B2UF… <https://docs.google.com/document/d/11slZDTqrcwTwywpbi3JwHuU_FoaoN54u0f3B2UF…> I look forward to many of us contibuting and joinning our next meeting scheduled for 14th Decmber 2020 at 16 Abdulkarim Oloyede WP Leader -- Website <http://www.unilorin.edu.ng>, Weekly Bulletin <http://www.unilorin.edu.ng/index.php/bulletin> UGPortal <http://uilugportal.unilorin.edu.ng/> PGPortal <https://uilpgportal.unilorin.edu.ng/>

1 0

Two Updates
by Ozan Sahin Dec. 3, 2020

Dec. 3, 2020

Dear RSSAC Caucus Members, I have two updates to share: 1. The meeting minutes from 3 November 2020 RSSAC Meeting have been approved during the last RSSAC Teleconference on Tuesday, 1 December 2020. The meeting minutes have been posted on the RSSAC Meetings page https://www.icann.org/resources/pages/rssac-meetings-2014-05-06-en. You may also find the meeting minutes attached to this note. 1. The RSSAC recently adopted the recommendation of the RSSAC Caucus Membership Committee to appoint a new RSSAC Caucus Member: Daniel Mahoney. Daniel has been subscribed to this mailing list and his statement of interest is available here: https://community.icann.org/display/RSI/RSSAC+Caucus+Statements+of+Interest. Please join me in welcoming Daniel. 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>

3 2

Rogue Operator Work Party: Meeting Summary
by Renard, Kenneth D CTR USARMY CCDC C5ISR (USA) Nov. 30, 2020

Nov. 30, 2020

Rogue Operator Work Party Meeting Notes – 24 November 2020 The primary discussion of today’s meeting was around the RSSAC037 guiding principles and document organization describing what it means for an RSO to be rogue. Instead of describing specific principles and examples of violating each, it was proposed to describe major activities and examples of rogue behavior in 2 different sections: Objective/Technical/Measureable? This section will pretty much be a summary of actions/examples described in the current document for Guiding principles #2 and #6. Things like changing or removing zone contents, or using alternate protocols. Note that some types of technical behaviors are not easily measured. Subjective/Non-Technical/Unmeasureable This section will be smaller section which references actions that _could_ lead to a rogue operator situation, but are not strict (binary) indicators. The document shall not explicitly define actions that are rogue, but instead describe work party discussions on activities that are undesirable or could be further investigated by the SAPF to determine if they constitute a rogue operator. These would replace the current section titled “Definition of a Rogue Operator”. Paul Hoffman graciously volunteered to draft the first section, and I will draft the second section. As always, assistance, comments, and thoughts to the process are greatly appreciated via the working document as well as via the RSSAC Caucus mail list and work party meetings Steve has created a new Google doc which has RSSAC formatting and can hopefully be accessed fully by ICANN accounts. https://docs.google.com/document/d/1XS2dIl_Sv1f7e4pA19QHnHEmLgRSkgEI2-zD7Tp… Thank you to all that participated in today’s call and for your input. Ken Renard S&TCD Contractor – ICF Sustaining Base Network Assurance Branch C5ISR Center, Space and Terrestrial Communications Directorate Office: 443-395-7809 kenneth.d.renard.ctr(a)mail.mil

2 1

Work Party: Statistical Prediction of RSS Failure
by Fred Baker Nov. 28, 2020

Nov. 28, 2020

Brad and I are looking at the question implied by the public call for comments at "Recommendations for Early Warning for Root Zone Scaling" <https://www.icann.org/public-comments/recommendations-early-warning-root-sc…>. My sense is that we don't know how to detect the onset of a potential problem. We wonder whether the Caucus might help us out - looking at extant statistics and other data to see if there is something that might be used as a triggering condition. RSSAC raised this question in RSSAC031, and SSAC raised it in SSAC100. We have a number of years worth of RSSAC002 data (and, if its useful, there is also DITL data) to review in https://github.com/rssac-caucus/rssac002-data, or reachable from https://root-servers.org. A proposed approach, at least to investigating the question, would be to: - start from https://github.com/rssac-caucus/rssac002-data - download available RSSAC002 data (there should be data for most RSOs for several years) - observe statistics around past burbles - if something jumps out, investigate it further and document it I could imagine this being a post-doc's paper, published somewhere, but I do want the caucus to be able to see it pre-publication, with any necessary confidentiality provisions (as in, if you send a paper to this list and you need to keep it confidential, please say so). What we might learn is that RSSAC002 data doesn't address the issue, but it might by adding some new statistic to it, or we might find it by looking at RSSAC047 data or that plus some new statistic added to it. The obvious question there would be to describe, prototype, and characterize the indicated data. For the record, I have done things like this myself in the past. Cloudflare started providing an anycast service to ISC in April of a few years ago, and the following August took a ten day outage for reasons I don't recall. I downloaded the indicated statistics and stuffed them into an Excel spreadsheet, from which I derived a graphic. In the graphic, I was able to observe: - a stable period before the outage - a transition period when the outage started, during which request/response traffic moved to other servers - a stable period during the outage - a transition period when the outage ended, during which request/response traffic moved back - a stable period after the outage. The question would be whether we could look at several events and see if there is some identifiable statistical behavior that consistently predicts an outage. Another discussion, a little more in the direction of pins with angels partying on them, would be to brainstorm what a failure of the RSS might look like and investigate that - what does a systemic failure look like? How would one detect such a failure? Let's make this a work party, in the sense that I'm the work party shepherd and interested people can also be part. If you want to be an investigator in the project, please reply to this email.

3 4

Initial implementation of RSSAC047
by Paul Hoffman Nov. 28, 2020

Nov. 28, 2020

Greetings again. As we discussed during the preparation of RSSAC047, ICANN org was going to create an initial implementation of the requirements in the document. The primary goal of this implementation is to help the RSSAC Caucus think more about metrics collecting. I have prepared a very early cut of the initial implementation: https://github.com/icann/root-metrics It is mostly (but not completely) functional, but could probably use a lot of help from the Caucus to make it more useful. If you have a GitHub account, please feel free to open issues or send pull requests. Note that I'm doing this as part of ICANN org, not as a formal part of the Caucus work. I'll add and fix things as a best-effort task among the rest of my work. One important note is that I have not set up the expected 20 vantage points, but am starting to do so now. I expect to have 20 up before the end of June so that the report at the end of July is representative (although it is likely to have flaws due to this being a very early implementation). I am having problems finding enough locations for vantage points in South America and Africa, but believe that I can have those regions filled in adequately in August. Let me know what you think, either in email or by opening issues. I'll send periodic progress reports to the Caucus mailing list. --Paul Hoffman

3 2

RSSAC Caucus Rogue RSO WP Teleconference #9 | Tuesday, 15 December | 14:00-15:00 UTC
by Ozan Sahin Nov. 25, 2020

Nov. 25, 2020

Ozan Sahin is inviting you to a scheduled Zoom meeting. Topic: RSSAC Caucus Rogue RSO WP Call #9 Time: Dec 15, 2020 02:00 PM Universal Time UTC Agenda: TBD Work party wiki space: https://community.icann.org/x/IonsBw Join Zoom Meeting https://icann.zoom.us/j/93981279806?pwd=TUdIYU9wSWJaelRJT2Y3cWJ5UXRLdz09 Meeting ID: 939 8127 9806 Passcode: TKgY#5b7H8 One tap mobile +16699006833,,93981279806#,,,,,,0#,,3860518454# US (San Jose) +12532158782,,93981279806#,,,,,,0#,,3860518454# US (Tacoma) Dial by your location         +1 669 900 6833 US (San Jose)         +1 253 215 8782 US (Tacoma)         +1 346 248 7799 US (Houston)         +1 312 626 6799 US (Chicago)         +1 929 436 2866 US (New York)         +1 301 715 8592 US (Washington D.C)         877 853 5247 US Toll-free         888 788 0099 US Toll-free         +61 8 7150 1149 Australia         +61 2 8015 6011 Australia         +61 3 7018 2005 Australia         +61 7 3185 3730 Australia         +61 8 6119 3900 Australia         1800 893 423 Australia Toll-free         1800 945 157 Australia Toll-free         1800 317 562 Australia Toll-free         +1 647 558 0588 Canada         +1 778 907 2071 Canada         +1 204 272 7920 Canada         +1 438 809 7799 Canada         +1 587 328 1099 Canada         +1 647 374 4685 Canada         855 703 8985 Canada Toll-free         +81 363 628 317 Japan         +81 524 564 439 Japan         +81 3 4578 1488 Japan         00 663 381 4092 Japan Toll-free         0 800 100 5040 Japan Toll-free         +31 20 794 7345 Netherlands         +31 707 006 526 Netherlands         +31 20 241 0288 Netherlands         +31 20 794 0854 Netherlands         +31 20 794 6519 Netherlands         +31 20 794 6520 Netherlands         0 800 022 1954 Netherlands Toll-free         0 800 220 0040 Netherlands Toll-free         +46 8 5052 0017 Sweden         +46 850 539 728 Sweden         +46 8 4468 2488 Sweden         +46 8 5016 3827 Sweden         +46 8 5050 0828 Sweden         +46 8 5050 0829 Sweden         0 200 123 514 Sweden Toll-free         0 200 123 720 Sweden Toll-free Meeting ID: 939 8127 9806 Passcode (for dial-in only): 386 0518 454 Find your local number: https://icann.zoom.us/u/ab6HHkOnwt

1 0

RSSAC Caucus Local Perspective Tool WP Teleconference #9 | Monday, 14 December | 16:00-17:00 UTC
by Ozan Sahin Nov. 25, 2020

Nov. 25, 2020

Ozan Sahin is inviting you to a scheduled Zoom meeting. Topic: RSSAC Caucus Local Perspective Tool WP Call #9 Time: Dec 14, 2020 04:00 PM Universal Time UTC Agenda: TBD Work party wiki space: https://community.icann.org/x/gInsBw Join Zoom Meeting https://icann.zoom.us/j/92961449914?pwd=T1QrNURHaEdpWkwwSjZNN3ArSnR6dz09 Meeting ID: 929 6144 9914 Passcode: 1BMZWet@EG One tap mobile +16699006833,,92961449914#,,,,,,0#,,3637619718# US (San Jose) +12532158782,,92961449914#,,,,,,0#,,3637619718# US (Tacoma) Dial by your location         +1 669 900 6833 US (San Jose)         +1 253 215 8782 US (Tacoma)         +1 346 248 7799 US (Houston)         +1 929 436 2866 US (New York)         +1 301 715 8592 US (Washington D.C)         +1 312 626 6799 US (Chicago)         877 853 5247 US Toll-free         888 788 0099 US Toll-free         +61 3 7018 2005 Australia         +61 7 3185 3730 Australia         +61 8 6119 3900 Australia         +61 8 7150 1149 Australia         +61 2 8015 6011 Australia         1800 945 157 Australia Toll-free         1800 317 562 Australia Toll-free         1800 893 423 Australia Toll-free         +1 587 328 1099 Canada         +1 647 374 4685 Canada         +1 647 558 0588 Canada         +1 778 907 2071 Canada         +1 204 272 7920 Canada         +1 438 809 7799 Canada         855 703 8985 Canada Toll-free         +81 524 564 439 Japan         +81 3 4578 1488 Japan         +81 363 628 317 Japan         00 663 381 4092 Japan Toll-free         0 800 100 5040 Japan Toll-free         +31 20 794 6519 Netherlands         +31 20 794 6520 Netherlands         +31 20 794 7345 Netherlands         +31 707 006 526 Netherlands         +31 20 241 0288 Netherlands         +31 20 794 0854 Netherlands         0 800 022 1954 Netherlands Toll-free         0 800 220 0040 Netherlands Toll-free         +46 8 5050 0828 Sweden         +46 8 5050 0829 Sweden         +46 8 5052 0017 Sweden         +46 850 539 728 Sweden         +46 8 4468 2488 Sweden         +46 8 5016 3827 Sweden         0 200 123 514 Sweden Toll-free         0 200 123 720 Sweden Toll-free Meeting ID: 929 6144 9914 Passcode (for dial-in only): 363 761 9718 Find your local number: https://icann.zoom.us/u/abtv39Z4LT

1 0

REMINDER: RSSAC Caucus Rogue RSO WP Teleconference #8 | Tuesday, 24 November | 14:00-15:00 UTC
by Ozan Sahin Nov. 23, 2020

Nov. 23, 2020

***REMINDER*** Ozan Sahin is inviting you to a scheduled Zoom meeting. Topic: RSSAC Caucus Rogue RSO WP Teleconference #8 Time: Nov 24, 2020 02:00 PM Universal Time UTC Agenda: https://docs.google.com/document/d/1kgZX4wI8nH-S-3JSKROS81sdKGi4bWXihwyrC6-… Work party wiki space: https://community.icann.org/x/IonsBw Join Zoom Meeting https://icann.zoom.us/j/93848452134?pwd=U2JYKzRFRVNKcXFmRm5FTndDYVI2dz09 Meeting ID: 938 4845 2134 Passcode: 8dnm6*$+a+ One tap mobile +16699006833,,93848452134#,,,,,,0#,,2524349345# US (San Jose) +12532158782,,93848452134#,,,,,,0#,,2524349345# US (Tacoma) Dial by your location         +1 669 900 6833 US (San Jose)         +1 253 215 8782 US (Tacoma)         +1 346 248 7799 US (Houston)         +1 301 715 8592 US (Washington D.C)         +1 312 626 6799 US (Chicago)         +1 929 436 2866 US (New York)         877 853 5247 US Toll-free         888 788 0099 US Toll-free         +61 3 7018 2005 Australia         +61 7 3185 3730 Australia         +61 8 6119 3900 Australia         +61 8 7150 1149 Australia         +61 2 8015 6011 Australia         1800 317 562 Australia Toll-free         1800 893 423 Australia Toll-free         1800 945 157 Australia Toll-free         +1 204 272 7920 Canada         +1 438 809 7799 Canada         +1 587 328 1099 Canada         +1 647 374 4685 Canada         +1 647 558 0588 Canada         +1 778 907 2071 Canada         855 703 8985 Canada Toll-free         +81 3 4578 1488 Japan         +81 363 628 317 Japan         +81 524 564 439 Japan         00 663 381 4092 Japan Toll-free         0 800 100 5040 Japan Toll-free         +31 20 241 0288 Netherlands         +31 20 794 0854 Netherlands         +31 20 794 6519 Netherlands         +31 20 794 6520 Netherlands         +31 20 794 7345 Netherlands         +31 707 006 526 Netherlands         0 800 022 1954 Netherlands Toll-free         0 800 220 0040 Netherlands Toll-free         +46 8 4468 2488 Sweden         +46 8 5016 3827 Sweden         +46 8 5050 0828 Sweden         +46 8 5050 0829 Sweden         +46 8 5052 0017 Sweden         +46 850 539 728 Sweden         0 200 123 514 Sweden Toll-free         0 200 123 720 Sweden Toll-free Meeting ID: 938 4845 2134 Passcode (for dial-in only): 2524349345 Find your local number: https://icann.zoom.us/u/adANbejloN

1 0

Local Perspective Work Party: "Underserved" use case text
by Ken Renard Nov. 22, 2020

Nov. 22, 2020

All: I have brought over the user narrative concerning RSOs wanting to determine underserved areas to the current working document. Along the way, I overhauled the description, hopefully making it more concise and readable. I think I have addressed all comments from the Narratives document. The new text is included below, but the google document will contain the latest edits. I would appreciate any comments or feedback on this topic and look forward to discussing it with the group at the work party meeting tomorrow (Monday). https://docs.google.com/document/d/11slZDTqrcwTwywpbi3JwHuU_FoaoN54u0f3B2UF… -Ken Renard While the RSS has relatively good global coverage, RSOs are interested in deploying additional instances, particularly to areas that are considered “underserved”. An underserved area has a reasonably-sized user base that perceives poor performance of the RSS due to its closest root server instances being topologically distant, resulting in high latency or low availability of the service. This is a subjective designation and it is not reasonable to expect that a tool could directly measure it. The metric described in this section serves only to inform a decision on placing new root server instances in an underserved area. A RSO would require multiple measurements run in diverse geographical locations. The goal of this metric is to assess performance of the RSS at a measurement point compared to other measurement points. A local metric that is much worse than others would be an indicator of an underserved area. Availability and latency are the primary measurements and the impact of slow links should be discarded. Since metric is trying to assess the performance of the RSS versus individual RSIs (Root Server Identities), only the best NRSI measurements should be used. The measurements are direct queries to the individual root servers (versus via a recursive resolver). A set of measurements should be taken at random intervals during a T=30 minute time period. All RSIs will be directly queried and their latencies recorded. Additionally, a normalization factor σ will be measured as the average latency of direct DNS queries to the first NTLD=20 somehow-chosen TLDs. If fewer than NTLD normalization measurements are available, the entire set of measurements are thrown away. Availability of an RSI is the success rate of queries to an RSI over the last 20 measurement periods that were not thrown away. The performance metric is the inverse of the average of the best NRSI=3 RSI latencies, where the availability for each of those RSIs is > p=0.65, divided by the normalization factor. Availability of an RSI: percentage of successful responses over the past 20 measurements Normalization factor: σ = mean latency of NTLD queries Normalized Latency = (best NRSI latencies where availability > p) / σ Performance Metric = 1 / Normalized Latency If fewer than NRSI latency measurements are available (due to timeouts), the performance metric should be multiplied by Navail / NRSI, where Navail is the number of RSIs that have availability > p. When comparing performance metrics among locations, the last 20 successful performance metrics should be averaged before comparison. The bottom P percentile among a large set of local performance metrics or performance metrics below a certain threshold (Θ) may be used to inform a determination of an underserved area. Determining P or Θ will require further analysis and will not be defined in this document.

2 3