September 2019 - rssac-caucus

Threat Mitigation for the Root Server System
by Joe Abley Oct. 4, 2019

Oct. 4, 2019

Hi all, I noticed this document today, published last month: https://root-servers.org/publications/Threat_Mitigation_For_the_Root_Server… <https://root-servers.org/publications/Threat_Mitigation_For_the_Root_Server…> Although I haven't gone through it in detail and could no doubt come up with some comments if I was asked to review it, this looks like a nice document. It'd be nice if it was citable and easier to find. Is there a reason it wasn't published through the RSSAC process? Or is the audience of this document other root server operators, and its publication a (welcome!) exercise in transparency? The introduction contains the phrase "Root Ops community" but I find that slightly ambiguous. I realise I'm crossing the streams a bit by asking here, but it seems like the right people will hear the question, and others here might be interested in the answer. Also if it's entirely obvious to everybody else here why this has happened the resulting public beating with clue bats will surely be therapeutic. Joe

6 12

[RSS Metrics WP] INPUT REQUESTED: Performance Thresholds for Root Servers and Root Server System
by Steve Sheng Sept. 28, 2019

Sept. 28, 2019

Dear RSSAC Metrics WP [and RSSAC Caucus Members], At the next call of the metrics WP, the metrics WP will discuss performance thresholds for individual root servers and the root server system as a whole. To prepare for those discussions, the co-chairs have requested that you fill out the following spreadsheet ahead of the meeting and provide your input. https://docs.google.com/spreadsheets/d/1ZM-eI3SLsG8QVic_bN8W15R52o3ZWXTu7OP… Kindly fill out the spreadsheet by COB Wed 18 September 2019. Best Steve

6 9

RSS Metrics WP Presentation Materials
by Ozan Sahin Sept. 27, 2019

Sept. 27, 2019

Dear all, Please find attached the presentation materials for the RSS Metrics WP discussions to be held at RSSAC October Workshop next week. We encourage you to review these materials ahead of the workshop. 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: Thursday, September 26, 2019 at 3:38 PM To: "rssac-caucus(a)icann.org" <rssac-caucus(a)icann.org> Subject: RSSAC Workshop Schedule and 3 October RSSAC Monthly Meeting Agenda Dear RSSAC Caucus, Please see below the RSSAC workshop schedule as well as 3 October RSSAC monthly meeting agenda: 1. Workshop Agenda: https://docs.google.com/document/d/1fOX707jmlPoaZrabbEvxqXcrkgrx8k3LGPf4kre… 2. RSSAC Monthly Meeting Agenda: https://docs.google.com/document/d/1AicBeuR3Jz9luS-1nQDOlBNbYKnDnbzNsM2sZ0H… PDF versions are also attached. Presentation materials for the RSS Metrics WP discussion will be shared shortly. We encourage you to read these materials ahead of the workshop. 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

RSSAC Workshop Schedule and 3 October RSSAC Monthly Meeting Agenda
by Ozan Sahin Sept. 26, 2019

Sept. 26, 2019

Dear RSSAC Caucus, Please see below the RSSAC workshop schedule as well as 3 October RSSAC monthly meeting agenda: 1. Workshop Agenda: https://docs.google.com/document/d/1fOX707jmlPoaZrabbEvxqXcrkgrx8k3LGPf4kre… 2. RSSAC Monthly Meeting Agenda: https://docs.google.com/document/d/1AicBeuR3Jz9luS-1nQDOlBNbYKnDnbzNsM2sZ0H… PDF versions are also attached. Presentation materials for the RSS Metrics WP discussion will be shared shortly. We encourage you to read these materials ahead of the workshop. 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

Tests on Resolver Testbed
by Paul M Sept. 23, 2019

Sept. 23, 2019

I was wondering what kind of tests are of interest in investigating resolver behaviour. I appreciate any feedback on how to begin conducting the tests. Best Regards, Paul Muchene

4 3

Plan for Updating RSSAC002
by Andrew McConachie Sept. 20, 2019

Sept. 20, 2019

Dear RSSAC Caucus, Thanks to everyone who contributed to the discussions around updating RSSAC002. Based on this feedback the RSSAC Admin Committee suggests the following list of topics to be covered in the update. Draft Topics List: A) Agree to new terminology around 'latency' B) Discuss removing root zone size measurements C) Discuss adding metric to measure number of resource records changed between zone updates D) Discuss adding metric to measure QNAME minimization The overall plan is to work through the topics list sequentially, one item at a time, securing consensus on each item before moving onto the next. For each topic at least one meeting will be held for discussion. More can be held if necessary. Mailing list discussions will use this list. This should be more lightweight than forming a work party and it provides discrete agendas for the meetings. For Caucus members not interested in a particular topic they can safely avoid that topic’s meeting(s). So I have two questions for the Caucus. First, is this a good overall plan for producing RSSAC002v4? Second, is the list of topics at the top of this mail the correct list and is it in the correct order? Please respond by September 26. Thanks, Andrew

