- rssac-caucus - lists.icann.org

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

Annual update of the RSSAC FAQ
by Andrew McConachie Sept. 12, 2019

Sept. 12, 2019

Dear RSSAC Caucus Members, The RSSAC Workplan states that the RSSAC should update the FAQ every year by December. <https://www.icann.org/en/system/files/files/rssac-work-plan-01apr19-en.pdf> I’ve placed the current RSSAC FAQ into a Google doc. <https://docs.google.com/document/d/1rG35p77RwBZrQq0YII2NlInVdiApADJKVL8Rl6P…> I reorganized the questions into sections so it can have a table of contents. All other changes to it have been added as suggestions, so the diff represents what is new. The only new question is 2.7. Please provide any suggested edits by September 1st, 2019. Thanks, Andrew

1 3

RSSAC Caucus Travel Support for IETF 106 Singapore
by Ozan Sahin Sept. 10, 2019

Sept. 10, 2019

Dear RSSAC Caucus, The RSSAC has approved guidelines for RSSAC Caucus members requesting travel support to attend even numbered IETF meetings. Please see the approved guidelines attached. IETF 106 will take place in Singapore from 16 - 22 November 2019. There is travel support for up to four (4) RSSAC Caucus Members to attend IETF 106 including economy class airfare, accommodation, registration, and per diem. Depending on how many requests we receive, the RSSAC Administrative Committee may need to make the selection based on the selection criteria outlined in the guidelines. If you would like to apply and be considered for travel support, please complete the following form by next Tuesday, 10 September 2018: https://forms.gle/VcNybeW8tPp4oSmn6 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 1

Some early results looking at publication latency
by Paul Hoffman Sept. 4, 2019

Sept. 4, 2019

