Change Article 18 and 19 ICANN Bylaws (Fundamental Bylaw change)
Dear all, ICANN org has recently opened a public comment forum pertaining to a change of Article 18 and 19 of the ICANN Bylaws on the IANA Naming Function Review and Special IANA naming Function Review (https://www.icann.org/en/public-comment/proceeding/iana-naming-function-revi... ). Note that both Article 18 and 19 are Fundamental Bylaw changes, therefore the in the end the Decisional Participants need to approve the change. According to the introduction there are four type of changes proposed: 1. The removal of a duplication at Article 18, Section 12(a), as identified by the first IANA Naming Function Review (IFR) Team in its Final Report. 2. Updates to the composition of IFR teams to address composition issues identified by the Registries Stakeholder Group (RySG) in 2019. 3. Clarification of ambiguities on the IFR processes identified through the first IFR after the IANA Stewardship Transition. 4. Updates to the composition of the team exploring an IANA Naming Function Separation Process (Article 19), to conform to composition updates for the IFRs within Article 18. The detailed changes are included in the redline version of the Bylaws ( https://itp.cdn.icann.org/en/files/additional-reviews/proposed-amendments-to...) Given the importance of the IANA Naming Review process for the ccTLD community (Article 18) and the related IANA Naming Function Separation Process ( Article 19) for the ccTLD community, may I suggest that a small drafting team, will review the proposed changes and related matters next week ( 11-14) and draft a Council Statement? As to related matters: note that the proposed change of Article 18 coincides with the upcoming second IANA Naming Function Review, which founded on the basis of Article 18. Please also note that, section 18.8 (d) final sentence has not been updated. As a result the ccNSO is expected to appoint a co-chair from the members appointed by th4e ccNSO and the RySG. Similarly section 19.6 (a) will not be adjusted. If you agree, please let volunteer as soon as possible, but no later than 11 April 2023, noon UTC. Thanks you and kind regards, Bart
Greetings Bart and fellow Council members, I am happy to participate in this exercise. Best Regards, Stephen From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Bart Boswinkel via Ccnso-council <ccNSO-Council@icann.org> Reply-To: Bart Boswinkel <bart.boswinkel@icann.org> Date: Wednesday, April 5, 2023 at 11:56 To: "ccNSO-Council@icann.org" <ccNSO-Council@icann.org> Subject: [ccnso-council] Change Article 18 and 19 ICANN Bylaws (Fundamental Bylaw change) Dear all, ICANN org has recently opened a public comment forum pertaining to a change of Article 18 and 19 of the ICANN Bylaws on the IANA Naming Function Review and Special IANA naming Function Review (https://www.icann.org/en/public-comment/proceeding/iana-naming-function-revi... ). Note that both Article 18 and 19 are Fundamental Bylaw changes, therefore the in the end the Decisional Participants need to approve the change. According to the introduction there are four type of changes proposed: 1. The removal of a duplication at Article 18, Section 12(a), as identified by the first IANA Naming Function Review (IFR) Team in its Final Report. 2. Updates to the composition of IFR teams to address composition issues identified by the Registries Stakeholder Group (RySG) in 2019. 3. Clarification of ambiguities on the IFR processes identified through the first IFR after the IANA Stewardship Transition. 4. Updates to the composition of the team exploring an IANA Naming Function Separation Process (Article 19), to conform to composition updates for the IFRs within Article 18. The detailed changes are included in the redline version of the Bylaws ( https://itp.cdn.icann.org/en/files/additional-reviews/proposed-amendments-to...) Given the importance of the IANA Naming Review process for the ccTLD community (Article 18) and the related IANA Naming Function Separation Process ( Article 19) for the ccTLD community, may I suggest that a small drafting team, will review the proposed changes and related matters next week ( 11-14) and draft a Council Statement? As to related matters: note that the proposed change of Article 18 coincides with the upcoming second IANA Naming Function Review, which founded on the basis of Article 18. Please also note that, section 18.8 (d) final sentence has not been updated. As a result the ccNSO is expected to appoint a co-chair from the members appointed by th4e ccNSO and the RySG. Similarly section 19.6 (a) will not be adjusted. If you agree, please let volunteer as soon as possible, but no later than 11 April 2023, noon UTC. Thanks you and kind regards, Bart
Dear all, To date only Irina and Stephen volunteered, anybody else willing to volunteer in helping to draft a ccNSO Council Statement? Thank you and kind regards, Bart From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Bart Boswinkel via Ccnso-council <ccNSO-Council@icann.org> Reply to: Bart Boswinkel <bart.boswinkel@icann.org> Date: Wednesday, 5 April 2023 at 17:56 To: "ccNSO-Council@icann.org" <ccNSO-Council@icann.org> Subject: [ccnso-council] Change Article 18 and 19 ICANN Bylaws (Fundamental Bylaw change) Dear all, ICANN org has recently opened a public comment forum pertaining to a change of Article 18 and 19 of the ICANN Bylaws on the IANA Naming Function Review and Special IANA naming Function Review (https://www.icann.org/en/public-comment/proceeding/iana-naming-function-revi... ). Note that both Article 18 and 19 are Fundamental Bylaw changes, therefore the in the end the Decisional Participants need to approve the change. According to the introduction there are four type of changes proposed: 1. The removal of a duplication at Article 18, Section 12(a), as identified by the first IANA Naming Function Review (IFR) Team in its Final Report. 2. Updates to the composition of IFR teams to address composition issues identified by the Registries Stakeholder Group (RySG) in 2019. 3. Clarification of ambiguities on the IFR processes identified through the first IFR after the IANA Stewardship Transition. 4. Updates to the composition of the team exploring an IANA Naming Function Separation Process (Article 19), to conform to composition updates for the IFRs within Article 18. The detailed changes are included in the redline version of the Bylaws ( https://itp.cdn.icann.org/en/files/additional-reviews/proposed-amendments-to... [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/additional-rev...>) Given the importance of the IANA Naming Review process for the ccTLD community (Article 18) and the related IANA Naming Function Separation Process ( Article 19) for the ccTLD community, may I suggest that a small drafting team, will review the proposed changes and related matters next week ( 11-14) and draft a Council Statement? As to related matters: note that the proposed change of Article 18 coincides with the upcoming second IANA Naming Function Review, which founded on the basis of Article 18. Please also note that, section 18.8 (d) final sentence has not been updated. As a result the ccNSO is expected to appoint a co-chair from the members appointed by th4e ccNSO and the RySG. Similarly section 19.6 (a) will not be adjusted. If you agree, please let volunteer as soon as possible, but no later than 11 April 2023, noon UTC. Thanks you and kind regards, Bart
Hi Bart I’m available Thank you Regards Molehe Wesi From: Ccnso-council <ccnso-council-bounces@icann.org> On Behalf Of Bart Boswinkel via Ccnso-council Sent: Tuesday, April 11, 2023 12:11 PM To: ccNSO-Council@icann.org Subject: Re: [ccnso-council] Change Article 18 and 19 ICANN Bylaws (Fundamental Bylaw change) Dear all, To date only Irina and Stephen volunteered, anybody else willing to volunteer in helping to draft a ccNSO Council Statement? Thank you and kind regards, Bart From: Ccnso-council <ccnso-council-bounces@icann.org<mailto:ccnso-council-bounces@icann.org>> on behalf of Bart Boswinkel via Ccnso-council <ccNSO-Council@icann.org<mailto:ccNSO-Council@icann.org>> Reply to: Bart Boswinkel <bart.boswinkel@icann.org<mailto:bart.boswinkel@icann.org>> Date: Wednesday, 5 April 2023 at 17:56 To: "ccNSO-Council@icann.org<mailto:ccNSO-Council@icann.org>" <ccNSO-Council@icann.org<mailto:ccNSO-Council@icann.org>> Subject: [ccnso-council] Change Article 18 and 19 ICANN Bylaws (Fundamental Bylaw change) Dear all, ICANN org has recently opened a public comment forum pertaining to a change of Article 18 and 19 of the ICANN Bylaws on the IANA Naming Function Review and Special IANA naming Function Review (https://www.icann.org/en/public-comment/proceeding/iana-naming-function-revi... ). Note that both Article 18 and 19 are Fundamental Bylaw changes, therefore the in the end the Decisional Participants need to approve the change. According to the introduction there are four type of changes proposed: 1. The removal of a duplication at Article 18, Section 12(a), as identified by the first IANA Naming Function Review (IFR) Team in its Final Report. 2. Updates to the composition of IFR teams to address composition issues identified by the Registries Stakeholder Group (RySG) in 2019. 3. Clarification of ambiguities on the IFR processes identified through the first IFR after the IANA Stewardship Transition. 4. Updates to the composition of the team exploring an IANA Naming Function Separation Process (Article 19), to conform to composition updates for the IFRs within Article 18. The detailed changes are included in the redline version of the Bylaws ( https://itp.cdn.icann.org/en/files/additional-reviews/proposed-amendments-to... [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/additional-rev...>) Given the importance of the IANA Naming Review process for the ccTLD community (Article 18) and the related IANA Naming Function Separation Process ( Article 19) for the ccTLD community, may I suggest that a small drafting team, will review the proposed changes and related matters next week ( 11-14) and draft a Council Statement? As to related matters: note that the proposed change of Article 18 coincides with the upcoming second IANA Naming Function Review, which founded on the basis of Article 18. Please also note that, section 18.8 (d) final sentence has not been updated. As a result the ccNSO is expected to appoint a co-chair from the members appointed by th4e ccNSO and the RySG. Similarly section 19.6 (a) will not be adjusted. If you agree, please let volunteer as soon as possible, but no later than 11 April 2023, noon UTC. Thanks you and kind regards, Bart
Hi Bart, I'm available too. Best, Jenifer. El 11 abr. 2023 5:10 a. m., Bart Boswinkel via Ccnso-council <ccnso-council@icann.org> escribió: Dear all, To date only Irina and Stephen volunteered, anybody else willing to volunteer in helping to draft a ccNSO Council Statement? Thank you and kind regards, Bart From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Bart Boswinkel via Ccnso-council <ccNSO-Council@icann.org> Reply to: Bart Boswinkel <bart.boswinkel@icann.org> Date: Wednesday, 5 April 2023 at 17:56 To: "ccNSO-Council@icann.org" <ccNSO-Council@icann.org> Subject: [ccnso-council] Change Article 18 and 19 ICANN Bylaws (Fundamental Bylaw change) Dear all, ICANN org has recently opened a public comment forum pertaining to a change of Article 18 and 19 of the ICANN Bylaws on the IANA Naming Function Review and Special IANA naming Function Review (https://www.icann.org/en/public-comment/proceeding/iana-naming-function-revi... ). Note that both Article 18 and 19 are Fundamental Bylaw changes, therefore the in the end the Decisional Participants need to approve the change. According to the introduction there are four type of changes proposed: 1. The removal of a duplication at Article 18, Section 12(a), as identified by the first IANA Naming Function Review (IFR) Team in its Final Report. 2. Updates to the composition of IFR teams to address composition issues identified by the Registries Stakeholder Group (RySG) in 2019. 3. Clarification of ambiguities on the IFR processes identified through the first IFR after the IANA Stewardship Transition. 4. Updates to the composition of the team exploring an IANA Naming Function Separation Process (Article 19), to conform to composition updates for the IFRs within Article 18. The detailed changes are included in the redline version of the Bylaws ( https://itp.cdn.icann.org/en/files/additional-reviews/proposed-amendments-to... [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/additional-rev...>) Given the importance of the IANA Naming Review process for the ccTLD community (Article 18) and the related IANA Naming Function Separation Process ( Article 19) for the ccTLD community, may I suggest that a small drafting team, will review the proposed changes and related matters next week ( 11-14) and draft a Council Statement? As to related matters: note that the proposed change of Article 18 coincides with the upcoming second IANA Naming Function Review, which founded on the basis of Article 18. Please also note that, section 18.8 (d) final sentence has not been updated. As a result the ccNSO is expected to appoint a co-chair from the members appointed by th4e ccNSO and the RySG. Similarly section 19.6 (a) will not be adjusted. If you agree, please let volunteer as soon as possible, but no later than 11 April 2023, noon UTC. Thanks you and kind regards, Bart ***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.************** ***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.**************
participants (4)
-
Bart Boswinkel -
Jenifer Lopez -
Molehe Wesi -
Stephen Deerhake ＠ ASNIC