<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=Generator content="Microsoft Word 14 (filtered medium)">
<STYLE>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<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>
</HEAD>
<BODY lang=EN-US dir=ltr link=blue vLink=purple>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>The three parts should be consistent to each other which couldn’t be
assured if not submitted as a whole.</DIV>
<DIV><BR>Best regards<BR><BR>Wolf-Ulrich<BR><BR></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=cgomes@verisign.com
href="mailto:cgomes@verisign.com">Gomes, Chuck</A> </DIV>
<DIV><B>Sent:</B> Saturday, October 11, 2014 5:21 PM</DIV>
<DIV><B>To:</B> <A title=wolf-ulrich.knoben@t-online.de
href="mailto:wolf-ulrich.knoben@t-online.de">WUKnoben</A> ; <A
title=kierenmccarthy@gmail.com href="mailto:kierenmccarthy@gmail.com">Kieren
McCarthy</A> ; <A title=ocl@gih.com href="mailto:ocl@gih.com">Olivier MJ
Crepin-Leblond</A> </DIV>
<DIV><B>Cc:</B> <A title=cwg-stewardship@icann.org
href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</A> </DIV>
<DIV><B>Subject:</B> RE: [CWG-Stewardship] Request for Interpretation on the
calls</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; 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: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d'>Chuck<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<DIV>
<DIV
style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<P class=MsoNormal><B><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"'>From:</SPAN></B><SPAN
style='FONT-SIZE: 10pt; 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: 12pt"><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: 10pt; 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: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: black'>From:</SPAN></B><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: black'> <A
title=cgomes@verisign.com href="mailto: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: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: black'>Sent:</SPAN></B><SPAN
style='FONT-SIZE: 10pt; 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: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: black'>To:</SPAN></B><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: black'> <A
title=kierenmccarthy@gmail.com href="mailto:kierenmccarthy@gmail.com">Kieren
McCarthy</A> ; <A title=ocl@gih.com href="mailto: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: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: black'>Cc:</SPAN></B><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: black'> <A
title=cwg-stewardship@icann.org
href="mailto: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: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: black'>Subject:</SPAN></B><SPAN
style='FONT-SIZE: 10pt; 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: 11pt; 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: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; 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: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; 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: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN></P>
<P class=MsoNormal><B><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: black'>From:</SPAN></B><SPAN
style='FONT-SIZE: 10pt; 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: 12pt"><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-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; PADDING-LEFT: 6pt; MARGIN: 5pt 0in 5pt 4.8pt; BORDER-LEFT: #cccccc 1pt solid; PADDING-RIGHT: 0in">
<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 style="TEXT-ALIGN: center" align=center><SPAN
style='FONT-FAMILY: "Calibri","sans-serif"; COLOR: black'>
<HR align=center SIZE=2 width="100%">
</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></DIV></DIV></DIV></BODY></HTML>