Dear IRT Members, We are pleased to share the proposed language of the AGB's Reserved Names<https://docs.google.com/document/d/1VW_7yzL_l4hjVkrjmS5nBvy69weflk2739c9OM-Z...> section based on the Board-adopted recommendations in Topic 21 of the Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-repo...>. Additionally, the agenda and a PDF version of the document for Tuesday’s discussion are accessible here<https://community.icann.org/pages/viewpage.action?pageId=244945128>. If you have any questions or concerns, please feel free to reach out. Thank you! Best, Michael
Thanks Michael, Just a note that the list of names which may not be applied for could be augmented depending on the outcome of the Name Collision Analysis Projects and any Recommendations from the SSAC coming out of that which may be adopted by the Board. I can say more about this on the call but at the moment, it's just a "placeholder". The NCAP Study 2 report will likely say something about the Sub Pro Implementation guidance to develop a "DO NOT APPLY" list if possible. We have a F2F meeting in DC next week and I believe this will be one of the topics for finalizing the Study 2 language for publication to the community. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Fri, Sep 22, 2023 at 11:43 AM Michael Karakash < michael.karakash@icann.org> wrote:
Dear IRT Members,
We are pleased to share the proposed language of the AGB's Reserved Names <https://docs.google.com/document/d/1VW_7yzL_l4hjVkrjmS5nBvy69weflk2739c9OM-Z...> section based on the Board-adopted recommendations in Topic 21 of the Final Report <https://gnso.icann.org/sites/default/files/file/field-file-attach/final-repo...> .
Additionally, the agenda and a PDF version of the document for Tuesday’s discussion are accessible here <https://community.icann.org/pages/viewpage.action?pageId=244945128>.
If you have any questions or concerns, please feel free to reach out.
Thank you!
Best,
Michael _______________________________________________ SubPro-IRT mailing list SubPro-IRT@icann.org https://mm.icann.org/mailman/listinfo/subpro-irt
_______________________________________________ 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.
Good evening This does indeed seem sensible as April 2026 is someway ahead, Best Nigel Sent from Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: SubPro-IRT <subpro-irt-bounces@icann.org> on behalf of Anne ICANN <anneicanngnso@gmail.com> Sent: Tuesday, September 26, 2023 8:29:26 PM To: Michael Karakash <michael.karakash@icann.org> Cc: subpro-irt@icann.org <subpro-irt@icann.org> Subject: Re: [SubPro-IRT] Topic 21: Reserved Names Thanks Michael, Just a note that the list of names which may not be applied for could be augmented depending on the outcome of the Name Collision Analysis Projects and any Recommendations from the SSAC coming out of that which may be adopted by the Board. I can say more about this on the call but at the moment, it's just a "placeholder". The NCAP Study 2 report will likely say something about the Sub Pro Implementation guidance to develop a "DO NOT APPLY" list if possible. We have a F2F meeting in DC next week and I believe this will be one of the topics for finalizing the Study 2 language for publication to the community. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Fri, Sep 22, 2023 at 11:43 AM Michael Karakash <michael.karakash@icann.org<mailto:michael.karakash@icann.org>> wrote: Dear IRT Members, We are pleased to share the proposed language of the AGB's Reserved Names<https://docs.google.com/document/d/1VW_7yzL_l4hjVkrjmS5nBvy69weflk2739c9OM-Z...> section based on the Board-adopted recommendations in Topic 21 of the Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-repo...>. Additionally, the agenda and a PDF version of the document for Tuesday’s discussion are accessible here<https://community.icann.org/pages/viewpage.action?pageId=244945128>. If you have any questions or concerns, please feel free to reach out. Thank you! Best, Michael _______________________________________________ SubPro-IRT mailing list SubPro-IRT@icann.org<mailto:SubPro-IRT@icann.org> https://mm.icann.org/mailman/listinfo/subpro-irt _______________________________________________ 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 all , For 1.2.1 3-letter ASCII Combinations : I am still under the impression that the 3-letter ISO3166 code is prohibited, primarily based on GAC Helsinki Communique : *20160630_GAC ICANN 56 Communique_FINAL [1].pdf * *Use of 3-letter codes in the ISO-3166 list as gTLDs in future rounds a. The GAC advises the ICANN Board to: * 1. *encourage the community to continue in depth analyses and discussions on all aspects related to a potential use of 3-letter codes in the ISO-3166 list as gTLDs in future rounds, in particular with regard to whether such a potential use is considered to be in the public interest or not. * 2. *keep current protections in place for 3-letter codes in the ISO-3166 list in place and not to lift these unless future in- depth discussions involving the GAC and the other ICANN constituencies would lead to a consensus that use of these 3-letter codes as TLDs would be in the public interest. * The SubPro WT-5 report should have remained the same position, but please correct me if I am wrong or missing something. Thank you very much ! Best, Ching On Fri, Sep 22, 2023 at 2:43 PM Michael Karakash <michael.karakash@icann.org> wrote:
Dear IRT Members,
We are pleased to share the proposed language of the AGB's Reserved Names <https://t.sidekickopen53.com/Ctc/DL+23284/cFFT304/Jll2-6qcW7Y8-PT6lZ3q7W6ldx...> section based on the Board-adopted recommendations in Topic 21 of the Final Report <https://t.sidekickopen53.com/Ctc/DL+23284/cFFT304/JjT4YGXpW50kH_H6lZ3m6W7LMk...> .
Additionally, the agenda and a PDF version of the document for Tuesday’s discussion are accessible here <https://t.sidekickopen53.com/Ctc/DL+23284/cFFT304/Jl22-6qcW7lCdLW6lZ3lNW8FRg...> .
If you have any questions or concerns, please feel free to reach out.
Thank you!
Best,
Michael _______________________________________________ SubPro-IRT mailing list SubPro-IRT@icann.org https://mm.icann.org/mailman/listinfo/subpro-irt
_______________________________________________ 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.
Hi Ching, Thank you for your email and input. While we are revising the document in this category to provide more clarity on the language based on our discussion during the previous IRT call, we do have a caveat to the “3-letter ASCII Combinations” category in the current draft language. It says: “3-letter ASCII combinations are eligible for delegation unless used by ISO 3166 as ISO 3-letter code.” Therefore, we are in agreement that they are prohibited if found on the ISO 3166 list. Thank you! Best, Michael From: Ching Chiao <ching.chiao@whoisxmlapi.com> Date: Thursday, September 28, 2023 at 11:20 AM To: Michael Karakash <michael.karakash@icann.org> Cc: "subpro-irt@icann.org" <subpro-irt@icann.org> Subject: [Ext] Re: [SubPro-IRT] Topic 21: Reserved Names Dear all , For 1.2.1 3-letter ASCII Combinations : I am still under the impression that the 3-letter ISO3166 code is prohibited, primarily based on GAC Helsinki Communique : 20160630_GAC ICANN 56 Communique_FINAL [1].pdf Use of 3-letter codes in the ISO-3166 list as gTLDs in future rounds a. The GAC advises the ICANN Board to: 1. encourage the community to continue in depth analyses and discussions on all aspects related to a potential use of 3-letter codes in the ISO-3166 list as gTLDs in future rounds, in particular with regard to whether such a potential use is considered to be in the public interest or not. 2. keep current protections in place for 3-letter codes in the ISO-3166 list in place and not to lift these unless future in- depth discussions involving the GAC and the other ICANN constituencies would lead to a consensus that use of these 3-letter codes as TLDs would be in the public interest. The SubPro WT-5 report should have remained the same position, but please correct me if I am wrong or missing something. Thank you very much ! Best, Ching On Fri, Sep 22, 2023 at 2:43 PM Michael Karakash <michael.karakash@icann.org<mailto:michael.karakash@icann.org>> wrote: Dear IRT Members, We are pleased to share the proposed language of the AGB's Reserved Names [t.sidekickopen53.com]<https://urldefense.com/v3/__https:/t.sidekickopen53.com/Ctc/DL*23284/cFFT304...> section based on the Board-adopted recommendations in Topic 21 of the Final Report [t.sidekickopen53.com]<https://urldefense.com/v3/__https:/t.sidekickopen53.com/Ctc/DL*23284/cFFT304...>. Additionally, the agenda and a PDF version of the document for Tuesday’s discussion are accessible here [t.sidekickopen53.com]<https://urldefense.com/v3/__https:/t.sidekickopen53.com/Ctc/DL*23284/cFFT304...>. If you have any questions or concerns, please feel free to reach out. Thank you! Best, Michael _______________________________________________ SubPro-IRT mailing list SubPro-IRT@icann.org<mailto:SubPro-IRT@icann.org> https://mm.icann.org/mailman/listinfo/subpro-irt _______________________________________________ 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.
Thank you Michael for the clarification, and it goes thru my little syntax check at the second look of the sentence. :) Best, Ching On Thu, Sep 28, 2023 at 3:33 PM Michael Karakash <michael.karakash@icann.org> wrote:
Hi Ching,
Thank you for your email and input. While we are revising the document in this category to provide more clarity on the language based on our discussion during the previous IRT call, we do have a caveat to the “3-letter ASCII Combinations” category in the current draft language.
It says: “3-letter ASCII combinations are eligible for delegation *unless used by ISO 3166 as ISO 3-letter code.”* Therefore, we are in agreement that they are prohibited if found on the ISO 3166 list.
Thank you!
Best,
Michael
*From: *Ching Chiao <ching.chiao@whoisxmlapi.com> *Date: *Thursday, September 28, 2023 at 11:20 AM *To: *Michael Karakash <michael.karakash@icann.org> *Cc: *"subpro-irt@icann.org" <subpro-irt@icann.org> *Subject: *[Ext] Re: [SubPro-IRT] Topic 21: Reserved Names
Dear all ,
For 1.2.1 *3-letter ASCII Combinations : *
I am still under the impression that the 3-letter ISO3166 code is prohibited, primarily based on GAC Helsinki Communique :
*20160630_GAC ICANN 56 Communique_FINAL [1].pdf *
*Use of 3-letter codes in the ISO-3166 list as gTLDs in future rounds a. The GAC advises the ICANN Board to: *
1. *encourage the community to continue in depth analyses and discussions on all aspects related to a potential use of 3-letter codes in the ISO-3166 list as gTLDs in future rounds, in particular with regard to whether such a potential use is considered to be in the public interest or not. * 2. *keep current protections in place for 3-letter codes in the ISO-3166 list in place and not to lift these unless future in- depth discussions involving the GAC and the other ICANN constituencies would lead to a consensus that use of these 3-letter codes as TLDs would be in the public interest. *
The SubPro WT-5 report should have remained the same position, but please correct me if I am wrong or missing something.
Thank you very much !
Best,
Ching
On Fri, Sep 22, 2023 at 2:43 PM Michael Karakash < michael.karakash@icann.org> wrote:
Dear IRT Members,
We are pleased to share the proposed language of the AGB's Reserved Names [t.sidekickopen53.com] <https://t.sidekickopen53.com/Ctc/DL+23284/cFFT304/JkMbTjqZW6N38Bs6lZ3nDW7_2D...> section based on the Board-adopted recommendations in Topic 21 of the Final Report [t.sidekickopen53.com] <https://t.sidekickopen53.com/Ctc/DL+23284/cFFT304/JlYbTjqZW95l6Qj6lZ3lRN3hlr...> .
Additionally, the agenda and a PDF version of the document for Tuesday’s discussion are accessible here [t.sidekickopen53.com] <https://t.sidekickopen53.com/Ctc/DL+23284/cFFT304/Jk8bTjqZW5BXHtx6lZ3mfW2mvy...> .
If you have any questions or concerns, please feel free to reach out.
Thank you!
Best,
Michael
_______________________________________________ SubPro-IRT mailing list SubPro-IRT@icann.org https://mm.icann.org/mailman/listinfo/subpro-irt
_______________________________________________ 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.
participants (4)
-
Anne ICANN -
Ching Chiao -
Hickson, Nigel (DSIT) -
Michael Karakash