SAC046 was published on 6 December 2010. All SSAC publications can be found at https://www.icann.org/groups/ssac/documents.
| Recommendation | Description | Current Phase |
|---|---|---|
The SSAC recommends the following steps be taken before launching additional gTLDs, in parallel with continued deployment of IDNs and IPv6: Formalize and publicly document the interactions between ICANN and the root server operators with respect to root zone scaling. | CLOSED | |
| Recommendation 2 | The SSAC recommends the following steps be taken before launching additional gTLDs, in parallel with continued deployment of IDNs and IPv6: ICANN, National Telecommunications and Information Administration (NTIA), and VeriSign should publish statements, or a joint statement, that they are materially prepared for the proposed changes. | CLOSED |
| Recommendation 3 | The SSAC recommends the following steps be taken before launching additional gTLDs, in parallel with continued deployment of IDNs and IPv6: ICANN should publish estimates of expected and maximum growth rates of TLDs, including IDNs and their variants, and solicit public feedback on these estimates, with the end goal of being as transparent as possible about the justification for these estimates. | CLOSED |
| Recommendation 4 | The SSAC recommends the following steps be taken before launching additional gTLDs, in parallel with continued deployment of IDNs and IPv6: ICANN should update its "Plan for Enhancing Internet Security, Stability, and Resiliency," 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. | DEFERRED |
| Recommendation 5 | The SSAC recommends the following steps be taken before launching additional gTLDs, in parallel with continued deployment of IDNs and IPv6: ICANN should commission and incent interdisciplinary studies of security and stability implications from expanding the root zone more than an order of magnitude, particularly for enterprises and other user communities who may implement strong assumptions about the number of TLDs or use local TLDs that may conflict with future allocations. | CLOSED |