Support regards Olga El mié, 2 abr 2025 a las 9:21, Bart Boswinkel via Ccnso-council (< ccnso-council@icann.org>) escribió:

Dear all,

Please find included the draft response to Kim Davies to provide clarification on the ccTLD retirement policy. For your reference the original questions are included as well (word document) The draft was compiled by Stephen, Chris, Jordan, Peter and Alejandra.

Goal is to approve this letter by email vote *by 9 April 2025*.

If you have any concerns or questions, please reply to the list. If you support, abstain or not support the letter, please use the list as well to let your position know.

Kind regards,

Bart

------------

​​XX April 2025

Dear Kim,

We refer to our meeting on 8 March 2025 in Seattle and thank you for your email of 13 March requesting clarification on the ICANN ccTLD Retirement Policy (the Policy).

For the avoidance of doubt, we would not characterise our meeting as a ‘discussion’. Rather, we listened to your concerns and took away your questions for discussion at the Council. Your email of 13 March puts in writing what you are asking and this letter responds to that.

Before we deal with the specific questions raised, it is important to stress:

a. The Policy is relevant only where a 2-letter code has been delegated in the root zone. The clarification of the standing or otherwise of any parts of ISO 3166-1 in the Policy or in this letter should not be considered in respect to policy matters relating to delegations, transfers, or revocations of ccTLDs; and

b. Although the Policy was developed by the ccNSO it has been adopted and implemented by ICANN and is therefore an ICANN policy not a ccNSO policy.

In your email you state that the language in the Policy suggests that a triggering event occurs when:

(i) An ascii entry identified as a ccTLD in the Root Zone database

(ii) That corresponds to any ISO 3166-1 Alpha 2 Code Element

(iii) Is deleted from the ISO 3166-1 standard by the ISO 3166-1 Maintenance Agency.

We believe that this is the correct understanding of a triggering event.

You go on to request clarification of the meaning of Alpha-2 Code Elements. It is not the role of the ccNSO to interpret the meaning of terms within ISO 3166-1. That said, when developing the policy, although the ccNSO did consider all of the various categories of code elements it took the view that the policy applied to those code elements that are defined in the fourth edition of the International Standard ISO3166, part 1, i.e. on the *list of country names *or as an *exceptionally reserved code element*, and crafted the policy on that basis.

Accordingly, it is our view that the Policy is relevant only in circumstances where, as a result of action taken by the ISO, a delegated 2-letter code is no longer on the list of country names or an exceptionally reserved code element.

If you have any further questions regarding this letter, please do not hesitate to reach out.

Best regards,

Alejandra Reynoso

ccNSO Council Chair

_______________________________________________ Ccnso-council mailing list -- ccnso-council@icann.org To unsubscribe send an email to ccnso-council-leave@icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

I support Wafa Le mer. 2 avr. 2025, 13:21, Bart Boswinkel via Ccnso-council < ccnso-council@icann.org> a écrit :

Dear all,

Please find included the draft response to Kim Davies to provide clarification on the ccTLD retirement policy. For your reference the original questions are included as well (word document) The draft was compiled by Stephen, Chris, Jordan, Peter and Alejandra.

Goal is to approve this letter by email vote *by 9 April 2025*.

If you have any concerns or questions, please reply to the list. If you support, abstain or not support the letter, please use the list as well to let your position know.

Kind regards,

Bart

------------

​​XX April 2025

Dear Kim,

We refer to our meeting on 8 March 2025 in Seattle and thank you for your email of 13 March requesting clarification on the ICANN ccTLD Retirement Policy (the Policy).

For the avoidance of doubt, we would not characterise our meeting as a ‘discussion’. Rather, we listened to your concerns and took away your questions for discussion at the Council. Your email of 13 March puts in writing what you are asking and this letter responds to that.

Before we deal with the specific questions raised, it is important to stress:

a. The Policy is relevant only where a 2-letter code has been delegated in the root zone. The clarification of the standing or otherwise of any parts of ISO 3166-1 in the Policy or in this letter should not be considered in respect to policy matters relating to delegations, transfers, or revocations of ccTLDs; and

b. Although the Policy was developed by the ccNSO it has been adopted and implemented by ICANN and is therefore an ICANN policy not a ccNSO policy.

In your email you state that the language in the Policy suggests that a triggering event occurs when:

(i) An ascii entry identified as a ccTLD in the Root Zone database

(ii) That corresponds to any ISO 3166-1 Alpha 2 Code Element

(iii) Is deleted from the ISO 3166-1 standard by the ISO 3166-1 Maintenance Agency.

We believe that this is the correct understanding of a triggering event.

You go on to request clarification of the meaning of Alpha-2 Code Elements. It is not the role of the ccNSO to interpret the meaning of terms within ISO 3166-1. That said, when developing the policy, although the ccNSO did consider all of the various categories of code elements it took the view that the policy applied to those code elements that are defined in the fourth edition of the International Standard ISO3166, part 1, i.e. on the *list of country names *or as an *exceptionally reserved code element*, and crafted the policy on that basis.

Accordingly, it is our view that the Policy is relevant only in circumstances where, as a result of action taken by the ISO, a delegated 2-letter code is no longer on the list of country names or an exceptionally reserved code element.

If you have any further questions regarding this letter, please do not hesitate to reach out.

Best regards,

Alejandra Reynoso

ccNSO Council Chair

_______________________________________________ Ccnso-council mailing list -- ccnso-council@icann.org To unsubscribe send an email to ccnso-council-leave@icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

