<div dir="auto">Hi Greg, <div dir="auto"><br></div><div dir="auto">From the section of Annex 6, only one item states a need to develop a document (which is the FoI), others started with the word "consider" which simply means that it's expected to carried out in respect to another action which is the development of the FoI. </div><div dir="auto"><br></div><div dir="auto">Whether we treat it individually or collectively isn't important, what seem to be most important is that the items are considered in development of the FoI. - As I understand it, no other implementation document is expected to be produced under Human rights except the FoI.</div><div dir="auto"><br></div><div dir="auto">Regards<br><br><div data-smartmail="gmail_signature" dir="auto">Sent from my LG G4<br>Kindly excuse brevity and typos</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 Jan 2017 04:26, "Greg Shatan" <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">The issue paper is not the mandate. That is merely a staff-prepared document intended to assist the subgroup in starting its work.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">The mandate is in the Workstream 1 final report. The issue is that Annex 6 (on Human Rights) and Annex 12 (on WS2) each lay out the mandate for the subgroup, but they are not the same and appear to conflict with each other. This is expressed in more detail in Niels's email.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">If we follow Annex 6, then each of the bullet point items needs to be dealt with by the subgroup separately from the FoI. If we follow Annex 12, then we do not deal with them separately, but we do need to consider (or need to have considered) the bullet point items in preparing the FoI.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 8, 2017 at 3:51 PM, Seun Ojedeji <span dir="ltr"><<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Hello again,<div dir="auto"><br></div><div dir="auto">Looking at the attached document (which I expect is the mandate referred to by Niel), it seem to me that Annex 12 clearly enumerate that those listed bullet points needs to be considered as the FoI is being developed. </div><div dir="auto"><br></div><div dir="auto">I did not follow the work of the HR holistically but if we say we now have an FoI, it is assumed that the group considered and fulfilled the bullet point items, otherwise there isn't an FoI yet as it is expected that those considerations would inform the FoI drafting.</div><div dir="auto"><br></div><div dir="auto">Regards<span><br><br><div data-smartmail="gmail_signature" dir="auto">Sent from my LG G4<br>Kindly excuse brevity and typos</div></span></div></div><div class="m_5120192530255944052HOEnZb"><div class="m_5120192530255944052h5"><div class="gmail_extra"><br><div class="gmail_quote">On 8 Jan 2017 17:57, "Seun Ojedeji" <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Hello Niel, <div dir="auto"><br></div><div dir="auto">Thanks for your mail, just a question inline on one of your point. <br><br><div data-smartmail="gmail_signature" dir="auto">Sent from my LG G4<br>Kindly excuse brevity and typos</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 7 Jan 2017 18:31, "Niels ten Oever" <<a href="mailto:lists@nielstenoever.net" target="_blank">lists@nielstenoever.net</a>> wrote:<br type="attribution"><blockquote class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear all,<br>
<br>
Please refer to this version of the email instead. The prior version<br>
<div class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319quoted-text">inadvertently quoted from a draft version of the WS1 report.</div></blockquote></div></div></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319quoted-text"></div></blockquote></div></div></div><div dir="auto">.......</div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319quoted-text"> In these discussions, it felt as though we were going into too much detail, and stepping outside of the mandate of our Subgroup.</div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">SO: Could you share reference to the mandate of the subgroup?</div><div dir="auto"><br></div><div dir="auto">Thanks</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319elided-text"><br>
5. A fifth option could be (and this might be a mix between option 1<br>
and 3) to issue high-level recommendations on how ICANN and the SO’s and<br>
AC’s could best operationalize the core value contained in the Human<br>
Rights Bylaw. These recommendations could include (a) chartering a GNSO<br>
Working Group on Human Rights to consider and recommend how the Bylaw<br>
should be taken into account in gTLD policy development and<br>
implementation, and/or (b) chartering Working Groups in each of the<br>
other SO’s and AC’s for purposes relevant to their remit, and/or (c)<br>
chartering a new CCWG on Human Rights to specifically consider the steps<br>
needed to make the Bylaw operational, and provide guidance to each of<br>
the SO's and AC's on how they could incorporate the CCWG’s output in<br>
their processes, as well as discussing measures that could be adopted by<br>
ICANN, the corporation, with respect to its own internal human<br>
resources, employment, and contracting practices based on the Bylaw.<br>
<br>
We would like to bring these five options in front of the plenary, and<br>
we would greatly appreciate your thoughts on these and potentially other<br>
options.<br>
<br>
The Human Rights Subgroup wishes you a revitalizing festive season and<br>
we're greatly looking forward to completing our work in Workstream 2<br>
with you all in 2017.<br>
<br>
All the best,<br>
<br>
The CCWG Accountability Human Rights Subgroup<br>
<br>
</div>PS Thanks Greg and Brett for finding this error and for helping to<br>
correct it.<br>
<div class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319quoted-text">--<br>
Niels ten Oever<br>
Head of Digital<br>
<br>
Article 19<br>
<a href="http://www.article19.org" rel="noreferrer" target="_blank">www.article19.org</a><br>
<br>
PGP fingerprint 8D9F C567 BEE4 A431 56C4<br>
678B 08B5 A0F2 636D 68E9<br>
______________________________<wbr>_________________<br>
</div><div class="m_5120192530255944052m_3668654647680496873m_-8343946190022868319elided-text">Ws2-hr mailing list<br>
<a href="mailto:Ws2-hr@icann.org" target="_blank">Ws2-hr@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-hr" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ws2-hr</a><br>
</div></blockquote></div><br></div></div></div>
</blockquote></div></div>
</div></div><br>______________________________<wbr>_________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community<wbr>@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/accountability-cross-c<wbr>ommunity</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div>