Resolution to Launch ccPDP 4
Dear all, Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager. Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic. If you have any questions or comments, please send them to the list. Kind regards, Bart ------------------------------------- Draft Resolution Background In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors. The recommended policy ccPDP2 contains two parts: · Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures. · Proposals to enable the inclusion of IDN ccTLD in the ccNSO. By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1]. In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings. In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach. Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team. Decisions 1. In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics: a. Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. b. Whether or not to convene a Taskforce or use other method to address these issues. In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line). 2. In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents: - RFC 1591 (https://www.ietf.org/rfc/rfc1591.txt ) - ISO 3166 standard (http://www.iso.org/iso/country_codes) - The ccNSO Framework of Interpretation working group Final Report, (http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf ) - The Fast Track Implementation Plan and related documents, latest version. - The draft policy for the selection IDN ccTLD strings ( September 2013) - The Final Report of the IDN policy preliminary review team ( June 2019) - The Board resolution on IDN (cc)TLD Variants (14 March 2019) (https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a) requesting the ccNSO to work on Variant Management - and any other matters and documents that the Issue Manager considers to be of relevance. 3. The ccNSO Council expects the Issue Report by its February 2020 meeting. 4. In accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager. 5. The secretariat is requested is publish this resolution as soon as possible. [1] See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4.
Agreement from me! From: Ccnso-council <ccnso-council-bounces@icann.org> On Behalf Of Bart Boswinkel Sent: Friday, December 20, 2019 12:49 PM To: ccNSO-Council@icann.org Subject: [ccnso-council] Resolution to Launch ccPDP 4 Dear all, Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager. Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic. If you have any questions or comments, please send them to the list. Kind regards, Bart ------------------------------------- Draft Resolution Background In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors. The recommended policy ccPDP2 contains two parts: · Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures. · Proposals to enable the inclusion of IDN ccTLD in the ccNSO. By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1]. In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings. In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach. Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team. Decisions 1. In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics: a. Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. b. Whether or not to convene a Taskforce or use other method to address these issues. In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line). 2. In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents: - RFC 1591 (https://www.ietf.org/rfc/rfc1591.txt ) - ISO 3166 standard (http://www.iso.org/iso/country_codes) - The ccNSO Framework of Interpretation working group Final Report, (http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf ) - The Fast Track Implementation Plan and related documents, latest version. - The draft policy for the selection IDN ccTLD strings ( September 2013) - The Final Report of the IDN policy preliminary review team ( June 2019) - The Board resolution on IDN (cc)TLD Variants (14 March 2019) (https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a) requesting the ccNSO to work on Variant Management - and any other matters and documents that the Issue Manager considers to be of relevance. 3. The ccNSO Council expects the Issue Report by its February 2020 meeting. 4. In accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager. 5. The secretariat is requested is publish this resolution as soon as possible. ________________________________ ________________________________ [1] See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4.
Hi Bart, I agree too. I believe the text should read 15 Jan 2020. Best, Giovanni [cid:image002.jpg@01D5B743.FDC585D0]<http://www.eurid.eu/>Giovanni Seppia / External Relations Manager EURid vzw Telecomlaan 9, 1831 Diegem, Belgium T: +32 2 401 27 50 | M: +39 335 8141733 www.eurid.eu<http://www.eurid.eu/> RPR Brussel – VAT BE 0864.240.405 [cid:image003.jpg@01D4F6BF.C28BB830]<https://twitter.com/EUregistry> [cid:image004.jpg@01D4F6BF.C28BB830] <https://www.linkedin.com/company/eurid/> [cid:image005.jpg@01D4F6BF.C28BB830] <https://www.facebook.com/EUregistry> From: Ccnso-council <ccnso-council-bounces@icann.org> On Behalf Of Nick Wenban-Smith Sent: 20 December 2019 14:09 To: Bart Boswinkel <bart.boswinkel@icann.org>; ccNSO-Council@icann.org Subject: Re: [ccnso-council] Resolution to Launch ccPDP 4 Agreement from me! From: Ccnso-council <ccnso-council-bounces@icann.org<mailto:ccnso-council-bounces@icann.org>> On Behalf Of Bart Boswinkel Sent: Friday, December 20, 2019 12:49 PM To: ccNSO-Council@icann.org<mailto:ccNSO-Council@icann.org> Subject: [ccnso-council] Resolution to Launch ccPDP 4 Dear all, Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager. Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic. If you have any questions or comments, please send them to the list. Kind regards, Bart ------------------------------------- Draft Resolution Background In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors. The recommended policy ccPDP2 contains two parts: · Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures. · Proposals to enable the inclusion of IDN ccTLD in the ccNSO. By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1]. In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings. In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach. Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team. Decisions 1. In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics: a. Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. b. Whether or not to convene a Taskforce or use other method to address these issues. In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line). 2. In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents: - RFC 1591 (https://www.ietf.org/rfc/rfc1591.txt ) - ISO 3166 standard (http://www.iso.org/iso/country_codes) - The ccNSO Framework of Interpretation working group Final Report, (http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf ) - The Fast Track Implementation Plan and related documents, latest version. - The draft policy for the selection IDN ccTLD strings ( September 2013) - The Final Report of the IDN policy preliminary review team ( June 2019) - The Board resolution on IDN (cc)TLD Variants (14 March 2019) (https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a) requesting the ccNSO to work on Variant Management - and any other matters and documents that the Issue Manager considers to be of relevance. 3. The ccNSO Council expects the Issue Report by its February 2020 meeting. 4. In accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager. 5. The secretariat is requested is publish this resolution as soon as possible. ________________________________ ________________________________ ________________________________ [1] See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4. Disclaimer: This email and any attachment hereto is intended solely for the person to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient or if you have received this email in error, please delete it and immediately contact the sender by telephone or email, and destroy any copies of this information. You should not use or copy it, nor disclose its content to any other person or rely upon this information. Please note that any views presented in the email and any attachment hereto are solely those of the author and do not necessarily represent those of EURid. Any processing of personal data via email is done in accordance with our Privacy Policy. While all care has been taken to avoid any known viruses, the recipient is advised to check this email and any attachment for presence of viruses. http://www.eurid.eu/en/legal-disclaimer https://eurid.eu/en/other-infomation/privacy-policy
+1 Best, Laura El El vie, 20 de dic. de 2019 a la(s) 15:45, Giovanni Seppia < Giovanni.Seppia@eurid.eu> escribió:
Hi Bart,
I agree too.
I believe the text should read 15 Jan 2020.
Best,
Giovanni
<http://www.eurid.eu/>*Giovanni Seppia* */ External Relations Manager*
*EURid vzw*
Telecomlaan 9 <https://www.google.com/maps/search/Telecomlaan+9?entry=gmail&source=g>, 1831 Diegem, Belgium
T: +32 2 401 27 50 | M: +39 335 8141733
www.eurid.eu
RPR Brussel – VAT BE 0864.240.405
[image: cid:image003.jpg@01D4F6BF.C28BB830] <https://twitter.com/EUregistry> [image: cid:image004.jpg@01D4F6BF.C28BB830] <https://www.linkedin.com/company/eurid/> [image: cid:image005.jpg@01D4F6BF.C28BB830] <https://www.facebook.com/EUregistry>
*From:* Ccnso-council <ccnso-council-bounces@icann.org> *On Behalf Of *Nick Wenban-Smith *Sent:* 20 December 2019 14:09 *To:* Bart Boswinkel <bart.boswinkel@icann.org>; ccNSO-Council@icann.org *Subject:* Re: [ccnso-council] Resolution to Launch ccPDP 4
Agreement from me!
*From:* Ccnso-council <ccnso-council-bounces@icann.org> *On Behalf Of *Bart Boswinkel *Sent:* Friday, December 20, 2019 12:49 PM *To:* ccNSO-Council@icann.org *Subject:* [ccnso-council] Resolution to Launch ccPDP 4
Dear all,
Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager.
Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic.
If you have any questions or comments, please send them to the list.
Kind regards,
Bart
-------------------------------------
*Draft Resolution*
*Background*
In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors.
The recommended policy ccPDP2 contains two parts:
· Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures.
· Proposals to enable the inclusion of IDN ccTLD in the ccNSO.
By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1] <#m_8079772561741537980__ftn1>.
In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any
The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings.
In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach.
Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team.
*Decisions*
*1. **In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics:*
*a. **Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. *
*b. **Whether or not to convene a Taskforce or use other method to address these issues. *
*In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line).*
*2. **In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents:*
- *RFC 1591 (**https://www.ietf.org/rfc/rfc1591.txt* <https://www.ietf.org/rfc/rfc1591.txt>* )*
- *ISO 3166 standard (**http://www.iso.org/iso/country_codes)* <http://www.iso.org/iso/country_codes)>
- *The ccNSO Framework of Interpretation working group Final Report, (**http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf* <http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf>* )*
- *The Fast Track Implementation Plan and related documents, latest version.*
- *The draft policy for the selection IDN ccTLD strings ( September 2013)*
- *The Final Report of the IDN policy preliminary review team ( June 2019)*
- *The Board resolution on IDN (cc)TLD Variants (14 March 2019) (* *https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a... <https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a>*) requesting the ccNSO to work on Variant Management *
- *and any other matters and documents that the Issue Manager considers to be of relevance.*
*3. **The ccNSO Council expects the Issue Report by its February 2020 meeting. *
*4. **In accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager.*
5. *The secretariat is requested is publish this resolution as soon as possible. *
------------------------------
------------------------------
------------------------------
[1] <#m_8079772561741537980__ftnref1> See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4.
*Disclaimer:*
* This email and any attachment hereto is intended solely for the person to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient or if you have received this email in error, please delete it and immediately contact the sender by telephone or email, and destroy any copies of this information. You should not use or copy it, nor disclose its content to any other person or rely upon this information. Please note that any views presented in the email and any attachment hereto are solely those of the author and do not necessarily represent those of EURid. Any processing of personal data via email is done in accordance with our Privacy Policy <https://eurid.eu/en/other-infomation/privacy-policy>. While all care has been taken to avoid any known viruses, the recipient is advised to check this email and any attachment for presence of viruses.*
Other languages: English <http://www.eurid.eu/en/legal-disclaimer> Estonian <http://www.eurid.eu/et/legal-disclaimer> Italian <http://www.eurid.eu/it/legal-disclaimer> Maltese <http://www.eurid.eu/mt/legal-disclaimer> Romanian <http://www.eurid.eu/ro/legal-disclaimer> Swedish <http://www.eurid.eu/sv/legal-disclaimer> Czech <http://www.eurid.eu/cs/legal-disclaimer> Spanish <http://www.eurid.eu/es/legal-disclaimer> Latvian <http://www.eurid.eu/lv/legal-disclaimer> Dutch <http://www.eurid.eu/nl/legal-disclaimer> Slovak <http://www.eurid.eu/sk/legal-disclaimer> Greek <http://www.eurid.eu/el/legal-disclaimer> Danish <http://www.eurid.eu/da/legal-disclaimer> French <http://www.eurid.eu/fr/legal-disclaimer> Lithuanian <http://www.eurid.eu/lt/legal-disclaimer> Polish <http://www.eurid.eu/pl/legal-disclaimer> Slovenian <http://www.eurid.eu/sl/legal-disclaimer> Bulgarian <http://www.eurid.eu/bg/legal-disclaimer> German <http://www.eurid.eu/de/legal-disclaimer> Gaelic <http://www.eurid.eu/ga/legal-disclaimer> Hungarian <http://www.eurid.eu/hu/legal-disclaimer> Portuguese <http://www.eurid.eu/pt/legal-disclaimer> Finnish <http://www.eurid.eu/fi/legal-disclaimer> Croatian <http://www.eurid.eu/hr/legal-disclaimer> _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ 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 agree to the launch of ccPDP4 Hiro On Fri, 20 Dec 2019 12:48:38 +0000 Bart Boswinkel <bart.boswinkel@icann.org> wrote:
Dear all,
Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are ?against. In accordance with Annex B of the Bylaws to ?launch the ccPDP it is required you request an ?Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue? Manager.
Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic.
If you have any questions or comments, please send them to the list.
Kind regards,
Bart
-------------------------------------
Draft Resolution
Background
In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors.
The recommended policy ccPDP2 contains two parts:
・ Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures.
・ Proposals to enable the inclusion of IDN ccTLD in the ccNSO.
By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1].
In March 2019 the ccNSO Council tasked a team? (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any
The? PRT advised Council to launch a ccNSO? Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings.
In order to implement the adopted PRT recommendations the ccNSO Council requested? the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach.
Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team.
Decisions
1. In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics:
a. Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs.
b. Whether or not to convene a Taskforce or use other method to address these issues.?
In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line).
2. In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents:
- RFC 1591 (https://www.ietf.org/rfc/rfc1591.txt )
- ISO 3166 standard (http://www.iso.org/iso/country_codes)
- The ccNSO Framework of Interpretation working group Final Report, (http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf )
- The Fast Track Implementation Plan and related documents, latest version.
- The draft policy for the selection IDN ccTLD strings ( September 2013)
- The Final Report of the IDN policy preliminary review team ( June 2019)
- The Board resolution on IDN (cc)TLD Variants (14 March 2019) (https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a) requesting the ccNSO to work on Variant Management
- and any other matters and documents that the Issue Manager considers to be of relevance.
3. The ccNSO Council expects the Issue Report by its February 2020 meeting.
?
4. In accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support ? ccNSO relations, as Issue Manager.
5. The secretariat is requested is publish this resolution as soon as possible.
[1] See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4.
Bart and all, I agree with the launch of ccPDP4. regards, This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. On Fri, Dec 20, 2019 at 8:48 AM Bart Boswinkel <bart.boswinkel@icann.org> wrote:
Dear all,
Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager.
Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic.
If you have any questions or comments, please send them to the list.
Kind regards,
Bart
-------------------------------------
*Draft Resolution*
*Background*
In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors.
The recommended policy ccPDP2 contains two parts:
· Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures.
· Proposals to enable the inclusion of IDN ccTLD in the ccNSO.
By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1] <#m_5276439999796414099__ftn1>.
In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any
The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings.
In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach.
Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team.
*Decisions*
*1. **In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics:*
*a. **Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. *
*b. **Whether or not to convene a Taskforce or use other method to address these issues. *
*In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line).*
*2. **In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents:*
- *RFC 1591 (**https://www.ietf.org/rfc/rfc1591.txt* <https://www.ietf.org/rfc/rfc1591.txt>* )*
- *ISO 3166 standard (**http://www.iso.org/iso/country_codes)* <http://www.iso.org/iso/country_codes)>
- *The ccNSO Framework of Interpretation working group Final Report, (**http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf* <http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf>* )*
- *The Fast Track Implementation Plan and related documents, latest version.*
- *The draft policy for the selection IDN ccTLD strings ( September 2013)*
- *The Final Report of the IDN policy preliminary review team ( June 2019)*
- *The Board resolution on IDN (cc)TLD Variants (14 March 2019) (* *https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a... <https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a>*) requesting the ccNSO to work on Variant Management *
- *and any other matters and documents that the Issue Manager considers to be of relevance.*
*3. **The ccNSO Council expects the Issue Report by its February 2020 meeting. *
*4. **I**n accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager.*
5. *The secretariat is requested is publish this resolution as soon as possible. *
------------------------------
[1] <#m_5276439999796414099__ftnref1> See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ 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.
Dear Bart I agree to the launch of ccPDP4. Best, Alejandra -- [image: Photograph] *Alejandra Reynoso*Investigación & Desarrollo | Dominios .gt *P:* +502 23688565 *E:* alejandra.reynoso@cctld.gt 18 Ave. 11-42 Zona 15, V.H. III. Guatemala, Guatemala www.gt On Fri, Dec 20, 2019 at 6:48 AM Bart Boswinkel <bart.boswinkel@icann.org> wrote:
Dear all,
Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager.
Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic.
If you have any questions or comments, please send them to the list.
Kind regards,
Bart
-------------------------------------
*Draft Resolution*
*Background*
In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors.
The recommended policy ccPDP2 contains two parts:
· Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures.
· Proposals to enable the inclusion of IDN ccTLD in the ccNSO.
By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1] <#m_1383777216514760478__ftn1>.
In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any
The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings.
In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach.
Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team.
*Decisions*
*1. **In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics:*
*a. **Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. *
*b. **Whether or not to convene a Taskforce or use other method to address these issues. *
*In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line).*
*2. **In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents:*
- *RFC 1591 (**https://www.ietf.org/rfc/rfc1591.txt* <https://www.ietf.org/rfc/rfc1591.txt>* )*
- *ISO 3166 standard (**http://www.iso.org/iso/country_codes)* <http://www.iso.org/iso/country_codes)>
- *The ccNSO Framework of Interpretation working group Final Report, (**http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf* <http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf>* )*
- *The Fast Track Implementation Plan and related documents, latest version.*
- *The draft policy for the selection IDN ccTLD strings ( September 2013)*
- *The Final Report of the IDN policy preliminary review team ( June 2019)*
- *The Board resolution on IDN (cc)TLD Variants (14 March 2019) (* *https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a... <https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a>*) requesting the ccNSO to work on Variant Management *
- *and any other matters and documents that the Issue Manager considers to be of relevance.*
*3. **The ccNSO Council expects the Issue Report by its February 2020 meeting. *
*4. **I**n accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager.*
5. *The secretariat is requested is publish this resolution as soon as possible. *
------------------------------
[1] <#m_1383777216514760478__ftnref1> See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ 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.
Dear Bart, I agree to the launch of ccPDP4. Thank you Kind regards ABDALLA OMARI On Fri, Dec 20, 2019 at 3:48 PM Bart Boswinkel <bart.boswinkel@icann.org> wrote:
Dear all,
Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager.
Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic.
If you have any questions or comments, please send them to the list.
Kind regards,
Bart
-------------------------------------
*Draft Resolution*
*Background*
In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors.
The recommended policy ccPDP2 contains two parts:
· Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures.
· Proposals to enable the inclusion of IDN ccTLD in the ccNSO.
By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1] <#m_-5648018649614945793__ftn1>.
In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any
The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings.
In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach.
Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team.
*Decisions*
*1. **In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics:*
*a. **Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. *
*b. **Whether or not to convene a Taskforce or use other method to address these issues. *
*In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line).*
*2. **In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents:*
- *RFC 1591 (**https://www.ietf.org/rfc/rfc1591.txt* <https://www.ietf.org/rfc/rfc1591.txt>* )*
- *ISO 3166 standard (**http://www.iso.org/iso/country_codes)* <http://www.iso.org/iso/country_codes)>
- *The ccNSO Framework of Interpretation working group Final Report, (**http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf* <http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf>* )*
- *The Fast Track Implementation Plan and related documents, latest version.*
- *The draft policy for the selection IDN ccTLD strings ( September 2013)*
- *The Final Report of the IDN policy preliminary review team ( June 2019)*
- *The Board resolution on IDN (cc)TLD Variants (14 March 2019) (* *https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a... <https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a>*) requesting the ccNSO to work on Variant Management *
- *and any other matters and documents that the Issue Manager considers to be of relevance.*
*3. **The ccNSO Council expects the Issue Report by its February 2020 meeting. *
*4. **I**n accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager.*
5. *The secretariat is requested is publish this resolution as soon as possible. *
------------------------------
[1] <#m_-5648018649614945793__ftnref1> See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ 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 also agree with this PDP. best demi On 13/01/2020 05:30, Abdalla Omari wrote:
Dear Bart,
I agree to the launch of ccPDP4.
Thank you
Kind regards ABDALLA OMARI
On Fri, Dec 20, 2019 at 3:48 PM Bart Boswinkel <bart.boswinkel@icann.org <mailto:bart.boswinkel@icann.org>> wrote:
Dear all,
Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager.
Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic.
If you have any questions or comments, please send them to the list.
Kind regards,
Bart
-------------------------------------
*Draft Resolution*
*/Background/*
In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Reportin September 2013 to the ICANN Board of Directors.
The recommended policy ccPDP2 contains two parts:
·Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures.
·Proposals to enable the inclusion of IDN ccTLD in the ccNSO.
By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1] <#m_-5648018649614945793__ftn1>.
In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any
The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings.
In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach.
Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team.
*/Decisions/*
*1.**In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics:*
*a.**Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. *
*b.**Whether or not to convene a Taskforce or use other method to address these issues. *
*In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line).*
**
*2.**In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents:*
-*RFC 1591 (**https://www.ietf.org/rfc/rfc1591.txt**)*
-*ISO 3166 standard (**http://www.iso.org/iso/country_codes)***
-*The ccNSO Framework of Interpretation working group Final Report, (**http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf**)*
-*The Fast Track Implementation Plan and related documents, latest version.*
-*The draft policy for the selection IDN ccTLD strings ( September 2013)*
-*The Final Report of the IDN policy preliminary review team ( June 2019)*
-*The Board resolution on IDN (cc)TLD Variants (14 March 2019) (**https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a...) requesting the ccNSO to work on Variant Management *
-*and any other matters and documents that the Issue Manager considers to be of relevance.*
**
*3.**The ccNSO Council expects the Issue Report by its February 2020 meeting. *
**
*4.**I**n accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager.*
**
5.*The secretariat is requested is publish this resolution as soon as possible. *
------------------------------------------------------------------------
[1] <#m_-5648018649614945793__ftnref1> See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org <mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ 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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ 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.
Dear Bart i agree to the launch of ccPDP4 Best Regard Le ven. 20 déc. 2019 à 12:48, Bart Boswinkel <bart.boswinkel@icann.org> a écrit :
Dear all,
Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager.
Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic.
If you have any questions or comments, please send them to the list.
Kind regards,
Bart
-------------------------------------
*Draft Resolution*
*Background*
In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors.
The recommended policy ccPDP2 contains two parts:
· Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures.
· Proposals to enable the inclusion of IDN ccTLD in the ccNSO.
By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1] <#m_6996654875243603171__ftn1>.
In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any
The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings.
In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach.
Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team.
*Decisions*
*1. **In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics:*
*a. **Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. *
*b. **Whether or not to convene a Taskforce or use other method to address these issues. *
*In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line).*
*2. **In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents:*
- *RFC 1591 (**https://www.ietf.org/rfc/rfc1591.txt* <https://www.ietf.org/rfc/rfc1591.txt>* )*
- *ISO 3166 standard (**http://www.iso.org/iso/country_codes)* <http://www.iso.org/iso/country_codes)>
- *The ccNSO Framework of Interpretation working group Final Report, (**http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf* <http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf>* )*
- *The Fast Track Implementation Plan and related documents, latest version.*
- *The draft policy for the selection IDN ccTLD strings ( September 2013)*
- *The Final Report of the IDN policy preliminary review team ( June 2019)*
- *The Board resolution on IDN (cc)TLD Variants (14 March 2019) (* *https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a... <https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a>*) requesting the ccNSO to work on Variant Management *
- *and any other matters and documents that the Issue Manager considers to be of relevance.*
*3. **The ccNSO Council expects the Issue Report by its February 2020 meeting. *
*4. **I**n accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager.*
5. *The secretariat is requested is publish this resolution as soon as possible. *
------------------------------
[1] <#m_6996654875243603171__ftnref1> See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ 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.
Dear Bart, I agree to the launch of ccPDP4. Best regards, Marie-Noémie De : Ccnso-council [mailto:ccnso-council-bounces@icann.org] De la part de Bart Boswinkel Envoyé : vendredi 20 décembre 2019 13:49 À : ccNSO-Council@icann.org Objet : [ccnso-council] Resolution to Launch ccPDP 4 Dear all, Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager. Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic. If you have any questions or comments, please send them to the list. Kind regards, Bart ------------------------------------- Draft Resolution Background In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors. The recommended policy ccPDP2 contains two parts: • Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures. • Proposals to enable the inclusion of IDN ccTLD in the ccNSO. By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1]. In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings. In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach. Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team. Decisions 1. In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics: a. Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. b. Whether or not to convene a Taskforce or use other method to address these issues. In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line). 2. In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents: - RFC 1591 (https://www.ietf.org/rfc/rfc1591.txt ) - ISO 3166 standard (http://www.iso.org/iso/country_codes) - The ccNSO Framework of Interpretation working group Final Report, (http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf ) - The Fast Track Implementation Plan and related documents, latest version. - The draft policy for the selection IDN ccTLD strings ( September 2013) - The Final Report of the IDN policy preliminary review team ( June 2019) - The Board resolution on IDN (cc)TLD Variants (14 March 2019) (https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a) requesting the ccNSO to work on Variant Management - and any other matters and documents that the Issue Manager considers to be of relevance. 3. The ccNSO Council expects the Issue Report by its February 2020 meeting. 4. In accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager. 5. The secretariat is requested is publish this resolution as soon as possible. ________________________________ ________________________________ [1] See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28..., general introduction page 4. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
participants (11)
-
Abdalla Omari -
Alejandra Reynoso -
Bart Boswinkel -
Demi Getschko -
Giovanni Seppia -
HiroHOTTA -
Laura Margolis -
marienoemie.marques@orange.com -
Nick Wenban-Smith -
Pablo Rodriguez -
Souleymane Oumtanaga