Versions Compared

Old Version 1

changes.mady.by.user Charla K. Shambley

Saved on

compared with

New Version 2

changes.mady.by.user Charla K. Shambley

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Recommendation DescriptionCurrent Phase
Recommendation 1

RSSAC has heard from some members of the technical community that have expressed concern that an increase in traffic from misconfigured resolvers may occur after the October 11th, 2018 date in the rollover plan. RSSAC is not aware of any method able to estimate such a potential load increase. However, RSSAC believes that there is little risk of this occurring and that there will be no impact to the stability of the RSS even if such a load increase occursRecommendation 1: Root Server Operators should consider the advantages and disadvantages of harmonization of anonymization for DITL Data.

RSOs need to decide whether to pursue harmonization of anonymization data that comes from multiple operators, particularly the DITL data. That decision needs to include consideration of the advantages and disadvantages from the standpoint of the RSO, of the users of the RSS, and of researchers looking at the anonymized data.

Harmonization using mixing full addresses or bit-by-bit will help the research community correlate sources of DNS queries across datasets that are collected from different RSOs. However, full harmonization inherently relies on sharing a secret value that will invalidate the anonymization if it is later revealed.

Even if the RSOs decide not to harmonize with sharing of secret values, harmonizing the method used can help RSOs choose an anonymization strategy, and simplify understanding the properties of the data for those who use data from multiple RSOs.

Status
colourGreen
titleClosed

Recommendation 2

Recommendation 2: Each RSO should consider the anonymization procedures in this document individually.

Any of the proposals given in Section 4 of this document can be used as the anonymization specification for IP addresses, depending on the policy of the party doing the anonymizing.

Status
colourGreen
titleClosed

Recommendation 3Recommendation 3: Autonomous System (AS) numbers of original addresses should be made available with the anonymized data if the origin AS is sufficiently general that it does not unnecessarily expose data that should have been anonymized.

It should be possible for an operator to publish a machine-readable table that maps the anonymized addresses to the AS of the original data. Such a table should have a timestamp for when the mapping was made due to AS values changing over timeThe KSK rollover back out plan was written in July of 2016, updated in April of 2018, and may become a critical procedure that needs to be invoked immediately in case of KSK rollover failure. This document, its procedures and triggers should be reviewed by all parties in the rollover (RSOs, RZERC, and IANA) to ensure it remains adequate and implementable. RSSAC pledges that all of the RSOs will be prepared to participate in monitoring and measuring to ensure adequate data is available upon which a rollback decision can be made.

Status
colourGreen
titleClosed

...