<html>
<body>
I can live with it either way, The wording I proposed was what was
mentioned on the call (by me) with no disagreement. 14 became semi
redundant with the change to 13, and the intent was that in addition to
the mandatory pointing to the R&R/B&R, Registrars/Resellers could
also point directly. With "..an additional best practice..",
additional to what?<br><br>
Alan<br><br>
At 08/09/2014 09:13 AM, James M. Bladel wrote:<br>
<blockquote type=cite class=cite cite="">I actually prefer the original
language on this. But maybe we can wordsmith something better
during our call.<br><br>
Thanks<br><br>
J.<br><br>
From: Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
><br>
Date: Sunday, September 7, 2014 at 23:45 <br>
To: Lars Hoffmann
<<a href="mailto:lars.hoffmann@icann.org">lars.hoffmann@icann.org</a>
>,
"<a href="mailto:gnso-irtpd@icann.org">gnso-irtpd@icann.org</a>
"
<<a href="mailto:gnso-irtpd@icann.org">gnso-irtpd@icann.org</a>><br>
Subject: Re: [gnso-irtpd] Updated Report<br><br>
One more small wording change. <br><br>
14 starts off with: <b>The WG recommends that, as an additional best
practice, ICANN accredited Registrars...<br><br>
</b>That should have been: <b>The WG recommends that, in addition, as a
best practice, ICANN accredited Registrars<br>
(See page 29 of the trascript -
<a href="http://gnso.icann.org/en/meetings/transcript-irtp-d-18aug14-en.pdf" eudora="autourl">
http://gnso.icann.org/en/meetings/transcript-irtp-d-18aug14-en.pdf</a> ot
at about minute 50 of the MP3).<br><br>
Alan a<br><br>
</b>At 07/09/2014 10:12 PM, Alan Greenberg wrote:<br>
<blockquote type=cite class=cite cite="">Sorry for the late comment.
<br><br>
Rec 13 now reads:<br><br>
<dl>
<dd><b>#13 The WG recommends that ICANN create and maintain a
user-friendly, one-stop website containing all relevant information
concerning disputed transfers and potential remedies to registrants. Such
a website should be clearly accessible from the ICANN Registrants'
Benefits and Responsibilities page (
<a href="https://www.icann.org/resources/pages/benefits-2013-09-16-en" eudora="autourl">
https://www.icann.org/resources/pages/benefits-2013-09-16-en</a>).<br><br>
</b>
</dl>I would suggest that "should be clearly accessible from"
be changed to "should be clearly accessible from or integrated
into"<br><br>
That gives those implementing the recommendation free reign to do this in
the most logical and "user-friendly" manner.<br><br>
I will be on at the start of the call, but will need to leave within a
few minutes, so if there are any questions about this, I would hope that
they can be addressed at the start of the meeting.<br><br>
Thanks, Alan<br><br>
At 29/08/2014 10:36 AM, Lars Hoffmann wrote:<br>
<blockquote type=cite class=cite cite="">Dear all,<br><br>
Apologies for the late distribution of this update but thanks to the
slight delay I was able to include comments from ICANN's GDD Team that
might be useful to the Group’s discussion. <br><br>
It would be great if you found some time to go through the Report –
especially the recommendations and observations in <b>Section 4</b> and
also consider the newly supplied comments from the GDD Team. <br><br>
Main edits from the last version are related to Charter Question F and
the additional recommendations 18 and 19. These can be found on pages 26,
27, 28, 29 and 30 – including the new Recommendation #19.<br><br>
Please also note the comments from ICANN’s GDD Team on:
<ul>
<li>page 14
<li>Page 16
<li>Page 18
<li>Page 22
<li>Page 24 (two comments)
<li>Page 26
<li>Page 28 (two comments)
<li>Page 30
<li>Page 42
</ul>Finally, please note that for ease of reading I have started the
latest changes from a clean copy, meaning that only the edits from the
last version are red-lined.<br><br>
Many thanks and have a good weekend and those lucky enough to have Monday
off – have a great Labour Day, too!<br><br>
Best,<br>
Lars<br>
</blockquote></blockquote></blockquote></body>
</html>