Leadership Proposal for IG21 (Additional Guidance to Supplement Rec.20)
Dear EPDP Team Members, Thank you to those that have already sent support in response to the ‘Leadership’s Proposed Consensus Designation.’ Though leadership recognizes that the consensus call is already in progress for EPDP-IDNs P2, another item has come up that needs the Team’s attention. After the Team confirmed all Outputs last week, your support staff reached out to the ccNSO support staff for the ccNSO to be informed of the updates to Outputs 18-20 following the public comment process. Unfortunately, they provided us with feedback requesting that ccNSO’s consideration process be included again to Final Recommendation 20, to become: “…approved by the GNSO Council after consulting the ccNSO Council, prior to consideration by the ICANN Board.” Their rationale was that though not directly affected, ccTLDs that register IDNs at the second-level will be affected by the Guidelines and are expected to abide by them. Hence, the request was for a consultation mechanism to be included in the Output to ensure that the ccNSO Council is involved while the ccTLDs are informed throughout the whole process. To reflect ccNSO’s request while also considering the Team’s agreement, and so as not to interrupt the current work plan, the leadership proposes a new implementation guidance to supplement the current Final Recommendation 20, and the proposal is as follows: Implementation Guidance 21: "The GNSO Council should consult with the ccNSO Council prior to taking action on any future versions of the IDN Implementation Guidelines." (Current language for Consensus Call) Final Recommendation 20: “Any future versions of the IDN Implementation Guidelines must be approved by the GNSO Council prior to consideration by the ICANN Board.” Kindly review the proposal together with your respective groups and provide feedback through the mailing list by Thursday, 26 September 2024 at 23:59 UTC. If no objections are received by then, leadership will circulate the updated consensus designation document for the Team to continue participating in the consensus call (responding to the mailing list with accept or not accept) that started on 20 September 2024. The deadline of the consensus call will remain unchanged (Monday, 30 September 2024 at 22:30 UTC). Thank you again for all your kind cooperation. Much appreciated, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> Reply-To: Saewon Lee <saewon.lee@icann.org> Date: Friday, September 20, 2024 at 6:11 PM To: "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Cc: GNSO-Secs <gnso-secs@icann.org> Subject: [Gnso-epdp-idn-team] Consensus Call for EPDP-IDNs Phase 2 Final Outputs: 20-30 September 2024 Dear EPDP Team Members, On behalf of the leadership team, and as discussed during the Team meeting #118<https://community.icann.org/pages/viewpage.action?pageId=371327501> on Thursday, 12 September 2024, this message is to notify you the opening of the Consensus Call process on the EPDP-IDNs Phase 2 Final Outputs. The leadership team has proposed a consensus designation for every final Output that the EPDP Team has finalized by 20 September 2024. These consensus designations are contained in the attached pdf document titled, “[P2 Final Report] Leadership Proposed Consensus Designation.” This Consensus Call process opens today, Friday, 20 September, 2024 at 22:30 UTC, for a 10-day period, closing on Monday, 30 September, 2024 at 22:30 UTC. In accordance with the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...>, the EPDP Team Members are required to indicate via reply to this message whether they accept, or do not accept, the leadership team’s proposed consensus designations. If no objection is raised by any Member, the consensus designation is considered accepted by that EPDP Team Member. If you do not respond before Monday, 30 September, 2024 at 22:30 UTC, the leadership team will take this as acceptance of the consensus designations. If any objection is raised for any specific final Output(s), the leadership team is expected to reevaluate the consensus designation of such Output(s) and publish an updated designation to be reviewed by the EPDP Team. In the event there is no disagreement by the EPDP Team with the proposed consensus designations, your Support Staff will incorporate the Final Outputs into the Phase 2 Final Report. As set out in the EPDP Team Charter<https://community.icann.org/display/epdpidn/2.+Charter?preview=/166265992/16...>, only Members appointed by their representative groups are expected to participate in the Consensus Call process. Participants and observers will not be able to participate. For reference, please also see the attached document titled “[P2 Final] FINAL OUTPUTS (ONLY)” that contains the nineteen (19) Outputs to be included in the Phase 2 Final Report. For more information about the Consensus Call, you may review the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> or the EPDP Team Charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> (Section VI: Decision Making Methodologies) (both documents also linked above). Best regards, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team
Hi Everyone Thanks for your indulgence on this one last request. We appreciate it is very late in the day, but given our previous discussions on this topic I don’t believe our approach to be controversial and therefore will be acceptable to everyone. Leadership did consider a number of options on how to deal with the feedback received, but we believe this is the most appropriate course of action and should not impact our efforts to finalise the report and provide it to the GNSO Council for their consideration. Many thanks for your understanding. Donna obo the Leadership Team Sent from my iPhone On 24 Sep 2024, at 8:39 AM, Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> wrote: Dear EPDP Team Members, Thank you to those that have already sent support in response to the ‘Leadership’s Proposed Consensus Designation.’ Though leadership recognizes that the consensus call is already in progress for EPDP-IDNs P2, another item has come up that needs the Team’s attention. After the Team confirmed all Outputs last week, your support staff reached out to the ccNSO support staff for the ccNSO to be informed of the updates to Outputs 18-20 following the public comment process. Unfortunately, they provided us with feedback requesting that ccNSO’s consideration process be included again to Final Recommendation 20, to become: “…approved by the GNSO Council after consulting the ccNSO Council, prior to consideration by the ICANN Board.” Their rationale was that though not directly affected, ccTLDs that register IDNs at the second-level will be affected by the Guidelines and are expected to abide by them. Hence, the request was for a consultation mechanism to be included in the Output to ensure that the ccNSO Council is involved while the ccTLDs are informed throughout the whole process. To reflect ccNSO’s request while also considering the Team’s agreement, and so as not to interrupt the current work plan, the leadership proposes a new implementation guidance to supplement the current Final Recommendation 20, and the proposal is as follows: Implementation Guidance 21: "The GNSO Council should consult with the ccNSO Council prior to taking action on any future versions of the IDN Implementation Guidelines." (Current language for Consensus Call) Final Recommendation 20: “Any future versions of the IDN Implementation Guidelines must be approved by the GNSO Council prior to consideration by the ICANN Board.” Kindly review the proposal together with your respective groups and provide feedback through the mailing list by Thursday, 26 September 2024 at 23:59 UTC. If no objections are received by then, leadership will circulate the updated consensus designation document for the Team to continue participating in the consensus call (responding to the mailing list with accept or not accept) that started on 20 September 2024. The deadline of the consensus call will remain unchanged (Monday, 30 September 2024 at 22:30 UTC). Thank you again for all your kind cooperation. Much appreciated, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> Reply-To: Saewon Lee <saewon.lee@icann.org> Date: Friday, September 20, 2024 at 6:11 PM To: "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Cc: GNSO-Secs <gnso-secs@icann.org> Subject: [Gnso-epdp-idn-team] Consensus Call for EPDP-IDNs Phase 2 Final Outputs: 20-30 September 2024 Dear EPDP Team Members, On behalf of the leadership team, and as discussed during the Team meeting #118<https://community.icann.org/pages/viewpage.action?pageId=371327501> on Thursday, 12 September 2024, this message is to notify you the opening of the Consensus Call process on the EPDP-IDNs Phase 2 Final Outputs. The leadership team has proposed a consensus designation for every final Output that the EPDP Team has finalized by 20 September 2024. These consensus designations are contained in the attached pdf document titled, “[P2 Final Report] Leadership Proposed Consensus Designation.” This Consensus Call process opens today, Friday, 20 September, 2024 at 22:30 UTC, for a 10-day period, closing on Monday, 30 September, 2024 at 22:30 UTC. In accordance with the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...>, the EPDP Team Members are required to indicate via reply to this message whether they accept, or do not accept, the leadership team’s proposed consensus designations. If no objection is raised by any Member, the consensus designation is considered accepted by that EPDP Team Member. If you do not respond before Monday, 30 September, 2024 at 22:30 UTC, the leadership team will take this as acceptance of the consensus designations. If any objection is raised for any specific final Output(s), the leadership team is expected to reevaluate the consensus designation of such Output(s) and publish an updated designation to be reviewed by the EPDP Team. In the event there is no disagreement by the EPDP Team with the proposed consensus designations, your Support Staff will incorporate the Final Outputs into the Phase 2 Final Report. As set out in the EPDP Team Charter<https://community.icann.org/display/epdpidn/2.+Charter?preview=/166265992/16...>, only Members appointed by their representative groups are expected to participate in the Consensus Call process. Participants and observers will not be able to participate. For reference, please also see the attached document titled “[P2 Final] FINAL OUTPUTS (ONLY)” that contains the nineteen (19) Outputs to be included in the Phase 2 Final Report. For more information about the Consensus Call, you may review the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> or the EPDP Team Charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> (Section VI: Decision Making Methodologies) (both documents also linked above). Best regards, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team _______________________________________________ Gnso-epdp-idn-team mailing list -- gnso-epdp-idn-team@icann.org To unsubscribe send an email to gnso-epdp-idn-team-leave@icann.org %(web_page_url)slistinfo/%(_internal_name)s
Saewon and colleagues Good afternoon; it is somewhat of a disappointment to see this late request for change to a text which is under consensus call process. In the spirit of compromise, however, we could agree to this if also agreed by others; Best Nigel From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> Sent: 23 September 2024 23:39 To: gnso-epdp-idn-team@icann.org Cc: GNSO-Secs <gnso-secs@icann.org> Subject: [Gnso-epdp-idn-team] Leadership Proposal for IG21 (Additional Guidance to Supplement Rec.20) Dear EPDP Team Members, Thank you to those that have already sent support in response to the ‘Leadership’s Proposed Consensus Designation.’ Though leadership recognizes that the consensus call is already in progress for EPDP-IDNs P2, another item has come up that needs the Team’s attention. After the Team confirmed all Outputs last week, your support staff reached out to the ccNSO support staff for the ccNSO to be informed of the updates to Outputs 18-20 following the public comment process. Unfortunately, they provided us with feedback requesting that ccNSO’s consideration process be included again to Final Recommendation 20, to become: “…approved by the GNSO Council after consulting the ccNSO Council, prior to consideration by the ICANN Board.” Their rationale was that though not directly affected, ccTLDs that register IDNs at the second-level will be affected by the Guidelines and are expected to abide by them. Hence, the request was for a consultation mechanism to be included in the Output to ensure that the ccNSO Council is involved while the ccTLDs are informed throughout the whole process. To reflect ccNSO’s request while also considering the Team’s agreement, and so as not to interrupt the current work plan, the leadership proposes a new implementation guidance to supplement the current Final Recommendation 20, and the proposal is as follows: Implementation Guidance 21: "The GNSO Council should consult with the ccNSO Council prior to taking action on any future versions of the IDN Implementation Guidelines." (Current language for Consensus Call) Final Recommendation 20: “Any future versions of the IDN Implementation Guidelines must be approved by the GNSO Council prior to consideration by the ICANN Board.” Kindly review the proposal together with your respective groups and provide feedback through the mailing list by Thursday, 26 September 2024 at 23:59 UTC. If no objections are received by then, leadership will circulate the updated consensus designation document for the Team to continue participating in the consensus call (responding to the mailing list with accept or not accept) that started on 20 September 2024. The deadline of the consensus call will remain unchanged (Monday, 30 September 2024 at 22:30 UTC). Thank you again for all your kind cooperation. Much appreciated, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> Reply-To: Saewon Lee <saewon.lee@icann.org<mailto:saewon.lee@icann.org>> Date: Friday, September 20, 2024 at 6:11 PM To: "gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>" <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> Cc: GNSO-Secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [Gnso-epdp-idn-team] Consensus Call for EPDP-IDNs Phase 2 Final Outputs: 20-30 September 2024 Dear EPDP Team Members, On behalf of the leadership team, and as discussed during the Team meeting #118<https://community.icann.org/pages/viewpage.action?pageId=371327501> on Thursday, 12 September 2024, this message is to notify you the opening of the Consensus Call process on the EPDP-IDNs Phase 2 Final Outputs. The leadership team has proposed a consensus designation for every final Output that the EPDP Team has finalized by 20 September 2024. These consensus designations are contained in the attached pdf document titled, “[P2 Final Report] Leadership Proposed Consensus Designation.” This Consensus Call process opens today, Friday, 20 September, 2024 at 22:30 UTC, for a 10-day period, closing on Monday, 30 September, 2024 at 22:30 UTC. In accordance with the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...>, the EPDP Team Members are required to indicate via reply to this message whether they accept, or do not accept, the leadership team’s proposed consensus designations. If no objection is raised by any Member, the consensus designation is considered accepted by that EPDP Team Member. If you do not respond before Monday, 30 September, 2024 at 22:30 UTC, the leadership team will take this as acceptance of the consensus designations. If any objection is raised for any specific final Output(s), the leadership team is expected to reevaluate the consensus designation of such Output(s) and publish an updated designation to be reviewed by the EPDP Team. In the event there is no disagreement by the EPDP Team with the proposed consensus designations, your Support Staff will incorporate the Final Outputs into the Phase 2 Final Report. As set out in the EPDP Team Charter<https://community.icann.org/display/epdpidn/2.+Charter?preview=/166265992/16...>, only Members appointed by their representative groups are expected to participate in the Consensus Call process. Participants and observers will not be able to participate. For reference, please also see the attached document titled “[P2 Final] FINAL OUTPUTS (ONLY)” that contains the nineteen (19) Outputs to be included in the Phase 2 Final Report. For more information about the Consensus Call, you may review the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> or the EPDP Team Charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> (Section VI: Decision Making Methodologies) (both documents also linked above). Best regards, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team
Hi Nigel I understand you’re disappointment—very similar to my initial reaction. However, we do have time to incorporate the new IG into our report and as I said in my previous email it’s not inconsistent with our discussions on the topic or our rationale. Thanks again everyone. Donna Sent from my iPhone On 24 Sep 2024, at 9:51 PM, Hickson, Nigel (DSIT) via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> wrote: Saewon and colleagues Good afternoon; it is somewhat of a disappointment to see this late request for change to a text which is under consensus call process. In the spirit of compromise, however, we could agree to this if also agreed by others; Best Nigel From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> Sent: 23 September 2024 23:39 To: gnso-epdp-idn-team@icann.org Cc: GNSO-Secs <gnso-secs@icann.org> Subject: [Gnso-epdp-idn-team] Leadership Proposal for IG21 (Additional Guidance to Supplement Rec.20) Dear EPDP Team Members, Thank you to those that have already sent support in response to the ‘Leadership’s Proposed Consensus Designation.’ Though leadership recognizes that the consensus call is already in progress for EPDP-IDNs P2, another item has come up that needs the Team’s attention. After the Team confirmed all Outputs last week, your support staff reached out to the ccNSO support staff for the ccNSO to be informed of the updates to Outputs 18-20 following the public comment process. Unfortunately, they provided us with feedback requesting that ccNSO’s consideration process be included again to Final Recommendation 20, to become: “…approved by the GNSO Council after consulting the ccNSO Council, prior to consideration by the ICANN Board.” Their rationale was that though not directly affected, ccTLDs that register IDNs at the second-level will be affected by the Guidelines and are expected to abide by them. Hence, the request was for a consultation mechanism to be included in the Output to ensure that the ccNSO Council is involved while the ccTLDs are informed throughout the whole process. To reflect ccNSO’s request while also considering the Team’s agreement, and so as not to interrupt the current work plan, the leadership proposes a new implementation guidance to supplement the current Final Recommendation 20, and the proposal is as follows: Implementation Guidance 21: "The GNSO Council should consult with the ccNSO Council prior to taking action on any future versions of the IDN Implementation Guidelines." (Current language for Consensus Call) Final Recommendation 20: “Any future versions of the IDN Implementation Guidelines must be approved by the GNSO Council prior to consideration by the ICANN Board.” Kindly review the proposal together with your respective groups and provide feedback through the mailing list by Thursday, 26 September 2024 at 23:59 UTC. If no objections are received by then, leadership will circulate the updated consensus designation document for the Team to continue participating in the consensus call (responding to the mailing list with accept or not accept) that started on 20 September 2024. The deadline of the consensus call will remain unchanged (Monday, 30 September 2024 at 22:30 UTC). Thank you again for all your kind cooperation. Much appreciated, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> Reply-To: Saewon Lee <saewon.lee@icann.org<mailto:saewon.lee@icann.org>> Date: Friday, September 20, 2024 at 6:11 PM To: "gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>" <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> Cc: GNSO-Secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [Gnso-epdp-idn-team] Consensus Call for EPDP-IDNs Phase 2 Final Outputs: 20-30 September 2024 Dear EPDP Team Members, On behalf of the leadership team, and as discussed during the Team meeting #118<https://community.icann.org/pages/viewpage.action?pageId=371327501> on Thursday, 12 September 2024, this message is to notify you the opening of the Consensus Call process on the EPDP-IDNs Phase 2 Final Outputs. The leadership team has proposed a consensus designation for every final Output that the EPDP Team has finalized by 20 September 2024. These consensus designations are contained in the attached pdf document titled, “[P2 Final Report] Leadership Proposed Consensus Designation.” This Consensus Call process opens today, Friday, 20 September, 2024 at 22:30 UTC, for a 10-day period, closing on Monday, 30 September, 2024 at 22:30 UTC. In accordance with the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...>, the EPDP Team Members are required to indicate via reply to this message whether they accept, or do not accept, the leadership team’s proposed consensus designations. If no objection is raised by any Member, the consensus designation is considered accepted by that EPDP Team Member. If you do not respond before Monday, 30 September, 2024 at 22:30 UTC, the leadership team will take this as acceptance of the consensus designations. If any objection is raised for any specific final Output(s), the leadership team is expected to reevaluate the consensus designation of such Output(s) and publish an updated designation to be reviewed by the EPDP Team. In the event there is no disagreement by the EPDP Team with the proposed consensus designations, your Support Staff will incorporate the Final Outputs into the Phase 2 Final Report. As set out in the EPDP Team Charter<https://community.icann.org/display/epdpidn/2.+Charter?preview=/166265992/16...>, only Members appointed by their representative groups are expected to participate in the Consensus Call process. Participants and observers will not be able to participate. For reference, please also see the attached document titled “[P2 Final] FINAL OUTPUTS (ONLY)” that contains the nineteen (19) Outputs to be included in the Phase 2 Final Report. For more information about the Consensus Call, you may review the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> or the EPDP Team Charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> (Section VI: Decision Making Methodologies) (both documents also linked above). Best regards, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team _______________________________________________ Gnso-epdp-idn-team mailing list -- gnso-epdp-idn-team@icann.org To unsubscribe send an email to gnso-epdp-idn-team-leave@icann.org %(web_page_url)slistinfo/%(_internal_name)s
Hi Saewon, Team Members, Michael and I, as RrSG reps, confirm that we agree with the newly proposed language of IG 21. Also, I reviewed all of the other Leadership's Proposed Concensus Designations of Phase 2, I have no objections. Thank you all. Best Zuan ________________________________ 发件人: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> 发送时间: 2024年9月24日 6:39 收件人: gnso-epdp-idn-team@icann.org <gnso-epdp-idn-team@icann.org> 抄送: GNSO-Secs <gnso-secs@icann.org> 主题: [Gnso-epdp-idn-team] Leadership Proposal for IG21 (Additional Guidance to Supplement Rec.20) Dear EPDP Team Members, Thank you to those that have already sent support in response to the ‘Leadership’s Proposed Consensus Designation.’ Though leadership recognizes that the consensus call is already in progress for EPDP-IDNs P2, another item has come up that needs the Team’s attention. After the Team confirmed all Outputs last week, your support staff reached out to the ccNSO support staff for the ccNSO to be informed of the updates to Outputs 18-20 following the public comment process. Unfortunately, they provided us with feedback requesting that ccNSO’s consideration process be included again to Final Recommendation 20, to become: “…approved by the GNSO Council after consulting the ccNSO Council, prior to consideration by the ICANN Board.” Their rationale was that though not directly affected, ccTLDs that register IDNs at the second-level will be affected by the Guidelines and are expected to abide by them. Hence, the request was for a consultation mechanism to be included in the Output to ensure that the ccNSO Council is involved while the ccTLDs are informed throughout the whole process. To reflect ccNSO’s request while also considering the Team’s agreement, and so as not to interrupt the current work plan, the leadership proposes a new implementation guidance to supplement the current Final Recommendation 20, and the proposal is as follows: Implementation Guidance 21: "The GNSO Council should consult with the ccNSO Council prior to taking action on any future versions of the IDN Implementation Guidelines." (Current language for Consensus Call) Final Recommendation 20: “Any future versions of the IDN Implementation Guidelines must be approved by the GNSO Council prior to consideration by the ICANN Board.” Kindly review the proposal together with your respective groups and provide feedback through the mailing list by Thursday, 26 September 2024 at 23:59 UTC. If no objections are received by then, leadership will circulate the updated consensus designation document for the Team to continue participating in the consensus call (responding to the mailing list with accept or not accept) that started on 20 September 2024. The deadline of the consensus call will remain unchanged (Monday, 30 September 2024 at 22:30 UTC). Thank you again for all your kind cooperation. Much appreciated, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> Reply-To: Saewon Lee <saewon.lee@icann.org> Date: Friday, September 20, 2024 at 6:11 PM To: "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Cc: GNSO-Secs <gnso-secs@icann.org> Subject: [Gnso-epdp-idn-team] Consensus Call for EPDP-IDNs Phase 2 Final Outputs: 20-30 September 2024 Dear EPDP Team Members, On behalf of the leadership team, and as discussed during the Team meeting #118<https://community.icann.org/pages/viewpage.action?pageId=371327501> on Thursday, 12 September 2024, this message is to notify you the opening of the Consensus Call process on the EPDP-IDNs Phase 2 Final Outputs. The leadership team has proposed a consensus designation for every final Output that the EPDP Team has finalized by 20 September 2024. These consensus designations are contained in the attached pdf document titled, “[P2 Final Report] Leadership Proposed Consensus Designation.” This Consensus Call process opens today, Friday, 20 September, 2024 at 22:30 UTC, for a 10-day period, closing on Monday, 30 September, 2024 at 22:30 UTC. In accordance with the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...>, the EPDP Team Members are required to indicate via reply to this message whether they accept, or do not accept, the leadership team’s proposed consensus designations. If no objection is raised by any Member, the consensus designation is considered accepted by that EPDP Team Member. If you do not respond before Monday, 30 September, 2024 at 22:30 UTC, the leadership team will take this as acceptance of the consensus designations. If any objection is raised for any specific final Output(s), the leadership team is expected to reevaluate the consensus designation of such Output(s) and publish an updated designation to be reviewed by the EPDP Team. In the event there is no disagreement by the EPDP Team with the proposed consensus designations, your Support Staff will incorporate the Final Outputs into the Phase 2 Final Report. As set out in the EPDP Team Charter<https://community.icann.org/display/epdpidn/2.+Charter?preview=/166265992/16...>, only Members appointed by their representative groups are expected to participate in the Consensus Call process. Participants and observers will not be able to participate. For reference, please also see the attached document titled “[P2 Final] FINAL OUTPUTS (ONLY)” that contains the nineteen (19) Outputs to be included in the Phase 2 Final Report. For more information about the Consensus Call, you may review the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> or the EPDP Team Charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> (Section VI: Decision Making Methodologies) (both documents also linked above). Best regards, EPDP-IDNs Support Staff on behalf of the EPDP-IDNs Leadership Team
Hi team, just to avoid any confusion (and thanks to Donna for always taking the time to help me sort out my confusions): Zuan and myself agree to the Consensus Designation while representing the RrSG. So, the RrSG is fine both with the Consensus Designation as well as the newly introduced IG 21. Cheers, Michael -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Dipl.-Informatiker Fon: +49 231 9703-0 Fax: +49 231 9703-200 Dr. Michael Bauland SIP: Michael.Bauland@knipp.de Software Development E-mail: Michael.Bauland@knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp Certified according DIN ISO/IEC 27001:2017
Thank you for your response, Zuan, and further clarification, Michael. We appreciate both your support on IG21 and the 'Leadership Proposed Consensus Designation' on behalf of RrSG. Much appreciated, EPDP-IDNs Support Staff On 9/25/24, 2:41 AM, "Michael Bauland via Gnso-epdp-idn-team" <gnso-epdp-idn-team@icann.org <mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org <mailto:gnso-epdp-idn-team@icann.org>>> wrote: Hi team, just to avoid any confusion (and thanks to Donna for always taking the time to help me sort out my confusions): Zuan and myself agree to the Consensus Designation while representing the RrSG. So, the RrSG is fine both with the Consensus Designation as well as the newly introduced IG 21. Cheers, Michael -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Dipl.-Informatiker Fon: +49 231 9703-0 Fax: +49 231 9703-200 Dr. Michael Bauland SIP: Michael.Bauland@knipp.de <mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de <mailto:Michael.Bauland@knipp.de>> Software Development E-mail: Michael.Bauland@knipp.de <mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de <mailto:Michael.Bauland@knipp.de>> Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp Certified according DIN ISO/IEC 27001:2017 _______________________________________________ Gnso-epdp-idn-team mailing list -- gnso-epdp-idn-team@icann.org <mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org <mailto:gnso-epdp-idn-team@icann.org>> To unsubscribe send an email to gnso-epdp-idn-team-leave@icann.org <mailto:gnso-epdp-idn-team-leave@icann.org> <mailto:gnso-epdp-idn-team-leave@icann.org <mailto:gnso-epdp-idn-team-leave@icann.org>> %(web_page_url)slistinfo/%(_internal_name)s
participants (5)
-
Donna austin -
Hickson, Nigel (DSIT) -
Michael Bauland -
Saewon Lee -
Zhang Zuan