<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=us-ascii">
<meta name=Generator content="Microsoft Word 12 (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: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-link:"Heading 1 Char";
margin:0in;
margin-bottom:.0001pt;
page-break-after:avoid;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h2
{mso-style-link:"Heading 2 Char";
margin:0in;
margin-bottom:.0001pt;
page-break-after:avoid;
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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-link:"Heading 1";
font-family:"Times New Roman","serif";
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
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;}
.MsoChpDefault
{mso-style-type:export-only;}
@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>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.</span><span style='color:black'> <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>
</div>
</body>
</html>