[Ssr2-review] Pointers to some of correspondence form the past

Thu Aug 23 18:46:08 UTC 2018

Denise,

I had also the same feeling. It was unfair to have hearing only in one side
and only consider ICANN resources to other hand.

As SSR2 RT volunteer there are a number resources we are spending as
volunteer for the better of this review. It sound like ICANN board does not
count RT resources as vital as that of ICANN. It should also be noted that
there are many risks associated with travelling taking into account recent
tendency of plane disappearing to unknown places and no one can find it.

Moving forward we need transparency among the team members and respect in
both side. We are just volunteer and we are committed for good work. That
only should be acknowledged.

SSAC and any other board members should be there to work with the team to
take forward this review not otherwise.

One more request, we need to have plans on how to update our constituency
and community members on our progress.

Regards,
Matogoro

On Aug 23, 2018 20:44, "Denise Michel" <denisemichel at fb.com> wrote:

> FYI - Following information pulled together last Nov. for bakcground
>
> 23 June Board letter
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_ranjbar-2Dto-2Dssr2-2Drt-2D23jun17-2Den.pdf&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=X9b9jkhVqzkIGF9vZP5o7vF93Mc2eu6m5Y0Y89CrFBY&s=E9-VX-Oq9es8ojJiRYhgaDdAnN3FnqoiwM2XdckJF90&e=> –
> Input on ToR
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_SSR_Terms-2Bof-2BReference-23-5Fftn1&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=X9b9jkhVqzkIGF9vZP5o7vF93Mc2eu6m5Y0Y89CrFBY&s=jO9NFLme_CgQKFjs4prNEwK7km8YyMcNyrTdpDJf0sQ&e=>
> . *(SSR2 discussed, shared views with Board-appointed SSR2 member)*
>
> Key points in Board letter (SSR2 responses in parentheses):
>
> ·      Board made suggestions regarding work plan, budget *(which were
> addressed in other documents)*
>
> ·      Board asked Staff to provide a different ToR template *(was not
> done)*
>
> ·      Board asked SSR2 to re-define “security” *(a community-vetted
> definition used for many years in the Security Framework; Board-appointed
> SSR2 member previously suggested this but it was not supported by most Team
> members and thus was not included in ToR)*
>
> ·      Board asked for the minimum number of dissenting RT members
> required for minority views *(ToR states SSR2 follows GNSO’s practice,
> which means any single member may offer a minority view)*
>
> 3 Oct Board letter
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__mm.icann.org_pipermail_ssr2-2Dreview_2017-2DOctober_000631.html&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=X9b9jkhVqzkIGF9vZP5o7vF93Mc2eu6m5Y0Y89CrFBY&s=6fJeJZbE8xeDHnZvaxzbkHOhpc6qHXT4UktJfcf2hrw&e=> –
> Scope of Subteam (Subteam lead replied 5 Oct
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__mm.icann.org_pipermail_ssr2-2Dreview_2017-2DOctober_000632.html&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=X9b9jkhVqzkIGF9vZP5o7vF93Mc2eu6m5Y0Y89CrFBY&s=qdFHIZIqWMoyow6QRyHDeBO9CpcnRcyp6aQZGByD9dU&e=>.;
> SSR2 Co-chairs replied 6 Oct
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__mm.icann.org_pipermail_ssr2-2Dreview_2017-2DOctober_000677.html&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=X9b9jkhVqzkIGF9vZP5o7vF93Mc2eu6m5Y0Y89CrFBY&s=QoZvTFQ8Vap2vLRiE6LBUe_Mv8Wh-hvLrl82N7IaoRY&e=>;
> )
>
> Key points in letter (SSR2 responses in parentheses):
>
> ·      Board asked for SSR2 work plan *(Board wasn’t aware that it was
> published previously)*
>
> ·      Board expressed concern on scope of Subgroup 2’s “audit plans” to
> be addressed and asked for changes *(the subteam leader and SSR2
> co-chairs explained that the subgroup leader used the term “audit” to refer
> to an information gathering exercise on issues related to SSR1
> recommendations, which the Team is required to assess. This had been
> clarified many times before. The Team asked for a dialogue to address the
> Board’s concerns to reach a mutual understanding. That has not happened.)*
>
> ·      Board asked subteam to change its scope before meeting in LA the
> next business day. *(See above, and that was not a feasible deadline)*
>
> ·      Board-appointed Team member subsequently emailed that the Subteam
> could “continue with their LA Workshop” *(it’s not clear why the Board
> felt the need to grant the Team permission)*
>
> 28 Oct Board letter
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_crocker-2Dto-2Dssr2-2D28oct17-2Den.pdf&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=X9b9jkhVqzkIGF9vZP5o7vF93Mc2eu6m5Y0Y89CrFBY&s=0fNntNpB9F8aL8l4bDkD7dEY9OQzsfaGgoWFKOqq3XE&e=> –
> Suspended SSR2 *(SSR2 discussed letter in scheduled outreach meetings)*
>
> Key points in letter (SSR2 responses in parentheses):
>
> ·      Board cited SSAC letter to Board and “a number of SO/AC chairs
> expressing concern about the composition, process and structure.” *(SSAC
> didn’t provide input or discuss anything with SSR2Team so Team didn’t know
> what the SSAC objections entailed; no other SO/AC chair shared their
> purported concerns with SSR2)*
>
> ·      Board suspended SSR2’s work pending responses from SOs/ACs,
> “except for engagement sessions, and use your scheduled face-to-face
> meeting on Friday to review the feedback from those sessions.”
>
> ·      Board will “formally ask the SOs and ACs to consider whether they
> believe there is a need to adjust the scope, terms of reference, work plan,
> skill set and/or resources allocated to SSR2.”
>
>
>
>
>
>
>
> *From: *Ssr2-review <ssr2-review-bounces at icann.org> on behalf of Kaveh
> Ranjbar <kaveh.ranjbar at board.icann.org>
> *Date: *Thursday, August 23, 2018 at 1:29 PM
> *To: *SSR2 <ssr2-review at icann.org>
> *Subject: *[Ssr2-review] Pointers to some of correspondence form the past
>
>
>
> Hello team,
>
>
>
> For reference:
>
> #1: https://www.icann.org/en/system/files/correspondence/
> ranjbar-to-ssr2-rt-23jun17-en.pdf
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_ranjbar-2Dto-2Dssr2-2Drt-2D23jun17-2Den.pdf&d=DwMFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=5PjAx6KwmmPffliFWSXNDgsBsFk0LZQJlpQKZouIT6E&s=iUlTYXI2GzyBby-BqU_CoARcv99oJutqZFLbYPI5ruI&e=>
>
> #2: http://mm.icann.org/pipermail/ssr2-review/2017-October/000631.html
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__mm.icann.org_pipermail_ssr2-2Dreview_2017-2DOctober_000631.html&d=DwMFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=5PjAx6KwmmPffliFWSXNDgsBsFk0LZQJlpQKZouIT6E&s=1u3nNQAj2DPmFn_0iR6FJI7fc8s3-Z29evDwaJa0uCI&e=>
>
> #3: https://www.icann.org/en/system/files/correspondence/
> crocker-to-ssr2-28oct17-en.pdf
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_crocker-2Dto-2Dssr2-2D28oct17-2Den.pdf&d=DwMFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=5PjAx6KwmmPffliFWSXNDgsBsFk0LZQJlpQKZouIT6E&s=NLSP5TtTDQrQVCOHt7JdpzFM1C_EK1VebgxXtTpzkR0&e=>
>
>
>
> and you can find them and consequent correspondence at:
>
>
>
> https://www.icann.org/resources/pages/correspondence-2017
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_correspondence-2D2017&d=DwMFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=5PjAx6KwmmPffliFWSXNDgsBsFk0LZQJlpQKZouIT6E&s=vxTvB4JONFJQdyeJ39LBOxKbso77u8bM1K5MipfO_jg&e=>
>
>
>
> All the best,
>
> Kaveh.
>
>
>
> _______________________________________________
> Ssr2-review mailing list
> Ssr2-review at icann.org
> https://mm.icann.org/mailman/listinfo/ssr2-review
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ssr2-review/attachments/20180823/de501b52/attachment.html>