<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<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:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =
"urn:schemas-microsoft-com:office:odc" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl =
"http://schemas.microsoft.com/repl/" xmlns:mt =
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =
"http://www.passport.com/NameSpace.xsd" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD><TITLE>Re: Communication with ACSO on the next RTs</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.17023" name=GENERATOR>
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
LI.MsoListParagraph {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
SPAN.EmailStyle18 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle19 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle20 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</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 vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=058243315-11062010><FONT face=Arial
color=#0000ff size=2>Thank you, Chuck. Well done.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> owner-council@gnso.icann.org
[mailto:owner-council@gnso.icann.org] <B>On Behalf Of </B>Gomes,
Chuck<BR><B>Sent:</B> Friday, June 11, 2010 11:21 AM<BR><B>To:</B>
council@gnso.icann.org<BR><B>Subject:</B> [council] FW: [soac-discussion] FW:
Communication with ACSO on the next RTs<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
sent this message to Janis regarding the composition of the AoC
RTs.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Chuck<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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'"> Gomes, Chuck
<BR><B>Sent:</B> Friday, June 11, 2010 11:00 AM<BR><B>To:</B> Janis Karklins;
soac-discussion@icann.org<BR><B>Cc:</B> 'Rod Beckstrom'; 'Donna Austin'; 'Olof
Nordling'<BR><B>Subject:</B> RE: [soac-discussion] FW: Communication with ACSO
on the next RTs<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">Janis,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">After
fairly extensive discussion on the GNSO Council list and additional discussion
in our Council meeting yesterday, the GNSO feels very strongly that it is
important to have four representatives on each of the RTs. I have
included a sampling of some of the comments and rationale provided by various
Councilors below. Note that most of these comments were reinforced by
multiple Councilors and that there was overall agreement in the Council
meeting for the position.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">Chuck<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><U><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">General
Comments</SPAN></U><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">I'm not sure that an additional 2
GNSO reps will be detrimental to efficiency, and I should think it would
actually add to the credibility of the process - which leaves "budgetary
limitations" as the remaining (relatively unconvincing)
reason.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">It seems to me that the
ramifications of the selectors rejecting GNSO input as to participant number
are potentially significant. In particular, the irony of doing so while
the accountability and transparency review is underway is pretty
amazing. I think that would play pretty well (against ICANN, that is) in
a number of important fora.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">It'd be a lot easier if they'd just
default to four across the board in order to ensure community representation
and diverse skill sets at the table, rather than turning RT size into a
needless source of angst.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">It is perfectly reasonable to allow
one seat each to the SSAC, GAC, and ASO. But I think it's totally implausible
to assume a well represented RT with only two for the GNSO and one each for
the ccNSO and the ALAC. I believe we make a very strong statement insisting
that each of those are doubled - four for the GNSO (one for each SG, no less),
two each for the ccNSO and the ALAC due to the size of their memberships. That
would make the RT 14 members, and that is certainly workable and more
realistic.<U><o:p></o:p></U></SPAN></P>
<P class=MsoNormal><U><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'"><o:p><SPAN
style="TEXT-DECORATION: none"> </SPAN></o:p></SPAN></U></P>
<P class=MsoNormal><U><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">SSR
RT</SPAN></U><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 6pt; mso-list: l3 level1 lfo4; mso-margin-top-alt: 0in"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">All three (SSR) are already huge
issues and will directly affect all the rollout and use of TLD’s, IDN_TLDs,
and ccTLDs and some of the issues that could be coming would
include:<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 3pt; mso-list: l4 level1 lfo6; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><![if !supportLists]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">Punycode storage of IDN names –
Neither any human nor most existing security mechanisms (anti-virus,
firewalls, etc) can read it directly. It is the main reason you need
“standard script” usage.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 3pt; mso-list: l4 level1 lfo6; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><![if !supportLists]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">DNSSec – Can it and should it be
pushed to all TLDs? (After a demo of DNS hacks a couple weeks back, I’m
not sure I will ever trust a wireless hotspot fully
again.)<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 3pt; mso-list: l4 level1 lfo6; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><![if !supportLists]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">DNSSec – Credentials – Key
distribution chains and processes, rollover mechanisms, and there will
likely be some of revocation process needed for bad
behavior.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 3pt; mso-list: l4 level1 lfo6; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><![if !supportLists]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">DNSSec – Operational issues yet to
be determined too. DNSSec generates a 30x increase in response traffic
for instance plus signature processing overhead.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 3pt; mso-list: l4 level1 lfo6; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><![if !supportLists]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">Network management systems likewise
will likely have initial issues with IDNs too.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 3pt; mso-list: l4 level1 lfo6; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><![if !supportLists]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">Increased discussions of “network
cyber identity requirements” and how these might work in an IDN
environment.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 3pt; mso-list: l4 level1 lfo6; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><![if !supportLists]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">Routing reliability as IPv6 vastly
increases the route table sizes<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 3pt; mso-list: l4 level1 lfo6; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><![if !supportLists]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">IPv6 reachability and initial usage
rollouts. (Outside of Microsoft, I could not say that anyone on the
globe has a large scale IPv6 infrastructure working
yet.)<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 3pt; mso-list: l4 level1 lfo6; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><![if !supportLists]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">New “whois” issues that could be
created by fact that more, maybe most, IPv6 addresses will be indirectly
assigned through an ISP to the end user or organization rather than directly
assigned via IANA and the RIRs.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 6pt; mso-list: l6 level1 lfo8; mso-margin-top-alt: 0in"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">From an operational point of view,
with implementation of TLDs, ccTLDs, IDN_TLDs, DNSSec, and IPv6 plus the
issues with route stability and huge growth in cybercrime; one could
reasonably expect that many unseen/unknown operational issues will affect GNSO
plans and policies. (and certainly keep the SSR busy!)
<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; MARGIN-RIGHT: 6pt; mso-list: l6 level1 lfo8; mso-margin-top-alt: 0in"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">The economies and critical
infrastructure (communications, power, financial, etc) of at least 50 nations
around the globe are completely tied to the security, stability, and
reliability of the Internet so SSR issues are considered very carefully by
most governments.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l2 level1 lfo10"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">The Commercial SG provides
combined expertise in technical, operational and legal respect of security
aspects of the DNS system.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><U><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">Whois
RT<o:p></o:p></SPAN></U></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l5 level1 lfo12"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">Whereas Internet users across the
whole ICANN community are impacted by Whois policy, I don’t think there is any
doubt that GNSO constituents are impacted the most. It is gTLD
registrants whose data is displayed and used. It is gTLD contracted
parties who are required to implement Whois and who best understand the
customer service and operational issues related to Whois offerings. It
is commercial gTLD registrants whose businesses are affected when IP rights
are violated. It is noncommercial users who have most often pointed out
the need for privacy of Whois information and noncommercial organizations that
are impacted in similar ways as commercial businesses.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l5 level1 lfo12"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">In addition, because of the GNSO’s
long and belabored Whois policy development history and varied Whois
operational offerings, the GNSO has the best source of Whois experts from
various points of view. There is also good evidence that each SG
provides a unique area of expertise and represents different points of view
with regard to Whois policy.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l5 level1 lfo12"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">Whois is one of the few areas where
people who are generally like-minded can have VERY different
positions.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l5 level1 lfo12"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">There really has to be four for
WHOIS, the perspectives of the SGs are just too variable for any two to
represent the others, and the whole process could become a focal point of
controversy.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l5 level1 lfo12"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">I strongly oppose accepting only two
seats on the Whois.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><U><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">New
gTLDs RT<o:p></o:p></SPAN></U></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo14"><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol"><SPAN style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'">Similar arguments could be made for
this future RT.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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'">
owner-soac-discussion@icann.org [mailto:owner-soac-discussion@icann.org] <B>On
Behalf Of </B>Janis Karklins<BR><B>Sent:</B> Friday, June 04, 2010 1:50
PM<BR><B>To:</B> soac-discussion@icann.org<BR><B>Cc:</B> 'Rod Beckstrom';
'Donna Austin'; 'Olof Nordling'<BR><B>Subject:</B> [soac-discussion] FW:
Communication with ACSO on the next RTs<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">Dear
colleagues<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">On
behalf of Selectors I would like to propose that the size and composition of
the two next review teams would be as follows:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"> Security
WHOIS<BR>GAC,
including the Chair
2
1<BR>GNSO
2
2<BR>ccNSO
2
1<BR>ALAC
2
1<BR>SSAC
1
1<BR>RSSAC
1<BR>ASO
1 1<BR>Independent
expert
1-2
2
(law enforcement/privacy experts)<BR>CEO
1
1<BR> 13-14
10<BR><BR>I
understand that your initial suggestions/requests were not fully accommodated,
but for the sake of efficiency, credibility of the process, budgetary
limitations Selectors have developed this proposal. If we would take into
account all wishes, the RT size would be over 20 which in Selectors’ view is
not credible option.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">I
hope that proposal will be <B>equally unacceptable</B> for everybody. I would
appreciate your <B>comments or expression of non-objection </B>in coming week.
Only after assessment of the violence of your opposition the Selectors will
make their proposal (<B>in present form or modified</B>)
public.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">Best
regards<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">JK
<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="COLOR: black"><o:p> </o:p></SPAN></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>