Page History
Adding Zone Data Protections to the Root Zone (R4)
Date Issued | Document | Reference ID | Current Phase | |||||||
---|---|---|---|---|---|---|---|---|---|---|
| Adding Zone Data Protections to the Root Zone (R4) | RZERC003 | Phase 4 | Implement |
|
Description:
Public Technical Identifiers (PTI) and the RZM should jointly develop a plan for deploying ZONEMD in the root zone, and make this plan available for review by RZERC.
STATUS UPDATES
Date | Phase | Type | Status Updates |
---|---|---|---|
| Closed | Phase Change | Advice Item is now Closed |
| Phase 5 | Phase Update | This Advice is considered closed according to the letter sent by ICANN org dated 9 April 2024 to the RZERC. See: https://www.icann.org/en/system/files/correspondence/davies-to-rzerc-09apr24-en.pdf. |
| Phase 5 | Phase Update | ICANN sent a letter (https://www.icann.org/en/system/files/correspondence/olive-to-april-13oct23-en.pdf) to the RZERC regarding this Advice item. |
| Phase 5 | Phase Change | Now in Phase 5 |
| Phase 4 | Phase Update | ICANN org considers implementation of this Advice complete and will prepare an Advice Complete Status Report for the ICANN Board and Advisory Committee's information. |
| Phase 4 | Phase Update | Planning efforts are complete. ICANN org will continue to work with Verisign with announcements around the implementation date. ICANN org will begin efforts to close this advice. |
| Phase 4 | Phase Update |
|
| Phase 4 | Phase Update | The advice has been in the implementation phase as of the 24 February 2022 Board meeting. ICANN org is scheduled to provide an update to the Board Technical Committee on 23 November 2022. The anticipated action item will be to ask ICANN org to draft a Board paper, to accept the implementation of the advice as completed. |
| Phase 4 | Phase Change | Now in Phase 4 |
| Phase 3 | Board Update | The Board approved RZERC003 recommendations 1,2 and 4 on 24 February 2022: https://www.icann.org/resources/board-material/resolutions-2022-02-24-en#1.a . As such these recommendations should be moved to implementation phase. |
| Phase 3 | Phase Change | Now in Phase 3 |
| Phase 2 | AP Feedback | ICANN received confirmation of understanding from the RZERC. |
| Phase 2 | AP Feedback | The RZERC understands “with its contractors” to mean that ICANN org intends to develop a plan jointly together with PTI and RZM. Following the actions mentioned in Recommendation 4, the RZERC would appreciate the opportunity to review the plan developed by ICANN org and any feedback received and provide comments. |
| Phase 2 | Board Understanding | ICANN org understands this recommendation to have ICANN org to develop a plan with its contractors and make the plan available to RZERC for review. ICANN org further understands input from RZERC should be incorporated into the final plan as appropriate. |
| Phase 2 | Phase Update | ICANN sent understanding to the RZERC for review. |
| Phase 2 | Phase Change | Now in Phase 2 |
| Phase 1 | Phase Update | Acknowledgement sent to RZERC. |
| Phase 1 | Phase Update | RZERC published RZERC003: Adding Zone Data Protections to the Root Zone: https://www.icann.org/uploads/ckeditor/rzerc-003-en.pdf. |