View source for CcNSO Policy Development Process - Retirement

{{ICANN Working Group
|Type= ccNSO
|Status= Final Report
|Issue Areas= Retirement of ccTLDs
|Date Established= April 10, 2017
|Charter= https://community.icann.org/download/attachments/64078882/charter-wg-retirement-cctlds-10apr17-en.pdf
|Workspace= https://community.icann.org/display/ccnsowkspc/Policy+Development+Process+%28PDP3.0%29+-+Retirement
}}

The [[ccNSO]]'s [[Policy Development Process]] (PDP) regarding retirement of country code [[Top-Level Domain|TLDs]] was initiated to fill a gap in ICANN's policy processes. When world events cause an Alpha-2 code to be removed from the [[ISO 3166-1]] list of country codes, there has been previously been no consistent or programmatic response from ICANN regarding the retirement of the associated [[ccTLD]]. The PDP seeks to provide consistent and predictable outcomes for ccTLDs that are no longer associated with an Alpha-2 country code on the ISO list.

==History==
The ISO 3166 list of country codes is a standard developed and maintained by the International Organization for Standardization.<ref name="iso">[https://www.iso.org/iso-3166-country-codes.html ISO.org - ISO 3166]</ref> Among other codes, the list contains two-letter codes for each sovereign entity in the world.<ref name="iso" /> In the early days of the Internet, [[Jon Postel]] utilized the ISO 3166 list to assign two-letter top-level domains to each country. [[RFC 1591]] lays out the rationale for using the list: 

<blockquote>The IANA is not in the business of deciding what is and what is not a country. The selection of the ISO 3166 list as a basis for country code top-level domain names was made with the knowledge that ISO has a procedure for determining which entities should be and should not be on that list.<ref>[https://tools.ietf.org/html/rfc1591 IETF.org - RFC 1591], page 5-6, March 1994</ref></blockquote>

===Exceptions and Anomalies===
This policy has remained consistent since RFC 1591.<ref name="eligible">[https://www.iana.org/help/eligible-tlds IANA - Eligible TLDs]</ref> ISO 3166 remains the canonical resource for all two-letter, top-level codes. However, certain exceptions exist within the DNS:

====ICANN Board-Approved Exceptions====
*EU, which is "exceptionally reserved" by the ISO 3166 Maintenance Agency as representative of the European Union. In 2000, the [[ICANN Board]] authorized the delegation of exceptionally reserved codes as TLDs under specific conditions.<ref>[https://features.icann.org/2000-09-25-delegation-cctlds ICANN Board Resolution 00-74], September 25, 2000</ref>
*UK and AC, which were grandfathered into the DNS under the same board resolution. (JE and GG were also originally grandfathered, but have since moved onto the list of country codes.)<ref name="eligible" />

====.su====
The .su ccTLD was delegated to the Soviet Union in 1990.<ref name="reuters">[https://www.reuters.com/article/us-russia-internet/ussr-still-alive-on-internet-and-wont-go-quietly-idUSL1986480720070919 Reuters - USSR is Still Alive on the Internet], September 19, 2007</ref> The country code was removed from the ISO 3166 list in 1992 following the dissolution of the Soviet Union.<ref>[https://www.iso.org/obp/ui/#iso:code:3166:SU ISO.org - SU]</ref> At the time, no consistent policy for retirement of ccTLDs associated with removed two-letter codes existed. Due to a variety of circumstances, no action was taken regarding the retirement of .su.<ref name="reuters" /> As Kim Davies, then the VP of IANA Services at ICANN, explained in 2007:

<blockquote>Traditionally when country codes have been retired, it has been left to their local Internet communities to determine the most appropriate way to arrange for a transition. This is in line with the general principle that country code domains are operated within countries for their local Internet community, in the way that best serves them...To retain .SU, under current policy [registry operators] would need to successfully apply for the code to be re-instated into the ISO 3166-1 standard, either as a regular two-letter country code, or as an “exceptionally reserved” code like UK and EU.<ref>[https://www.icann.org/en/blogs/details/the-lives-of-country-code-domains-19-9-2007-en ICANN.org - The Lives of Country Code Domains], September 19, 2007</ref></blockquote>

However, registration of .su domains continued, and continues to the present day.<ref>[https://www.inverse.com/article/8672-the-bizarre-afterlife-of-su-the-domain-name-and-last-bastion-of-the-ussr Inverge.com - The Bizarre Afterlife of .su], April 21, 2021</ref> The SU code was added to the "exceptionally reserved" list in 2010 at the urging of the registry operator.<ref name="background">[https://community.icann.org/pages/viewpage.action?pageId=64081623&preview=/64081623/158141028/icann59-cctld-lifecycle.pdf ICANN 59 Presentation - Background on the Implementation of the ccTLD Eligibility Lifecycle], June 29, 2017</ref>

===PDP History===
The origin of the push to review and/or implement retirement procedures dates to the .su situation, when ICANN issued a call for comments regarding its retirement procedures for ccTLDs.<ref>[https://www.icann.org/en/announcements/details/discussion-paper-on-retiring-country-code-top-level-domains-5-12-2006-en ICANN.org - Discussion Paper on Retiring ccTLDs], May 12, 2006</ref> The responses were varied, but a common theme was that ICANN's action to date had been inconsistent.<ref>[https://forum.icann.org/lists/cctld-sunset-comments/ ICANN.org Forum - Comments on ccTLD Sunset Procedures]</ref> 

The ccNSO's Delegation & Redelegation Working Group issued a final report on the retirement of ccTLDs as part of its work in 2011.<ref name="delreport">[http://ccnso.icann.org/workinggroups/drd-wg-retirement-report-07mar11-en.pdf DRD-WG - Final Report], March 7, 2011</ref> The report again identified the lack of policy as a pressing concern, and recommended a policy development process to establish a consistent and transparent policy.<ref name="delreport" /> In 2014, the Framework of Interpretation working group regarding the delegation and redelegation of ccTLDs provided interpretive guidance to RFC 1591 and ICANN's policy standing as it related to IANA functions around ccTLDs.<ref name="foi">[http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf ccNSO FOI-WG Final Paper], October 7, 2014</ref> The report did not propose policy; rather, the working group's goal was "to give IANA and the ICANN Board clear guidance on the meaning and intent of RFC1591, in order to clarify existing policy and to facilitate consistent and predictable application of this policy."<ref name="foi" />

In 2017, the ccNSO convened a drafting team to develop charters for a Retirement PDP Working Group and a Review Mechanism PDP Working Group.<ref>[https://community.icann.org/display/ccnsowkspc/DT+-+Review+Mechanism%2C+Retirement Drafting Team Workspace, ccNSO]</ref> The group issued a final draft charter for the Retirement PDP on February 27, 2017.<ref>[https://community.icann.org/download/attachments/64068742/Charter%20Working%20Group%20Retirement%20of%20ccTLDs%20version%204.pdf?version=1&modificationDate=1488463374000&api=v2 Charter v. 4.0, Retirement Working Group], Feb. 27, 2017</ref> 

The Working Group was established in April 2017, under a finalized charter<ref>[https://community.icann.org/download/attachments/64081623/Charter%20Working%20Group%20%20Retirement%20ccTLDs.pdf Retirement Working Group Charter], April 10 2017</ref> and accompanying issue report.<ref>[https://community.icann.org/download/attachments/64081623/Issues%20report%20ccPDP%203%20-%20April%2010%202017.docx Retirement Issue Report], April 10, 2017</ref> At [[ICANN 59]], Kim Davies presented a historical look back at delegation, redelegation, and retirement decisions in the ccTLD space.<ref name="background" /> The presentation also described IANA's current policy and process. 

After deliberation, drafting, and public comment, the Working Group issued its final report in February 2021.<ref name="final">[https://ccnso.icann.org/en/workinggroups/pdp3-retirement-final-report-09feb21-en.pdf ccNSO Retirement Working Group - Final Report], February 9, 2021</ref>

All proposals were adopted by both the ccNSO Council and the ccNSO membership in August 2021. 
On September 28, 2021, the ccNSO Council transmitted the policy recommendation pertaining to the retirement of ccTLDs to the ICANN Board for consideration and approval.<ref>[https://www.icann.org/en/system/files/correspondence/reynoso-to-botterman-28sep21-en.pdf ccNSO Chair Reynoso to Board Chair Botterman, Correspondence, ICANN]</ref>

During the [[ICANN 75]] ICANN Annual General Meeting in September 2022, the ICANN Board adopted the ccNSO policy recommendation pertaining to the retirement of the delegated Top Level Domains associated with the country codes. The next step is the implementation of the policy.<ref>[https://community.icann.org/display/ccnsowkspc/ICANN76+%7C+ccNSO+Session+Highlights ICANN76 Session Highlights]</ref>

==Policy==
The Working Group developed a five- to ten-year phase-out plan for ccTLDs upon specific triggering events:
#for ccTLDs whose codes are on the ISO-3166-1 list, when that code is removed from the list by ISO;
#for ccTLDs whose codes do not appear on the ISO-3166-1 list, when the ISO 3166 Maintenance Agency makes any change to that code; and
#for IDN ccTLDs, the triggering event will be separately established by the [[CcNSO Policy Development Process - IDN Strings|PDP on selection and deselection of IDN ccTLDs]] (launched May 2020).<ref name="final" />

In response to a triggering event, the IANA Naming Functions Operator (IFO) sends a Notice of Removal to the ccTLD manager, stating that the ccTLD will be removed from the root in five years' time. The ccTLD manager may submit a Retirement Plan that extends the retirement timeframe to up to ten years. In the case of triggering event #2, above, the manager may also appeal the decision to retire the TLD.<ref name="final" /> A ccTLD manager may also appeal an IFO decision to not grant an extension of the five-year timeline for retirement. No appeal is allowed for ccTLD managers whose country code is removed from the ISO 3166-1 list (triggering event #1).<ref name="final" />

===Submission and Board Action===
The ICANN Board received the ccNSO's policy report in September 2021.<ref name="74session">[https://74.schedule.icann.org/meetings/jboc23nMv7ewMYjMX ICANN 74 Archive - ccNSO Council Meeting], June 16, 2022 (Presentation of Patricio Poblete beginning at 56:00)</ref> [[Patricio Poblete]] presented an update to the ccNSO Council on the board's process at [[ICANN 74]].<ref name="74session" /> He noted that the relative lack of ccNSO policy activity caused a need to develop some procedures for processing the policy recommendations on an ad hoc basis. He noted specific provisions of the [[ICANN Bylaws]] that required certain steps upon receipt of a policy proposal that would "substantially affect the operation of the Internet:"<ref>[https://www.icann.org/resources/pages/governance/bylaws-en/#article3 ICANN Bylaws, Article 3.6], as amended June 2, 2022</ref>
# A public comment period on the proposed policy is required;
# The opinion of the [[GAC]] must be requested; and
# Where practically feasible and consistent with the policy development process, a public forum should be held.<ref name="74session" />

Poblete stated in his presentation that, to his surprise, the public comment periods that occurred during the policy development process were not sufficient to satisfy the "notice and comment" requirement. As a result, upon receipt of the policy, a number of actions were taken. At its October 2021 board workshop, the board created an ad hoc group to shepherd the policy assessment process. The ad hoc group was comprised of [[Avri Doria]], [[Becky Burr]], [[Katrina Sataki]], with Poblete chairing the group. The group worked with the [[Board Governance Committee]] to draft a charter for the group's work, and after BGC approval of the charter,<ref>[https://www.icann.org/resources/board-material/minutes-bgc-2022-02-15-en Minutes of the Meeting of the Board Governance Committee], February 15, 2022</ref> the ad hoc group began meeting in March 2022. In addition to addressing the retirement policy, the group charter also called for more formal procedures to receive and process ccNSO policy recommendations.<ref name="74session" /> 

As the group was working through the preliminaries, the retirement policy was published for public comment<ref>[https://www.icann.org/en/public-comment/proceeding/ccnso-proposed-policy-on-the-retirement-of-cctlds-22-11-2021 ICANN Public Comment Archive - ccNSO Proposed Policy on the Retirement of ccTLDs], initiated November 22, 2021</ref> and the GAC was invited to evaluate and provide advice on the policy.<ref>[https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-06dec21-en.pdf ICANN Correspondence Archive - Maarten Botterman to Manal Ismail], December 6, 2021</ref> There were only four responses to the public comment process, largely positive regarding the policy. The GAC responded in January, noting that they had paid close attention during the PDP and had no objections or concerns.<ref>[https://www.icann.org/en/system/files/correspondence/ismail-to-botterman-31jan22-en.pdf ICANN Correspondence Archive - Manal Ismail to Maarten Botterman], January 31, 2022</ref>

====ccNSO Reactions====
Poblete's presentation was met with varying degrees of disappointment by the assembled council members. [[Chris Disspain]] requested more information regarding the delay between receipt of the policy and action on the policy. Poblete agreed that the the timeframe for establishing the charter was longer than he anticipated. [[Nick Wenban-Smith]] wondered if "it is just that ICANN is rubbish at everything, and five years is a reasonable time to do something quite simple..." Poblete agreed again, noting that he was part of the PDP process, and was surprised that "yet another" public comment period was needed. [[Stephen Deerhake]] asked Poblete not to take his comments personally, and then commented that 
<blockquote>This grade of inaction, I think, is not only inexcusable, I think it's insulting to the volunteer community as Nick pointed out, has worked a long, long time on this policy. I don't understand why it appears the board got caught flat-footed when this policy was delivered to them. We've been working on it for years. The board's known that - the working group has been the butt of jokes within the board for taking so long, if I understand correctly. So it should not have been a surprise when this policy picked up...pitched up...It would be nice to have some semblance of communication from the board to the working group of any concerns or questions you might have. We've heard nothing.<ref name="74session" /></blockquote>

==Implications for Open Use ccTLDs==
The policy presents a risk for registrants who want to utilize an [[Open Use ccTLD]] on the web. In the event that a country code such as TV is removed from the ISO-3166 list, for example, many companies who presently use .tv as a signifier for streaming video content would have to transition to a new domain.

==References==
{{reflist}}

[[Category:PDPs]]