- rssac-caucus - lists.icann.org

RSSAC Caucus Meeting | Tuesday, 13 October 2020 | 12:00-13:30 UTC
by Ozan Sahin Oct. 12, 2020

Oct. 12, 2020

ICANN69 Schedule page: https://69.schedule.icann.org/meetings/rY2CbwMRhxjJ2mSND#/?limit=10&sortByF… Agenda: https://docs.google.com/document/d/11kUzC_4Mr5XeenQ4Y5iYBGsUB14gjtkku_1S5Tp… Participation Information: ICANN69 Page: https://69.schedule.icann.org/meetings/rY2CbwMRhxjJ2mSND Zoom Link: https://icann.zoom.us/j/97995418862?pwd=Y0ZWSVpyNk1iM0xEQUpEUDNvQ1Vsdz09 Zoom Session ID: 979 9541 8862 Zoom Session Passcode: xT+K5dcqn^ Zoom International Dial-In Numbers: https://icann.zoom.us/u/abpFVtYJAa Zoom Phone Passcode: 476 492 5880

1 0

Re: [RSSAC Caucus] Rogue Operator Work Party: Source of zone data
by Fred Baker Oct. 12, 2020

Oct. 12, 2020

Sending again, this time with the right “from” address... Speaking strictly for myself, I would argue, as you did in your email, that getting the root zone from another party has a safety issue in it - how do we know it has the right data? I could imagine an RSO downloading the relevant files to somewhere in its own cloud, and then distributing from there to its constellation. Doing so would offload the RZM source. But I would consider getting the first copy from anywhere else as unsafe. > On Oct 6, 2020, at 10:19 AM, Renard, Kenneth D CTR USARMY CCDC C5ISR (USA) via rssac-caucus <rssac-caucus(a)icann.org> wrote: > > A discussion topic brought up at the last Rogue Operator Work Party call was on where [technically] an RSO fetches their root zone information from. Typically, an RSO will fetch zone data directly from the RZM’s servers [distribution of the zone files among the RSO’s instances is not considered here, just the initial fetch(es) from a source]. What if an RSO obtained their copy of the zone data from an intermediate source? #RootZone > > The RSO is responsible for publishing the correct IANA zone, as made available by the RZM. Whether they get it directly from the RZM or via some other party should(?) be irrelevant. An intermediate source certainly does introduce additional risk that the zone could have been modified, but it is still the responsibility of the RSO to publish true IANA data. I would not consider it _wise_ to obtain the zone from an intermediate source, but would we go so far as to say that this is a _rogue_ operation? Historically (1998?), fetching from an intermediate was seen as a pre-cursor to rogue operations, where new source may have had intentions of changing the zone, but there seem to be different interpretations of those events. > > The question to the group is: “Would using an intermediate source of root zone data, by itself, be considered a ROGUE operation?” Regardless of who the intermediate is…, regardless of the authenticity of the zone data… > > Thoughts? > > > Ken Renard > S&TCD Contractor – ICF > Sustaining Base Network Assurance Branch > C5ISR Center, Space and Terrestrial Communications Directorate > Office: 443-395-7809 > kenneth.d.renard.ctr(a)mail.mil > > _______________________________________________ > rssac-caucus mailing list > rssac-caucus(a)icann.org > https://mm.icann.org/mailman/listinfo/rssac-caucus > > _______________________________________________ > 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.

2 1

Rogue Operator Work Party: Source of zone data
by Renard, Kenneth D CTR USARMY CCDC C5ISR (USA) Oct. 11, 2020

Oct. 11, 2020

A discussion topic brought up at the last Rogue Operator Work Party call was on where [technically] an RSO fetches their root zone information from. Typically, an RSO will fetch zone data directly from the RZM’s servers [distribution of the zone files among the RSO’s instances is not considered here, just the initial fetch(es) from a source]. What if an RSO obtained their copy of the zone data from an intermediate source? #RootZone The RSO is responsible for publishing the correct IANA zone, as made available by the RZM. Whether they get it directly from the RZM or via some other party should(?) be irrelevant. An intermediate source certainly does introduce additional risk that the zone could have been modified, but it is still the responsibility of the RSO to publish true IANA data. I would not consider it _wise_ to obtain the zone from an intermediate source, but would we go so far as to say that this is a _rogue_ operation? Historically (1998?), fetching from an intermediate was seen as a pre-cursor to rogue operations, where new source may have had intentions of changing the zone, but there seem to be different interpretations of those events. The question to the group is: “Would using an intermediate source of root zone data, by itself, be considered a ROGUE operation?” Regardless of who the intermediate is…, regardless of the authenticity of the zone data… Thoughts? Ken Renard S&TCD Contractor – ICF Sustaining Base Network Assurance Branch C5ISR Center, Space and Terrestrial Communications Directorate Office: 443-395-7809 kenneth.d.renard.ctr(a)mail.mil

