<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Indeed, this difference in use always confused me. I learned that
it means delaying a proposal as well, not raising it.</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 21.06.2018 um 17:13 schrieb Carlton
Samuels:<br>
</div>
<blockquote type="cite"
cite="mid:CAOZQb9TZrU4LHRoC7FhimVUvqvFZkSr0fyhEB2oZ=UDxhkE5cw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:large">True
about the meaning assigned 'tabling' and 'tabled'; in my part
of the world its a parliamentary action that is used to 'park'
or delay discussion on a matter before a committee. -;)</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:large"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:large">One
small comment per Slide 4. It really isn't ICANN's thing to
comply with national laws - save and except U.S. law in
general and California law in particular - but the contracted
parties. When I was a corporate officer we used to sign
contracts that mutually bind parties to adjudication of
disputes in a third country's court. In ICANN's case, the
Procedure for Handling Conflicts with National [Privacy] Laws
is the evidence to support my contention; really a 'get out of
jail' card for the contracted parties.</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:large"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:large">-Carlton</div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div><br>
==============================<br>
<i><font face="comic sans ms, sans-serif">Carlton A
Samuels</font></i><br>
<font face="comic sans ms, sans-serif"><i>Mobile:
876-818-1799<br>
<font color="#33CC00">Strategy, Process,
Governance, Assessment & Turnaround</font></i></font><br>
=============================</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Thu, Jun 21, 2018 at 9:19 AM Stephanie Perrin
<<a href="mailto:stephanie.perrin@mail.utoronto.ca"
moz-do-not-send="true">stephanie.perrin@mail.utoronto.ca</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">The edits are
great, thank you Susan! Tabling is a confusing term
for many, means different things in different
countries.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">cheers
Stephanie</font></font><br>
</p>
<div class="m_-6122632131265940225moz-cite-prefix">On
2018-06-20 22:15, Lisa Phifer wrote:<br>
</div>
<blockquote type="cite">All, <br>
<br>
Attached are updated slides for the "Anything New"
subgroup section of the ICANN62 Engagement Session slide
deck. This update includes two additions: <br>
<br>
1) A table from the subgroup's report, listing all
policies and procedures considered. Some table cells that
were previously empty have been filled in to identify
which subgroup is handling the associated
policy/procedure. <br>
<br>
2) Two new issues supplied by Stephanie in response to her
action item, along with two edits suggested by Stephanie
(see comment on that slide) <br>
<br>
Thanks to Stephanie and Susan for these inputs. These
updated slides will now be folded into the ICANN62 master
deck. Corresponding edits should be made to the subgroup
report to maintain alignment. <br>
<br>
Best, Regards <br>
Lisa<br>
<br>
<fieldset
class="m_-6122632131265940225mimeAttachmentHeader"></fieldset>
<pre class="m_-6122632131265940225moz-quote-pre">_______________________________________________
RDS-WHOIS2-RT mailing list
<a class="m_-6122632131265940225moz-txt-link-abbreviated" href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank" moz-do-not-send="true">RDS-WHOIS2-RT@icann.org</a>
<a class="m_-6122632131265940225moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
RDS-WHOIS2-RT mailing list<br>
<a href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank"
moz-do-not-send="true">RDS-WHOIS2-RT@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a><br>
</blockquote>
</div>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
RDS-WHOIS2-RT mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RDS-WHOIS2-RT@icann.org">RDS-WHOIS2-RT@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt">https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
</pre>
</body>
</html>