January 2020 - rssac-caucus

REMINDER: RSSAC023v2: History of the Root Server System Update | 6 January 2020 | 16:00 UTC
by Ozan Sahin Jan. 6, 2020

Jan. 6, 2020

***REMINDER*** Ozan Sahin is inviting you to a scheduled Zoom meeting. Topic: RSSAC023v2: History of the Root Server System Update Time: Jan 6, 2020 04:00 PM Universal Time UTC Link to RSSAC023v2: https://docs.google.com/document/d/16FaQzGJnqBsy5zk4xmLPU2v7FUqLQT8readmSYI… Join Zoom Meeting https://icann.zoom.us/j/352004892?pwd=MHFVTngwM0pDU0N0cVJ1Ky9VdElCdz09 Meeting ID: 352 004 892 Password: 997060 **Please note this added security/privacy feature. Participants will only be required to enter the password if they are joining via the application and typing in the meeting ID manually. Anyone who joins a meeting via a link in a calendar or e-mail invitation will not be required to enter the password upon joining** One tap mobile +16699006833,,352004892# US (San Jose) +19294362866,,352004892# US (New York) Dial by your location +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 Meeting ID: 352 004 892 Password: 997060 Find your local number: https://icann.zoom.us/u/aTk0DNsyG

2 1

Fwd: Proposed final report for the Resolvers Work Party
by Fred Baker Jan. 6, 2020

Jan. 6, 2020

Paul sent me the following. > Begin forwarded message: > > From: Paul Hoffman <paul.hoffman(a)icann.org> > Subject: Proposed final report for the Resolvers Work Party > Date: January 3, 2020 at 10:36:43 AM PST > To: Fred Baker <fred(a)isc.org> > Cc: Andrew McConachie <andrew.mcconachie(a)icann.org>, Danielle Rutherford <danielle.rutherford(a)icann.org>, Ozan Sahin <ozan.sahin(a)icann.org> > > Greetings in the new year. As we discussed last year, the Resolvers Work Party needs at least a short report before we close completely. My proposal for the report is at: > https://docs.google.com/document/d/1b_FZwMRnNQRKzy5O8FX0P5yj8NRD8j_EDbgrMX3… > If that meets your expectations, great; if not, feel free to add suggestions or comments and I can include them. Let me know what else you think should be done before we declare victory here. > > --Paul I would suggest that folks take a look, and if they have proposed changes or other comments, add them. Make sure you are *suggesting* as opposed to *editing*, please. That way, folks will be able to see the proposed change, and Paul can accept it or not. If RSSAC were to try to accept it by a vote Tuesday, I don't think there is adequate time to review it. Hence, I suggest we put it on the agenda for the February RSSAC call - that assuming that it stabilizes a week in advance. But I would encourage people to go read it and comment.

1 0

Metrics vantage point connectivity
by Paul Hoffman Jan. 3, 2020

Jan. 3, 2020

Greetings again. The current text on vantage point connectivity says: > 3.3 Connectivity and Other Requirements > > Vantage points shall be hosted inside data centers with reliable power and diverse connectivity providers. > > Vantage points within the same geographic region should use different connectivity providers if at all possible. E.g., VP#1 uses ISP#1, VP#2 uses ISP#2, etc. Diversity of connectivity providers helps to increase RSS coverage and avoid situations where multiple vantage points all reach the same root server instance. > > Vantage points may be deployed on “bare metal” or virtual machines (VMs). When VMs are utilized, they should provide dedicated IP addresses and a dedicated operating system environment. In essence, the text in the second paragraph requires that every vantage point allow provisioning of the connectivity provider. It basically restricts the kind of VMs that could be used, since none of the widely-used VM providers I have found allow for such provisioning. In fact, it kinda pushes the vantage points to be on bare metal, since those rentals are more likely to allow such provisioning. Given that the regions are quite large and so the cities could be quite far from each other, it is not clear how much advantage (if any) this restriction would have. It is also not clear why the diversity is given just for within a region. Separately, the text "E.g., VP#1 uses ISP#1, VP#2 uses ISP#2, etc." is not terribly grammatical. It also uses "ISP" instead of "connectivity provider". It doesn't add anything to the paragraph, and can safely be removed. If this is really what RSSAC wants, that's fine, but it will place limits on which cities can have vantage points because not all cities have data centers that allow this kind of provisioning. If RSSAC instead wants to give itself more freedom for vantage point placement, maybe just change the second paragraph to: Having diverse connectivity providers for the vantage points helps to increase RSS coverage and avoid situations where multiple vantage points all reach the same root server instance. The network routing used by vantage points is detectable using the measurements described in Section 4.8. If configuring particular vantage points allows selecting a connectivity provider, this can be used to increase the diversity of the measurement system. --Paul Hoffman

4 9

FOR REVIEW: RSSAC Advisory on Metrics for the DNS Root Servers and Root Server System
by Steve Sheng Jan. 3, 2020

Jan. 3, 2020

Dear RSSAC Caucus, On behalf of the RSSAC Caucus Metrics work party, please find the draft RSSAC Advisory on Metrics for the DNS Root Servers and Root Server System. The work party was formed in January 2019. It is led by Duane Wessels and Russ Mundy. After 12 months of deliberations through teleconferences, workshops, face to face meetings at ICANN and IETF, the draft final advisory is ready. Kindly review the document by 10 January 2020: * for any proposed changes, please send to the caucus list identifying the page number, the original paragraph or sentence, and your proposed edit. * We are also copy-editing the document. For any copy-edit changes, please email it to steve.sheng(a)icann.org<mailto:steve.sheng@icann.org>. WP members, please pay attention to the first bullet in the introduction, as it has been revised today as a result of the teleconference. Best Steve

4 5