<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 12 (filtered medium)">
<STYLE><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></STYLE>
</HEAD>
<BODY lang=EN-GB dir=ltr link=blue bgColor=white vLink=purple>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>No doubt, this liaison shall be extremely helpful for both sides, the ICG
and the related Cross Community Group, as it may impact the ICG timeline at
least.</DIV>
<DIV> </DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">Full
support.<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=Martin.Boyle@nominet.org.uk
href="mailto:Martin.Boyle@nominet.org.uk">Martin Boyle</A> </DIV>
<DIV><B>Sent:</B> Wednesday, October 15, 2014 9:46 AM</DIV>
<DIV><B>To:</B> <A title=joseph.alhadeff@oracle.com
href="mailto:joseph.alhadeff@oracle.com">joseph alhadeff</A> ; <A
title=daniel.karrenberg@ripe.net href="mailto:daniel.karrenberg@ripe.net">Daniel
Karrenberg</A> </DIV>
<DIV><B>Cc:</B> <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] Thursday session on
accountability</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'>Sorry
to come late to this thread (mobile & vpn lock-out).<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'>I
would be really concerned if the ICG did not have a liaison / exchange with the
ICANN accountability discussion. In the current proposal “ ICANN suggests
that a mechanism to liaise with work of the IANA Stewardship Transition
Coordination Group (ICG) be established for Work Stream 1 of the Enhancing ICANN
Accountability process, as the output of this is interconnected and part of the
deliverable for the IANA Stewardship Transition proposal to
NTIA.”<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'>Meanwhile,
our RfP asks the communities to look at their existing and proposed
accountability associated with their piece of the IANA. This will need to
be built in to the ICANN accountability discussion, too. So I think that,
while we shouldn’t be putting in a lot of effort to shape this discussion, we
should be asking for a liaison, so that we do see the development of coherence
between the crossover part between IANA transition and ICANN
accountability.<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'>Best<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'>Martin<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: 0cm; PADDING-TOP: 3pt; PADDING-LEFT: 0cm; BORDER-LEFT: medium none; PADDING-RIGHT: 0cm">
<P class=MsoNormal><B><SPAN lang=EN-US
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: windowtext'>From:</SPAN></B><SPAN
lang=EN-US
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: windowtext'>
internal-cg-bounces@icann.org [mailto:internal-cg-bounces@icann.org] <B>On
Behalf Of </B>joseph alhadeff<BR><B>Sent:</B> 15 October 2014
08:47<BR><B>To:</B> Daniel Karrenberg<BR><B>Cc:</B>
internal-cg@icann.org<BR><B>Subject:</B> Re: [Internal-cg] Thursday session on
accountability<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p></o:p> </P>
<P class=MsoNormal>Daniel:<BR><BR>I think we mostly agree, but let me highlight
the where I think the intersection might be.<BR><BR>Today the operational
communities have internal processes which include reviews, audits etc as part of
their internal processes, but those operational accountability mechanisms exist
within an overall ecosystem in which the NTIA plays an oversight role, albeit
light touch. We are going into a process where there will be changes
proposed to operational community processes which may include
accountability mechanisms. At the same time, the overall ecosystem will
also be impacted by possibly expanded roles of ICANN or other multistakeholder
NTIA substitute organization and how they deal with accountability.
<BR><BR>I agree that we need to focus on our narrower issues, but if the changes
in broader accountability, due to the exit of NTIA, impact how operational
accountability processes may work within or across communities then we need to
pay attention to those changes and coordinate as needed. As we are not the
creators of substantive positions, we would need to be in communication with the
operational communities and other stakeholders in relation to their concerns
should there be negative implications related to links between operational
accountability and broader accountability processes.<BR><BR>This issue would
hopefully be a remote possibility and will be determined by how the variables
play out...<BR><BR>Joe<o:p></o:p></P>
<DIV>
<P class=MsoNormal>On 10/15/2014 10:57 AM, Daniel Karrenberg
wrote:<o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<P class=MsoNormal>Joe, <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>My intention is not to be 'hard' or confrontational.
Neither do i suggest that we should project that attitude. I am just concerned
that we stay focussed on our particular deliverable and project that image.
<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>The only way i personally see a definite need for us to
coordinate with any icann accountability process would be if the operational
communities choose to reference it in their proposals while it has not yet
produced a final result. I literally see no other reason for coordination. If
that does not happen there is no way how these processes would influence any
language or semanics in our deliverable. <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>That does not mean we should close our eyes. But it does
mean we should stay focussed on *our* work and expand our energy on working
proactively with the operational communities and not waste it on coordination
that we need much much less. <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>I am willing to reconsider my advice/position one the
basis of concrete ways any coordination would influence the content of our
deliverable. <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>Daniel<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>Hoping i can make at least par of Friday's meeting
remotely. <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>--- <o:p></o:p></P>
<DIV>
<P class=MsoNormal><SPAN class=apple-style-span>Sent from a handheld
device.</SPAN><o:p></o:p></P></DIV></DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><BR>On 15.10.2014, at 15:01,
joseph alhadeff <<A
href="mailto:joseph.alhadeff@oracle.com">joseph.alhadeff@oracle.com</A>>
wrote:<o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">Daniel:<BR><BR>I would take a
slightly softer tone than yours, as we do not wish to suggest that the ICANN
accountability work has no relevance to ours. We will need to
coordinate with that group as part of our work. We need to be very
clear, however, that we are not driving that work and do not control its
agendas or timelines and therefore are not in position to address it in any
substantive way. <BR><BR>Joe<o:p></o:p></P>
<DIV>
<P class=MsoNormal>On 10/15/2014 1:10 AM, Daniel Karrenberg
wrote:<o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<P class=MsoNormal>i understand the dynamics of 'icann week'. i also sense
the desire of the crowd to link everything and anything as well as a good
number of competing "complications departments" at work. my advice
is to resist that very pressure and to project that icg is very focused on
our deliverable and its particular content related to accountability. we
are not here to discuss icann accountability or to create a web of
additional linkages that complicate our specific work. if ntia wants to
base their decision to withdraw on other input besides our deliverable,
that should not be our concern. we should be focused on our specific work.
ultimately we will be judged by the quality of that one document and we
should put our energy into working with the operational communities to
produce that one document and with everyone else to explain that one
document and to make sure there are no show-stopping concerns about that
one document. this is the approach i advise and the one i advise to
project. <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>again, € 0.02 <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>Daniel<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><BR>---------- <o:p></o:p></P>
<DIV>
<P class=MsoNormal>Sent from a hand held
device.<o:p></o:p></P></DIV></DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><BR>On 14.10.2014, at
20:56, Alissa Cooper <<A
href="mailto:alissa@cooperw.in">alissa@cooperw.in</A>>
wrote:<o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<DIV>
<P class=MsoNormal>Agreed. The only thing I would say is that people are
very interested in #3 and #4. I got questions about them both in
meetings and in the hallway yesterday. So I don't think we can avoid
talking about them altogether, even if we haven't fully sorted out how
we will handle them.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>Alissa<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><BR>On Oct 14, 2014, at
11:06 AM, Daniel Karrenberg <<A
href="mailto:daniel.karrenberg@ripe.net">daniel.karrenberg@ripe.net</A>>
wrote:<o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<DIV>
<P class=MsoNormal>alissa,<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>please stress point 2 above all else and add a good
dose of lynn's first para about focus. we should project that we are
focussed on our specific deliverable above anything else. in a "one of
a dozen statements" situation it pays to leave all non-essentials off.
if people ask about them, you get more airtime to answer those in a
susequent round. it is most important to get a clear message out and
not obscure it in any way. to my ears your points after 2 have a
strong subtext suggesting that we might become creative. something we
have agreed to avoid. <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>so far my €0.02 <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>daniel<BR><BR>---------- <o:p></o:p></P>
<DIV>
<P class=MsoNormal>Sent from a hand held
device.<o:p></o:p></P></DIV></DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><BR>On 14.10.2014, at
16:50, Alissa Cooper <<A
href="mailto:alissa@cooperw.in">alissa@cooperw.in</A>>
wrote:<o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<P class=MsoNormal>I have been invited to participate in the
Thursday community session about enhancing ICANN accountability
<<A
href="http://la51.icann.org/en/schedule/thu-enhancing-accountability">http://la51.icann.org/en/schedule/thu-enhancing-accountability</A>>.
There is a large panel of speakers and I will have a 5-minute slot.
I have been asked to talk about how the ICG plans to link to the
parallel accountability process and what discussions have taken
place about this so far. <o:p></o:p></P>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>Obviously we have been discussing this a bit
amongst ourselves in the context of the proposal finalization
process and the FAQ, both of which are on our agenda for further
discussion on Friday. We also have a slot on Friday to discuss how
we will liaise with the accountability CCWG. While the results of
these discussions are TBD, I think there are a few points I can
make, slightly expanding on what is in the FAQ:<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>1. Our charter recognizes that maintaining the
accountability of Internet identifier governance is central to the
transition process.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>2. The ICG has asked the operational communities
to consider oversight and accountability — writ large, i.e., "all
the ways in which oversight is conducted over the IANA functions
operator’s provision of the services and activities” — in their
proposals.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>3. After receiving consensus proposals from the
operational communities regarding IANA, the ICG will conduct an
analysis and assessment of their implications for ICANN
accountability. We are still discussing what this analysis and
assessment will entail, and this will depend somewhat on the extent
to which ICANN accountability is the focus of one or more community
proposals. <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>4. We will be having further discussion on Friday
to determine how we will procedurally liaise with the accountability
CCWG, including how and when we might communicate the
analysis/assessment described in (3).<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>Thoughts?<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>Alissa<o:p></o:p></P>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P
class=MsoNormal><o:p></o:p> </P></DIV></DIV></DIV></BLOCKQUOTE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<P
class=MsoNormal>_______________________________________________<BR>Internal-cg
mailing list<BR><A
href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</A><BR><A
href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</A><o:p></o:p></P></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE>
<P class=MsoNormal><BR><BR><BR><o:p></o:p></P><PRE>_______________________________________________<o:p></o:p></PRE><PRE>Internal-cg mailing list<o:p></o:p></PRE><PRE><A href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</A><o:p></o:p></PRE><PRE><A href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</A><o:p></o:p></PRE></BLOCKQUOTE>
<P class=MsoNormal><o:p></o:p> </P></DIV></BLOCKQUOTE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<P
class=MsoNormal>_______________________________________________<BR>Internal-cg
mailing list<BR><A
href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</A><BR><A
href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</A><o:p></o:p></P></DIV></BLOCKQUOTE></BLOCKQUOTE>
<P class=MsoNormal><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>