- rssac-caucus - lists.icann.org

List of Research Papers about the RSS, was Possible new work for the Caucus
by Andrew McConachie March 27, 2023

March 27, 2023

Dear RSSAC Caucus, The RSSAC held their monthly meeting Tuesday and discussed the possibility of the Caucus hosting a list of research papers about the RSS. I took an action item to write this mail to the Caucus to continue the discussion and provide some feedback from the RSSAC. Any list that the Caucus maintains will likely be incomplete and can never be authoritative. There will always be papers that we don’t know about and the list will certainly grow over time. So while it’s an interesting idea, we may be biting off more that we can chew. We expect the list to start with a large number of papers (maybe 50-100?) and will grow significantly over time. [I recently helped create a similar list on routing security for the SSAC’s publication SAC121, and that list has a little over 100 entries, I suspect this list will start with a similar amount.] At that point it’s no longer a simple list, but rather a list of lists that must be broken up into categories. The management of this list would certainly require a considerable labor investment. It would be best if the people who want this list are therefore the ones who curate it. We can develop guidelines for curation, but the actual work should be handled by those who want to volunteer for creating and maintaining the list. A good first step would be for a Caucus member to curate a list themselves of the kind of papers they would like to see and share it. Maybe someone reading this already has such a list. Finally, assuming the RSSAC Caucus takes this work on and we develop guidelines for curation, are there any volunteers who are interested in managing this list of papers? Thanks, Andrew

8 20

Draft RSSAC Caucus Statement of Work Baseline Models for Outliers/Anomalies Detection in the DNS Root Server System
by Andrew McConachie March 26, 2023

March 26, 2023

Dear RSSAC Caucus Members, Here is a link to the SoW that Desselegn presented in today’s RSSAC Caucus meeting. <https://docs.google.com/document/d/1WRFzbbq0rU8Doyo1dhTdfB4xG4HmDyhli-6KqFM…> Thanks, Andrew

1 0

RSSAC Meeting Minutes | 14 February 2023 Meeting
by Ozan Sahin March 26, 2023

March 26, 2023

Dear RSSAC Caucus Members, The meeting minutes from 14 February 2023 RSSAC Teleconference have been approved during the RSSAC Meeting on Tuesday, 14 March 2023. 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 Development Support Senior Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

1 0

RSSAC Caucus Meeting at IETF 116
by Ozan Sahin March 26, 2023

March 26, 2023

Dear RSSAC Caucus members, Next RSSAC Caucus meeting will take place at IETF 116 in Yokohama, Japan. The meeting will be held on Sunday, 26 March in Pacifico North Yokohama from 15:30 – 17:00 JST (local time), 06:30 – 08:00 UTC. Pacifico North Yokohama is the IETF 116 venue. Please find the proposed agenda for this meeting attached and here: https://docs.google.com/document/d/1X5za8TfDMQigjIvuv-PvCzFcZs6S3-LxLNXKkum… Please also consider this a call for agenda items. Best, Ozan Sahin Policy Development Support Senior Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

5 5

REMINDER: RSSAC Caucus Meeting | Sunday, 26 March 2023 | 07:00 - 08:00 UTC (16:00 - 17:00 JST)
by Ozan Sahin March 26, 2023

March 26, 2023

***REMINDER*** Remote participation link has been added. Note that you must have an account on the IETF Datatracker to access the session remotely; however, you do not need to be registered for the IETF 116 meeting to participate in the RSSAC Caucus meeting remotely. IETF Datatracker accounts can be created here: https://datatracker.ietf.org/accounts/create/ Topic: RSSAC Caucus Meeting Time: Mar 26, 2023 07:00 Universal Time UTC (16:00 JST – local time) Location: Room TBD | Pacifico North | Yokohama, Japan Agenda: https://docs.google.com/document/d/1X5za8TfDMQigjIvuv-PvCzFcZs6S3-LxLNXKkum… Remote Participation Link: https://meetecho.ietf.org/conference/?group=rssac Note that you must have an account on the IETF Datatracker to access the session remotely; however, you do not need to be registered for the IETF 116 meeting to participate in the RSSAC Caucus meeting remotely. IETF Datatracker accounts can be created here: https://datatracker.ietf.org/accounts/create/

3 3

Forever URLs
by Dessalegn Yehuala March 25, 2023

March 25, 2023

This might be of interest. https://rmf.vc/ForeverURLs

1 0

RFC7701bis and RSSAC001 update proposal: require NSID
by Wes Hardaker March 21, 2023

March 21, 2023

