February 2018 - Ws2-staff_acct

CCWG-Accountability-WS2-StaffAcct - Final Recommendations - Next Steps
by Bernard Turcotte Feb. 21, 2018

Feb. 21, 2018

All, Given there have been no additional comments on the list and that the published deadline has passed (see below) the final recommendations of the Staff Accountability sub-group will be forwarded to the plenary for consideration at its next meeting. Please find attached a clean and red lined version attached to this email for your convenience. Additionally please note that we have also attached the proposed responses to all the comments made in the public comment exercise. Please review these and provide any feedback on the list by Friday 23 February 23:59 UTC. If no significant comments are made by the deadline this will be considered final and published. Thank You. Bernard Turcotte ICANN Staff Support to the CCWG-Accountability-WS2 for Jordan Carter CCWG-Accountability-WS2 Co-Chair and Rapporteur for the Staff Accountability sub-group. On Mon, Feb 19, 2018 at 11:46 AM, Bernard Turcotte < turcotte.bernard(a)gmail.com> wrote: > Minor cut and paste error - apologies - fixed below > > B. > > On Mon, Feb 19, 2018 at 9:25 AM, Bernard Turcotte < > turcotte.bernard(a)gmail.com> wrote: > >> All, >> >> We have failed to obtain the 5 required confirmations to be able to hold >> the above mentioned call and are therefore forced to cancel it. >> >> As noted below we will now consider the current draft, with amendments >> suggested by Jordan, to be the final recommendations >> for Staff Accountability >> >> which will be sent to the CCWG-Accountability-WS2 plenary Wednesday 21 >> February 1200 UTC unless there is significant objection on the list prior >> to the deadline. >> >> Thank You. >> >> >> Bernard Turcotte >> ICANN Staff Support to the CCWG-Accountability-WS2 >> >> >> On Wed, Feb 14, 2018 at 7:02 PM, Bernard Turcotte < >> turcotte.bernard(a)gmail.com> wrote: >> >>> All, >>> >>> Given the positive comments with respect to the latest draft of the >>> recommendations we are proposing the following way forward: >>> >>> >>> - We are proposing a meeting of the Staff Acct sub-group >>> >>> Tuesday February 20 1900 UTC to finalize the latest version of the >>> recommendations. >>> - As per the current procedure we will require 5 confirmation of >>> attendance to confirm the meeting 36 hours prior to the proposed meeting >>> time. >>> - Please reply to this email or to the list to confirm you >>> participation by Monday 19 February 0700 UTC. If we do not obtain 5 >>> confirmations the meeting will be cancelled. >>> - If we are obliged to cancel the Tuesday 20 February 1900 UTC >>> meeting we will consider that the latest draft of the recommendations as >>> final and these will be forwarded to the plenary 21 February for a reading >>> at its Wednesday 28 February 1900 UTC meeting. >>> >>> Thank You. >>> >>> Bernard Turcotte >>> ICANN Staff Support to the CCWG-Accountability-WS2 >>> >>> for Jordan. >>> >>> >>> >> >

1 0

CCWG-Accountability-WS2-StaffAcct - Meeting Tuesday February 20 1900 UTC CANCELLED
by Bernard Turcotte Feb. 19, 2018

Feb. 19, 2018

