- rssac-caucus - lists.icann.org

RSSAC026v2 is now Stable
by Andrew McConachie March 3, 2020

March 3, 2020

Dear RSSAC Caucus Members, Thanks to everyone who participated in the discussion on RSSAC026v2. The attached version is now final and will be voted on by the RSSAC during their March 10th meeting. Thanks, Andrew

1 1

RSSAC002v4 is now Stable
by Andrew McConachie March 2, 2020

March 2, 2020

Dear RSSAC Caucus Members, Thanks to everyone who participated in the discussion on RSSAC002v4. The attached version is now final and will be voted on by the RSSAC during their March 10th meeting. Two proposals brought up on the list are being deferred until work begins on RSSAC002v5. -Addition of sampling percentages to unique-sources metric to show what percentage of instances are involved in traffic sampling See mail from John Heidemann on February 24 -Addition of comments to YAML data to aid interpretation of statistics See mail from Warren Kumari on February 25 Thanks, Andrew

1 0

48 HOUR REVIEW: RSSAC026v2
by Andrew McConachie Feb. 27, 2020

Feb. 27, 2020

Dear RSSAC Caucus Members, Thanks everyone who gave feedback during the review of RSSAC026v2. I made a couple of nits to the document. The one substantial change was to the definition of instance (anycast instance). The definition now reads: An instance, or an anycast instance,[0] is the portion of a root server operator's infrastructure that serves root data at one site (i.e., topological location on the Internet) using an IP address associated with a root server identifier. [0] See https://datatracker.ietf.org/doc/rfc4786/ You can review the whole document here: <https://docs.google.com/document/d/14Un1lCkek4aAyCi9a_oBcoRP02kJ72NtX1ic-LD…> The RSSAC would like vote on this document at its March 10th meeting, so the document must be stable by March 3rd. If you have any final comments please send them to the list before Monday March 2. Thanks, Andrew

3 3

48 HOUR LAST CALL : RSSAC002v4
by Andrew McConachie Feb. 25, 2020

Feb. 25, 2020

Dear RSSAC Caucus Members, Thanks everyone who submitted edits to RSSAC002v4. The review period ended on Feb 17th and I have incorporated all edits received. None of them were particularly major. Section 10.4 has been updated to list the major changes from v3 to v4. If no comments are received by Sunday February 23 this document will be forwarded to the RSSAC for voting. <https://docs.google.com/document/d/1na7VpPYfo4VEBfQMHwix6I2Puohvc1hvwRh0aW1…> Thanks, Andrew

7 19

In can you haven't heard
by Fred Baker Feb. 20, 2020

Feb. 20, 2020

Cancel your Cancun Plans... https://www.icann.org/news/announcement-2020-02-19-en

2 1

Re: [RSSAC Caucus] 48 HOUR LAST CALL: UPDATED RSSAC Advisory on Metrics for the DNS Root Servers and Root Server System
by Steve Sheng Feb. 20, 2020

Feb. 20, 2020

