<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks Wolf-Ulrich. Why would it be a problem if the final proposal was submitted in parts? I am not suggesting that that would be ideal, but I am curious
to your perspective.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> WUKnoben [mailto:wolf-ulrich.knoben@t-online.de]
<br>
<b>Sent:</b> Saturday, October 11, 2014 7:59 PM<br>
<b>To:</b> Gomes, Chuck; Kieren McCarthy; Olivier MJ Crepin-Leblond<br>
<b>Cc:</b> cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] Request for Interpretation on the calls<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">As a member of the ICG – but not speaking on behalf of them – I would see this approach as very helpful.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Calibri","sans-serif";color:black">However, as you know the ICG target is to submit a common proposal re the three “operational” lines (names, addresses, protocols). So timeline coordination
between those 3 should start as early as possible, too. A situation should be avoided where – due to a time gap of providing the 3 sub-proposals – a discussion takes place to fraction the submission of the final proposal.<br>
<br>
Best regards<br>
<br>
Wolf-Ulrich<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
<a href="mailto:cgomes@verisign.com" title="cgomes@verisign.com">Gomes, Chuck</a>
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Sent:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> Saturday, October 11, 2014 3:51
PM<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">To:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
<a href="mailto:kierenmccarthy@gmail.com" title="kierenmccarthy@gmail.com">Kieren McCarthy</a> ;
<a href="mailto:ocl@gih.com" title="ocl@gih.com">Olivier MJ Crepin-Leblond</a> <o:p>
</o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Cc:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
<a href="mailto:cwg-stewardship@icann.org" title="cwg-stewardship@icann.org">cwg-stewardship@icann.org</a>
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Subject:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> Re: [CWG-Stewardship] Request
for Interpretation on the calls<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I want to be clear that I am not opposed to Kieran’s suggestions, but as he indicates at least in part, they will require more time. To do a valid bottom up
process it was already not possible to meet the deadline of January 15. This will move the date out further. But that is okay in my opinion. It is better to do this thing right than doing it fast, while at the same time doing everything within reason to
work as quickly as possible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I think what the CWG needs to do is to develop a reasonable timeline for our work including translation services and send that to the ICG. It is insufficient
for us to simply say we need more time; we need to show them why with a reasonable target.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>
<a href="mailto:[mailto:cwg-stewardship-bounces@icann.org]">[mailto:cwg-stewardship-bounces@icann.org]</a>
<b>On Behalf Of </b>Kieren McCarthy<br>
<b>Sent:</b> Saturday, October 11, 2014 7:57 AM<br>
<b>To:</b> Olivier MJ Crepin-Leblond<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] Request for Interpretation on the calls<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Hello all,<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">I just reviewed the timeline for the CWG. With respect to transition: there is no way it can be done effectively under the current timeline. So:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">1. Is the timeline end point moveable? (I assume it is designed to fit it with the other group's deadline)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">2. If it is moveable, we need to add two weeks to it- first to translate the draft proposal and second to translate comments received in other languages.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">3. If it is not moveable, translation and the inclusion of languages other than English is going to require significantly more planning than just referring to ICANN policy. The timeline is already optimistically
tight.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">4. I would propose that the group recognize the importance of providing its information and considering comments in languages other than English and select someone (Olivier?) whose role it is to identify how best
that can be done. The group would also need to agree not to move on until it has provided an equal opportunity for all language speakers to review and comment on the proposal.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">5. My best bet is that to be effective, translation of the draft doc in December would need to be done in two stages- first when it is nearly compete and second when it is. This will speed up the process considerably.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">6. The chosen language person would need to judge when they can best send a working copy of the draft document, as it is being written, for translation. My best guess would be a week or so before its release. BUT
this does mean that the larger group should try to avoid deadline-itis where most of the writing is done in the last few days.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">7. If the "draft draft" is translated, it will be much faster to create a translation of the final draft. And so it may not break the timeline.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">8. Realistically, there will only be time to translate non-English comments into English for review and consideration by the group. The chosen language person would, I think, need to send those comments off for
translation in small batches as they come in rather than wait until the end of the comment period.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">9. The biggest and most important issue would be to prepare non-English speakers for the arrival of the translated draft, including explaining ahead of time and in very clear language what the draft will be, why
it is important, when they should expect it and in what timeframe they would need to respond.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Without this preparation, because all the CWG work will be carried out in English, there is a substantial risk that the report will simply appear in other languages and then effectively vanish again as the comment
deadline passes. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">In other words, the whole thing would be a complete waste of time and energy as well as reinforce the (incorrect) notion that non-English speakers are not present or needed in ICANN processes.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">10. If this group is not able or willing to do these extra steps, for whatever reason (and tbh it does look like a tricky proposition), then I think the best option is to be honest and upfront and say this particular
process will be in English- and then point to where in the broader process languages other than English will be given equal consideration.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">My thoughts, hope they are helpful.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Kieren<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><br>
-<br>
[sent through phone]<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p><span style="color:black">On Fri, Oct 10, 2014 at 3:00 PM, Olivier MJ Crepin-Leblond <<a href="mailto:ocl@gih.com" target="_blank">ocl@gih.com</a>> wrote:<o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p><span style="color:black">Dear Jonathan, <br>
Dear Byron, <br>
<br>
I draw your attention to my email to the CWG Stewardship mailing list <br>
sent on behalf of the At-Large working group that feeds into the CWG. <br>
May I take the opportunity of also reflecting that in addition to <br>
interpretation, many feel that the documents themselves that are under <br>
review should also be available in the UN 6 languages in line with the <br>
ICANN language policy. <br>
<br>
I remind you that the path to a true globalisation of ICANN starts with <br>
following its own language policy. Please be so kind to make sure we do <br>
not stumble at the first barrier that's the language barrier. <br>
<br>
Kind regards, <br>
<br>
Olivier <br>
<br>
On 07/10/2014 18:19, Olivier MJ Crepin-Leblond wrote: <br>
> Dear interim co-chairs of the CWG to Develop an IANA Stewardship <br>
> Transition Proposal on Naming Related Functions, <br>
> <br>
> The ALAC working group that feeds into the CWG on Stewardship Transition <br>
> (short version of the full name "CWG to Develop an IANA Stewardship <br>
> Transition Proposal on Naming Related Functions") as well as the IANA <br>
> Coordination Group (ICG) has discussed the issue of the CWG on <br>
> Stewardship Transition having no interpretation on its first call. <br>
> <br>
> Understandably, the work of the CWG on Stewardship Transition is going <br>
> to be under the spotlight. This being a Global effort, the CWG needs to <br>
> operate in line with ICANN language policy. We therefore ask for the <br>
> CWG's calls to be interpreted in the 6 UN Languages in line with ICANN <br>
> language policy. As globalisation of ICANN is so often advertised, ICANN <br>
> should set the standard in this process. <br>
> <br>
> Kindest regards, <br>
> <br>
> Olivier MJ Crépin-Leblond <br>
> (for the ALAC IANA Issues WG) <br>
> <br>
> <br>
> _______________________________________________ <br>
> CWG-Stewardship mailing list <br>
> <a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a> <br>
> <a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
<br>
> <br>
<br>
_______________________________________________ <br>
CWG-Stewardship mailing list <br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a> <br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
<o:p></o:p></span></p>
</blockquote>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>