Recommendations on Anonymization Processes for Source IP Addresses Submitted for Future Analysis
RSSAC Advisory on Organizational Reviews (R1)
| Date Issued | Document | Reference ID | Current Phase | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Recommendations on Anonymization Processes for Source IP Addresses Submitted for Future Analysis RSSAC Advisory on Organizational Reviews (R1) | RSSAC040RSSAC041 |
| Closed
|
Description:
Recommendation 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 UPDATES
The ICANN organization should, with sufficient detail, define an ICANN organizational review. This definition should be documented and available to the community. Details should be crisp and tight in order to ensure complete clarity of scope.
STATUS UPDATES
| Date | Phase | Type | Status Updates |
|---|---|---|---|
| Closed | Phase Change | This Advice Item will now be Closed |
| Phase 5 | AP Feedback | ICANN received confirmation from the RSSAC that the items included in the letter (https://www.icann.org/en/system/files/correspondence/olive-to-osborn-22jun23-en.pdf) from David Olive can be formally closed. |
| Phase 5 | Phase Update | A letter (https://www.icann.org/en/system/files/correspondence/olive-to-osborn-22jun23-en.pdf) was sent from David Olive to Jeff Osborn regarding the status of the Advice Item. |
| Phase 5 | Phase Update | This advice has been taken over by subsequent events and is no longer relevant. Specifically, the Third Accountability and Transparency Review (ATRT3) has issued recommendations that have direct impact on Organizational Reviews (see Recommendation 3.6 which calls for Organizational Reviews to evolve into a Continuous Improvement Program). The Board approved these recommendations subject to prioritization. Community prioritization placed recommendation 3.6 into P2 category and implementation design is currently underway. The Board deferred all upcoming Organizational Reviews to allow for the implementation of ATRT3 recommendations. As a result, consideration of this Advice is considered complete. |
| Phase 5 | Phase Change | Now in Phase 5: Close |
| Phase 3 | Phase Update | This advice has been taken over by subsequent events and is no longer relevant. Specifically, the Third Accountability and Transparency Review (ATRT3) has issued recommendations that have direct impact on Organizational Reviews (see Recommendation 3.6 which calls for Organizational Reviews to evolve into a Continuous Improvement Program). The Board approved these recommendations subject to prioritization. Community prioritization placed recommendation 3.6 into P2 category and implementation design is currently underway. The Board deferred all upcoming Organizational Reviews to allow for the implementation of ATRT3 recommendations. This Advice will be moved to Phase 5 | Close. |
| Phase 3 | Phase Change | Now in Phase 3: Evaluate & Consider |
| Phase 2 | AP Feedback | ICANN received confirmation of understanding from the RSSAC. |
| Phase 2 | Board Understanding | The ICANN org understands RSSAC041 Recommendation 1 to mean that the ICANN org should define the ICANN organizational review. The definition should be documented and available to the community. Details should be straightforward and unambiguous in order to ensure complete clarity of scope. This updated understandings was sent to RSSAC for review. |
| Phase 2 | Phase Update | Updated Understanding sent to RSSAC for review. |
| Phase 2 | AP Feedback | ICANN received confirmation of Understanding from the RSSAC. |
| Phase 2 | Board Understanding | The ICANN org understands RSSAC041 Recommendation 1 to mean that the ICANN org should define the ICANN organizational review. The definition should be documented and available to the community. Details should be straightforward and unambiguous in order to ensure complete clarity of scope. This recommendation will be considered as part of a broader audit of streamlining organizational reviews with oversight by the Organizational Effectiveness Committee (OEC) of the Board. Because this recommendation will be addressed via a separate process, there is no further action for the ICANN Board in the context of the Board Advice process, and this item will be closed. |
| Phase 2 | Phase Update | Understanding sent to RSSAC for review. |
| Phase 2 | Phase Change | Now in Phase 2: Understand |
| Phase 1 | Phase Update | ICANN acknowledged receipt of Advice. |
| Phase 1 | Phase Update | RSSAC published RSSAC041: RSSAC Advisory on Organizational Reviews Link: https://www.icann.org/en/system/files/files/rssac-041-05oct18-en.pdf. |