4 9

Some very different early results looking at publication latency
by Paul Hoffman Sept. 18, 2019

Sept. 18, 2019

Hi there. If you read my last message, you saw some data at the bottom. It turns out the data was all wrong. Duane caught the fact that some of it was clearly wrong, and after a bunch of futzing with my report program, I saw the error (hint: time gaps are hard). The new data is below. >From the output, you can see that it is not always the same RSO that is lagging. None of the SOA transitions of the four so far took place in a single five-minute window. Looking at the individual measurements, some collectors see different SOAs from the same RSO in the same collection period between v4 and v6; this could be routing differences, Some collectors see different SOAS from the same RSO in the same collection period between TCP and UDP; this is possibly due to load balancers and some of the systems behind them not being updated at the same time. I hope this helps. --Paul Hoffman There are 213354 result records in the database Out of 4638 five-minute gaps, 12 have more than one SOA ========== 20190902:221500 (1567487700): a 2019090201: 30 2019090300: 02 b 2019090201: 32 2019090300: 00 c 2019090201: 32 2019090300: 00 d 2019090201: 32 2019090300: 00 e 2019090201: 32 2019090300: 00 f 2019090201: 32 2019090300: 00 g 2019090201: 32 2019090300: 00 h 2019090201: 28 2019090300: 04 i 2019090201: 32 2019090300: 00 j 2019090201: 28 2019090300: 04 k 2019090201: 30 2019090300: 02 l 2019090201: 32 2019090300: 00 m 2019090201: 30 2019090300: 02 20190902:222000 (1567488000): a 2019090201: 00 2019090300: 32 b 2019090201: 00 2019090300: 32 c 2019090201: 00 2019090300: 32 d 2019090201: 00 2019090300: 32 e 2019090201: 00 2019090300: 32 f 2019090201: 04 2019090300: 28 g 2019090201: 00 2019090300: 30 h 2019090201: 00 2019090300: 32 i 2019090201: 00 2019090300: 32 j 2019090201: 00 2019090300: 32 k 2019090201: 01 2019090300: 31 l 2019090201: 25 2019090300: 07 m 2019090201: 00 2019090300: 32 ========== 20190903:101500 (1567530900): a 2019090300: 00 2019090301: 32 b 2019090300: 00 2019090301: 32 c 2019090300: 00 2019090301: 30 d 2019090300: 04 2019090301: 28 e 2019090300: 00 2019090301: 32 f 2019090300: 04 2019090301: 28 g 2019090300: 00 2019090301: 31 h 2019090300: 00 2019090301: 32 i 2019090300: 03 2019090301: 28 j 2019090300: 00 2019090301: 31 k 2019090300: 01 2019090301: 30 l 2019090300: 13 2019090301: 19 m 2019090300: 00 2019090301: 32 20190903:102000 (1567531200): a 2019090300: 00 2019090301: 32 b 2019090300: 00 2019090301: 32 c 2019090300: 00 2019090301: 32 d 2019090300: 00 2019090301: 32 e 2019090300: 00 2019090301: 32 f 2019090300: 04 2019090301: 28 g 2019090300: 00 2019090301: 32 h 2019090300: 00 2019090301: 32 i 2019090300: 00 2019090301: 32 j 2019090300: 00 2019090301: 32 k 2019090300: 00 2019090301: 32 l 2019090300: 00 2019090301: 32 m 2019090300: 00 2019090301: 32 ========== 20190903:222000 (1567574400): a 2019090301: 00 2019090400: 32 b 2019090301: 10 2019090400: 22 c 2019090301: 25 2019090400: 06 d 2019090301: 04 2019090400: 28 e 2019090301: 01 2019090400: 31 f 2019090301: 32 2019090400: 00 g 2019090301: 01 2019090400: 29 h 2019090301: 12 2019090400: 20 i 2019090301: 28 2019090400: 02 j 2019090301: 00 2019090400: 32 k 2019090301: 30 2019090400: 02 l 2019090301: 29 2019090400: 02 m 2019090301: 00 2019090400: 32 20190903:222500 (1567574700): a 2019090301: 00 2019090400: 32 b 2019090301: 00 2019090400: 32 c 2019090301: 00 2019090400: 32 d 2019090301: 00 2019090400: 32 e 2019090301: 00 2019090400: 32 f 2019090301: 04 2019090400: 28 g 2019090301: 00 2019090400: 31 h 2019090301: 00 2019090400: 32 i 2019090301: 00 2019090400: 32 j 2019090301: 00 2019090400: 32 k 2019090301: 01 2019090400: 31 l 2019090301: 01 2019090400: 31 m 2019090301: 00 2019090400: 32 20190903:223000 (1567575000): a 2019090301: 00 2019090400: 32 b 2019090301: 00 2019090400: 32 c 2019090301: 00 2019090400: 32 d 2019090301: 00 2019090400: 32 e 2019090301: 00 2019090400: 32 f 2019090301: 04 2019090400: 28 g 2019090301: 00 2019090400: 31 h 2019090301: 00 2019090400: 32 i 2019090301: 00 2019090400: 32 j 2019090301: 00 2019090400: 32 k 2019090301: 00 2019090400: 32 l 2019090301: 00 2019090400: 32 m 2019090301: 00 2019090400: 32 20190903:223500 (1567575300): a 2019090301: 00 2019090400: 32 b 2019090301: 00 2019090400: 32 c 2019090301: 00 2019090400: 32 d 2019090301: 00 2019090400: 32 e 2019090301: 00 2019090400: 32 f 2019090301: 04 2019090400: 28 g 2019090301: 00 2019090400: 29 h 2019090301: 00 2019090400: 32 i 2019090301: 00 2019090400: 32 j 2019090301: 00 2019090400: 31 k 2019090301: 00 2019090400: 32 l 2019090301: 00 2019090400: 32 m 2019090301: 00 2019090400: 32 20190903:224000 (1567575600): a 2019090301: 00 2019090400: 32 b 2019090301: 00 2019090400: 32 c 2019090301: 00 2019090400: 32 d 2019090301: 00 2019090400: 32 e 2019090301: 00 2019090400: 32 f 2019090301: 04 2019090400: 28 g 2019090301: 00 2019090400: 30 h 2019090301: 00 2019090400: 32 i 2019090301: 00 2019090400: 31 j 2019090301: 00 2019090400: 32 k 2019090301: 00 2019090400: 32 l 2019090301: 00 2019090400: 32 m 2019090301: 00 2019090400: 32 ========== 20190904:081500 (1567610100): a 2019090400: 00 2019090401: 32 b 2019090400: 00 2019090401: 32 c 2019090400: 00 2019090401: 32 d 2019090400: 00 2019090401: 32 e 2019090400: 00 2019090401: 32 f 2019090400: 04 2019090401: 28 g 2019090400: 00 2019090401: 30 h 2019090400: 00 2019090401: 32 i 2019090400: 01 2019090401: 27 j 2019090400: 00 2019090401: 32 k 2019090400: 00 2019090401: 31 l 2019090400: 18 2019090401: 14 m 2019090400: 00 2019090401: 32 20190904:082000 (1567610400): a 2019090400: 00 2019090401: 32 b 2019090400: 00 2019090401: 32 c 2019090400: 00 2019090401: 32 d 2019090400: 00 2019090401: 32 e 2019090400: 00 2019090401: 32 f 2019090400: 04 2019090401: 28 g 2019090400: 00 2019090401: 31 h 2019090400: 00 2019090401: 32 i 2019090400: 01 2019090401: 28 j 2019090400: 00 2019090401: 32 k 2019090400: 00 2019090401: 31 l 2019090400: 00 2019090401: 32 m 2019090400: 00 2019090401: 32 20190904:082500 (1567610700): a 2019090400: 00 2019090401: 32 b 2019090400: 00 2019090401: 32 c 2019090400: 00 2019090401: 32 d 2019090400: 00 2019090401: 32 e 2019090400: 00 2019090401: 32 f 2019090400: 00 2019090401: 32 g 2019090400: 00 2019090401: 29 h 2019090400: 00 2019090401: 32 i 2019090400: 02 2019090401: 27 j 2019090400: 00 2019090401: 32 k 2019090400: 00 2019090401: 32 l 2019090400: 00 2019090401: 31 m 2019090400: 00 2019090401: 32