All, We have failed to obtain the 5 required confirmations to be able to hold the above mentioned call and are therefore forced to cancel it. As noted below we will now consider the current draft, with amendments suggested by Jordan, to be the final recommendations of the Ombuds-IOO which will be sent to the CCWG-Accountability-WS2 plenary Wednesday 21 February 1200 UTC unless there is significant objection on the list prior to the deadline. Thank You. Bernard Turcotte ICANN Staff Support to the CCWG-Accountability-WS2 On Wed, Feb 14, 2018 at 7:02 PM, Bernard Turcotte < turcotte.bernard(a)gmail.com> wrote: > All, > > Given the positive comments with respect to the latest draft of the > recommendations we are proposing the following way forward: > > > - We are proposing a meeting of the Staff Acct sub-group > > Tuesday February 20 1900 UTC to finalize the latest version of the > recommendations. > - As per the current procedure we will require 5 confirmation of > attendance to confirm the meeting 36 hours prior to the proposed meeting > time. > - Please reply to this email or to the list to confirm you > participation by Monday 19 February 0700 UTC. If we do not obtain 5 > confirmations the meeting will be cancelled. > - If we are obliged to cancel the Tuesday 20 February 1900 UTC meeting > we will consider that the latest draft of the recommendations as final and > these will be forwarded to the plenary 21 February for a reading at its > Wednesday 28 February 1900 UTC meeting. > > Thank You. > > Bernard Turcotte > ICANN Staff Support to the CCWG-Accountability-WS2 > > for Jordan. > > On Tue, Feb 13, 2018 at 12:54 PM, Jordan Carter <jordan(a)internetnz.net.nz> > wrote: > >> Thanks Cheryl, Klaus! >> >> Pam, others? >> >> Jordan >> >> On Wed, 14 Feb 2018 at 3:14 AM, Klaus Stoll <kdrstoll(a)gmail.com> wrote: >> >>> Dear Jordan >>> >>> Greeting. Keeping things short and sweet: I support the changes to >>> Recommendation 3. >>> >>> Yours >>> >>> Klaus >>> >>> On 2/12/2018 11:34 PM, Jordan Carter wrote: >>> >>> Hi all >>> >>> Thanks to Pam and to others for comments and discussion of the proposed >>> updated recommendations. >>> >>> I've had a call with ICANN staff and with Avri as the former rapporteur, >>> and I've carefully considered the on list traffic. >>> >>> I'm proposing a different approach that works service levels back in, >>> closer to our original recommendations. You can find that in the re-revised >>> Recommendation 3. >>> >>> This approach may result in ICANN org or board pushback, but I think it >>> responds to their key concern about scope of the work on service levels >>> while providing a way to make that work, and inviting the organisation to >>> commit to service level targets and guidelines that are meaningful for the >>> community. >>> >>> PDFs with track changes and clean are attached. >>> >>> *I would be grateful if you could share comments about this asap, as we >>> will need to take it through the plenary for approval as a first reading on >>> 21 Feb. *That means in theory 14 Feb is our deadline to send the >>> document around. >>> >>> *Could I ask for comments within the next 24hrs from send time for this >>> message?* >>> >>> I paste the revised proposed language below too for your reference. >>> >>> Thanks in advance, >>> Jordan >>> >>> >>> *3. ICANN Organization should work with the community to develop and >>> publish service level targets and guidelines (similar to the Service Level >>> Agreement for the IANA Numbering Services) that clearly define the services >>> provided by ICANN to community as well as the service level target for each >>> service. In this context:* >>> >>> >>> >>> *a) ICANN should work with the community to identify and prioritize the >>> classes of services for which service level targets and guidelines will be >>> implemented, and to define how service level targets and guidelines will be >>> defined.* >>> >>> >>> >>> *b) Develop clear and reasonable guidelines for expected behavior >>> between ICANN organization and the community for those newly-identified >>> activities. * >>> >>> >>> >>> *c) Develop and publish the resulting service levels, targets and >>> guidelines in a single area on icann.org <http://icann.org/>. These targets >>> and guidelines should also inform any regular information acquisition >>> mechanism described in recommendation 2 of this report.* >>> >>> >>> >>> *The structure and specific timing of this effort should be determined >>> by ICANN organization (but be substantially under way before the end of >>> 2018). We suggest that representatives of ICANN's executive team, the ICANN >>> Board, and SO/AC Leadership participate in this effort to ensure a >>> constructive dialogue across all parts of the ICANN community. This work >>> should be, and be seen as, a genuine chance for collaboration and improved >>> relationships between the Board, organization and community. * >>> >>> >>> >>> -- >>> Jordan Carter >>> >>> >>> >>> >>> _______________________________________________ >>> Ws2-staff_acct mailing listWs2-staff_acct@icann.orghttps://mm.icann.org/mailman/listinfo/ws2-staff_acct >>> >>> -- >> Jordan Carter >> Group Chief Executive, InternetNZ >> +64-21-442-649 <+64%2021%20442%20649> >> >> Sent on the run, apologies for brevity >> >> _______________________________________________ >> Ws2-staff_acct mailing list >> Ws2-staff_acct(a)icann.org >> https://mm.icann.org/mailman/listinfo/ws2-staff_acct >> >> >

1 1

Re: [Ws2-staff_acct] CCWG-Accountability-WS2-StaffAcct - Me eting âTuesday February 20 1900 UTC CANCELLED
by Alan Greenberg Feb. 19, 2018

Feb. 19, 2018

