FW: [Ccnsosecretariat] RZERC report for the ccNSO Council
Dear all, Please find included an update from Peter Koch on latest RZERC On 24/05/18 00:31, "Ccnsosecretariat on behalf of Peter Koch" Dear ccNSO Council, please find attached my most recent report on RZERC and an addendum. Best regards, Peter ----------------------------------------------------------------------------- 2018-05-23, Peter Koch, DENIC (DE) ccNSO appointee to the Root Zone Evolution Review Committee (RZERC) <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_rzerc&d=D...> ----------------------------------------------------------------------------- The work of RZERC is made transparent by means of the website above and the publicly accessible mailing list archive at <http://mm.icann.org/pipermail/rzerc/>. ----------------------------------------------------------------------------- This is the first written report regarding RZERC in 2018. The committee had ended its initialization phase on 11 December 2017 and went dormant afterwards. On 22 May 2018, the committee held a teleconference with two main action items: o Discussion and comments of the Root Zone Management Evolution Study Following a recommendation in the ICG IANA Stewardship Proposal the ICANN OCTO (Office of the CTO) team has drafted a study (Details to be found in the PDF attached to <https://mm.icann.org/pipermail/rzerc/2018-April/000290.html>) "Root Zone Management Evolution Study" that is believed to be conducted by an outside contractor. RZERC was asked for comments, most likely because part of the genesis of RZERC's was the discontinuation of NTIA oversight. RZERC members preliminary assessed the request as informal, given that the current draft envisions any study results to be addressed by RZERC. RZERC will seek clarification with OCTO. Relevance for the ccNSO/ccTLDs: Given that the study is an open issue from the IANA Stewardship Transition, policy level attention is advised. The current scope of the study as well as requirements for recommendations need to be evaluated against both the letter and the spirit of the recommendation made by the ICG. A risk analysis and the prevention of unintended and/or unauthorized changes to content of the root zone and/or the root zone database are vital issues for all TLDs. o Board Resolution on KSK Rollover After the postponed initial rollover of the DNSSEC root zone key signing key (KSK), the current schedule aims at 11 October 2018 for the KSK roll. (Details at <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources...>) The revised schedule has been subject to outreach events and a public comment perios, a summary of the latter to be found at <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system...>. The ICANN Board noted that neither RSSAC, nor SSAC, nor RZERC had submitted contributions during the comment period and so, per Board Resolution on 13 May 2018 <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources...> asked all three committees to provide advices (mind the plural) per 10 August 2018. RZERC will deliberate on a response. Relevance for the ccNSO/ccTLDs: Any DNSSEC enabled DNS resolver failing to accept the new root KSK by the rollover date would cease to properly resolve any domain underneath the root, signed or unsigned. While this would be local to the user population behind those resolvers, TLD managers and anybody else running DNS services might be affected by confusion on the side of end users or other customers. Detailed discussion has been part of the planning process. It should be noted that most of the limited number of comments received during the public consultation were submitted by well known individuals from the tech/ops community. This gives no clear signal regarding the effectiveness of the outreach efforts. ----------------------------------------------------------------------------- Addendum outside the report: The RZM study might need a bit more attention by teh ccTLD community, so if the schedule allows for an RZERC report, I'd elaborate a bit on this, or maybe even consult with the community via email beforehand. For the KSK roll, it appears the Board is seeking utmost coverage of any potential impact, but it is not yet clear (at least to me) what exactly is asked of RZERC in addition to SSAC and RSSAC. There are some meta issues around the decision making and the more genaral question of change and innovation within the Internet's technical infrastructure and whether 'failure thresholds' are an appropriate instrument for decision making, both technically and policy wise. -- Peter Koch DENIC eG |
participants (1)
-
Bart Boswinkel