<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">First, as a fellow rapporteur I understand the need to move forward, and to create something to react to. I do feel however that we are jumping the gun.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I would like to sign on to the concerns expressed by Bastiaan, who in turn is citing the concerns of Matthew and Tatiana.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Based on our discussions so far, we have no consensus on whether, to what extent, or how any of the UNGPs might be applied. Yet the document seems to start from the opposite assumption. That concerns me, as I don't think that makes the process shorter but rather complicates our process.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I'll paste in a statement that I made in comments to the document (apologies for not providing context):</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default"><font face="verdana, sans-serif">We are not merely seeing "where specific problems may be identified." That is tantamount to assuming the UNGPs are in, unless "problems can be identified." We are not operating under any such assumption. If anything, we are operating under the opposite assumption. We are seeing where the UNGPs can be applied to our work. In other words, no part of the UNGPs are in, unless there is consensus that they are in. Furthermore, there is no assumption that we are taking all or any part of the UNGP "as is" as opposed to being revised, modified, limited, etc. </font><br></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 Tue, Oct 4, 2016 at 4:36 AM, <span dir="ltr"><<a href="mailto:Jorge.Cancio@bakom.admin.ch" target="_blank">Jorge.Cancio@bakom.admin.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sorry, I forgot to add that I have included a series of comments in the Google doc - hope they are helpful<br>
Regards<br>
Jorge<br>
<br>
-----Ursprüngliche Nachricht-----<br>
Von: <a href="mailto:ws2-hr-bounces@icann.org">ws2-hr-bounces@icann.org</a> [mailto:<a href="mailto:ws2-hr-bounces@icann.org">ws2-hr-bounces@icann.<wbr>org</a>] Im Auftrag von <a href="mailto:Jorge.Cancio@bakom.admin.ch">Jorge.Cancio@bakom.admin.ch</a><br>
Gesendet: Dienstag, 4. Oktober 2016 10:06<br>
An: <a href="mailto:lists@nielstenoever.net">lists@nielstenoever.net</a><br>
Cc: <a href="mailto:ws2-hr@icann.org">ws2-hr@icann.org</a><br>
Betreff: Re: [Ws2-hr] New Draft Text for FoI<br>
<div class="HOEnZb"><div class="h5"><br>
Dear Niels<br>
<br>
thanks for this constructive and useful first draft on the issue.<br>
<br>
best<br>
<br>
Jorge<br>
<br>
Von meinem iPhone gesendet<br>
<br>
> Am 03.10.2016 um 17:07 schrieb Niels ten Oever <<a href="mailto:lists@nielstenoever.net">lists@nielstenoever.net</a>>:<br>
><br>
> Dear all,<br>
><br>
> I hope this e-mail finds you well. To ensure nothing of our<br>
> constructive discussions is getting lost, and to help us continue to<br>
> be very concrete, I would like to share with you the attached<br>
> document, that can also be found here (page 2 onwards):<br>
><br>
> <a href="https://docs.google.com/document/d/1emqmzyB9_0vm6oKxhIWZ47L7lxcFKUBHVn" rel="noreferrer" target="_blank">https://docs.google.com/<wbr>document/d/1emqmzyB9_<wbr>0vm6oKxhIWZ47L7lxcFKUBHVn</a><br>
> kBYUOsA2Q/edit<br>
><br>
> The document aims to represent a sedimentation of our discussion and<br>
> suggest a way forward, by providing potential text for the Framework<br>
> of Interpretation. Partially inspired by the reaction of John Ruggie<br>
> when I brought up our concerns with him.<br>
><br>
> I hope this proves to be useful, and I am more than happy to discuss<br>
> it with you all on the list and the call, and of course work on<br>
> suggestions and comments in the Google Doc.<br>
><br>
> Best,<br>
><br>
> Niels<br>
><br>
><br>
> --<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 <ICANN Bylaws Commentary<br>
> Table.doc> ______________________________<wbr>_________________<br>
> Ws2-hr mailing list<br>
> <a href="mailto:Ws2-hr@icann.org">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/<wbr>listinfo/ws2-hr</a><br>
______________________________<wbr>_________________<br>
Ws2-hr mailing list<br>
<a href="mailto:Ws2-hr@icann.org">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/<wbr>listinfo/ws2-hr</a><br>
______________________________<wbr>_________________<br>
Ws2-hr mailing list<br>
<a href="mailto:Ws2-hr@icann.org">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/<wbr>listinfo/ws2-hr</a><br>
</div></div></blockquote></div><br></div>