| Recommendation | Description | Current Phase |
|---|---|---|
| Recommendation 1 | ICANN should expand the range of situations that would trigger an emergency response, for example national security, emergency preparedness, critical infrastructure, key economic processes, commerce, and the preservation of law and order. | CLOSED |
| Recommendation 2 | Instead of a single controlled interruption period, ICANN should introduce rolling interruption periods, broken by periods of normal operation, to allow affected end-user systems to continue to function during the 120-day test period with less risk of catastrophic business impact. | CLOSED |
| Recommendation 3 | ICANN should perform an evaluation of potential notification approaches against at least the requirements provided by the SSAC prior to implementing any notification approach. | CLOSED |
| Recommendation 4 | ICANN should implement a notification approach that accommodates Internet Protocol Version 6 (IPv6)-only hosts as well as IP Version 4 (IPv4)-only or dual-stack hosts. | CLOSED |
| Recommendation 5 | ICANN should provide clarity to registries on the rules and the method of allocation of blocked names after the conclusion of the test period. | CLOSED |
| Recommendation 6 | ICANN should consider not taking any actions solely based on the JAS Phase One Report. If action is planned to be taken before the entire report is published, communications to the community should be provided to indicate this clearly. | CLOSED |
| Recommendation 7 | ICANN should in due course publish information about not yet disclosed issues. | CLOSED |
| Recommendation 8 | ICANN should seek to provide stronger justification for extrapolating findings based on one kind of measurement or data gathering to other situations. | CLOSED |
