lists.icann.org
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

comments-bylaws-amend-iana-naming-function-10jun19

Download
Threads by month
  • ----- 2026 -----
  • May
  • April
  • March
  • February
  • January
  • ----- 2025 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2020 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2019 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
comments-bylaws-amend-iana-naming-function-10jun19@icann.org

  • 7 discussions
[Comments-bylaws-amend-iana-naming-function-10jun19] Ratified: ALAC Statement on Fundamental Bylaws Amendment Proposal – IANA Naming Function Review
by ICANN At-Large Staff July 31, 2019

July 31, 2019
Dear All, Please find attached the ALAC statement regarding Fundamental Bylaws Amendment Proposal – IANA Naming Function Review<https://community.icann.org/x/mpajBg>. Content of the statement remains unchanged. Ratification information is included on the cover page. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>
1 0
0 0
[Comments-bylaws-amend-iana-naming-function-10jun19] NCSG Comments
by Rafik Dammak July 28, 2019

July 28, 2019
Hi. please find NCSG Comment attached. Best Regards, Rafik
1 0
0 0
[Comments-bylaws-amend-iana-naming-function-10jun19] Pending Ratification: ALAC Statement on Fundamental Bylaws Amendment Proposal – IANA Naming Function Review
by ICANN At-Large Staff July 26, 2019

July 26, 2019
Dear All, Please find attached the ALAC statement regarding Fundamental Bylaws Amendment Proposal – IANA Naming Function Review<https://community.icann.org/x/mpajBg>. In the interest of time, the ALAC Chair requested that the statement be transmitted to the ICANN public comment process with a note that the statement is pending ALAC ratification. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>
1 0
0 0
[Comments-bylaws-amend-iana-naming-function-10jun19] RySG Comments on the Fundamental Bylaws Amendment Proposal – IANA Naming Function Review
by Demetriou, Samantha July 26, 2019

July 26, 2019
Hello, On behalf of the gTLD Registries Stakeholder Group (RySG), please find attached our comments on the Fundamental Bylaws Amendment Proposal – IANA Naming Function Review. In the interest of time, we did not conduct a vote on these comments. We did discuss them on our mailing list and during a biweekly conference call, and no member opposed their submission. Please feel free to contact me with any questions or concerns. Best, Samantha Demetriou RySG Vice Chair, Policy
1 0
0 0
[Comments-bylaws-amend-iana-naming-function-10jun19] Business Constituency (BC) support for Fundamental Bylaws Amendment – IANA Naming Function Review
by Steve DelBianco July 26, 2019

July 26, 2019
The ICANN Business Constituency (BC) supports the proposed Fundamental Bylaws Amendment – IANA Naming Function Review. This regards the public comment page at https://www.icann.org/public-comments/bylaws-amend-iana-naming-function-201… -- Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency (BC)
1 0
0 0
[Comments-bylaws-amend-iana-naming-function-10jun19] ccNSO Council Statement: Fundamental Bylaws Amendment Proposal
by Katrina Sataki July 19, 2019

July 19, 2019
ccNSO Council Statement: Fundamental Bylaws Amendment Proposal - IANA Naming Function Review Date: 19 July 2019 The ccNSO Council respectfully urges the amendment of the ICANN Bylaws as proposed. Experience has shown again and again that the pool of experienced and skilled candidates for IANA Naming Function review is very limited. With the declining number of non-ccNSO members and the limited interest of non-ccNSO member ccTLDs in ICANN (related) affairs, it has proved difficult to find a non-ccNSO member representative to the IFR team. Furthermore, when evaluating applications, the ccNSO and ccNSO Council have always strived to select the best professionals regardless of their membership status in the ccNSO. For example, the ccNSO appointed co-chair of the CCWG-Stewardship was a representative of a non-ccNSO member at the time. The ccNSO Council believes that when it comes to appoint candidates to IFR team and/or any other important tasks/committees/working groups, applicants from ccTLDs should be treated equally and be assessed on the basis of their professional qualifications and not of their membership status in the ccNSO. On behalf of the ccNSO Council, Katrina Sataki Chair
1 0
0 0
[Comments-bylaws-amend-iana-naming-function-10jun19] IANA Naming Function Review Team by laws amendment
by Nick Wenban-Smith June 17, 2019

June 17, 2019
I would like to write in support amending the ICANN by laws here, as requested by the ccNSO Council (for full disclosure I do sit on the Council). There are now very few active ccTLDs who are not members of the ccNSO; and those that are not members of the ccNSO are necessarily either not very engaged in ICANN or who for constitutional or other reasons have taken a deliberate decision not to participate. Hence the requirement that a non ccNSO member be part of the IANA Naming Function Review team is now frustrating the whole review process, despite the intent of that provision presumably being that the review team would be inclusive and representative of all ccTLDs globally. Personally I would not be too prescriptive about the process the Council needs to follow in appointing the individuals to the review team in the by laws themselves. I wouldn't want to get into legal arguments about whether the process was 'inclusive' for example, as those sorts of words are inherently fairly subjective and mean different things to different people. I trust that the Council in making the appointments would follow due process and appoint appropriately without any formal requirement to do so. Best wishes Nick Nick Wenban-Smith General Counsel and Head of Stakeholder Relations [UK Domain] Website<http://www.nominet.uk/> | Twitter<https://twitter.com/Nominet> | Facebook<https://www.facebook.com/nominet/> DD: +44 (0)1865 332287 E: nick.wenban-smith(a)nominet.uk<mailto:nick.wenban-smith@nominet.uk> Minerva House, Edmund Halley Road, Oxford Science Park, Oxford, OX4 4DQ, United Kingdom Nominet UK. Registered in England and Wales No. 3203859 This message is intended exclusively for the individual(s) to whom it is addressed and may contain information that is privileged, or confidential. If you are not the addressee, you must not read, use or disclose the contents of this e-mail. If you receive this e-mail in error, please advise us immediately and delete the e-mail. Nominet UK has taken every reasonable precaution to ensure that any attachment to this e-mail has been swept for viruses. However, Nominet cannot accept liability for any damage sustained as a result of software viruses and would advise that you carry out your own virus checks before opening any attachment
1 0
0 0

HyperKitty Powered by HyperKitty version 1.3.12.