<div dir="ltr">Dear all, <div><br></div><div>I apologise in advance for not being able to make it to tomorrow's call since I will be held at work until late evening CET. </div><div><br></div><div>While there will probably be more discussions of this topic tomorrow, I have prepared a skeleton draft recommendation as a google doc so that we can start working towards our final objective, since it does seem at this point that there is a form of consensus emerging on both the fact that this is an issue and over solutions. </div><div><br></div><div><a href="https://docs.google.com/document/d/1xAyla8FTaL7jZ0D2rYtAzQUr3gEnirTKiAG-kqD0ZSs/edit?usp=sharing">https://docs.google.com/document/d/1xAyla8FTaL7jZ0D2rYtAzQUr3gEnirTKiAG-kqD0ZSs/edit?usp=sharing</a> <br></div><div><br></div><div>To be very honest I do not know of the formal or even substantive requirements for recommendations, so I just took some ideas from the OFAC one.</div><div><br></div><div>I guess at this point is just for everyone to jump in and contribute, as this is far from complete (and maybe even accurate.) I will myself be adding more materials from our discussions into this during the coming week. </div><div><br></div><div>I remember Greg you said you would prepare some form of wrap-up/forward looking document, in any case (and especially if yours is more fleshed out) feel free to incorporate whatever can be incorporated from this one into yours so that we work in a single document. </div><div><br></div><div>Best, </div><div><br></div><div>Raphael </div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-09-14 17:37 GMT+02:00 Mueller, Milton L <span dir="ltr"><<a href="mailto:milton@gatech.edu" target="_blank">milton@gatech.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">As long as registries have the choice, a regional "menu" approach seems ok to me.<br>
<span class="im HOEnZb"><br>
> -----Original Message-----<br>
> From: Paul Rosenzweig [mailto:<a href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@<wbr>redbranchconsulting.com</a>]<br>
> Sent: Wednesday, September 13, 2017 11:25 AM<br>
> To: Mueller, Milton L <<a href="mailto:milton@gatech.edu">milton@gatech.edu</a>>; <a href="mailto:ws2-jurisdiction@icann.org">ws2-jurisdiction@icann.org</a><br>
> Subject: RE: [Ws2-jurisdiction] [EXTERNAL] issues on applicable law<br>
><br>
</span><div class="HOEnZb"><div class="h5">> We can't avoid inconsistency altogether if there is more than one jurisdiction<br>
> involved. Almost by definition, with more than one jurisdiction available the<br>
> risk of inconsistency and uncertainty is heightened.<br>
><br>
> At the other end of the spectrum is a world with 190+ jurisdictions. In that<br>
> context the risk of inconsistency is at its maximum.<br>
><br>
> I personally have no concerns about the use of California law exclusively.<br>
> Others in the community, however, do have those concerns. A menu option<br>
> with a few regional choices seems to answer those concerns without a huge<br>
> increase in the risk of inconsistency -- especially if it is accompanied by an<br>
> urge toward uniformity in areas where uniformity is most essential (like<br>
> operational issues).<br>
><br>
> It is an imperfect solution -- offered in the spirit of compromise, not as a<br>
> canonically correct exposition of principle.<br>
><br>
> Paul<br>
><br>
> Paul Rosenzweig<br>
> <a href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@<wbr>redbranchconsulting.com</a><br>
> O: +1 (202) 547-0660<br>
> M: +1 (202) 329-9650<br>
> VOIP: +1 (202) 738-1739<br>
> <a href="http://www.redbranchconsulting.com" rel="noreferrer" target="_blank">www.redbranchconsulting.com</a><br>
> My PGP Key:<br>
> <a href="https://keys.mailvelope.com/pks/lookup?op=get&search=0x9A830097CA06" rel="noreferrer" target="_blank">https://keys.mailvelope.com/<wbr>pks/lookup?op=get&search=<wbr>0x9A830097CA06</a><br>
> 6684<br>
><br>
> -----Original Message-----<br>
> From: Mueller, Milton L [mailto:<a href="mailto:milton@gatech.edu">milton@gatech.edu</a>]<br>
> Sent: Wednesday, September 13, 2017 10:22 AM<br>
> To: Paul Rosenzweig <<a href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@<wbr>redbranchconsulting.com</a>>;<br>
> <a href="mailto:ws2-jurisdiction@icann.org">ws2-jurisdiction@icann.org</a><br>
> Subject: RE: [Ws2-jurisdiction] [EXTERNAL] issues on applicable law<br>
><br>
> Very interesting post Paul. But, are you agreeing or disagreeing with the<br>
> "menu" being based on regions? If you are agreeing, then how do we avoid<br>
> this problem:<br>
><br>
> > And we cannot, from an accountability perspective, want a world in<br>
> > which there are inconsistent results and how a contract provision is<br>
> > enforced depends on whether the suit is brought in Europe or in Asia.<br>
> > That type of uncertainty is also the enemy of accountability. Thus, I<br>
> > disagree with the submission that the presumption should be that the<br>
> > law of the registry apply to the agreement. That way lies chaos.<br>
> ><br>
<br>
______________________________<wbr>_________________<br>
Ws2-jurisdiction mailing list<br>
<a href="mailto:Ws2-jurisdiction@icann.org">Ws2-jurisdiction@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/ws2-jurisdiction</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr">Raphaël Beauregard-Lacroix<div><a href="https://www.linkedin.com/in/rapha%C3%ABl-beauregard-lacroix-88733786/" style="font-size:12.8px" target="_blank">LinkedIn</a><span style="font-size:12.8px"> - </span><a href="https://twitter.com/rbl0112" style="font-size:12.8px" target="_blank">@rbl0012</a><span style="font-size:12.8px"> - M: </span><span style="font-size:small">+33 7 86 39 18 15</span><br></div><div><br></div><div><br></div></div></div></div></div></div></div>
</div>