9 14

Re: [RSSAC Caucus] [Non-DoD Source] Re: [Ext] Re: Rogue Operator Work Party: Source of zone data
by Renard, Kenneth D CTR USARMY CCDC C5ISR (USA) Oct. 11, 2020

Oct. 11, 2020

> So may be it’s worth for the Caucus draft to also consider those scenarios even if we do not like them. The work party is addressing "unofficial" responses, which could be anything from route hijacks to hyperlocal/8806. The relevance is that indicators of a rogue RSO, such as incorrect responses, could come from unofficial responders just as well as from an RSO. -Ken

2 1

Two Updates
by Ozan Sahin Oct. 8, 2020

Oct. 8, 2020

Dear RSSAC Caucus Members, I have two updates to share: 1. The meeting minutes from 1 September 2020 RSSAC Meeting have been approved during the last RSSAC Teleconference on Tuesday, 6 October 2020. 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. 1. ICANN org. Policy Development Support team published the ICANN69 Policy Outlook Report to provide an overview of the planned work and activities of the Supporting Organizations and Advisory Committees at ICANN69. The report is available here: http://go.icann.org/outlook69 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

Call for Volunteers | NextGen@ICANN Selection Committee Members and NextGen@ICANN Mentors
by Ozan Sahin Oct. 8, 2020

Oct. 8, 2020

Dear RSSAC Caucus Members, ICANN’s Supporting Organizations, Advisory Committees, Stakeholder Groups, Constituencies, and Regional At-Large Organizations are invited to nominate one individual each to serve on the NextGen@ICANN Selection Committee and one individual to serve as NextGen@ICANN mentor. Learn more here: https://www.icann.org/news/announcement-2020-09-28-en NextGen@ICANN Selection Committee members will typically serve for two years, or six application rounds, whereas NextGen@ICANN mentors will typically serve for one year. Mentors cannot serve on the Selection Committee at the same time they are serving as mentors. For more information on the guidelines and expectations, please visit this page<https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-14…> for more information about Mentors and this page<https://www.icann.org/resources/pages/nextgen-selection-committee-2020-09-2…> for the Selection Committee. By 23:59 UTC on Friday, 9 October please e-mail ozan.sahin(a)icann.org<mailto:ozan.sahin@icann.org> if you would like to be considered for any of the two roles indicating which role you are interested in. 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 1

Fwd: Proposed MOU or LOI between an RSO and the contracting company
by Fred Baker Oct. 7, 2020

Oct. 7, 2020

We agreed on the MOU/LOI proposal yesterday, and are discussing it with the GWG tomorrow afternoon. Paul asked us to send It to the Caucus as well, so with this email I'm doing so. > From: Fred Baker <fred(a)isc.org> > Subject: Proposed MOU or LOI between an RSO and the contracting company > Date: October 6, 2020 at 6:21:21 PM PDT > To: Ted Hardie <hardie(a)qualcomm.com> > Cc: ICANN RSSAC <rssac(a)icann.org> > > As we have discussed in the past, the RSSAC has asked itself what a contract between an RSO and a contracting organization might look like. There are a number of issues, as you can imagine and we have discussed. The paper we came up with is attached. > > This morning, PDT, the RSSAC agreed that we are done with it and are happy to send it to you. Note that we neither expect nor intend that the GWG issue exactly what we have produced, but we hope it might help the GWG with its deliberations. > > Thursday, there will be a call between the RSSAC and the GWG, in which we hope to discuss this paper. When we talk with the ICANN BTC, we similarly expect to bring this up as one of the things the RSSAC has been thinking about. >

1 0

RSSAC Caucus Local Perspective Tool WP Teleconference #7 | Thursday, 15 October | 14:00-15:00 UTC
by Ozan Sahin Sept. 30, 2020

Sept. 30, 2020

ICANN69 Schedule page: https://69.schedule.icann.org/meetings/W5mobZvsR595JurZy#/?limit=10&sortByF… Agenda: TBD Participation Information: TBD Work party wiki space: https://community.icann.org/x/gInsBw

1 0

RSSAC Caucus Rogue RSO WP Teleconference #7 | Tuesday, 13 October | 14:00-15:00 UTC
by Ozan Sahin Sept. 30, 2020

Sept. 30, 2020

ICANN69 Schedule page: https://69.schedule.icann.org/meetings/jYsMTZngAhRthts5h#/?limit=10&sortByF… Agenda: TBD Participation Information: TBD Work party wiki space: https://community.icann.org/x/IonsBw

1 0

RSSAC Caucus Meeting | Tuesday, 13 October 2020 | 12:00-13:30 UTC
by Ozan Sahin Sept. 30, 2020

Sept. 30, 2020

ICANN69 Schedule page: https://69.schedule.icann.org/meetings/rY2CbwMRhxjJ2mSND#/?limit=10&sortByF… Agenda: TBD Participation Information: TBD

1 0