<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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{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:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">No votes for liaisons. (No votes at all should be the rule, but the registry voice should not be overruled by the liaisons.)<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 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> dt3-bounces@icann.org [mailto:dt3-bounces@icann.org]
<b>On Behalf Of </b>Staffan Jonson<br>
<b>Sent:</b> 04 June 2015 14:20<br>
<b>To:</b> Kim Davies; Donna Austin<br>
<b>Cc:</b> dt3@icann.org<br>
<b>Subject:</b> Re: [DTC CSC] Member/Liaison definitions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kim<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We’ve had some extra effort keeping away all kinds of interests from this minimal functions, so I would not recommend any new full members. It
would risk opening up a Lot. If there’ll be discussion on outnumbering (i.e. voting similar behavior), then we’re already lost.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Staffan J<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" 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 #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Från:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:dt3-bounces@icann.org">dt3-bounces@icann.org</a> [<a href="mailto:dt3-bounces@icann.org">mailto:dt3-bounces@icann.org</a>]
<b>För </b>Kim </span><span lang="SV" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Davies<br>
<b>Skickat:</b> den 4 juni 2015 04:04<br>
<b>Till:</b> Donna Austin<br>
<b>Kopia:</b> <a href="mailto:dt3@icann.org">dt3@icann.org</a><br>
<b>Ämne:</b> Re: [DTC CSC] Member/Liaison definitions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="SV"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="SV">Hi Donna, <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="SV"><o:p> </o:p></span></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="SV" style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#333333;background:white"> </span><span lang="SV"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="SV" style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#333333;background:white">There is one caution that I have with regard to this. Our members will be outnumbered by Liaisons by 4 to 5, so if Liaisons are
participating on equal footing it could get tricky.</span><span lang="SV" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="SV" style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#333333;background:white"> </span><span lang="SV" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="SV" style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#333333;background:white">As RSSAC is a direct customer perhaps we elevate them to ‘member’, and similarly for the RIRs which offered a Liaison through the
public comment.</span><span lang="SV" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="SV" style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#333333;background:white"> </span><span lang="SV" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="SV" style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#333333;background:white">Sorry for the curve ball, but I’d appreciate any thoughts any of you might have.</span><span lang="SV" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<p class="MsoNormal"><span lang="SV"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="SV">For what it’s worth, in the context of the IANA naming functions I think we have more customer interactions with .INT registrants, and the IAB in the context of .ARPA, than we do with root server operators which probably
represent ~0.1% of requests (<1 request per year)<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="SV"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="SV">kim<o:p></o:p></span></p>
</div>
</div>
</body>
</html>