<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=us-ascii" http-equiv=Content-Type>
<META name=Generator content="Microsoft Word 14 (filtered medium)">
<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:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.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=#0563c1 vLink=#954f72>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>I also support this but have some reservartions to the strict obligation
imposed: “...<FONT style="FONT-SIZE: 11pt" color=#ff0000>the ICG must assess
proposed solutions in the light of the of the other accountability process”
<FONT color=#000000>which could lead to an open-end discussion. Can we add:
<FONT style="FONT-SIZE: 12pt">“...</FONT><FONT style="COLOR: #ff0000">the ICG
must assess proposed solutions in the light of the of the other accountability
process <FONT color=#0000ff>as available</FONT><FONT
color=#000000>”?</FONT></FONT></FONT></FONT></DIV>
<DIV> </DIV>
<DIV
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000"><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=kdrazek@verisign.com
href="mailto:kdrazek@verisign.com">Drazek, Keith</A> </DIV>
<DIV><B>Sent:</B> Thursday, July 17, 2014 2:02 PM</DIV>
<DIV><B>To:</B> <A title=mueller@syr.edu href="mailto:mueller@syr.edu">Milton L
Mueller</A> ; <A title=internal-cg@icann.org
href="mailto:internal-cg@icann.org">internal-cg@icann.org</A> </DIV>
<DIV><B>Subject:</B> Re: [Internal-cg] scope language</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="COLOR: #1f497d">I support the language
circulated by Milton. I’m also supportive of Paul’s suggestion that we not limit
it to accountability alone. I made two suggested edits in blue
below:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="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"'>
internal-cg-bounces@icann.org [mailto:internal-cg-bounces@icann.org] <B>On
Behalf Of </B>Milton L Mueller<BR><B>Sent:</B> Thursday, July 17, 2014 8:57
AM<BR><B>To:</B> internal-cg@icann.org<BR><B>Subject:</B> [Internal-cg] scope
language<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p></o:p> </P>
<P class=MsoNormal><SPAN style="COLOR: red">The IANA stewardship transition
process is taking place alongside a </SPAN><SPAN style="COLOR: #1f497d">parallel
and</SPAN><SPAN style="COLOR: red"> related process on enhancing ICANN
accountability. While maintaining the accountability of Internet identifier
governance is central to both processes, this group’s scope is limited to
filling the accountability gaps created by the end of the NTIA’s role as
principal in the IANA contract, whereas the other process focuses on enhancing
the accountability of ICANN’s policy development process. Nevertheless, the two
processes are interrelated </SPAN><SPAN style="COLOR: #1f497d">and
interdependent </SPAN><SPAN style="COLOR: red">and the ICG must assess proposed
solutions in the light of the of the other accountability process.
</SPAN><o:p></o:p></P></DIV>
<P>
<HR>
_______________________________________________<BR>Internal-cg mailing
list<BR>Internal-cg@icann.org<BR>https://mm.icann.org/mailman/listinfo/internal-cg<BR></DIV></DIV></DIV></BODY></HTML>