4 5

ICANN66 Prep Week
by Ozan Sahin Sept. 17, 2019

Sept. 17, 2019

Dear RSSAC Caucus members, Yesterday, ICANN announced the dates of the ICANN66 Prep Week, an initiative that consolidates all pre-ICANN Public Meeting webinars into one week, with a link to the registration form. Prep Week will take place from 14-17 October offering seven (7) webinars. ICANN66 Prep Week Announcement: https://www.icann.org/news/announcement-2019-09-16-en Please feel free to sign-up for the webinars of your interest through the link below: Link to the registration form: http://go.icann.org/prepweeksignup 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

Re: [RSSAC Caucus] IETF 106 Travel Suport
by Steve Sheng Sept. 15, 2019

Sept. 15, 2019

Dear RSSAC Caucus, We have completed RFC3797 verifiable random selection. The list of people are: 1. Ihtisham Khalid 2. Abdulkarim Oloyede 3. Abdalmonem Tharwat Galila 4. Brian Dickson 5. Shailesh Gupta 6. Alejandro Acosta 7. Daniel Migault Randomness: * USA Pennyslvania Cash 5 Lottery Friday , 13 September 2019 – 1, 27,28,36,43 https://www.lotteryusa.com/pennsylvania/friday [lotteryusa.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.lotteryusa.com_pen…> * USA Mega millions Friday, 13 September 2019 – 5,6,16,37,59,62 (https://www.lotteryusa.com/mega-millions/) * NASDAQ closing index (rounded to the nearest integer) on Friday, September 13 2019 - 8177 https://finance.yahoo.com/quote/%5EIXIC/ [finance.yahoo.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__finance.yahoo.com_quot…> Results: Key String: 1.27.28.36.43./5.6.16.37.59.62./8177./ 6. Alejandro Acosta 4. Brian Dickson 1. Ihtisham Khalid 3. Abdalmonem Tharwat Galila 5. Shailesh Gupta 7. Daniel Migault 2. Abdulkarim Oloyede Thus, Alejandro Acosta and Brian Dickson will receive funding to travel to IETF 106, in addition to Russ Mundy and Paul Muchene. Best Steve From: rssac-caucus <rssac-caucus-bounces(a)icann.org> on behalf of Steve Sheng <steve.sheng(a)icann.org> Date: Friday, September 13, 2019 at 4:12 PM To: "rssac-caucus(a)icann.org" <rssac-caucus(a)icann.org> Subject: [RSSAC Caucus] IETF 106 Travel Suport Dear RSSAC Caucus, We have received the following requests for travel support to IETF 106. 1. Ihtisham Khalid 2. Abdulkarim Oloyede 3. Abdalmonem Tharwat Galila 4. Brian Dickson 5. Paul Muchene 6. Shailesh Gupta 7. Alejandro Acosta 8. Daniel Migault 9. George (Russ) Mundy According to the latest guideline. We are allocating the following: * Russ Mundy (RSS Metrics WP chair) * Paul Muchene (active participant of the resolver WP, as determined by chairs) Please note: active participation in a work party meaning wp members participate in the writing and review of the working group document. For the remaining two slots, we will do a verifiable random selection as specified by RFC 3797. The process is as follows: Number of slots: 2 We use 3 Lists of Randomness: #1 USA Pennyslvania Cash 5 Lottery Friday , 13 September 2019 https://www.lotteryusa.com/pennsylvania/friday [lotteryusa.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.lotteryusa.com_pen…> #2 USA Mega millions Friday, 13 September 2019 (https://www.lotteryusa.com/mega-millions/) #3 NASDAQ closing index (rounded to the nearest integer) on Friday, September 13 2019 https://finance.yahoo.com/quote/%5EIXIC/ [finance.yahoo.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__finance.yahoo.com_quot…> A Publicly Verifiable Random Selection Process will be conducted by Staff on Saturday 14 September 2019, using the RFC 3797 method. The results (as well as other data) will be announced to the list on the same day, after which you can verify the result yourself. Best regards, Steve Sheng