Dear RSSAC Caucus, Following the 48 hour last call, this document is now finalized. Thank you Geoff for your feedback. Your list of items is now added to a running document that tracks improvements / revision requests for this document. ICANN staff and also RSSAC026v2 WP Chair have also copy-edited the document to align the terms used in this document with RSSAC026v2. The final redline and clean version is attached. The document will now be sent to RSSAC for approval. Thank you all for your contribution to the review of this document. Best Steve On 2/12/20, 10:00 AM, "rssac-caucus on behalf of Steve Sheng" <rssac-caucus-bounces(a)icann.org on behalf of steve.sheng(a)icann.org> wrote: Dear RSSAC Caucus, Following Duane's last email, the review period for the updated document has concluded. As we have not received additional feedback to the document, the co-chairs of the WP would like to put this document to the 48 hour last call status. Please provide any last feedback you have by close of business everywhere Friday 14 February 2020. Please also note that RSSAC0026v2 (the terminology document) is also being updated concurrently. So prior to the publication, there will be a consistency check of terms used in the metric document against those defined in RSSAC026. Best Steve On 2/4/20, 2:14 AM, "rssac-caucus on behalf of Wessels, Duane via rssac-caucus" <rssac-caucus-bounces(a)icann.org on behalf of rssac-caucus(a)icann.org> wrote: Dear RSSAC Caucus, As you know, the RSS Metrics document was recently finalized within the Caucus and to be voted on by RSSAC this week. However, we, the work party leaders, are proposing two small additions to the document in order to resolve some recently discovered deficiencies in the correctness checking rules of section 5.3. The attached PDF file shows the proposed new text, on pages 18 and 19. While we are somewhat hesitant to make these additions after having gone through a last call phase, we feel that these are important enough to get right for the first version. Briefly, the two changes are: (1) to exclude ARPA/NS queries, and (2) to require at least one "glue" RR in a delegation response. To be clear, if (1) is not addressed at this time, all RSIs would, in all likelihood, fail the correctness thresholds as written through no fault of their own. Therefore, we are proposing to delay the RSSAC vote on this document by one month and to request the Caucus' approval to proceed with these additions. Russ and I kindly ask you to focus only the new additions. It is not our intention to open up the entire document for editing or other additions at this time. Please provide any comments regarding the additions here on the list by Monday, February 10th. Duane/Russ

1 0

Fwd: [ICANN Community Leaders] ICANN67 Update
by Fred Baker Feb. 20, 2020

Feb. 20, 2020

I just received this. FYI Sent from my iPad Begin forwarded message: > From: David Olive <david.olive(a)icann.org> > Date: February 19, 2020 at 4:20:05 PM PST > To: "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> > Subject: [ICANN Community Leaders] ICANN67 Update > > > Dear Community Leaders: > > Here is the ICANN announcement which will be posted shortly. > > More information later. > > Best regards. David > > > > > > Sent from my iPhone > > David A. Olive > Senior Vice President > Policy Development Support > Internet Corporation for Assigned Names and Numbers (ICANN) > > > _______________________________________________ > SO-AC-SG-CLeaders mailing list > SO-AC-SG-CLeaders(a)icann.org > https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders > > _______________________________________________ > By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Fwd: More assistance needed: Planning DNSSEC for Everybody: A Beginner's Guide in Cancun at ICANN67
by Fred Baker Feb. 19, 2020

Feb. 19, 2020

Passing along a request. At ICANN meetings, RSSAC and SSAC perform a little skit (in this case, during a session Sunday evening) to explain DNSSEC and underscore its importance. Kathy is looking for two additional volunteers. If you're available and interested, please contact her. > Begin forwarded message: > > From: Kathy Schnitt <kathy.schnitt(a)icann.org> > Subject: More assistance needed: Planning DNSSEC for Everybody: A Beginner's Guide in Montreal at ICANN66 > Date: February 19, 2020 at 11:19:09 AM PST > To: Danielle Rutherford <danielle.rutherford(a)icann.org>, Fred Baker <fred(a)isc.org>, Russ Mundy <mundy(a)tislabs.com>, Warren Kumari <warren(a)kumari.net>, Andrew McConachie <andrew.mcconachie(a)icann.org>, "Wes Hardaker" <hardaker(a)isi.edu>, Dan York <york(a)isoc.org> > > Hello everyone, > > *****We need some folks to fill in for the below roles, so if you have any suggestions please let us know. Wes will take over Dan’s role the fore we need someone for Joe User, and Russ will not be attending ICANN 67 so we need a filler for BigBank.***** > > It's time to plan for our session in Cancun at ICANN67. The Beginner’s Guide session is part of the outreach/newcomer activities that are scheduled for Sunday, 08 March 2020. > > Our Beginner’s Guide session is 1700 to 1830 local time on Sunday, 03 November 2019. It would be very helpful if you could confirm your availability for the session. (Room: Auditorio) > > Attached is the script Andrew has created for us. https://docs.google.com/document/d/1XM0kA4IA-qwd6Zmcdx8N51Ch2Yk686LGJBbOGNv… <https://docs.google.com/document/d/1XM0kA4IA-qwd6Zmcdx8N51Ch2Yk686LGJBbOGNv…> > > Here are the roles: > > Root Server — Fred Baker > .com TLD — Danielle Rutherford > BigBank — ??? > ISP — Warren Kumari > Dr. Evil — Andrew McConachie > Joe User – ??? > Narrator — Wes Hardaker > > Thanks for your help! > > Best regards, > Andrew and Kathy