Bernie, the Subject says Staff-Acct and the Body says Ombuds. Alan At 19/02/2018 09:25 AM, Bernard Turcotte wrote: >All, > >We have failed to obtain the 5 required >confirmations to be able to hold the above >mentioned call and are therefore forced to cancel it. > >As noted below we will now consider the current >draft, with amendments suggested by Jordan, to >be the final recommendations of the Ombuds-IOO >which will be sent to the >CCWG-Accountability-WS2 plenary Wednesday 21 >February 1200 UTC unless there is significant >objection on the list prior to the deadline. > >Thank You. > >â >Bernard Turcotte >ICANN Staff Support to the CCWG-Accountability-WS2 > > >On Wed, Feb 14, 2018 at 7:02 PM, Bernard >Turcotte <<mailto:turcotte.bernard@gmail.com>turcotte.bernard(a)gmail.com> wrote: >All, > >Given the positive comments with respect to the >latest draft of the recommendations we are proposing the following way forward: > >We are proposing a meeting of the Staff Acct sub-group >ââ >Tuesday February 20 1900 UTC to finalize the >latest version of the recommendations. > * As per the current procedure we will > require 5 confirmation of attendance to confirm > the meeting 36 hours prior to the proposed meeting time. > * Please reply to this email or to the list > to confirm you participation by Monday 19 > February 0700 UTC. If we do not obtain 5 > confirmations the meeting will be cancelled. > * If we are obliged to cancel the Tuesday 20 > February 1900 UTC meeting we will consider that > the latest draft of the recommendations as > final and these will be forwarded to the > plenary 21 February for a reading at its > Wednesday 28 February 1900 UTC meeting. Thank You. > > Bernard Turcotte > ICANN Staff Support to the CCWG-Accountability-WS2 > > for Jordan. > > On Tue, Feb 13, 2018 at 12:54 PM, Jordan > Carter <<mailto:jordan@internetnz.net.nz>jordan(a)internetnz.net.nz> wrote: > Thanks Cheryl, Klaus! > > Pam, others? > > Jordan > > On Wed, 14 Feb 2018 at 3:14 AM, Klaus Stoll > <<mailto:kdrstoll@gmail.com>kdrstoll(a)gmail.com> wrote: > > Dear Jordan > > Greeting. Keeping things short and sweet: I > support the changes to Recommendation 3. > > Yours > > Klaus > > On 2/12/2018 11:34 PM, Jordan Carter wrote: >> Hi all >> >> Thanks to Pam and to others for comments >> and discussion of the proposed updated recommendations. >> >> I've had a call with ICANN staff and with >> Avri as the former rapporteur, and I've >> carefully considered the on list traffic. >> >> I'm proposing a different approach that >> works service levels back in, closer to our >> original recommendations. You can find that in the re-revised Recommendation 3. >> >> This approach may result in ICANN org or >> board pushback, but I think it responds to >> their key concern about scope of the work on >> service levels while providing a way to make >> that work, and inviting the organisation to >> commit to service level targets and guidelines >> that are meaningful for the community. >> >> PDFs with track changes and clean are attached. >> >> I would be grateful if you could share >> comments about this asap, as we will need to >> take it through the plenary for approval as a >> first reading on 21 Feb. That means in theory >> 14 Feb is our deadline to send the document around. >> >> Could I ask for comments within the next >> 24hrs from send time for this message? >> >> I paste the revised proposed language below too for your reference. >> >> Thanks in advance, >> Jordan >> >> >> 3. ICANN Organization should work with the >> community to develop and publish service level >> targets and guidelines (similar to the Service >> Level Agreement for the IANA Numbering >> Services) that clearly define the services >> provided by ICANN to community as well as the >> service level target for each service. In this context: >> >> >> >> a) ICANN should work with the community to >> identify and prioritize the classes of >> services for which service level targets and >> guidelines will be implemented, and to define >> how service level targets and guidelines will be defined. >> >> >> >> b) Develop clear and reasonable guidelines >> for expected behavior between ICANN >> organization and the community for those newly-identified activities. >> >> >> >> c) Develop and publish the resulting >> service levels, targets and guidelines in a >> single area on <http://icann.org/>icann.org. >> These targets and guidelines should also >> inform any regular information acquisition >> mechanism described in recommendation 2 of this report. >> >> >> >> The structure and specific timing of this >> effort should be determined by ICANN >> organization (but be substantially under way >> before the end of 2018). We suggest that >> representatives of ICANN's executive team, the >> ICANN Board, and SO/AC Leadership participate >> in this effort to ensure a constructive >> dialogue across all parts of the ICANN >> community. This work should be, and be seen >> as, a genuine chance for collaboration and >> improved relationships between the Board, organization and community. >> >> >> >> -- >> Jordan Carter >> >> >> >> >> >> _______________________________________________ >> >> Ws2-staff_acct mailing list >> >> <mailto:Ws2-staff_acct@icann.org>Ws2-staff_acct(a)icann.org >> >> https://mm.icann.org/mailman/listinfo/ws2-staff_acct > -- > Jordan Carter > Group Chief Executive, InternetNZ > <tel:+64%2021%20442%20649>+64-21-442-649 > > Sent on the run, apologies for brevity > > _______________________________________________ > Ws2-staff_acct mailing list > <mailto:Ws2-staff_acct@icann.org>Ws2-staff_acct(a)icann.org > https://mm.icann.org/mailman/listinfo/ws2-staff_acct > > > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:BFG48JcWNl8ncdf+7o7Hz8/eiuGRGrROiaRuBkhVJEeYIeYXTSBjqNSS79YzVxxz2PKRqzMkHVJNaLDErWTulKM/7kjw7QEL3sVEiFJxRiiSBr9UuhS122+GAT/GxKgF >X-Microsoft-Antispam-Message-Info: > >hRYu16cxXc9cwOaKJSCenpl2izJvW/yATkPs10TkOL/HFdAXli6zuQI7PaxLKcr/t0UsUHc0TQDIQh9EDkaddXFoOuORUslugUFYQdxPU0QUUqN8+Osc5D0GKvAyeSbjJoJtlTLzfbkKrOhbrr6rWt8h6Ac2uwIM6DiK+pjoVtg= > >_______________________________________________ >Ws2-staff_acct mailing list >Ws2-staff_acct(a)icann.org >https://mm.icann.org/mailman/listinfo/ws2-staff_acct