Greetings. This data might be useful for tomorrow's Metrics WP call. In my proof-of-concept testbed, I am now collecting the SOA values that are coming in for the response latency tests. The output below shows the results of the five-minute gaps where not all the SOAs matched over a couple of days. >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. FWIW, based on feedback from my earlier response latency numbers, I reduced the number of collectors to 8 instead of having multiple collectors in the same city. I hope this helps. --Paul Hoffman There are 213354 result recordss in the database Out of 513 five-minute gaps, 14 have more than one SOA 20190902:221502 (1567487702): a 2019090201: 14 2019090300: 20 b 2019090201: 19 2019090300: 13 c 2019090201: 22 2019090300: 06 d 2019090201: 22 2019090300: 06 e 2019090201: 22 2019090300: 06 f 2019090201: 24 2019090300: 04 g 2019090201: 26 2019090300: 05 h 2019090201: 24 2019090300: 07 i 2019090201: 28 2019090300: 02 j 2019090201: 24 2019090300: 06 k 2019090201: 27 2019090300: 04 l 2019090201: 32 2019090300: 00 m 2019090201: 28 2019090300: 04 20190902:222002 (1567488002): a 2019090201: 00 2019090300: 29 b 2019090201: 00 2019090300: 32 c 2019090201: 00 2019090300: 36 d 2019090201: 00 2019090300: 35 e 2019090201: 00 2019090300: 32 f 2019090201: 02 2019090300: 30 g 2019090201: 00 2019090300: 30 h 2019090201: 00 2019090300: 33 i 2019090201: 00 2019090300: 34 j 2019090201: 00 2019090300: 34 k 2019090201: 01 2019090300: 31 l 2019090201: 23 2019090300: 09 m 2019090201: 00 2019090300: 32 ===== 20190903:101002 (1567530602): a 2019090300: 17 2019090301: 15 b 2019090300: 22 2019090301: 13 c 2019090300: 24 2019090301: 10 d 2019090300: 27 2019090301: 03 e 2019090300: 25 2019090301: 06 f 2019090300: 28 2019090301: 03 g 2019090300: 27 2019090301: 04 h 2019090300: 28 2019090301: 04 i 2019090300: 28 2019090301: 04 j 2019090300: 28 2019090301: 04 k 2019090300: 29 2019090301: 03 l 2019090300: 31 2019090301: 01 m 2019090300: 30 2019090301: 02 20190903:101503 (1567530903): a 2019090300: 00 2019090301: 36 b 2019090300: 00 2019090301: 36 c 2019090300: 00 2019090301: 35 d 2019090300: 00 2019090301: 39 e 2019090300: 00 2019090301: 39 f 2019090300: 04 2019090301: 35 g 2019090300: 00 2019090301: 36 h 2019090300: 00 2019090301: 36 i 2019090300: 03 2019090301: 32 j 2019090300: 00 2019090301: 35 k 2019090300: 01 2019090301: 33 l 2019090300: 12 2019090301: 22 m 2019090300: 00 2019090301: 34 20190903:102002 (1567531202): a 2019090300: 00 2019090301: 28 b 2019090300: 00 2019090301: 26 c 2019090300: 00 2019090301: 25 d 2019090300: 00 2019090301: 26 e 2019090300: 00 2019090301: 27 f 2019090300: 02 2019090301: 26 g 2019090300: 00 2019090301: 27 h 2019090300: 00 2019090301: 28 i 2019090300: 00 2019090301: 26 j 2019090300: 00 2019090301: 26 k 2019090300: 00 2019090301: 28 l 2019090300: 00 2019090301: 30 m 2019090300: 00 2019090301: 30 ===== 20190903:221503 (1567574103): a 2019090301: 16 2019090400: 18 b 2019090301: 31 2019090400: 07 c 2019090301: 35 2019090400: 02 d 2019090301: 26 2019090400: 10 e 2019090301: 25 2019090400: 11 f 2019090301: 38 2019090400: 00 g 2019090301: 26 2019090400: 10 h 2019090301: 30 2019090400: 04 i 2019090301: 32 2019090400: 00 j 2019090301: 27 2019090400: 04 k 2019090301: 34 2019090400: 00 l 2019090301: 32 2019090400: 00 m 2019090301: 30 2019090400: 02 20190903:222003 (1567574403): a 2019090301: 00 2019090400: 31 b 2019090301: 00 2019090400: 30 c 2019090301: 14 2019090400: 18 d 2019090301: 02 2019090400: 32 e 2019090301: 00 2019090400: 34 f 2019090301: 22 2019090400: 12 g 2019090301: 01 2019090400: 32 h 2019090301: 10 2019090400: 28 i 2019090301: 24 2019090400: 14 j 2019090301: 00 2019090400: 39 k 2019090301: 26 2019090400: 08 l 2019090301: 28 2019090400: 06 m 2019090301: 00 2019090400: 34 20190903:222504 (1567574704): a 2019090301: 00 2019090400: 35 b 2019090301: 00 2019090400: 35 c 2019090301: 00 2019090400: 34 d 2019090301: 00 2019090400: 34 e 2019090301: 00 2019090400: 34 f 2019090301: 06 2019090400: 28 g 2019090301: 00 2019090400: 34 h 2019090301: 00 2019090400: 34 i 2019090301: 00 2019090400: 33 j 2019090301: 00 2019090400: 33 k 2019090301: 01 2019090400: 32 l 2019090301: 00 2019090400: 33 m 2019090301: 00 2019090400: 34 20190903:223002 (1567575002): a 2019090301: 00 2019090400: 29 b 2019090301: 00 2019090400: 27 c 2019090301: 00 2019090400: 28 d 2019090301: 00 2019090400: 26 e 2019090301: 00 2019090400: 22 f 2019090301: 02 2019090400: 18 g 2019090301: 00 2019090400: 19 h 2019090301: 00 2019090400: 22 i 2019090301: 00 2019090400: 23 j 2019090301: 00 2019090400: 22 k 2019090301: 00 2019090400: 27 l 2019090301: 00 2019090400: 28 m 2019090301: 00 2019090400: 28 20190903:223504 (1567575304): a 2019090301: 00 2019090400: 35 b 2019090301: 00 2019090400: 35 c 2019090301: 00 2019090400: 36 d 2019090301: 00 2019090400: 36 e 2019090301: 00 2019090400: 40 f 2019090301: 04 2019090400: 38 g 2019090301: 00 2019090400: 38 h 2019090301: 00 2019090400: 40 i 2019090301: 00 2019090400: 38 j 2019090301: 00 2019090400: 39 k 2019090301: 00 2019090400: 38 l 2019090301: 00 2019090400: 36 m 2019090301: 00 2019090400: 36 20190903:224003 (1567575603): a 2019090301: 00 2019090400: 32 b 2019090301: 00 2019090400: 36 c 2019090301: 00 2019090400: 34 d 2019090301: 00 2019090400: 34 e 2019090301: 00 2019090400: 34 f 2019090301: 02 2019090400: 32 g 2019090301: 00 2019090400: 32 h 2019090301: 00 2019090400: 34 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:081003 (1567609803): a 2019090400: 18 2019090401: 18 b 2019090400: 22 2019090401: 17 c 2019090400: 24 2019090401: 14 d 2019090400: 26 2019090401: 14 e 2019090400: 28 2019090401: 14 f 2019090400: 30 2019090401: 12 g 2019090400: 29 2019090401: 11 h 2019090400: 30 2019090401: 08 i 2019090400: 30 2019090401: 07 j 2019090400: 30 2019090401: 06 k 2019090400: 30 2019090401: 06 l 2019090400: 38 2019090401: 00 m 2019090400: 32 2019090401: 04 20190904:081502 (1567610102): a 2019090400: 00 2019090401: 26 b 2019090400: 00 2019090401: 24 c 2019090400: 00 2019090401: 26 d 2019090400: 00 2019090401: 23 e 2019090400: 00 2019090401: 22 f 2019090400: 04 2019090401: 18 g 2019090400: 00 2019090401: 23 h 2019090400: 00 2019090401: 28 i 2019090400: 01 2019090401: 24 j 2019090400: 00 2019090401: 30 k 2019090400: 00 2019090401: 28 l 2019090400: 12 2019090401: 15 m 2019090400: 00 2019090401: 28 20190904:082004 (1567610404): a 2019090400: 00 2019090401: 42 b 2019090400: 00 2019090401: 44 c 2019090400: 00 2019090401: 44 d 2019090400: 00 2019090401: 45 e 2019090400: 00 2019090401: 45 f 2019090400: 02 2019090401: 42 g 2019090400: 00 2019090401: 42 h 2019090400: 00 2019090401: 42 i 2019090400: 03 2019090401: 34 j 2019090400: 00 2019090401: 38 k 2019090400: 00 2019090401: 38 l 2019090400: 00 2019090401: 41 m 2019090400: 00 2019090401: 41

