<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: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="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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;}
@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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
margin:0in;
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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Times New Roman","serif";
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Times New Roman","serif";
color:black;
font-weight:bold;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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 link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>All,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>The GNSO Council wiki workspaces
are accessible from the GNSO home page: <a href="http://gnso.icann.org/">http://gnso.icann.org/</a>.
Please note that the wiki references are provided in the left-side menu. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>We could certainly create a
glossary page on the GNSO Council workspace for Council members to add and
update definitions of key terms if the Council feels that would be useful to create
in addition to the ICANN glossary. If the Council requests that staff
resources be allocated to creating, adding to and maintaining a GNSO-specific
glossary, we should consider timing and expectations in light of other current activities.
It certainly makes sense to have a glossary that is more dynamic and enables “new”
terms to be added, and definitions updated, given how frequently new terms
arise “in Internet time”. I will bring that idea to the attention of the
Corporate Affairs staff, and also suggest that additional terms (that you have
identified) be added. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks, Liz<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] <b>On Behalf
Of </b>Adrian Kinderis<br>
<b>Sent:</b> Tuesday, April 28, 2009 6:29 PM<br>
<b>To:</b> Rosette, Kristina; Council GNSO<br>
<b>Subject:</b> RE: [council] RE: Pending additions to ICANN glossary -- update
on Council request from Mexico City<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>Yes. Didn’t think to
address access... although isn’t the GNSO Council wiki public?<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=EN-AU
style='color:#1F497D'>Adrian Kinderis</span></b><span lang=EN-AU
style='color:black'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] <b>On Behalf
Of </b>Rosette, Kristina<br>
<b>Sent:</b> Wednesday, 29 April 2009 11:25 AM<br>
<b>To:</b> Council GNSO<br>
<b>Subject:</b> RE: [council] RE: Pending additions to ICANN glossary -- update
on Council request from Mexico City<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Definitely agree with listing entries by acronym.</span><span
lang=EN-AU style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Would definitely be helpful to have a more informal glossary for
Council, but many who can most benefit from the glossary don't have access to
the wiki.</span><span lang=EN-AU style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>While we're suggesting terms, I'd add: domain tasting, fast
flux, IPv4, IPv6, RALO, Nominating Committee</span><span lang=EN-AU
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>K</span><span lang=EN-AU style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<p class=MsoNormal><span lang=EN-AU style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> owner-council@gnso.icann.org
[mailto:owner-council@gnso.icann.org] <b>On Behalf Of </b>Adrian Kinderis<br>
<b>Sent:</b> Tuesday, April 28, 2009 9:19 PM<br>
<b>To:</b> Liz Gasster; Council GNSO<br>
<b>Subject:</b> [council] RE: Pending additions to ICANN glossary -- update on
Council request from Mexico City</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>Thanks Liz.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>Would it be possible
to have this glossary in a wiki format that could be added to and adjusted on
the fly?<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>I understand having
it as an ‘official’ ICANN Glossary in this way may be problematic but maybe a
GNSO Council specific one on our wiki? I note that such things as IRT, IDN,
DNSSEC etc are not there... we could all pitch in to add definitions if it was
a wiki. Folks in the industry that speak different languages could provide
translations ‘on the fly’.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>Just a thought...<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>Also it would help to
list them by acronym not by true name. So when someone hears the acronym they
can find it easily. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=EN-AU
style='color:#1F497D'>Adrian Kinderis</span></b><span lang=EN-AU
style='font-size:9.0pt;color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-AU style='color:black'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] <b>On Behalf
Of </b>Liz Gasster<br>
<b>Sent:</b> Wednesday, 29 April 2009 7:29 AM<br>
<b>To:</b> Council GNSO<br>
<b>Subject:</b> [council] Pending additions to ICANN glossary -- update on
Council request from Mexico City<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p>
<p class=MsoNormal>All,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>During our after-action meeting in Mexico City, several of
you suggested that we update the ICANN glossary to add some basic terms that we
refer to frequently but that are missing currently from that compendium <a
href="http://www.icann.org/en/general/glossary.htm">http://www.icann.org/en/general/glossary.htm</a>
. Definitions have been developed for the terms that were identified by
Council members (copied below for your reference, note also an updated
definition of WHOIS has been prepared). These definitions are currently
being translated and they will be added to the glossary when the translations
are complete. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>ICANN’s Corporate Affairs department will be updating the
glossary more broadly in the upcoming weeks. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>We will also be adding a link to the glossary from the GNSO
home page, <a href="http://gnso.icann.org/">http://gnso.icann.org/</a> .
This was also suggested in the Mexico meeting. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks, Liz<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<h1><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>PDP -
Policy Development Process <o:p></o:p></span></h1>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>A set of formal steps, as defined in the ICANN bylaws, to
guide the initiation, internal and external review, timing and approval of
policies needed to coordinate the global Internet’s system of unique
identifiers.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<h1><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Operations
Steering Committee<o:p></o:p></span></h1>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN>The Operations Steering Committee (OSC)
coordinates, recommends and reviews changes to certain operational activities
of the GNSO and its constituencies with a view to efficient outcomes.</span>
These operational activity areas cover GNSO operations, Stakeholder Group and
Constituency operations, and communications with GNSO and between GNSO and
other ICANN structures.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<h1><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Policy
Process Steering Committee<o:p></o:p></span></h1>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The Policy Process Steering Committee (PPSC) <span
style='color:black'>reviews and recommends processes used within the GNSO for
developing policy, including the use of Working Groups, and recommending any
changes. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
<h2><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Registry
Services Evaluation Process<o:p></o:p></span></h2>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:black'>The Registry Services Evaluation
Process (RSEP) is ICANN’s process for evaluating proposed gTLD registry
services or contractual modifications for security, stability or competition
issues. Further information on RSEP is available at <a
href="http://www.icann.org/en/registries/rsep/">http://www.icann.org/en/registries/rsep/</a>.
<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
<h2><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>WHOIS<o:p></o:p></span></h2>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText><b><span lang=EN style='font-size:11.0pt;font-family:
"Calibri","sans-serif"'>WHOIS</span></b><span lang=EN style='font-size:11.0pt;
font-family:"Calibri","sans-serif"'> (pronounced "<b>who is</b>"; not
an acronym) </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>An
Internet protocol that is used to query databases to obtain information about
the registration of a domain name (or IP address). The WHOIS protocol was
originally specified in RFC 954 <<a href="http://www.ietf.org/rfc/rfc954.txt">http://www.ietf.org/rfc/rfc954.txt</a>>,
published in 1985. The current specification is documented in RFC 3912
<<a href="http://www.ietf.org/rfc/rfc3912.txt">http://www.ietf.org/rfc/rfc3912.txt</a>>.
ICANN's gTLD agreements require registries and registrars to offer an
interactive web page and a port 43 WHOIS service providing free public access
to data on registered names. Such data is commonly referred to as "WHOIS
data," and includes elements such as the domain registration creation and
expiration dates, nameservers, and contact information for the registrant and designated
administrative and technical contacts.<o:p></o:p></span></p>
<p class=MsoNormal>WHOIS services are typically used to identify domain holders
for business purposes and to identify parties who are able to correct technical
problems associated with the registered domain.<o:p></o:p></p>
</blockquote>
</div>
</body>
</html>