<!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>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5726" name=GENERATOR><!--[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-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Consolas;
}
@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.0pt; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
H1 {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 9; mso-style-link: "Heading 1 Char"
}
H2 {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; COLOR: black; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 9; mso-style-link: "Heading 2 Char"
}
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.MsoPlainText {
FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "Plain Text Char"
}
LI.MsoPlainText {
FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "Plain Text Char"
}
DIV.MsoPlainText {
FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "Plain Text Char"
}
SPAN.Heading1Char {
FONT-WEIGHT: bold; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 9; mso-style-link: "Heading 1"; mso-style-name: "Heading 1 Char"
}
SPAN.Heading2Char {
FONT-WEIGHT: bold; COLOR: black; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 9; mso-style-link: "Heading 2"; mso-style-name: "Heading 2 Char"
}
SPAN.PlainTextChar {
FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "Plain Text"; mso-style-name: "Plain Text Char"
}
SPAN.EmailStyle21 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle22 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle23 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle24 {
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
}
</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-AU vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=225433601-29042009><FONT face=Arial
color=#0000ff size=2>I stand corrected. But they still have to find it .
.. </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> Adrian Kinderis
[mailto:adrian@ausregistry.com.au] <BR><B>Sent:</B> Tuesday, April 28, 2009
9:35 PM<BR><B>To:</B> Adrian Kinderis; Rosette, Kristina; Council
GNSO<BR><B>Subject:</B> RE: [council] RE: Pending additions to ICANN glossary
-- update on Council request from Mexico City<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">From my quick click around it
seems to be public to me!<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"><A
href="https://st.icann.org/gnso-council/index.cgi?gnso_council_workspace">https://st.icann.org/gnso-council/index.cgi?gnso_council_workspace</A>
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><B><SPAN style="COLOR: #1f497d">Adrian
Kinderis</SPAN></B><SPAN style="COLOR: #1f497d"><BR><BR></SPAN><SPAN
style="FONT-SIZE: 9pt; COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: black"><o:p> </o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN lang=EN-US
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
lang=EN-US style="FONT-SIZE: 10pt; 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> Wednesday, 29 April 2009 11:29
AM<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 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 style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN
style="COLOR: #1f497d">Adrian Kinderis</SPAN></B><SPAN
style="COLOR: black"><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN lang=EN-US
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
lang=EN-US style="FONT-SIZE: 10pt; 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><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Definitely
agree with listing entries by acronym.</SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">While
we're suggesting terms, I'd add: domain tasting, fast flux, IPv4, IPv6,
RALO, Nominating Committee</SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">K</SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: 0cm">
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p> </o:p></SPAN></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN lang=EN-US
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
lang=EN-US style="FONT-SIZE: 10pt; 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 lang=EN-US
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><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>
<P class=MsoNormal><SPAN 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 style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN 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 style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Just a
thought...<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">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 style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN
style="COLOR: #1f497d">Adrian Kinderis</SPAN></B><SPAN
style="FONT-SIZE: 9pt; COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: black"><o:p> </o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN lang=EN-US
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
lang=EN-US style="FONT-SIZE: 10pt; 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><o:p> </o:p></P>
<P class=MsoNormal><SPAN lang=EN-US>All,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>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></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>ICANN’s Corporate Affairs department
will be updating the glossary more broadly in the upcoming weeks.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>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></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>Thanks, Liz<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<H1><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">PDP - Policy
Development Process <o:p></o:p></SPAN></H1>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>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></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<H1><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">Operations
Steering Committee<o:p></o:p></SPAN></H1>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></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><SPAN lang=EN-US> 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></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<H1><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">Policy Process
Steering Committee<o:p></o:p></SPAN></H1>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>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></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US
style="COLOR: black"><o:p> </o:p></SPAN></P>
<H2><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">Registry
Services Evaluation Process<o:p></o:p></SPAN></H2>
<P class=MsoNormal><SPAN lang=EN-US
style="COLOR: black"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 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 lang=EN-US
style="COLOR: black"><o:p> </o:p></SPAN></P>
<H2><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">WHOIS<o:p></o:p></SPAN></H2>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoPlainText><B><SPAN lang=EN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">WHOIS</SPAN></B><SPAN
lang=EN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">
(pronounced "<B>who is</B>"; not an acronym) </SPAN><SPAN lang=EN-US
style="FONT-SIZE: 11pt; 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><SPAN lang=EN-US>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></SPAN></P></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>