<html>
<body>
I largely tend to agree, although I do believe that we are seeing a case
of "Don't presume conspiracy when incompetence explain
it".<br><br>
But I do think we will have to spend some time crafting a reply to post
to the comment once we get some hard financial data. That is a
distraction we didn't need.<br><br>
Alan<br><br>
At 16/05/2018 02:08 PM, Susan Kawaguchi wrote:<br><br>
<blockquote type=cite class=cite cite="">I agree with Chris, except on
the secret motive, and think we should continue on with our work until
the community provides their comments and ICANN provides an in depth
report on those comments. By that time we will have most of our
work completed. I am working diligently to provide the draft
reports I am responsible for by the May 24th deadline. <br><br>
It should be business as usual. <br><br>
Hopefully, ICANN org will continue to learn about how to treat RT's.
<br>
"Sigh"... <br><br>
On Wed, May 16, 2018 at 12:47 PM, Chris Disspain
<<a href="mailto:chris@disspain.uk">chris@disspain.uk</a>>
wrote:<br>
<dl>
<dd>Hi All,<br><br>
<dd>1. ICANN does not ‘want to pause’. ICANN is asking the community
what they want to do. There is no secret motive nor any attempt to
manipulate the situation. <br><br>
<dd>2. I accept that a heads up would have been appropriate.<br><br>
<dd>3. Please let us try to concentrate on the actual issue rather than
the minor irritants. In the same way as the RT has asked itself on a
number of occasions whether it can usefully re-time its work, in the
context of the community looking at all reviews and figuring out how best
to manage them both from a resource and budget point of view, it would be
odd not to ask the same question. <br><br>
<dd>4. My personal view is that we should continue. <br><br>
<dd>5. I recommend that the RT respond to the call for comment ASAP with
a note acknowledging that we serve at the behest of the community,
summarising where we are at with the work and our timing going forward
and saying that the RT believes it should continue (assuming we do think
that). <br><br>
<dd>Cheers,<br><br>
<dd>Chris<br><br>
<dd>On 16 May 2018, at 07:23, Volker Greimann
<<a href="mailto:vgreimann@key-systems.net">
vgreimann@key-systems.net</a>> wrote:<br><br>
<blockquote type=cite class=cite cite="">
<dd>Hi Alan,<br><br>
<dd>I absolutely agree that it is strange that ICANN seems to want to
pause this without consulting us first. But as this is the cards we have
been dealt, we need to figure out how to play them and in this case I
vote for following the community consensus, if any. <br><br>
<dd>As for Monday, it is a public holiday that I will be travelling
on.<br><br>
<dd>Best,<br><br>
<dd>Volker<br><br>
<dd>Am 16.05.2018 um 16:08 schrieb Alan Greenberg:<br>
<blockquote type=cite class=cite cite="">
<dd>Volker, <br><br>
<dd>Of course we serve at the pleasure of the community. <br><br>
<dd>The question is process and timing. That this was done with no
consultation with us, I find strange. But the really difficult part is
that we are being told to keep on working (and I have confirmed that this
is the intent) with a target of having a draft report complete just after
the July F2F, and at THAT point, we may be told to scrap part of what we
have been working on between now an then, or put the entire project on
hold for some indeterminate time, and when it resumes it may be with a
different team and much of the work will have to be redone.<br><br>
<dd>We will discuss this further at the Monday meeting, and for those who
will not be there, your input is appreciated ahead of time.<br><br>
<dd>Susan has suggested that we go back to our appointing groups for
their input.<br><br>
<dd>Alan<br><br>
<br><br>
<br>
<dd>At 16/05/2018 06:03 AM, Volker Greimann wrote:<br><br>
<br>
<blockquote type=cite class=cite cite=""><br>
<dd><pre>We serve at the pleasure of
<dd>the community, so I would not object to any
<dd>consensus position either way. While a) is the most logical choice,
<dd>preserving most of our work efforts so far, the others also have some
<dd>merit due to the changes ahead. And as ICANN has just thrown another
<dd>curve-ball in the form of the proposed temporary specification, more
<dd>change seems to be on the horizon, which could further outdate our
work
<dd>product.
<dd>Best,
<dd>Volker
<dd>Am 16.05.2018 um 04:30 schrieb Alan Greenberg:
<dd>> I call your attention to a Public Comment (PC) launched
yesterday
<dd>> asking for input on alternatives to alter the RDS-WHOIS2-RT
Scope
<dd>and
<dd>> plans (as well possible changes to the not yet started ATRT3) -
<dd>>
<dd>
<a href="https://www.icann.org/public-comments/specific-reviews-short-term-timeline-2018-05-14-en" eudora="autourl">
https://www.icann.org/public-comments/specific-reviews-short-term-timeline-2018-05-14-en</a>
.
<dd>>
<dd>> I proposes three possible scenarios for our RT:
<dd>>
<dd>> a) Proceeds as planned;
<dd>>
<dd>> b) reduce scope to just an analysis of the WHOIS1-RT
<dd>Recommendations;
<dd>>
<dd>> c) pause the review entirely for some as yet to be determined
time.
<dd>>
<dd>> If recommended by the community, b) and c) would require our
<dd>> agreement. The implications of a community recommendation that
we
<dd>> refused to agree with are not known. If there is a pause, it is
not
<dd>> clear when the unpause would happen and to what extent it would
be
<dd>the
<dd>> same team moving forward.
<dd>>
<dd>> The PC ends on 06 July 2018 and the report on input received is
due
<dd>on
<dd>> 23 July 2018, a few days before we are currently planning to
meet in
<dd>> Brussels to close-to-finalize our report.
<dd>>
<dd>> Although the PC was issues yesterday, neither I nor Susan and
<dd>Cathrin
<dd>> had any prior knowledge of it and in fact we only heard of it
<dd>today.
<dd>>
<dd>> We have initiated discussions with MSSI on exactly what this
means
<dd>and
<dd>> will get back when I have a better understanding.
<dd>>
<dd>> Alan
<dd>>
<dd>> _______________________________________________
<dd>> RDS-WHOIS2-RT mailing list
<dd>>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt">
<dd>RDS-WHOIS2-RT at icann.org</a>
<dd>>
<dd>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" eudora="autourl">
https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a>
<dd>--
<dd>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
<dd>Mit freundlichen Grüßen,
<dd>Volker A. Greimann
<dd>- Rechtsabteilung -
<dd>Key-Systems GmbH
<dd>Im Oberen Werk 1
<dd>66386 St. Ingbert
<dd>Tel.: +49 (0) 6894 - 9396 901
<dd>Fax.: +49 (0) 6894 - 9396 851
<dd>Email:
<dd><a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt">
vgreimann
<dd>at key-systems.net</a>
<dd>Web:
<dd><a href="http://www.key-systems.net/" eudora="autourl">
www.key-systems.net</a> /
<dd><a href="http://www.rrpproxy.net/">www.RRPproxy.net</a>
<dd><a href="http://www.domaindiscount24.com/" eudora="autourl">
www.domaindiscount24.com</a> /
<dd><a href="http://www.brandshelter.com/" eudora="autourl">
www.BrandShelter.com</a>
<dd>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<dd><a href="http://www.facebook.com/KeySystems" eudora="autourl">
www.facebook.com/KeySystems</a>
<dd><a href="http://www.twitter.com/key_systems" eudora="autourl">
www.twitter.com/key_systems</a>
<dd>Geschäftsführer: Alexander Siffrin
<dd>Handelsregister Nr.: HR B 18835 - Saarbruecken
<dd>Umsatzsteuer ID.: DE211006534
<dd>Member of the KEYDRIVE GROUP
<dd><a href="http://www.keydrive.lu/">www.keydrive.lu</a>
<dd>Der Inhalt dieser Nachricht ist vertraulich und nur für den
angegebenen
<dd>Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung
oder
<dd>Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte
diese
<dd>Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit
uns
<dd>per E-Mail oder telefonisch in Verbindung zu setzen.
<dd>--------------------------------------------
<dd>Should you have any further questions, please do not hesitate to
contact
<dd>us.
<dd>Best regards,
<dd>Volker A. Greimann
<dd>- legal department -
<dd>Key-Systems GmbH
<dd>Im Oberen Werk 1
<dd>66386 St. Ingbert
<dd>Tel.: +49 (0) 6894 - 9396 901
<dd>Fax.: +49 (0) 6894 - 9396 851
<dd>Email:
<dd><a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt">
vgreimann
<dd>at key-systems.net</a>
<dd>Web:
<dd><a href="http://www.key-systems.net/" eudora="autourl">
www.key-systems.net</a> /
<dd><a href="http://www.rrpproxy.net/">www.RRPproxy.net</a>
<dd><a href="http://www.domaindiscount24.com/" eudora="autourl">
www.domaindiscount24.com</a> /
<dd><a href="http://www.brandshelter.com/" eudora="autourl">
www.BrandShelter.com</a>
<dd>Follow us on Twitter or join our fan community on Facebook and stay
<dd>updated:
<dd><a href="http://www.facebook.com/KeySystems" eudora="autourl">
www.facebook.com/KeySystems</a>
<dd><a href="http://www.twitter.com/key_systems" eudora="autourl">
www.twitter.com/key_systems</a>
<dd>CEO: Alexander Siffrin
<dd>Registration No.: HR B 18835 - Saarbruecken
<dd>V.A.T. ID.: DE211006534
<dd>Member of the KEYDRIVE GROUP
<dd><a href="http://www.keydrive.lu/">www.keydrive.lu</a>
<dd>This e-mail and its attachments is intended only for the person to
whom
<dd>it is addressed. Furthermore it is not permitted to publish any
content
<dd>of this email. You must not use, disclose, copy, print or rely on
this
<dd>e-mail. If an addressing or transmission error has misdirected this
<dd>e-mail, kindly notify the author by replying to this e-mail or
contacting
<dd>us by telephone.
</pre></blockquote></blockquote><br><br>
<dd><pre>--
<dd>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
<dd>Mit freundlichen Grüßen,
<dd>Volker A. Greimann
<dd>- Rechtsabteilung -
<dd>Key-Systems GmbH
<dd>Im Oberen Werk 1
<dd>66386 St. Ingbert
<dd>Tel.: +49 (0) 6894 - 9396 901
<dd>Fax.: +49 (0) 6894 - 9396 851
<dd>Email:
<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
<dd>Web: <a href="http://www.key-systems.net">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" eudora="autourl">www.RRPproxy.net</a>
<dd><a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a>
/
<a href="http://www.brandshelter.com/" eudora="autourl">
www.BrandShelter.com</a>
<dd>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<dd><a href="http://www.facebook.com/KeySystems">
www.facebook.com/KeySystems</a>
<dd><a href="http://www.twitter.com/key_systems" eudora="autourl">
www.twitter.com/key_systems</a>
<dd>Geschäftsführer: Alexander Siffrin
<dd>Handelsregister Nr.: HR B 18835 - Saarbruecken
<dd>Umsatzsteuer ID.: DE211006534
<dd>Member of the KEYDRIVE GROUP
<dd><a href="http://www.keydrive.lu">www.keydrive.lu</a>
<dd>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.
<dd>--------------------------------------------
<dd>Should you have any further questions, please do not hesitate to
contact us.
<dd>Best regards,
<dd>Volker A. Greimann
<dd>- legal department -
<dd>Key-Systems GmbH
<dd>Im Oberen Werk 1
<dd>66386 St. Ingbert
<dd>Tel.: +49 (0) 6894 - 9396 901
<dd>Fax.: +49 (0) 6894 - 9396 851
<dd>Email:
<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
<dd>Web: <a href="http://www.key-systems.net">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" eudora="autourl">www.RRPproxy.net</a>
<dd><a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a>
/
<a href="http://www.brandshelter.com/" eudora="autourl">
www.BrandShelter.com</a>
<dd>Follow us on Twitter or join our fan community on Facebook and stay
updated:
<dd><a href="http://www.facebook.com/KeySystems">
www.facebook.com/KeySystems</a>
<dd><a href="http://www.twitter.com/key_systems" eudora="autourl">
www.twitter.com/key_systems</a>
<dd>CEO: Alexander Siffrin
<dd>Registration No.: HR B 18835 - Saarbruecken
<dd>V.A.T. ID.: DE211006534
<dd>Member of the KEYDRIVE GROUP
<dd><a href="http://www.keydrive.lu">www.keydrive.lu</a>
<dd>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><br>
<dd>_______________________________________________
<dd>RDS-WHOIS2-RT mailing list<br>
<dd><a href="mailto:RDS-WHOIS2-RT@icann.org">RDS-WHOIS2-RT@icann.org</a>
<br>
<dd>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" eudora="autourl">
https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a></blockquote><br>
<dd>_______________________________________________<br>
<dd>RDS-WHOIS2-RT mailing list<br>
<dd><a href="mailto:RDS-WHOIS2-RT@icann.org">RDS-WHOIS2-RT@icann.org</a>
<br>
<dd>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" eudora="autourl">
https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a><br>
<br>
</dl><br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;YTOPR01MB0396;27:kvy5XA00QHUCMafejnUZZy4hM1iMKt0R4knQUrlNQYWDwE9nYtVK/8uhrS+4WG7kFDxbchkspCuuDX1Ve8e/PdDszZGbEjKidhc49/eeGJU7YfMSHoyXFvZ2PfUAFnOo<br>
X-Microsoft-Antispam-Message-Info:<br>
<x-tab> </x-tab>
HYPZrxfZy2UCpaTx5sgMU15AzjHMvqsEfJm8/WPFqWnGkT5ZOlZ3tGJHBbEmvyq4AQ0zuHaSkK90jMQLYVQWWxZfmmk+z8K6J6HtxbgXa/zs9+1kVRFzKhe2LMtwE5sXoXd2DO3jgP1Q/jxwXloQ54OfzGNThkHo33m8gw/bupgGmErSrU32XF5WBZyj707oS56L4gvKUE3d1pJnUL/UhoeuRZIJIvF86i2IGbQrdvoUPOhYA/7hOucCmi0a6ofoqI/nASyCQsxWVsy9U5dOJ9htHMo90Ji2ncQqmqFjZJSXcWB/w0zaADAsYgMBb+JuaKEsV7VtS4hQI26UTUFxpimP/YSTLyHCeDGrPm1b4IrRWpiQRpfY5Rd6u04a7eARVOh5OPnZUlyshuTh8Zl5pNnrTNjkLWal/yFIO8ahp9oMZ9hN668EFeklAVWKAPSqY3UUUGg3iqsyUv4FwQbGFOqYg4iZ+NrzJe4cCtRO3UXK3AU3gkul0poDvZaPgZuCVS9IKfsjaLrztbWa/th+/g==<br>
<br>
_______________________________________________<br>
RDS-WHOIS2-RT mailing list<br>
RDS-WHOIS2-RT@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" eudora="autourl">
https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a></blockquote>
</body>
</html>