1 0

CCWG-Accountability-WS2-StaffAcct - Next meeting and next steps
by Bernard Turcotte Feb. 15, 2018

Feb. 15, 2018

All, Given the positive comments with respect to the latest draft of the recommendations we are proposing the following way forward: - We are proposing a meeting of the Staff Acct sub-group Tuesday February 20 1900 UTC to finalize the latest version of the recommendations. - As per the current procedure we will require 5 confirmation of attendance to confirm the meeting 36 hours prior to the proposed meeting time. - Please reply to this email or to the list to confirm you participation by Monday 19 February 0700 UTC. If we do not obtain 5 confirmations the meeting will be cancelled. - If we are obliged to cancel the Tuesday 20 February 1900 UTC meeting we will consider that the latest draft of the recommendations as final and these will be forwarded to the plenary 21 February for a reading at its Wednesday 28 February 1900 UTC meeting. Thank You. Bernard Turcotte ICANN Staff Support to the CCWG-Accountability-WS2 for Jordan. On Tue, Feb 13, 2018 at 12:54 PM, Jordan Carter <jordan(a)internetnz.net.nz> wrote: > Thanks Cheryl, Klaus! > > Pam, others? > > Jordan > > On Wed, 14 Feb 2018 at 3:14 AM, Klaus Stoll <kdrstoll(a)gmail.com> wrote: > >> Dear Jordan >> >> Greeting. Keeping things short and sweet: I support the changes to >> Recommendation 3. >> >> Yours >> >> Klaus >> >> On 2/12/2018 11:34 PM, Jordan Carter wrote: >> >> Hi all >> >> Thanks to Pam and to others for comments and discussion of the proposed >> updated recommendations. >> >> I've had a call with ICANN staff and with Avri as the former rapporteur, >> and I've carefully considered the on list traffic. >> >> I'm proposing a different approach that works service levels back in, >> closer to our original recommendations. You can find that in the re-revised >> Recommendation 3. >> >> This approach may result in ICANN org or board pushback, but I think it >> responds to their key concern about scope of the work on service levels >> while providing a way to make that work, and inviting the organisation to >> commit to service level targets and guidelines that are meaningful for the >> community. >> >> PDFs with track changes and clean are attached. >> >> *I would be grateful if you could share comments about this asap, as we >> will need to take it through the plenary for approval as a first reading on >> 21 Feb. *That means in theory 14 Feb is our deadline to send the >> document around. >> >> *Could I ask for comments within the next 24hrs from send time for this >> message?* >> >> I paste the revised proposed language below too for your reference. >> >> Thanks in advance, >> Jordan >> >> >> *3. ICANN Organization should work with the community to develop and >> publish service level targets and guidelines (similar to the Service Level >> Agreement for the IANA Numbering Services) that clearly define the services >> provided by ICANN to community as well as the service level target for each >> service. In this context:* >> >> >> >> *a) ICANN should work with the community to identify and prioritize the >> classes of services for which service level targets and guidelines will be >> implemented, and to define how service level targets and guidelines will be >> defined.* >> >> >> >> *b) Develop clear and reasonable guidelines for expected behavior between >> ICANN organization and the community for those newly-identified >> activities. * >> >> >> >> *c) Develop and publish the resulting service levels, targets and >> guidelines in a single area on icann.org <http://icann.org/>. These targets >> and guidelines should also inform any regular information acquisition >> mechanism described in recommendation 2 of this report.* >> >> >> >> *The structure and specific timing of this effort should be determined by >> ICANN organization (but be substantially under way before the end of 2018). >> We suggest that representatives of ICANN's executive team, the ICANN Board, >> and SO/AC Leadership participate in this effort to ensure a constructive >> dialogue across all parts of the ICANN community. This work should be, and >> be seen as, a genuine chance for collaboration and improved relationships >> between the Board, organization and community. * >> >> >> >> -- >> Jordan Carter >> >> >> >> >> _______________________________________________ >> Ws2-staff_acct mailing listWs2-staff_acct@icann.orghttps://mm.icann.org/mailman/listinfo/ws2-staff_acct >> >> -- > Jordan Carter > Group Chief Executive, InternetNZ > +64-21-442-649 <+64%2021%20442%20649> > > Sent on the run, apologies for brevity > > _______________________________________________ > Ws2-staff_acct mailing list > Ws2-staff_acct(a)icann.org > https://mm.icann.org/mailman/listinfo/ws2-staff_acct > >