1 0

48 HOUR LAST CALL: UPDATED RSSAC Advisory on Metrics for the DNS Root Servers and Root Server System
by Steve Sheng Feb. 18, 2020

Feb. 18, 2020

Dear RSSAC Caucus, Following Duane's last email, the review period for the updated document has concluded. As we have not received additional feedback to the document, the co-chairs of the WP would like to put this document to the 48 hour last call status. Please provide any last feedback you have by close of business everywhere Friday 14 February 2020. Please also note that RSSAC0026v2 (the terminology document) is also being updated concurrently. So prior to the publication, there will be a consistency check of terms used in the metric document against those defined in RSSAC026. Best Steve On 2/4/20, 2:14 AM, "rssac-caucus on behalf of Wessels, Duane via rssac-caucus" <rssac-caucus-bounces(a)icann.org on behalf of rssac-caucus(a)icann.org> wrote: Dear RSSAC Caucus, As you know, the RSS Metrics document was recently finalized within the Caucus and to be voted on by RSSAC this week. However, we, the work party leaders, are proposing two small additions to the document in order to resolve some recently discovered deficiencies in the correctness checking rules of section 5.3. The attached PDF file shows the proposed new text, on pages 18 and 19. While we are somewhat hesitant to make these additions after having gone through a last call phase, we feel that these are important enough to get right for the first version. Briefly, the two changes are: (1) to exclude ARPA/NS queries, and (2) to require at least one "glue" RR in a delegation response. To be clear, if (1) is not addressed at this time, all RSIs would, in all likelihood, fail the correctness thresholds as written through no fault of their own. Therefore, we are proposing to delay the RSSAC vote on this document by one month and to request the Caucus' approval to proceed with these additions. Russ and I kindly ask you to focus only the new additions. It is not our intention to open up the entire document for editing or other additions at this time. Please provide any comments regarding the additions here on the list by Monday, February 10th. Duane/Russ

6 7

Covid-19 at ICANN 67
by Fred Baker Feb. 18, 2020

Feb. 18, 2020

Passing along a discussion that happened this morning. The attachment contains a transcript of the shoot log, and a link to the recording. This morning (my time), ICANN held a meeting of the SO/AC chairs and other folks regarding the status of ICANN 67 with respect to the Corona Virus (Covid-19). In short: - ICANN is sufficiently worried to be thinking about this. - a board decision on whether the meeting will happen should happen Wednesday, and could be revisited as events unfold. - the current assumption is that the meeting will happen, but there will be defensive measures taken. : attendees will be temperature-checked entering the venue, and tested and quarantined if appropriate. : hand sanitizers will be available; masks (which seem to be ineffective) may or may not be. - right now, there are no known cases in Mexico (https://www.yourcentralvalley.com/news/top-stories/mexico-in-brief-11-suspe…) - the Mexican health authorities are involved and will be involved. - in any event, there will be the usual zoom access for remote attendees. If folks are cancelling plans, including because their companies are cancelling travel, I would appreciate being told, so that I can bubble the message up. I personally plan to attend unless the meeting is cancelled. With respect to ICANN 68 (Kuala Lumpur), that situation is right now stable, but in four months could easily evolve. "Stay tuned". https://www.straitstimes.com/asia/se-asia/two-new-coronavirus-cases-detecte…

1 0