There was a discussion during the last call about whether or not RSOs should be required (via RFC7701bis at least) to support and transmit NSID. Currently all the existing RSOs do support NSID and return some value (see below). Since they all do, it seems like an easy jump to put the requirement into RFC7701bis. But there is also a question of what value should be reported; I'd think it should be a fairly simple statement that doesn't prescribe an explicit format, but rather should say something generic like "indicates a unique identifier for a given deployed instance". Thoughts? $ for i in a b c d e f g h i j k l m ; do echo -e -n "$i.root-servers.net:\t" ; dig @$i.root-servers.net . soa +nsid | grep -i nsid: | sed 's/.*//' ; done a.root-servers.net: ("a8.us-lax.root") b.root-servers.net: ("b4-lax") c.root-servers.net: ("lax1a.c.root-servers.org") d.root-servers.net: ("bbca1.droot.maxgigapop.net") e.root-servers.net: ("c01.LAX.eroot") f.root-servers.net: ("LAX.cf.f.root-servers.org") g.root-servers.net: ("sat3.groot") h.root-servers.net: ("001.nzy.h.root-servers.org") i.root-servers.net: ("s1.bnx") j.root-servers.net: ("a8.us-lax.root") k.root-servers.net: ("ns3.us-mia.k.ripe.net") l.root-servers.net: ("us-rtv-aa") m.root-servers.net: ("M-SJC-3") -- Wes Hardaker USC/ISI

7 21

RSSAC001v2 Work Party Teleconference #12 | Thursday, 6 April 2023 | 15:00-16:00 UTC
by ICANN Policy Calendar March 16, 2023

March 16, 2023

Ozan Sahin - ICANN Org is inviting you to a scheduled Zoom meeting. Topic: RSSAC001v2 Work Party Teleconference #12 Time: Apr 6, 2023 03:00 PM Universal Time UTC Statement of Work: https://www.icann.org/en/system/files/files/rssac-sow-rssac002v5-31jul22-en… Work party wiki space: https://community.icann.org/x/7oCLD Working document: https://docs.google.com/document/d/1fTRTplssJUayL6XD-qAmkGltXOxmeuPe/edit?u…<https://docs.google.com/document/d/1fTRTplssJUayL6XD-qAmkGltXOxmeuPe/edit?u…> Agenda: TBD Join Zoom Meeting https://icann.zoom.us/j/96793919322?pwd=QnEydEhJWFVtRStoT3J6TkFUQ25RUT09 Meeting ID: 967 9391 9322 Passcode: 9$kW?t=zEr One tap mobile +12532158782,,96793919322#,,,,*6952477511# US (Tacoma) +13017158592,,96793919322#,,,,*6952477511# US (Washington DC) Dial by your location +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 929 436 2866 US (New York) 877 853 5247 US Toll-free 888 788 0099 US Toll-free 833 548 0276 US Toll-free 833 548 0282 US Toll-free +61 8 6119 3900 Australia +61 8 7150 1149 Australia +61 2 8015 6011 Australia +61 3 7018 2005 Australia +61 7 3185 3730 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 3 4579 0545 Japan +81 363 628 317 Japan 00 663 381 4092 Japan Toll-free 0 800 100 5040 Japan Toll-free 0 120 829 768 Japan Toll-free 0 120 836 177 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 025 0113 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 0 201 604 329 Sweden Toll-free Meeting ID: 967 9391 9322 Passcode (for dial-ins only): 6952477511 Find your local number: https://icann.zoom.us/u/abwnfipa6c

1 0

RSSAC Caucus Meeting | Sunday, 26 March 2023 | 07:00 - 08:00 UTC (16:00 - 17:00 JST)
by Ozan Sahin March 13, 2023

March 13, 2023

Topic: RSSAC Caucus Meeting Time: Mar 26, 2023 07:00 Universal Time UTC (16:00 JST – local time) Location: Room TBD | Pacifico North | Yokohama, Japan Agenda: https://docs.google.com/document/d/1X5za8TfDMQigjIvuv-PvCzFcZs6S3-LxLNXKkum… Remote Participation Links: TBD - Remote participation information will be added.

1 0

RSSAC002v5: New title for section 3.1
by Andrew McConachie March 8, 2023

March 8, 2023

Dear RSSAC Caucus Members, I had an action item to propose a new title for §3.1 in RSSAC002v5. <https://docs.google.com/document/d/187k3b64DgkeCM6ib6ny6Ok7LzNxdT_v5X6FE0l0…> Once the new title is determined I will then affect the language throughout the section in accordance with its new title. First I thought about some terms for time durations in networking. time, latency, lag, delay ‘latency’ would seem the obvious choice, but my problem with ‘latency’ is that it often refers to a mean over many trips. When we talk about ‘high latency’ in networking we’re usually referring to many trips, or a state of the network, whereas here we’re talking about a single transfer of data. ‘latency’ like ‘delay’ and ‘lag’ are also negative. We can add qualifiers to both like ‘low-‘, but without that qualifier it has negative connotations. This leaves me with ’time’, because it does not evoke a mean or negativity. And then I considered the definitions of publish and serve from RSSAC026v2. <https://www.icann.org/en/system/files/files/rssac-026-lexicon-12mar20-en.pdf> The period we’re titling here is between publishing and serving root zone data. More specifically it is between receipt of a NOTIFY message from the Root Zone Maintainer until 95% of the RSI’s instances are serving the new data. All the other titles in §3 start with ‘The’, and §3.1 needs to blend in. 3.2 The volume of traffic 3.3 The query and response size distribution 3.4 The RCODE distribution 3.5 The number of sources seen So how about this: 3.1 The time elapsed between publishing and serving Thanks, Andrew

10 18