Security and Stability Advisory Committee (SSAC) Advice Status
Board Advice Home | ALAC Advice Status | RSSAC Advice Status | GAC Advice Status
Latest Advice to the ICANN Board
As of 31 December 2022
| Date | Advice Document |
|---|---|
9 June 2022 |
Action Request Register Phases and Descriptions
Advice Items by Phase
| Phase | SSAC |
| Phase 1 | Receive & Acknowledge | - |
| Phase 2 | Understand | 7 |
| Phase 3 | Evaluate & Consider | 4 |
| Phase 3 | Deferred | 2 |
| Phase 4 | Implement | 13 |
| Phase 4 | Deferred | 7 |
| Phase 5 | Close | 16 |
| Total Open Items | 49 |
| Total Items Closed in Past 12 Months | 3 |
Open Advice Items
See also "Advice Status Reports" on Board Advice Home for PDF/Excel versions of the information below.
| Advice Item | Phase | Action(s) Taken | Dependencies |
|---|---|---|---|
Phase 2 | Understand Request |
ICANN received SAC114 on 17 February 2021 and is currently reviewing. The SSAC provided an addendum to SAC114 (https://www.icann.org/en/system/files/files/sac-114-addendum-en.pdf). ICANN is currently reviewing SAC114 and the addendum. |
||
Phase 2 | Understand Request |
ICANN received SAC114 on 17 February 2021 and is currently reviewing. The SSAC provided an addendum to SAC114 (https://www.icann.org/en/system/files/files/sac-114-addendum-en.pdf). ICANN is currently reviewing SAC114 and the addendum. |
||
Phase 2 | Understand Request |
ICANN received SAC114 on 17 February 2021 and is currently reviewing. The SSAC provided an addendum to SAC114 (https://www.icann.org/en/system/files/files/sac-114-addendum-en.pdf). ICANN is currently reviewing SAC114 and the addendum. |
||
Phase 2 | Understand Request |
ICANN received SAC114 on 17 February 2021 and is currently reviewing. The SSAC provided an addendum to SAC114 (https://www.icann.org/en/system/files/files/sac-114-addendum-en.pdf). ICANN is currently reviewing SAC114 and the addendum. |
||
Phase 2 | Understand Request |
ICANN received SAC114 on 17 February 2021 and is currently reviewing. The SSAC provided an addendum to SAC114 (https://www.icann.org/en/system/files/files/sac-114-addendum-en.pdf). ICANN is currently reviewing SAC114 and the addendum. |
||
Phase 2 | Understand Request |
ICANN received SAC114 on 17 February 2021 and is currently reviewing. The SSAC provided an addendum to SAC114 (https://www.icann.org/en/system/files/files/sac-114-addendum-en.pdf). ICANN is currently reviewing SAC114 and the addendum. |
||
Phase 2 | Understand Request |
ICANN received SAC114 on 17 February 2021 and is currently reviewing. The SSAC provided an addendum to SAC114 (https://www.icann.org/en/system/files/files/sac-114-addendum-en.pdf). ICANN is currently reviewing SAC114 and the addendum. |
||
Phase 3 | Deferred |
The org (OCTO) understands SSAC to be requesting that the study described in SAC059 related to the expansion of the root zone be performed. More specifically, the study should focus on areas that have not already been explored in other studies related to scaling the root or on areas within completed studies that the community felt were inadequately addressed, as evidenced by responses provided during those studies' public comment period. The study should also explore potential interactions among the areas of inquiry suggested in SAC059. The study should be undertaken by representatives from communities that may not have been fully consulted or engaged during previous investigations into the impacts of the new gTLD program. These communities are listed in SAC059. ICANN sent this understanding to the SSAC for review on 04 June 2020. ICANN received confirmation of understanding on 13 July 2020. Issues related to the expansion of the root zone have been/are being considered through other means, including Name Collision and DNSSEC roll over. Other reports on the expansion of the root zone include: - Scaling the Root Report on the Impact on the DNS Root System of Increasing the Size and Volatility of the Root Zone: https://www.icann.org/en/system/files/files/root-scaling-study-report-31aug09-en.pdf - Summary of the Impact of Root Zone Scaling: https://archive.icann.org/en/topics/new-gtlds/summary-of-impact-root-zone-scaling-06oct10-en.pdf - Impact on Root Server Operations and Provisioning Due to New gTLDs: http://newgtlds.icann.org/en/about/historical-documentation/root-scaling-27jun12-en.pdf - Continuous Data Driven Analysis of Root Server System Stability Study Plan (Public Comment): https://www.icann.org/public-comments/cdar-study-plan-2015-12-02-en ICANN continues to work to address the issues identified in SAC059. |
SSAC is putting SAC059 on hold until they've had time to do more work and determine if SAC059 still stands as is, or the recommendations' requests needs revision. |
|
Phase 3 | Deferred |
The Org (OCTO) understands SSAC to be requesting that the study described in SAC059 related to the expansion of the root zone be performed. More specifically, the study should focus on areas that have not already been explored in other studies related to scaling the root or on areas within completed studies that the community felt were inadequately addressed, as evidenced by responses provided during those studies' public comment period. The study should also explore potential interactions among the areas of inquiry suggested in SAC059. The study should be undertaken by representatives from communities that may not have been fully consulted or engaged during previous investigations into the impacts of the new gTLD program. These communities are listed in SAC059ICANN sent this understanding to the SSAC for review on 04 June 2020. ICANN received confirmation of understanding on 13 July 2020. Issues related to the expansion of the root zone have been/are being considered through other means, including Name Collision and DNSSEC roll over. Other reports on the expansion of the root zone include: - Scaling the Root Report on the Impact on the DNS Root System of Increasing the Size and Volatility of the Root Zone: https://www.icann.org/en/system/files/files/root-scaling-study-report-31aug09-en.pdf - Summary of the Impact of Root Zone Scaling: https://archive.icann.org/en/topics/new-gtlds/summary-of-impact-root-zone-scaling-06oct10-en.pdf - Impact on Root Server Operations and Provisioning Due to New gTLDs: http://newgtlds.icann.org/en/about/historical-documentation/root-scaling-27jun12-en.pdf - Continuous Data Driven Analysis of Root Server System Stability Study Plan (Public Comment): https://www.icann.org/public-comments/cdar-study-plan-2015-12-02-en ICANN continues to work to address the issues identified in SAC059. |
SSAC is putting SAC059 on hold until they've had time to do more work and determine if SAC059 still stands as is, or the recommendations' requests needs revision. |
|
Phase 3 | Evaluate & Consider |
ICANN org understands SAC113 to mean SSAC is requesting the Board to choose a TLD as described in Section 4.1 of the document, and to reserve that TLD in the DNS root for private use, and to be sure that that TLD is never delegated in the DNS root. ICANN sent this understanding to the SSAC for review on 01 October 2020. ICANN Received confirmation of understanding on 22 April 2021. |
||
Phase 3 | Evaluate & Consider |
With respect to the SSAD recommendations, the Board understands that the SSAC is recommending that the ICANN Board, Generic Name Supporting Organization (GNSO) and ICANN org should take into account the SSAC's previous advice and minority opinion on the SSAD recommendations and collectively rethink and refocus their attention on how to achieve a complete system that is usable, effective, reliable, accessible, and timely. As SSAC is aware, the Board has received additional information from ICANN org's recently completed ODP assessment of the recommendations. We are also looking forward to hearing from the GNSO Small Team (that SSAC is participating in) that has been recently formed to look at the ODP work. We welcome continued dialogue with the SSAC and the entire ICANN community with regards to the next steps as the Board considers the SSAD recommendations. ICANN sent the above Understanding to the SSAC on 08 April 2022. |
||
SSAC Advisory on DNS "Search List" Processing (R-3A) |
Phase 3 | Evaluate & Consider |
The ICANN organization understands that SAC064 R-3 means that the SSAC recommends that in the context of mitigating name collisions, ICANN should consider the following steps to address search list processing behavior: a. ICANN should consider whether to commission additional studies to further understand the cause of invalid queries to the root zone and the significance of search list processing as a contributor to those queries. On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b). ICANN org will draft a preliminary evaluation in which a feasibility assessment is conducted and the item is brought before the Board for implementation consideration. The preliminary evaluation for the advice item will be completed by 8 December 2022. |
Further implementation of this item is deferred as of 23 September 2019 pending external activity. ICANN org will take up further action once the NCAP's work on analyzing the causes of queries for non-existent TLDs to the root is complete. |
SSAC Advisory on DNS "Search List" Processing (R-3B) |
Phase 3 | Evaluate & Consider |
The ICANN organization understands that SAC064 R-3 means that the SSAC recommends that in the context of mitigating name collisions, ICANN should consider the following steps to address search list processing behavior: b. ICANN should communicate to system administrators that search list behaviors currently implemented in some operating systems will cause collision with names delegated as new gTLDs from the 2012 application round for the New gTLD Program. On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b). ICANN org will draft a preliminary evaluation in which a feasibility assessment is conducted and the item is brought before the Board for implementation consideration. The preliminary evaluation for the advice item will be completed by 8 December 2022. |
|
Phase 4 | Deferred |
RZ-LGR-3 integrating 16 scripts is being released in July 2019. The inclusion of RZ-LGR to validate TLD labels and their variant labels has also been recommended as part of managing IDN variant TLDs. GNSO and ccNSO are currently considering this recommendation. The Study Group on Technical Utilization of Root Zone Label Generation Rules took up this item to discuss. Recommendation four (4) of their report suggests a way forward. This work has been released for public comment and will be finalized afterwards for further consideration of the ICANN Board. See report at https://www.icann.org/en/system/files/files/recommendations-rz-lgr-14may19-en.pdf and public comment at https://www.icann.org/public-comments/technical-rz-lgr-2019-05-15-en. Further implementation of this item is deferred as of 30 June 2019 pending external activity. ICANN org will take up further work once the GNSO and ccNSO have considered these items as part of their policy development work. RZ-LGR procedure already suggests that the relevant script community can review their decision within the existing process and propose an updated version. The Technical Study Group on RZ-LGR supported this solution. This process is being considered by both GNSO and ccNSO in their respective policy development processes for IDN TLDs. This advice will be addressed through these PDPs. |
This item remains deferred pending further consideration by the ccNSO and GNSO in the context of their IDN related PDPs. |
|
Phase 4 | Deferred |
ICANN org recently developed the Recommendations for Managing IDN Variant TLDs, published at https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07-26-en. These have been adopted by ICANN Board at their meeting at ICANN64, where the Board asked the GNSO and ccNSO to consider these in their policy and procedures. Further implementation of this item is deferred as of 30 June 2019 pending external activity. ICANN org will take up further work once the GNSO and ccNSO have considered these items as part of their policy development work. This has already been proposed by SubPro WG for gTLDs with more details being developed by the IDN EPDP underway. ccNSO is also working on a solution for variant TLDs through its ongoing IDN ccPDP4. |
This item remains deferred pending further consideration by the ccNSO and GNSO in the context of their IDN related PDPs. |
|
Phase 4 | Deferred |
A detailed analysis has been published as part of recommendations for managing IDN variant TLDs, which has been approved by ICANN Board at ICANN64. The analysis has been forwarded to the GNSO and ccNSO for their consideration for relevant policy and procedure development. The analysis is available at https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07-26-en. Specifically see section 3 of the report at https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations-analysis-25jan19-en.pdf. |
Further implementation of this item is deferred as of 25 June 2019 pending external activity. ICANN org will take up further action once the GNSO and ccNSO consider this item as part of the policy development work. |
|
Report of the Security and Stability Advisory Committee on Root Scaling (R-4) |
Phase 4 | Deferred |
The plan will be updated to include actual measurement, monitoring, and data sharing capability of root zone performance, in cooperation with RSSAC and other root zone management participants to define the specific measurements, monitoring, and data sharing framework. Further implementation of this item is deferred as of 04 December 2019 pending external activity. ICANN org will take up further action once the implementation of RSSAC037-038 and the work of the Root Server System Governance Working Group is complete. |
Further implementation of this item is deferred as of 04 December 2019 pending external activity. ICANN org will take up further action once the implementation of RSSAC037-038 and the work of the Root Server System Governance Working Group is complete. |
SAC095: SSAC Advisory on the Use of Emoji in Domain Names R-1 |
Phase 4 | Deferred |
On 2 Nov 2017, the ICANN Board directed the ICANN org to engage with gTLD and ccTLD communities on the findings and recommendations in SAC095 in addition to requesting that the ccNSO and GNSO integrate conformance with IDNA2008 and its successor into their relevant policies so as to safeguard security, stability, resiliency and interoperability of domain names (see: https://www.icann.org/resources/board-material/resolutions-2017-11-02-en#1.e). IDN ccTLD Fast Track process already limits labels at top level to IDNA2008 which does not allow for emojis (see https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28mar19-en.pdf). Further, GNSO is considering limiting the TLDs to IDNA2008 (through the use of Root Zone Label Generation Rules) for the subsequent procedures for the gTLDs. The policy work is still under development by the community. Limiting TLDs to Root Zone LGRs is also recommended in the recent recommendations for IDN variant TLDs published at https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07-26-en and adopted by the ICANN Board at ICANN64 for further consideration by GNSO and ccNSO. Finally the recent work on technical use of Root Zone LGR by the study group also recommends the same: see recommendations 1 and 2 in the report at https://www.icann.org/en/system/files/files/recommendations-rz-lgr-14may19-en.pdf. Further implementation of this item is deferred as of 30 June 2019 pending external activity. ICANN org will take up further work once the GNSO and ccNSO have considered these items as part of their policy development work. SubPro WG has included RZ-LGR based on IDNA2008 for validating TLDs. Existing IDN gTLDs and ccTLDs are also based on IDNA2008. So this advice is already addressed to a large extent. ccNSO is also doing its policy development to replace IDN ccTLD Fast Track Process and is most likely to utilize IDNA2008 as a base standard for IDN ccTLDs. Thus, this advice is being implemented both currently and in upcoming policies for GNSO and ccNSO. |
This item remains deferred pending further consideration by the ccNSO and GNSO in the context of their IDN related PDPs. |
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-1C) |
Phase 4 | Deferred |
On 23 June 2019 the ICANN Board considered SAC101v2 and accepted Recommendation 1 and directed the ICANN President and CEO, or his designee(s), to create a plan that reports on ICANN org's and the community's progress toward the four objectives identified in the advice (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "In accepting advice item one, the Board further notes that the creation of an "accredited RDDS access program," is a topic under discussion in the EPDP Phase 2. The Board cannot dictate outcomes of PDPs. Once the EPDP delivers its final Phase 2 report, the Board will consider the policy recommendations." This item continues to be deferred. It is also subject of correspondence (https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-29jan21-en.pdf) between the GNSO Council and the Board, following a motion (https://community.icann.org/display/gnsocouncilmeetings/Motions+21+January+2021) passed by the GNSO Council. The topic will be parsed and placed in Phase 4 | Deferred. |
Once the EPDP delivers its final Phase 2 report, the Board will consider the policy recommendations. Deferred pending work in the Implementation Review Team |
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-3) |
Phase 4 | Deferred |
On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item three suggests that the 'Board and EPDP policy-makers should ensure that security practitioners and law enforcement authorities have access to domain name contact data, via RDDS, to the full extent allowed by applicable law.' As this is a policy matter and the topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs." |
As this is a policy matter and the topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs. Pending the closure of the SSAD ODP |
Phase 4 | Implement |
ICANN org has completed its review of existing materials to understand where there are gaps in training programs for registrars and registries related to the credential management cycle. ICANN org is now in the process of updating existing courses TE10 - DNS Ecosystem Security, and TE12 - Network Operations Security, to meet the requirements of SAC074 recommendation 4. Further, ICANN org is developing materials for a new course, TE15 - Credential Management Lifecycle. This work is expected to be complete by the end of the calendar year 2022. ICANN org will provide a formal update to the Board to complete the implementation of this recommendation, per the ARR process. |
||
Phase 4 | Implement |
On 23 June 2018, the Board accepted this advice and directed the ICANN President and CEO or his designee to implement an auto-renew feature in the CZDS system (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). CZDS platform migration is complete, making it possible to add new features to address the problem of gaps in user access to zone files. The feature has been scoped and is in the process of being added to the next product road map for future system enhancements. Due to additional updates to the roadmap, substantial updates for new features on CZDS is expected to be available in 2QFY20. Despite not implementing new features to CZDS, ICANN org did work to expand the utility of CZDS by adding the five largest legacy gTLDs, .biz, .com, .info, .net, and .org and most others to the platform as their contracts were being renewed or revised. New functionality for automated renewal of access by default was proposed and discussed with CZDS users, the RySG and SSAC to incorporate their feedback. The development of the functional changes is pending prioritization and incorporation to ICANN's frozen development pipeline. The CZDS 3.0 project has started recently, which among other things will address the SAC097 recommendations related to CZDS including support for zone file access extension prior to their expiration date, automatic renewal of access as the default system behavior, and automatic compliance escalation of unattended access requests in pending status. ICANN org plans to release this new functionality to CZDS in phases during the following months, and is available to provide a briefing to SSAC on the CZDS 3.0 project if it is of interest. The ICANN org continues work on the CZDS 3.0 project, the following milestones have been completed: On 25-April-2022 the CZDS system also offers requestors the option to cancel their pending requests if desired, which was functionality that the community asked for. On 24-May-2022 infrastructure updates were deployed to the CZDS system to improve performance and service availability for users downloading gTLD zone files. On 28-June-2022 support was added in the CZDS system to allow zone file access requestors to submit an access extension request prior to expiration of their current access, which makes it possible for users to retain uninterrupted access to already authorized zone files as long as the registry operator approves such requests prior to expiration. Optional email notifications for registry operators were also improved to provide a summary of received requests in a single daily digest as opposed to individual notifications. Future project milestones still in development include functionality to support automatic renewal of zone file access as the default system behavior, and automatic compliance escalation of unattended access requests in pending status. The ICANN org provided SSAC a briefing on the CZDS 3.0 project during the ICANN75 annual general meeting detailing the completed and upcoming project milestones. Work on the CZDS system continues to include functionality to support automatic renewal of zone file access as the default system behavior. In parallel, the development team is also working on improving the system availability and performance for the zone download service. In the future the system will also support automatic compliance escalation of unattended access requests in pending status. Support of automatic renewal of zone file access as the default system behavior has been deployed in the CZDS system on 15-November-2022. Registry operators were notified a month in advance and given the opportunity to opt out. In parallel, the development team is also working on improving the system usability to make it easier for registry operators to manage the configuration for automatic renewal of their current CZDS requests going forward. Enhancements in availability and performance for the zone download service are also in progress. In the future the system will also support automatic compliance escalation of unattended access requests in pending status. |
New functionality for automated renewal of access by default was proposed and discussed with CZDS users, the RySG and SSAC to incorporate their feedback. The development of the functional changes is pending prioritization and incorporation to ICANN's frozen development pipeline. |
|
Phase 4 | Implement |
On 23 June 2018, the Board accepted this advice and directed the ICANN President and CEO or his designee to adjust the zone file access subscription agreement to the extent necessary to accommodate the implementation of Recommendation 1 (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). ICANN org continues to work with the Policy team to inform the community to have the recommendation to be considered for the subsequent rounds of new gTLDs. Once the described functional updates that resulted from Recommendation 1 are applied to the CZDS system, any TLDs added to the CZDS system in the future would be able to offer the same approval policies to end-users. Once the CZDS 3.0 project is completed, the CZDS system will support the same functionality and zone file access approval policies for any TLD added in the future. Functionality already implemented as part of the CZDS 3.0 project will continue to be supported for any TLD added to the system in future rounds. |
Recommendation 2 is dependent on the implementation and completion of Recommendation 1 |
|
Phase 4 | Implement |
On 23 June 2018, the Board accepted this advice and directed the ICANN President and CEO or his designee to produce educational materials for registry operators to increase their awareness of ICANN's expectations with respect to zone file access (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). The number of complaints requiring Contractual Compliance follow-up is decreasing. The adoption rate of the new auto-approve feature increased to 45% from 40% in June 2019. The number of TLDs that approve requests for a period longer than 2 years is increasing. SAC097 was prepared in the first half of 2017. Since then ICANN org has worked with registry operators to decrease the number of zone file related complaints by creating awareness about zone files access. This includes multiple engagements and presentations to the gTLD Registries Stakeholder Group, the Brand Registry Group, and individual registries. ICANN Contractual Compliance is currently training additional staff members to assist in processing complaints related to zone file access requests. ICANN Contractual Compliance continues to address the contractual scope of denials and revocation of access to zone files with registry operators that appear to misunderstand the boundaries within which registry operators are allowed to do so. As previously reported, ICANN Contractual Compliance has dedicated additional members to processing complaints regarding zone file access requests and continues to train new members to assist in processing. As a result, ICANN Contractual Compliance has been able to address new complaints consistently on a timely basis. Additionally, ICANN Contractual Compliance has initiated outreach efforts with contracted parties to resolve processing concerns. The total volume of complaints received has remained consistently lower than the total received in June 2021, which was the highest volume received between June 2021 and May 2022. However, ICANN Contractual Compliance reiterates that successful implementation of the CZDS 3.0 project should help reduce the number of complaints, as it will, among other things support zone file access extension prior to their expiration date, automatic renewal of access as the default system behavior, and automatic compliance escalation of unattended access requests in pending status. ICANN Contractual Compliance continues to support the additional members dedicated to processing complaints regarding zone file access requests and continues to address new complaints consistently on a timely basis. Additionally, ICANN Contractual Compliance has initiated outreach efforts with contracted parties to resolve processing concerns. The total volume of complaints received per month remains consistently low since the last spike that occurred June of 2021. However, ICANN Contractual Compliance reiterates that implementation of the CZDS 3.0 project should help further reduce the number of complaints as the overwhelming majority of complaints concern pending requests for access, and most of the features of that project are aimed at quickening the renewal process. |
||
Phase 4 | Implement |
On 23 June 2018, the Board accepted this advice and directed the ICANN President and CEO or his designee to clarify the Zone File Access (ZFA) metric and to support registry operators to increase the accuracy of the public reporting for Web based WHOIS query statistics (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). ICANN org continues to facilitate the conversation between SSAC and RySG. The SSAC and RySG met to discuss observations of SSAC during ICANN65 where RySG members raised concerns. ICANN org will work with registries to improve the accuracy of the Zonefile access metric. ICANN encourages SSAC to continue engagement directly with the Registries to potentially develop best practices that can be utilized across the gTLDs. ICANN has created an interim solution for zone file access statistics, which is available through CZDS. ICANN org will continue to increase the awareness of registry operators to provide reports with the information provided by CZDS. During the September 2020 meeting with ICANN Org, SSAC leadership agreed to work with the TechOps group, which includes registry operators for a solution to have a standardization about the reported data about web-based WHOIS query statistics. In the past five years since SAC097 was published, the number of gTLDs that inaccurately report zfa-passwords field was reduced by almost 2/3 (June 2017: 45% to May 2022:14%), resulting with 86% of gTLDs reporting this field accurately. Every month, the exact number of zone file access provided (zfa-passwords) are available on CZDS Reports (https://czds.icann.org/reports) publicly for all gTLDs, as required by SAC097. ICANN Org published the Registry Monthly Reporting FAQs document (https://www.icann.org/en/system/files/files/registry-monthly-reporting-faqs-31mar22-en.pdf) in June 2022 to provide answers to the common questions and concerns that were received during ICANN Org's outreaches. This new document will be a continuous support for the registry operators and their technical service providers to generate and submit all reports accurately, despite cases such as turnover volume increases. The conversations between SSAC and registry operators clarified that ICANN Org cannot measure the accuracy of the web-based WHOIS query statistics. Therefore, it is not possible for ICANN Org to compare the past and current status of the issue by itself. ICANN Org is looking forward to supporting the SSAC leadership in their work with the TechOps group, which brings registry operators and their technical service providers together. To improve the accuracy of the WHOIS metric, ICANN and the RysG agreed to a clarification in the reporting requirements for Specification 3 of the Base Registry Agreement. This is available for public comment in the Proposed Amendments to the Base Registry Agreement to incorporate operational requirements for RDAP. https://www.icann.org/en/public-comment/proceeding/proposed-amendments-to-the-base-gtld-ra-and-raa-to-add-rdap-contract-obligations-06-09-2022. |
||
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-1B) |
Phase 4 | Implement |
On 23 June 2019 the ICANN Board considered SAC101v2 and accepted Recommendation 1 and directed the ICANN President and CEO, or his designee(s), to create a plan that reports on ICANN org's and the community's progress toward the four objectives identified in the advice (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "In accepting advice item one, the Board further notes that the creation of an "accredited RDDS access program," is a topic under discussion in the EPDP Phase 2. The Board cannot dictate outcomes of PDPs. Once the EPDP delivers its final Phase 2 report, the Board will consider the policy recommendations." ICANN notes that the SSAC has stated this item is complete pending implementation work. ICANN continues to work with gTLD registries and registrars to implement a service-level agreement and registry reporting requirements for RDAP. Per the 26 February 2019 legal notification "Pursuant to Appendix A (Section 1.1) of the Temporary Specification for gTLD Registration Data [https://www.icann.org/resources/pages/gtldregistration-data-specs-en [icann.org]] and other contractual provisions relating to Registration Data Directory Services, all gTLD registries and registrars are required to implement RDAP no later than 26 August 2019." Accordingly, this item will also be parsed and placed in Phase 5. |
|
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-1D) |
Phase 4 | Implement |
On 23 June 2019 the ICANN Board considered SAC101v2 and accepted Recommendation 1 and directed the ICANN President and CEO, or his designee(s), to create a plan that reports on ICANN org's and the community's progress toward the four objectives identified in the advice (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "In accepting advice item one, the Board further notes that the creation of an "accredited RDDS access program," is a topic under discussion in the EPDP Phase 2. The Board cannot dictate outcomes of PDPs. Once the EPDP delivers its final Phase 2 report, the Board will consider the policy recommendations." This item remains in Phase 4 | Implement. ICANN org notes the Public Comment period regarding Phase 2 Priority 2 Topics prior to Board consideration, as well as a pending Public Comment regarding Phase 2 Priority 1 Topics. The EPDP issued the Phase 2 Final Report on the Temporary Specification for gTLD Registration Data on 31 July 2020, and was subsequently adopted by the GNSO council on 24 September 2020 and was provided to the Board for consideration. ICANN org notes the Public Comment period regarding Phase 2 Priority 2 Topics closed on 22 January 2021 and a staff report was issued on 5 February 2021 (https://www.icann.org/en/system/files/files/report-comments-policy-recommendations-epdp-phase-2-05feb21-en.pdf). ICANN org also notes as the Public Comment regarding Phase 2 closed on 30 March 2021 (https://www.icann.org/public-comments/epdp-2-policy-recs-board-2021-02-08-en). Additionally, the Board resolved (https://www.icann.org/resources/board-material/resolutions-2021-03-25-en#2.c) to direct ICANN org to conduct the Operational Design Phase (ODP) for the SSAD on 25 March 2021. |
|
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-2B) |
Phase 4 | Implement |
On 23 June 2019 the ICANN Board considered SAC101v2 and accepted Recommendation 1 and directed the ICANN President and CEO, or his designee(s), to work with the community to clarify existing contractual obligations relating to rate limits (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board state "Advice item 2B suggests that the Board direct ICANN org to work with the community to 'clarify current expectations for the use of rate limiting under existing policy and agreements.' In accepting advice item 2B, the Board notes that the community should be involved in the discussion to clarify existing contractual obligations relating to rate limits." ICANN org is currently reviewing this advice to determine how it should be implemented. Once ICANN org has determined a path forward for implementation, further updates will be provided to the SSAC. The EPDP issued the Phase 2 Final Report on the Temporary Specification for gTLD Registration Data on 31 July 2020, and was subsequently adopted by the GNSO council on 24 September 2020 and was provided to the Board for consideration. ICANN org notes the Public Comment period regarding Phase 2 Priority 2 Topics closed on 22 January 2021 and a staff report was issued on 5 February 2021 (https://www.icann.org/en/system/files/files/report-comments-policy-recommendations-epdp-phase-2-05feb21-en.pdf). ICANN org also notes as the Public Comment regarding Phase 2 closed on 30 March 2021 (https://www.icann.org/public-comments/epdp-2-policy-recs-board-2021-02-08-en). Additionally, the Board resolved (https://www.icann.org/resources/board-material/resolutions-2021-03-25-en#2.c) to direct ICANN org to conduct the Operational Design Phase (ODP) for the SSAD on 25 March 2021. The ODP for the SSAD was launched on 29 April 2021 (https://www.icann.org/en/announcements/details/icann-organization-launches-operational-design-phase-for-system-for-standardized-accessdisclosure-29-4-2021-en). Additionally, the Board resolved on the EPDP Phase 2 Priority 2 topics on 21 June 2021, adopted GNSO Council Recommendations 19-22 and directed ICANN org to develop and execute an implementation plan for the recommendations (https://www.icann.org/resources/board-material/resolutions-2021-06-21-en). |
|
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-4) |
Phase 4 | Implement |
On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item four suggests that 'initiation of charges for RDS access, or any significant future changes in fees for RDDS access, must include a formal assessment of user impacts and the security and stability impacts, and be conducted as part of a formal Policy Development Process (PDP).' As this is a policy matter and the topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs." ICANN org is currently reviewing this advice to determine how it should be implemented. Once ICANN org has determined a path forward for implementation, further updates will be provided to the SSAC. The EPDP issued the Phase 2 Final Report on the Temporary Specification for gTLD Registration Data on 31 July 2020, and was subsequently adopted by the GNSO council on 24 September 2020 and was provided to the Board for consideration. ICANN org notes the Public Comment period regarding Phase 2 Priority 2 Topics closed on 22 January 2021 and a staff report was issued on 5 February 2021 (https://www.icann.org/en/system/files/files/report-comments-policy-recommendations-epdp-phase-2-05feb21-en.pdf). ICANN org also notes as the Public Comment regarding Phase 2 closed on 30 March 2021 (https://www.icann.org/public-comments/epdp-2-policy-recs-board-2021-02-08-en). Additionally, the Board resolved (https://www.icann.org/resources/board-material/resolutions-2021-03-25-en#2.c) to direct ICANN org to conduct the Operational Design Phase (ODP) for the SSAD on 25 March 2021. |
|
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-6) |
Phase 4 | Implement |
On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item six suggests that the 'ICANN Board should direct the ICANN Organization to work to ensure that all methods of access to RDDS data provide an equivalent response to the same query.' As this is a policy matter and the topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs." The EPDP issued the Phase 2 Final Report on the Temporary Specification for gTLD Registration Data on 31 July 2020, and was subsequently adopted by the GNSO council on 24 September 2020 and was provided to the Board for consideration. Pending Board consideration, this item will remain in a deferred status. The EPDP issued the Phase 2 Final Report on the Temporary Specification for gTLD Registration Data on 31 July 2020, and was subsequently adopted by the GNSO council on 24 September 2020 and was provided to the Board for consideration. ICANN org notes the Public Comment period regarding Phase 2 Priority 2 Topics closed on 22 January 2021 and a staff report was issued on 5 February 2021 (https://www.icann.org/en/system/files/files/report-comments-policy-recommendations-epdp-phase-2-05feb21-en.pdf). ICANN org also notes as the Public Comment regarding Phase 2 closed on 30 March 2021 (https://www.icann.org/public-comments/epdp-2-policy-recs-board-2021-02-08-en). Additionally, the Board resolved (https://www.icann.org/resources/board-material/resolutions-2021-03-25-en#2.c) to direct ICANN org to conduct the Operational Design Phase (ODP) for the SSAD on 25 March 2021. |
|
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-7) |
Phase 4 | Implement |
On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item seven suggests that the 'ICANN Board should direct the ICANN Organization to work to ensure that RDDS access is provided in a measurable and enforceable framework, which can be understood by all parties.' As this is a policy matter and the topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs." The EPDP issued the Phase 2 Final Report on the Temporary Specification for gTLD Registration Data on 31 July 2020, and was subsequently adopted by the GNSO council on 24 September 2020 and was provided to the Board for consideration. Pending Board consideration, this item will remain in a deferred status. The EPDP issued the Phase 2 Final Report on the Temporary Specification for gTLD Registration Data on 31 July 2020, and was subsequently adopted by the GNSO council on 24 September 2020 and was provided to the Board for consideration. ICANN org notes the Public Comment period regarding Phase 2 Priority 2 Topics closed on 22 January 2021 and a staff report was issued on 5 February 2021 (https://www.icann.org/en/system/files/files/report-comments-policy-recommendations-epdp-phase-2-05feb21-en.pdf). ICANN org also notes as the Public Comment regarding Phase 2 closed on 30 March 2021 (https://www.icann.org/public-comments/epdp-2-policy-recs-board-2021-02-08-en). Additionally, the Board resolved (https://www.icann.org/resources/board-material/resolutions-2021-03-25-en#2.c) to direct ICANN org to conduct the Operational Design Phase (ODP) for the SSAD on 25 March 2021. |
|
SAC106: SSAC Comments on Evolving the Governance of the Root Server System (R-2) |
Phase 4 | Implement |
The ICANN organization understands SAC106 Recommendation 2 to mean that the SSAC recommends to the Root Server System Governance Working Group (GWG) that the SSAC not be given any operational roles in any standing committees, operational committees, or other bodies that emerge from the deliberations of the GWG. The ICANN org also understands the SSAC is open to invitations from the bodies that emerge from the deliberations of the GWG to participate in an advisory capacity, consistent with SSAC's charter, experience and capabilities. ICANN sent this understanding to the SSAC for review on 15 August 2019. SAC106 Recommendations 2 through 4 have been received by the Root Server System Governance Working Group and is incorporating it into its proposal. The Root Server System Governance Working Group (RSS GWG) is aware of this SSAC statement. The emerging proposal from the RSS GWG includes a community performing the Strategy, Architecture, and Policy Function (SAPF). SAC106 is under consideration by the Root Server System Governance Working Group as it develops its proposal for root server system governance and root server operator accountability. The Root Server System Governance Working Group continues it discussions and will consider SSAC input. |
SAC106 is under consideration by the Root Server System Governance Working Group as it develops its proposal for root server system governance and root server operator accountability. |
SAC106: SSAC Comments on Evolving the Governance of the Root Server System (R-4) |
Phase 4 | Implement |
The ICANN organization understands SAC106 Recommendation 4 to mean that the SSAC recommends the SSAC recommends to the Root Server System Governance Working Group (GWG) that bodies involved in the ongoing oversight of the Root Server System (RSS) be reviewed regularly to ensure that the RSS is both meeting its commitments and that it remains responsive to evolutionary needs and changing environmental factors as appropriate. ICANN sent this understanding to the SSAC for review on 15 August 2019. SAC106 Recommendations 2 through 4 have been received by the Root Server System Governance Working Group and is incorporating it into its proposal. The Root Server System Governance Working Group continues it discussions and will consider SSAC input. |
|
Phase 5 | Close Request |
The IDN Guidelines were updated to version 4 in May 2018 (https://www.icann.org/en/system/files/files/idn-guidelines-10may18-en.pdf). However, these Guidelines are currently being held for review of GNSO, following the request from GNSO to the ICANN Board. In March 2020, the Guidelines for Developing Reference Label Generation Rules (LGRs) for the Second Level Version 2 were published for public comment, and the public comment staff report was issued in May 2020. The IANA Repository of IDN tables is also now being updated to address any gaps. ICANN org has been developing reference LGRs for the second level in consultation with the community and in-line with the RZ-LGRs. SubPro WG has included a recommendation for ROs to utilize reference LGRs when they design their IDN tables. Also, the updated IDN table review process now utilizes the reference LGRs. Therefore, this recommendation is now largely addressed. Additional reference LGRs will be developed against the additional RZ-LGR proposals received in the future. With the new IDN table review process now implemented, this item can now be closed. |
||
Phase 5 | Close Request |
On 23 June 2018, the Board accepted this advice and noted that implementation has been completed (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). Subsequently, on 2 August 2018 the SSAC contacted the ICANN org to oppose this determination and requested the ICANN org change SAC061 Recommendation 2's status from 'Closed' to 'Open." Upon review of SAC061 and SAC101v2, the ICANN org has returned SAC061 to Phase 2 | Understand. SAC061 Recommendation 2 will be considered in conjunction with SAC101v2. On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item five reiterates Recommendation 2 from SAC061 and suggests that 'The ICANN Board should ensure that a formal security risk assessment of the registration data policy be conducted as an input into the Policy Development Process. A separate security risk assessment should also be conducted regarding the implementation of the policy.' The advice further suggests that 'These assessments should be incorporated in PDP plans at the GNSO.' As the advice suggests that the assessments be incorporated into PDP plans and the GNSO is the manager of PDPs, the Board notes and refers this advice to the GNSO Council." |
||
SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-1 |
Phase 5 | Close Request |
On 23 June 2018, the Board accepted this advice and will ask the GNSO Subsequent Procedures PDP to include this recommendation in its work (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). |
|
SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-2 |
Phase 5 | Close Request |
On 23 June 2018, the Board accepted this advice and will ask the GNSO Subsequent Procedures PDP to include this recommendation in its work (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). |
|
SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-3 |
Phase 5 | Close Request |
On 23 June 2018, the Board accepted this advice and will ask the GNSO Subsequent Procedures PDP to include this recommendation in its work (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). |
|
SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-4 |
Phase 5 | Close Request |
On 23 June 2018, the Board accepted this advice and will ask the GNSO Subsequent Procedures PDP to include this recommendation in its work (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). |
|
SAC095: SSAC Advisory on the Use of Emoji in Domain Names R-2 |
Phase 5 | Close Request |
On 2 Nov 2017, the ICANN Board directed the ICANN org to engage with gTLD and ccTLD communities on the findings and recommendations in SAC095 in addition to requesting that the ccNSO and GNSO integrate conformance with IDNA2008 and its successor into their relevant policies so as to safeguard security, stability, resiliency and interoperability of domain names (see: https://www.icann.org/resources/board-material/resolutions-2017-11-02-en#1.e). Registrations under gTLDs are limited to IDNA2008 under the new gTLDs program. So registrations for such gTLDs do not permit emojis. The same restrictions are also extended for contracts for other gTLDs. There is active outreach to the ccTLDs for following the same practice, and not register emojis, by ICANN org's GSE team and the IDN program team. ICANN org has also translated the advice from SSAC to training materials, e.g. see the flyer and its translations at the bottom of the webpage www.icann.org/idn - which is being disseminated by the GSE team. ICANN org continues to conduct outreach to ccTLDs to inform them of the risks of registering emoji domains. Outreach has been done to ccTLDs since the advice, and materials were produced, distributed and presented at multiple forums. This item was requested to be closed. |
|
SAC098: The Security, Stability and Resiliency of the DNS Review (SSR2) |
Phase 5 | Close Request |
On 28 October 2017, the Board issued a letter to the SSR2 Review Team instructing the team to pause all work related to the review, excepting only planned engagement meetings at ICANN 60 (https://www.icann.org/en/system/files/correspondence/crocker-to-ssr2-28oct17-en.pdf). On 7 June 2018 ICANN Org announced the formal restart of the SSR2 Review with four additional Review Team members (https://www.icann.org/news/announcement-2-2018-06-07-en). This advice has been taken over by subsequent events and is no longer relevant. The Third Accountability and Transparency Review (ATRT3) issued recommendation 3.3 which called for the next SSR Review to be deferred until the next Accountability and Transparency Review team is convened and will evaluate whether this review should continue. Accordingly, the Board deferred SSR3 in March 2021. The SSR2 issued its final report in January 2021 and the Board took action on 63 recommendations in July 2021. The Board took action on 3 recommendations placed into "pending" category and plans to address the remaining "pending" recommendations within the next 6 months. In addition, the ICANN org initiated Lifecycle of Reviews project will address the intent of this SSAC advice - to better plan and manage the end-to-end process of reviews. |
|
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-1A) |
Phase 5 | Close Request |
On 23 June 2019 the ICANN Board considered SAC101v2 and accepted Recommendation 1 and directed the ICANN President and CEO, or his designee(s), to create a plan that reports on ICANN org's and the community's progress toward the four objectives identified in the advice (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "In accepting advice item one, the Board further notes that the creation of an "accredited RDDS access program," is a topic under discussion in the EPDP Phase 2. The Board cannot dictate outcomes of PDPs. Once the EPDP delivers its final Phase 2 report, the Board will consider the policy recommendations." The EPDP issued the Phase 2 Final Report on the Temporary Specification for gTLD Registration Data on 31 July 2020, and was subsequently adopted by the GNSO council on 24 September 2020 and was provided to the Board for consideration. The EPDP Phase 2 Report contains recommendations regarding: Accreditation of SSAD requestors, Required criteria and content of SSAD requests, Response requirements, Required Service Level Agreements (SLAs), Automation of SSAD processing, Terms and conditions of SSAD, Logging, auditing, and reporting requirements, Implementation of a GNSO Standing Committee. ICANN org notes the SSAC confirmation that item "a" is considered complete. This item will be parsed and placed in Phase 5. |
|
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-2A) |
Phase 5 | Close Request |
On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item 2A suggests that the Board direct ICANN org to work with the community to 'develop policy with clearly defined uniform purposes for RDDS rate-limiting and corresponding service level agreement requirements.' As policy is developed by the community and this topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs. In taking this action, the Board also notes that in the Annex to the Temporary Specification for gTLD Registration Data, the Board asked that the topic of rate limit be discussed and resolved by the community as quickly as possible." |
|
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-5) |
Phase 5 | Close Request |
On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item five reiterates Recommendation 2 from SAC061 and suggests that 'The ICANN Board should ensure that a formal security risk assessment of the registration data policy be conducted as an input into the Policy Development Process. A separate security risk assessment should also be conducted regarding the implementation of the policy.' The advice further suggests that 'These assessments should be incorporated in PDP plans at the GNSO.' As the advice suggests that the assessments be incorporated into PDP plans and the GNSO is the manager of PDPs, the Board notes and refers this advice to the GNSO Council." |
|
SAC106: SSAC Comments on Evolving the Governance of the Root Server System (R-3) |
Phase 5 | Close Request |
The ICANN organization understands SAC106 Recommendation 3 to mean that the SSAC recommends to the Root Server System Governance Working Group (GWG) that decisions of the GWG be made on the basis of consensus, and that votes only be taken when formality is required or consensus is not achievable. ICANN sent this understanding to the SSAC for review on 15 August 2019. SAC106 Recommendation 2 through 4 was provided to the Root Server System Governance Working Group (GWG) and is operating on the basis of consensus. The Root Server System Governance Working Group operates transparently and makes decision by consensus. This item is in Phase 5 | Close Request as of 07 April 2021. The charter of the Root Server System Governance Working Group requires consensus. |
|
SSAC Advisory on DNS "Search List" Processing (R-2) |
Phase 5 | Close Request |
The ICANN organization understands that SAC064 R-2 means that the SSAC recommends that ICANN organization work with the DNS community and the IETF to encourage the standardization of search list processing behavior, beginning with the submission of an Internet-Draft to the IETF and advocating for its standardization within the IETF process. Updates to RFC 1535 and other RFCs related to this topic should be included within the Internet-Draft. On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b). |
R-2 is completed but will not be closed until the entire SAC064 Advisory is complete and R-3 is dependent on the NCAP implementation |
SSAC Comment on the ICANN gTLD Registry Transition Processes Model (R-2) |
Phase 5 | Close Request |
On 23 June 2018, the Board accepted this advice and directed the CEO or his designee to implement the advice (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). |
|
SSAC Report on Domain Name Registration Data Validation (R-3) |
Phase 5 | Close Request |
The ICANN organization understands SAC058 Recommendation 3 to mean that the ICANN community should seek to identify validation techniques to be used by registrars and registries for validating registration data. On 23 June 2018, the Board accepted this advice and directed the CEO or his designee to implement the advice (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). |
|
SSAC Report on WHOIS Terminology and Structure (R-2) |
Phase 5 | Close Request |
The Board accepted this advice in October 2011 and requested that a roadmap to implementation of SAC051 be developed (https://www.icann.org/resources/board-material/minutes-2011-10-28-en#5). A roadmap to implementing SAC051 was published for public comment in February 2012: https://www.icann.org/news/announcement-6-2012-06-04-en. As of 26 August 2019 all contracted parties are required to provide an RDAP service in addition to the WHOIS service. ICANN org expects to initiate the formal process for amending the Base gTLD Registry Agreement and 2013 Registrar Accreditation Agreement respectively to incorporate robust requirements for RDAP and define a smooth transition from WHOIS to RDAP including a sunset of the obligations for the WHOIS service. |
Advice Items Closed in the Last 12 Months
| Advice Item | Close Date | Action(s) Taken |
|---|---|---|
11/21/22 |
The ICANN org understands the SSAC recommends that, following the completion and submission of the CCWG's report, the next step in the process be to have an outside expert with a demonstrated track-record in designing funding programs review the report, comment on its finding and recommendations, and use it as a basis to inform the Board on the design of a grant making process for the auction proceeds that implements grant making best practices. The ICANN org also understands that the SSAC recommends that this step should be undertaken before the Board formally considers the CCWG's Final Report as its advice would assist the Board in its consideration of the CCWG recommendations. ICANN sent this understanding to the SSAC for review on 16 June 2020. ICANN received confirmation of understanding on 22 July 2020. The Board reviewed the CCWG-AP recommendations, including feasibility information, in line with the 2018 Board Principles transmitted to the CCWG-AP, including a review of an ICANN Org assessment document. On 12 June 2022, the Board formally approved the recommendations of the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP) and directed ICANN's President and CEO, or his designee(s), to take all actions as directed within the Board Scorecard to ultimately implement an ICANN Grant Program aligned with ICANN's mission and based in sound governance practices. Work has commenced on delivering a preliminary implementation plan to the Board by 10 October 2022 as outlined in the resolutions, and updates to the Board and Community will take place during this work. The ICANN Board expressed its expectation that ICANN org will access expertise in developing and implementing the ICANN Grant Program. |
|
6/15/22 |
The ICANN organization understands SAC121 is the SSAC Briefing on Routing Security of the DNS. There are no actionable items for the ICANN Board. This understanding was sent to the SSAC on 22 June 2022. |
|
SAC120: SSAC Input to GNSO IDN EPDP on Internationalized Domain Name Variants |
5/9/22 |
The ICANN understands SAC120 is a report from the ICANN Security and Stability Advisory Committee (SSAC) providing advice to the ICANN Generic Name Supporting Organization (GNSO) Expedited Policy Development Process (EPDP) on Internationalized Domain Names (IDNs). The advice concerns the management of internationalized domain name variants. There are no actionable items for the ICANN Board. This understanding was sent to the SSAC on 09 May 2022. |