<div dir="ltr"><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small">Desperation you say, Dear Holly? Nooooooooo. Not!!!</div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small">Just plain common sense, if you look at the lay of the land. We have enough going on without more. And absent a definitive policy position reported from the RDS WG, I think its a fool's taask to keep going on about these matters.</div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small">-Carlton</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><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, Planning, Governance, Assessment & Turnaround</font></i></font><br>=============================</div></div></div></div>
<br><div class="gmail_quote">On Mon, Jan 9, 2017 at 4:43 PM, Holly Raiche <span dir="ltr"><<a href="mailto:h.raiche@internode.on.net" target="_blank">h.raiche@internode.on.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Thanks Leon<div><br></div><div>My recommendation for a VERY limited review is really more from desperation. And, since this is a really important issue for users. maybe we should revive something Rinalia started but I did for a couple of ICANN meetings - devote a couple of hours of ALAC time to explain policy issues in detail. (and those discussions have included discussion of Whois). So - in planning for Copenhagen, I would like to strongly suggest we make time for two things: a workshop on the Review, and time for ALAC to work through its thoughts on current policy issues. I am more than aware of the Hot Topic sessions - and to an extent they replace our policy sessions. But I am talking about specific sessions just to discuss what an ALAC policy position should be. (using Garth’s suggestion for an ALAC consideration of issues)</div><div><br></div><div>And top of my list - Whois - what it is and why there is so much discussion - and groups - on the issue. I’m sure there are others. But what this discussion has brought to my mind is that more of us should be at least a bit aware of the current policy issues before ICANN.</div><div><br></div><div>So Leon - you’re next</div><span class="HOEnZb"><font color="#888888"><div><br></div></font></span><div><span class="HOEnZb"><font color="#888888">Holly</font></span><div><div class="h5"><br><div><div>On 10 Jan 2017, at 8:20 am, León Felipe Sánchez Ambía <<a href="mailto:leonfelipe@sanchez.mx" target="_blank">leonfelipe@sanchez.mx</a>> wrote:</div><br class="m_1009534404477795391Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap:break-word">Thanks Holly,<div><br></div><div>If that is what you recommend, I am happy to follow. You’re experience in the subject and the discussions around it is extensive so I trust your recommendation is the best way to go.</div><div><br></div><div>On the other hand, I reiterate my willingness to work on the subject if required :-)</div><div><br></div><div><br><div><div>
<div>Best regards,</div><div><br></div><div><br></div><div>León</div>
</div>
<br><div><blockquote type="cite"><div>El 09/01/2017, a las 15:16, Holly Raiche <<a href="mailto:h.raiche@internode.on.net" target="_blank">h.raiche@internode.on.net</a>> escribió:</div><br class="m_1009534404477795391Apple-interchange-newline"><div><div style="word-wrap:break-word">Hi Leon<div><br></div><div>Careful - you may be pressed into service. As I have already said, the issues revolve around Whois information (Clause 3.3.1 RAA), what is published and who has access. And what we don’t need is yet another group looking at the same issues. So - again - PLEASE confine the review terms of reference</div><div><br></div><div>Holly</div><div><br></div><div><br><div><div>On 10 Jan 2017, at 8:03 am, León Felipe Sánchez Ambía <<a href="mailto:leonfelipe@sanchez.mx" target="_blank">leonfelipe@sanchez.mx</a>> wrote:</div><br class="m_1009534404477795391Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap:break-word">Thanks Alan,<div><br></div><div>If the case is that the review would be looking at the same issues that the WG would, then I would support reducing the scope as we did with the CCWG in order to avoid duplicative efforts.</div><div><br></div><div>In any case I put my work where my mouth is and should there be the need to join the RDS WG, count me in.</div><div><br></div><div><br></div><div><div>
<div>Best regards,</div><div><br></div><div><br></div><div>León</div>
</div>
<br><div><blockquote type="cite"><div>El 09/01/2017, a las 00:08, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>> escribió:</div><br class="m_1009534404477795391Apple-interchange-newline"><div>
<div>
To be clear, the issue was never staff support. The reduced scope came
from the volunteer community because of the worry that the same people
who were working on other RDS-related work (and particularly the GNSO
PDP) would be the ones to best serve on this RT.<br><br>
That is largely the same logic used by the CCWG-Accountability for
suggesting that the scope of ATRT3 be reduced.<br><br>
I'm not arguing for or against, just wanted to make sure we are all on
the same page.<br><br>
Alan<br><br>
At 09/01/2017 12:28 AM, León Felipe Sánchez AmbÃa wrote:<br>
<blockquote type="cite" class="m_1009534404477795391cite">I agree with Tijani. The widened
scope seems justified although it will surely require more staff support.
<br><br>
Kind regards,<br><br>
León <br><br>
Enviado desde mi iPhone<br><br>
El ene. 8, 2017, a las 11:02 PM, Tijani BEN JEMAA
<<a href="mailto:tijani.benjemaa@benjemaa.com" target="_blank">
tijani.benjemaa@benjemaa.com</a>> escribió:<br><br>
<blockquote type="cite" class="m_1009534404477795391cite"><font color="#002E7A">
Alan,</font><br>
<font color="#002E7A"><br>
I understand the issue of bandwidth but would accept the GNSO
proposal because of the merit of the wide scope. In our comment we should
note that we support the wide scope assuming that more time and more
staff support would be provided to the review team.<br>
</font><br>
------------------------------<wbr>------------------------------<wbr>-----------------<br>
<b>Tijani BEN JEMAA<br>
</b>Executive Director<br>
Mediterranean Federation of Internet Associations (<b>FMAI</b>)<br>
Phone: <a href="tel:+216%2098%20330%20114" value="+21698330114" target="_blank">+216 98 330 114</a><br>
<a href="tel:+216%2052%20385%20114" value="+21652385114" target="_blank">+216 52 385 114</a><br>
------------------------------<wbr>------------------------------<wbr>-----------------<br>
<br>
<br>
<blockquote type="cite" class="m_1009534404477795391cite">Le 9 janv. 2017 Ã 05:07,
Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>
> a écrit :<br><br>
I am attaching a document from the GNSO on the proposed RDS (formerly
WHOIS) Review to be started very soon.<br><br>
You will recall that we previously had approved a narrowing of the scope
of the RDS Review to focus just on the extent to which the previous WHOIS
Review Recommendations had been implemented. This GNSO proposal widens
the scope considerably. Although there is no question that the wider
scope is interesting and ptentially useful, it will also require far more
community involvement that the earlier proposal.<br><br>
The call for volunteers was to close on 13 January and a decision needs
to be made quickly on exactly what the Review should be.<br><br>
Comments please, with some urgency.<br><br>
Alan<br><br>
<br>
<blockquote type="cite" class="m_1009534404477795391cite">From: "James M.
Bladel"
<<a href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a>><br>
Subject: Re: RDS Review<br>
Date: Sun, 8 Jan 2017 17:42:53 +0000<br><br>
<br>
Dear Karen and Community Leaders –<br><br>
The GNSO Council, working wiith its component Stakeholder Groups and
Constituencies, has produced this document (attached), which outlines our
feedback and concerns with the proposed “limited scope†for the
upcominoming RDS review. The document was submitted to ICANN Staff,
and sharing with this team for your reference.<br><br>
Thank you,<br><br>
J.<br>
----------------<br>
James Bladel<br>
GNSO Chair</blockquote><GNSO Council feedback on
RDS.pdf>______________________<wbr>_________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" target="_blank">http://www.atlarge.icann.org</a>
<br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">
https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a>
</blockquote><br>
______________________________<wbr>_________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" target="_blank">http://www.atlarge.icann.org</a>
<br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">
https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a>
</blockquote></blockquote></div>
</div></blockquote></div><br></div></div>______________________________<wbr>_________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>At-Large Online: <a href="http://www.atlarge.icann.org" target="_blank">http://www.atlarge.icann.org</a><br>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a></blockquote></div><br></div></div></div></blockquote></div><br></div></div></div></blockquote></div><br></div></div></div></div><br>______________________________<wbr>_________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer" target="_blank">https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a><br></blockquote></div><br></div>