1 0

RSSAC Meeting Minutes | 6 August 2019 Teleconference
by Ozan Sahin Sept. 4, 2019

Sept. 4, 2019

Dear RSSAC Caucus Members, The meeting minutes from 6 August 2019 RSSAC Meeting have been approved during the last RSSAC Teleconference on Tuesday, 3 September 2019. 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. 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

Revisiting RSSAC002v3
by Andrew McConachie Aug. 20, 2019

Aug. 20, 2019

Dear RSSAC Caucus, RSSAC002v3 recommendation 3 states: "Measurements outlined in this document should be revisited in two years to accommodate changes in DNS technologies." <https://www.icann.org/en/system/files/files/rssac-002-measurements-root-06j…> RSSAC002v3 was published in June 2016 so we are over due in revisiting it. The purpose of this mail is to solicit feedback on whether a new version of RSSAC002 is needed. If you feel there is a compelling reason for the RSSAC to produce a new version of RSSAC002 please reply all to this email. Please explain the reason why and which measurement(s) you believe should be altered. Please reply all to this email by September 1, 2019. Thanks, Andrew

8 11

Two new RSSAC Caucus members
by Carlos Reyes Aug. 14, 2019

Aug. 14, 2019

Dear all, The RSSAC recently adopted the recommendation of the RSSAC Caucus Membership Committee to appoint two new RSSAC Caucus members: · Michael Casadevall · Chris Ishisoko They have been subscribed to this mailing list and their statements of interest are available here: https://community.icann.org/display/RSI/RSSAC+Caucus+Statements+of+Interest Please join me in welcoming them. Best, Carlos Carlos Reyes Strategic Policy Planning Director Internet Corporation for Assigned Names and Numbers (ICANN) +1 202 802 8019 www.icann.org

1 0