2 1

IETF 106 Travel Suport
by Steve Sheng Sept. 13, 2019

Sept. 13, 2019

Dear RSSAC Caucus, We have received the following requests for travel support to IETF 106. 1. Ihtisham Khalid 2. Abdulkarim Oloyede 3. Abdalmonem Tharwat Galila 4. Brian Dickson 5. Paul Muchene 6. Shailesh Gupta 7. Alejandro Acosta 8. Daniel Migault 9. George (Russ) Mundy According to the latest guideline. We are allocating the following: * Russ Mundy (RSS Metrics WP chair) * Paul Muchene (active participant of the resolver WP, as determined by chairs) Please note: active participation in a work party meaning wp members participate in the writing and review of the working group document. For the remaining two slots, we will do a verifiable random selection as specified by RFC 3797. The process is as follows: Number of slots: 2 We use 3 Lists of Randomness: #1 USA Pennyslvania Cash 5 Lottery Friday , 13 September 2019 https://www.lotteryusa.com/pennsylvania/friday #2 USA Mega millions Friday, 13 September 2019 (https://www.lotteryusa.com/mega-millions/) #3 NASDAQ closing index (rounded to the nearest integer) on Friday, September 13 2019 https://finance.yahoo.com/quote/%5EIXIC/ A Publicly Verifiable Random Selection Process will be conducted by Staff on Saturday 14 September 2019, using the RFC 3797 method. The results (as well as other data) will be announced to the list on the same day, after which you can verify the result yourself. Best regards, Steve Sheng

1 0