3 3

Revised proposal - final recs - comments please
by Jordan Carter Feb. 13, 2018

Feb. 13, 2018

Hi all Thanks to Pam and to others for comments and discussion of the proposed updated recommendations. I've had a call with ICANN staff and with Avri as the former rapporteur, and I've carefully considered the on list traffic. I'm proposing a different approach that works service levels back in, closer to our original recommendations. You can find that in the re-revised Recommendation 3. This approach may result in ICANN org or board pushback, but I think it responds to their key concern about scope of the work on service levels while providing a way to make that work, and inviting the organisation to commit to service level targets and guidelines that are meaningful for the community. PDFs with track changes and clean are attached. *I would be grateful if you could share comments about this asap, as we will need to take it through the plenary for approval as a first reading on 21 Feb. *That means in theory 14 Feb is our deadline to send the document around. *Could I ask for comments within the next 24hrs from send time for this message?* I paste the revised proposed language below too for your reference. Thanks in advance, Jordan *3. ICANN Organization should work with the community to develop and publish service level targets and guidelines (similar to the Service Level Agreement for the IANA Numbering Services) that clearly define the services provided by ICANN to community as well as the service level target for each service. In this context:* *a) ICANN should work with the community to identify and prioritize the classes of services for which service level targets and guidelines will be implemented, and to define how service level targets and guidelines will be defined.* *b) Develop clear and reasonable guidelines for expected behavior between ICANN organization and the community for those newly-identified activities. * *c) Develop and publish the resulting service levels, targets and guidelines in a single area on icann.org <http://icann.org/>. These targets and guidelines should also inform any regular information acquisition mechanism described in recommendation 2 of this report.* *The structure and specific timing of this effort should be determined by ICANN organization (but be substantially under way before the end of 2018). We suggest that representatives of ICANN's executive team, the ICANN Board, and SO/AC Leadership participate in this effort to ensure a constructive dialogue across all parts of the ICANN community. This work should be, and be seen as, a genuine chance for collaboration and improved relationships between the Board, organization and community. * -- Jordan Carter

3 3

CCWG-Accountability-WS2 -StaffAcct - Notice of cancellation of meeting on Wednesday 14 February 0500 UTC
by Bernard Turcotte Feb. 12, 2018

Feb. 12, 2018

