[RSSAC Caucus] Rogue Operator Work Party: Source of zone data

Renard, Kenneth D CTR USARMY CCDC C5ISR (USA) kenneth.d.renard.ctr at mail.mil
Tue Oct 6 17:19:00 UTC 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 at mail.mil

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rssac-caucus/attachments/20201006/a29d6c76/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5162 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/rssac-caucus/attachments/20201006/a29d6c76/smime.p7s>


More information about the rssac-caucus mailing list