I support. Jen Obtener Outlook para iOS<https://aka.ms/o0ukef> ________________________________ De: Bart Boswinkel via Ccnso-council <ccnso-council@icann.org> Enviado: miércoles, abril 2, 2025 7:21 a. m. Para: ccnso-council@icann.org <ccnso-council@icann.org> Asunto: [ccnso-council] Draft Response clarification ccTLD retirement policy Dear all, Please find included the draft response to Kim Davies to provide clarification on the ccTLD retirement policy. For your reference the original questions are included as well (word document) The draft was compiled by Stephen, Chris, Jordan, Peter and Alejandra. Goal is to approve this letter by email vote by 9 April 2025. If you have any concerns or questions, please reply to the list. If you support, abstain or not support the letter, please use the list as well to let your position know. Kind regards, Bart ------------ ​​XX April 2025 Dear Kim, We refer to our meeting on 8 March 2025 in Seattle and thank you for your email of 13 March requesting clarification on the ICANN ccTLD Retirement Policy (the Policy). For the avoidance of doubt, we would not characterise our meeting as a ‘discussion’. Rather, we listened to your concerns and took away your questions for discussion at the Council. Your email of 13 March puts in writing what you are asking and this letter responds to that. Before we deal with the specific questions raised, it is important to stress: a. The Policy is relevant only where a 2-letter code has been delegated in the root zone. The clarification of the standing or otherwise of any parts of ISO 3166-1 in the Policy or in this letter should not be considered in respect to policy matters relating to delegations, transfers, or revocations of ccTLDs; and b. Although the Policy was developed by the ccNSO it has been adopted and implemented by ICANN and is therefore an ICANN policy not a ccNSO policy. In your email you state that the language in the Policy suggests that a triggering event occurs when: (i) An ascii entry identified as a ccTLD in the Root Zone database (ii) That corresponds to any ISO 3166-1 Alpha 2 Code Element (iii) Is deleted from the ISO 3166-1 standard by the ISO 3166-1 Maintenance Agency. We believe that this is the correct understanding of a triggering event. You go on to request clarification of the meaning of Alpha-2 Code Elements. It is not the role of the ccNSO to interpret the meaning of terms within ISO 3166-1. That said, when developing the policy, although the ccNSO did consider all of the various categories of code elements it took the view that the policy applied to those code elements that are defined in the fourth edition of the International Standard ISO3166, part 1, i.e. on the list of country names or as an exceptionally reserved code element, and crafted the policy on that basis. Accordingly, it is our view that the Policy is relevant only in circumstances where, as a result of action taken by the ISO, a delegated 2-letter code is no longer on the list of country names or an exceptionally reserved code element. If you have any further questions regarding this letter, please do not hesitate to reach out. Best regards, Alejandra Reynoso ccNSO Council Chair ***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.************** ***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.**************

Fully support Jaijit Dr. Jaijit Bhattacharya President Centre for Digital Economy Policy M: +91 9818213076 W: http://www.c-dep.org/ The content of this message is confidential. If you have received it by mistake, please inform us by an email reply and then delete the message. It is forbidden to copy, forward, or in any way reveal the contents of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet. Therefore, the sender will not be held liable for any damage caused by the message. ---- On Wed, 02 Apr 2025 17:50:55 +0530 Bart Boswinkel via Ccnso-council <ccnso-council@icann.org> wrote --- Dear all, Please find included the draft response to Kim Davies to provide clarification on the ccTLD retirement policy. For your reference the original questions are included as well (word document) The draft was compiled by Stephen, Chris, Jordan, Peter and Alejandra.   Goal is to approve this letter by email vote by 9 April 2025.   If you have any concerns or questions, please reply to the list. If you support, abstain or not support the letter, please use the list as well to let your position know. Kind regards, Bart   ------------   ​​XX April 2025 Dear Kim,   We refer to our meeting on 8 March 2025 in Seattle and thank you for your email of 13 March requesting clarification on the ICANN ccTLD Retirement Policy (the Policy).    For the avoidance of doubt, we would not characterise our meeting as a ‘discussion’. Rather, we listened to your concerns and took away your questions for discussion at the Council. Your email of 13 March puts in writing what you are asking and this letter responds to that.   Before we deal with the specific questions raised, it is important to stress: a.                   The Policy is relevant only where a 2-letter code has been delegated in the root zone. The clarification  of the standing or otherwise of any parts of ISO 3166-1 in the Policy or in this letter should not be considered in respect to policy matters relating to  delegations, transfers, or revocations of  ccTLDs; and b.                   Although the Policy was developed by the ccNSO it has been adopted and implemented by ICANN and is therefore an ICANN policy not a ccNSO policy.    In your email you state that the language in the Policy suggests that a triggering event occurs when: (i) An ascii entry identified as a ccTLD in the Root Zone database (ii) That corresponds to any ISO 3166-1 Alpha 2 Code Element (iii) Is deleted from the ISO 3166-1 standard by the ISO 3166-1 Maintenance Agency.   We believe that this is the correct understanding of a triggering event.   You go on to request clarification of the meaning of Alpha-2 Code Elements. It is not the role of the ccNSO to interpret the meaning of terms within ISO 3166-1. That said, when developing the policy, although the ccNSO did consider all of the various categories of code elements it took the view that the policy applied to those code elements that are defined in the fourth edition of the  International Standard ISO3166, part 1, i.e. on the list of country names or as an exceptionally reserved code element, and crafted the policy on that basis.    Accordingly, it is our view that the Policy is relevant only in circumstances where, as a result of action taken by the ISO, a delegated 2-letter code is no longer on the list of country names or an exceptionally reserved code element.    If you have any further questions regarding this letter, please do not hesitate to reach out.   Best regards,   Alejandra Reynoso ccNSO Council Chair       _______________________________________________ Ccnso-council mailing list -- ccnso-council@icann.org To unsubscribe send an email to ccnso-council-leave@icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.