All, Due to a lack of confirmed participants the above mentioned call is cancelled. Thank You. Bernard Turcotte ICANN Staff Support tot he CCWG-Accountability-WS2 ---------- Forwarded message ---------- From: Bernard Turcotte <turcotte.bernard(a)gmail.com> Date: Thu, Feb 8, 2018 at 10:06 AM Subject: Re: CCWG-Accountability-WS2 - Roundup of meetings for the week of 12 February - Request for confirmation - Update To: Accountability Cross Community <accountability-cross-community(a)icann.org > All, Here is a summary of the WS2 associated meetings for the week of 12 February. Please note that if a confirmation of attendance is requested and less than 5 participants confirm 36 hours prior that this call will be cancelled (this message replaces all the individual sub-group requests for confirmation of attendance - your single reply may indicate participation in any or all of these meetings - no need to send confirmations per individual meetings - we need to provide 24 hour notice of cancellation of calls to avoid certain costs). - Monday 12 February 1900 UTC - Ombuds IOO sub-group meeting - Please confirm participation bu Sunday 11 February 0700 UTC - Wednesdday 14 February 0500 UTC - Staff Accountability sub-group meeting - Please confirm participation by Monday 1 2 February 1700 UTC - Wednesday 14 February 1300 UTC - Plenary - Note this meeting may be cancelled - confirmation, or it being held or cancelled, will be sent Monday 12 February. - Wednesday 14 February 1900 UTC - Jurisdiction sub-group meeting - Please confirm participation by Tuesday 13 February 0700 UTC - Thursday 15 February 1300 UTC - Diversity sub-group meeting - Please confirm participation by Wednesday February 14 0100 UTC. - Thursday 15 February 1900 UTC - IRP-IOT meeting - Please confirm participation by Wednesday February 14 0700 UTC. Thank You Bernard Turcotte ICANN Staff Support tot he CCWG-Accountability-WS2

1 0

CCWG-Accountability-WS2-StaffAccountability- Draft Recommendations post public comment.
by Bernard Turcotte Feb. 11, 2018

Feb. 11, 2018

All, Given the difficulty in getting quorum for meetings of the sub-group coupled with the urgency to complete the review of these recommendations in light of the public comments, so they can be included in the WS2 final report, a new draft of the recommendations has been produced which incorporates what the rapporteur considers required changes to address the public comments which have been made. Attached to this email you will find both a clean and a red-lined PDF versions of this draft document for your consideration. Please provide any significant comments to the list by 23:59 UTC Sunday February 11. If there are no significant issues are brought up on the list which need to be addressed, this version of the report will be forwarded to the WS2 Plenary as the final recommendations of the Staff Accountability sub-Group. Should there be no significant comments by the deadline the work of the sub-group will be considered completed and all future meetings will be cancelled including the Wednesday 14 February 0500 UTC meeting. Thank You. Bernard Turcotte for Jordan Carter Staff Accountability Rapporteur.

3 3

Re: [Ws2-staff_acct] CCWG-Accountability-WS2-StaffAccountability-Meeting Wednesday 7 February 1300 UTC Reminder and request to confirm participation
by Bernard Turcotte Feb. 6, 2018

Feb. 6, 2018

All, Having received only two confirmations this does not meet the requirement to hold this meeting. As such the above meeting is cancelled. Bernard Turcotte ICANN Staff support to the CCWG-Accountability-WS2 On Sat, Feb 3, 2018 at 10:48 AM, Bernard Turcotte < turcotte.bernard(a)gmail.com> wrote: > > All Staff-Acct participants, > > T > his is both a reminder of and a request to confirm your participation in > the above mentioned meeting. > > If you intend to participate please reply to the email and simply state > that you will be attending. > > If there are less than 5 participants > who confirm prior to 23:59 UTC Monday 5 February > we will be forced to cancel the call and will advise the list. > > Thank you for you cooperation > > > Bernard Turcotte > ICANN Staff support to the CCWG-Accountability-WS2 > >

1 0

CCWG-Accountability-WS2-StaffAccountability-Meeting Wednesday 7 February 1300 UTC Reminder and request to confirm participation
by Bernard Turcotte Feb. 3, 2018

Feb. 3, 2018

All Staff-Acct participants, T his is both a reminder of and a request to confirm your participation in the above mentioned meeting. If you intend to participate please reply to the email and simply state that you will be attending. If there are less than 5 participants who confirm prior to 23:59 UTC Monday 5 February we will be forced to cancel the call and will advise the list. Thank you for you cooperation Bernard Turcotte ICANN Staff support to the CCWG-Accountability-WS2

1 0