<!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:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.6082" name=GENERATOR><BASE href=x-msg://2565/>
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Consolas;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 70.85pt 70.85pt 70.85pt 70.85pt; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 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
}
SPAN.apple-style-span {
mso-style-name: apple-style-span
}
SPAN.apple-converted-space {
mso-style-name: apple-converted-space
}
SPAN.EmailStyle19 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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=FR
style="WORD-WRAP: break-word; webkit-nbsp-mode: space; webkit-line-break: after-white-space"
vLink=purple link=blue>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=961372303-23062011>FYI</SPAN></FONT></DIV>
<DIV> </DIV>
<P style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px"><FONT face=arial
color=#000000>Kind regards<BR>Wolf-Ulrich </FONT></P><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=de dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>Von:</B> owner-council@gnso.icann.org
[mailto:owner-council@gnso.icann.org] <B>Im Auftrag von </B>Glen de Saint
Géry<BR><B>Gesendet:</B> Mittwoch, 22. Juni 2011 13:25<BR><B>An:</B> Council
GNSO<BR><B>Betreff:</B> [council] GNSO Council resolutions - Singapore 22 June
2011<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Dear
All,</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Ahead of the
official Council minutes, please find the<SPAN
class=apple-converted-space> </SPAN><A
name=Motions22June2011-Motion%26nbsp%3B1onthe></A><A
name=Motions22June2011-Motion1%26nbsp%3Bonthe></A>resolutions passed by the
GNSO Council today, 22 June 2011 in Singapore:</SPAN><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><SPAN
lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Motion 1 on
the Adoption of the IRTP Part B Final Report and
Recommendations</SPAN></B><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">WHEREAS
on 24 June 2009, the GNSO Council launched a Policy Development Process (PDP)
on IRTP Part B addressing the following five charter questions:</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">a.
Whether a process for urgent return/resolution of a domain name should be
developed, as discussed within the SSAC hijacking report<BR>(</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><A
href="http://www.icann.org/announcements/hijacking-report-12jul05.pdf"><SPAN
lang=EN-US
style="COLOR: windowtext">http://www.icann.org/announcements/hijacking-report-12jul05.pdf</SPAN></A></SPAN><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">); see
also (</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><A
href="http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm"><SPAN
lang=EN-US
style="COLOR: windowtext">http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm</SPAN></A></SPAN><SPAN
lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">);</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">b.
Whether additional provisions on undoing inappropriate transfers are needed,
especially with regard to disputes between a Registrant and Admin Contact
(AC). The policy is clear that the Registrant can overrule the AC, but how
this is implemented is currently at the discretion of the
registrar;</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">c.
Whether special provisions are needed for a change of registrant when it
occurs near the time of a change of registrar. The policy does not currently
deal with change of registrant, which often figures in hijacking
cases;</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">d.
Whether standards or best practices should be implemented regarding use of a
Registrar Lock status (e.g. when it may/may not, should/should not be
applied);</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">e.
Whether, and if so, how best to clarify denial reason #7: A domain name was
already in 'lock status' provided that the Registrar provides a
readily<BR>accessible and reasonable means for the Registered Name Holder to
remove the lock status.</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">WHEREAS
this PDP has followed the prescribed PDP steps as stated in the Bylaws,
resulting in a Final Report delivered on 30 May 2011;</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">WHEREAS
the IRTP Part B WG has reached full consensus on the recommendations in
relation to each of the five issues outlined above;</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">WHEREAS
the GNSO Council has reviewed and discussed these recommendations.</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<TABLE class=MsoNormalTable
style="MARGIN-LEFT: 0.75pt; BORDER-COLLAPSE: collapse" cellSpacing=0
cellPadding=0 border=0>
<TBODY>
<TR>
<TD
style="BORDER-RIGHT: #dddddd 1pt solid; PADDING-RIGHT: 3.75pt; BORDER-TOP: #dddddd 1pt solid; PADDING-LEFT: 3.75pt; PADDING-BOTTOM: 3.75pt; BORDER-LEFT: #dddddd 1pt solid; PADDING-TOP: 3.75pt; BORDER-BOTTOM: #dddddd 1pt solid"
vAlign=top>
<P class=MsoNormal
style="MARGIN-BOTTOM: 3.75pt; LINE-HEIGHT: 13pt"><B><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Resolved</SPAN></B><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></TD></TR>
<TR>
<TD
style="BORDER-RIGHT: #dddddd 1pt solid; PADDING-RIGHT: 3.75pt; BORDER-TOP: medium none; PADDING-LEFT: 3.75pt; PADDING-BOTTOM: 3.75pt; BORDER-LEFT: #dddddd 1pt solid; PADDING-TOP: 3.75pt; BORDER-BOTTOM: #dddddd 1pt solid"
vAlign=top>
<DIV>
<P class=MsoNormal style="LINE-HEIGHT: 13pt"><B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">RESOLVED
(A)</SPAN></B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">, the GNSO
Council recommends to the ICANN Board of Directors:<SPAN
class=apple-converted-space> </SPAN><BR>1. Requiring Registrars to
provide a Transfer Emergency Action Contact (TEAC). To this end the
language of section 4 (Registrar Coordination) and Section 6 (Registry
Requirements of the Inter-Registrar Transfer Policy should be updated as
follows:<SPAN class=apple-converted-space> </SPAN><BR>Transfer
Emergency Action Contact (Append to Section 4)<SPAN
class=apple-converted-space> </SPAN><BR>Registrars will establish a
Transfer Emergency Action Contact (TEAC) for urgent communications
relating to transfers. The goal of the TEAC is to quickly establish a
real-time conversation between registrars (in a language that both
parties can understand) in an emergency. Further actions can then be
taken towards a resolution, including initiating existing (or future)
transfer dispute or undo processes.<SPAN
class=apple-converted-space> </SPAN><BR>Communications to TEACs
will be reserved for use by ICANN-Accredited Registrars, gTLD Registry
Operators and ICANN Staff. The TEAC point of contact may be designated
as a telephone number or some other real-time communication channel and
will be recorded in, and protected by, the ICANN RADAR system.<SPAN
class=apple-converted-space> </SPAN><BR>Communications to a TEAC
must be initiated in a timely manner, within a reasonable period of time
following the alleged unauthorized loss of a domain.<SPAN
class=apple-converted-space> </SPAN><BR>Messages sent via the TEAC
communication channel must generate a non-automated response by a human
representative of the gaining Registrar. The person or team responding
must be capable and authorized to investigate and address urgent
transfer issues. Responses are required within 4 hours of the initial
request, although final resolution of the incident may take longer.<SPAN
class=apple-converted-space> </SPAN><BR>The losing registrar will
report failures to respond to a TEAC communication to ICANN Compliance
and the registry operator. Failure to respond to a TEAC communication
may result in a transfer-undo in accordance with Section 6 of this
policy and may also result in further action by ICANN, up to and
including non-renewal or termination of accreditation.<SPAN
class=apple-converted-space> </SPAN><BR>Both parties will retain
correspondence in written or electronic form of any TEAC communication
and responses, and share copies of this documentation with ICANN and the
registry operator upon request. This documentation will be retained in
accordance with Section 3.4 of the Registrar Accreditation Agreement
(RAA). Users of the TEAC communication channel should report
non-responsive Registrars to ICANN. Additionally, ICANN may conduct
periodic tests of the Registrar TEAC communication channel in situations
and a manner deemed appropriate to ensure that registrars are indeed
responding to TEAC messages.<SPAN
class=apple-converted-space> </SPAN><BR>(Append to Section 6) 6 iv.
Documentation provided by the Registrar of Record prior to transfer that
the Gaining Registrar has not responded to a message via the TEAC within
the timeframe specified in Section 4.<SPAN
class=apple-converted-space> </SPAN><BR>In addition, update section
6 to reflect that the registry, in case of a transfer undo, will reverse
the transfer and reset the registrar of record filed to its original
state (‘In such case, the transfer will be reversed and the Registrar of
Record field reset to its original state'). (IRTP Part B Recommendation
#1)<SPAN class=apple-converted-space> </SPAN><BR>2. Modifying
section 3 of the IRTP to require that the Registrar of Record/Losing
Registrar be required to notify the Registered Name Holder/Registrant of
the transfer out. The Registrar of Record has access to the contact
information for the Registrant and could modify their systems to
automatically send out the Standardized Form for Losing Registrars
("Confirmation FOA") to the Registrant. (IRTP Part B Recommendation
#5)<SPAN class=apple-converted-space> </SPAN><BR>3. Modifying
Reason for Denial #6 as follows: Express objection to the transfer by
the authorized Transfer Contact. Objection could take the form of
specific request (either by paper or electronic means) by the authorized
Transfer Contact to deny a particular transfer request, or a general
objection to all transfer requests received by the Registrar, either
temporarily or indefinitely. In all cases, the objection must be
provided with the express and informed consent of the authorized
Transfer Contact on an opt-in basis and upon request by the authorized
Transfer Contact, the Registrar must remove the lock or provide a
reasonably accessible method for the authorized Transfer Contact to
remove the lock within five (5) calendar days. (IRTP Part B
Recommendation #6)<SPAN class=apple-converted-space> </SPAN><BR>4.
Deleting denial reason #7 as a valid reason for denial under section 3
of the IRTP as it is technically not possible to initiate a transfer for
a domain name that is locked, and hence cannot be denied, making this
denial reason obsolete.<SPAN
class=apple-converted-space> </SPAN></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">(IRTP Part B
Recommendation #9 - part 1)</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV></TD></TR>
<TR>
<TD
style="BORDER-RIGHT: #dddddd 1pt solid; PADDING-RIGHT: 3.75pt; BORDER-TOP: medium none; PADDING-LEFT: 3.75pt; PADDING-BOTTOM: 3.75pt; BORDER-LEFT: #dddddd 1pt solid; PADDING-TOP: 3.75pt; BORDER-BOTTOM: #dddddd 1pt solid"
vAlign=top>
<P class=MsoNormal
style="MARGIN-BOTTOM: 3.75pt; LINE-HEIGHT: 13pt"><B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">RESOLVED
(B),</SPAN></B><SPAN class=apple-converted-space><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN></SPAN><SPAN
lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">the GNSO
Council recommends the promotion by ALAC and other ICANN structures of
the measures outlined in the recent report of the Security and Stability
Advisory Committee on A Registrant's Guide to Protecting Domain Name
Registration Accounts (SAC 044). In particular, the GNSO Council
recommends that registrants consider the measures to protect domain
registrar accounts against compromise and misuse described in SAC044,
Section 5. These include practical measures that registrants can
implement "in house", such as ways to protect account credentials and
how to incorporate domain name registrations into employee or resource
management programs typically found in medium and large businesses. It
suggests ways that registrants can use renewal and change notifications
from registrars as part of an early warning or alerting system for
possible account compromise. The GNSO Council Chair will reach out to
the ALAC and other ICANN structures to inform them of this
recommendation and discuss how the GNSO may contribute to this
promotion.<SPAN class=apple-converted-space> </SPAN></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">(IRTP Part B
Recommendation #2)</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></TD></TR>
<TR>
<TD
style="BORDER-RIGHT: #dddddd 1pt solid; PADDING-RIGHT: 3.75pt; BORDER-TOP: medium none; PADDING-LEFT: 3.75pt; PADDING-BOTTOM: 3.75pt; BORDER-LEFT: #dddddd 1pt solid; PADDING-TOP: 3.75pt; BORDER-BOTTOM: #dddddd 1pt solid"
vAlign=top>
<P class=MsoNormal
style="MARGIN-BOTTOM: 3.75pt; LINE-HEIGHT: 13pt"><B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Resolved
(C),</SPAN></B><SPAN class=apple-converted-space><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN></SPAN><SPAN
lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">the GNSO
Council acknowledges receipt of IRTP Part B Recommendation #7 and will
consider this recommendation when it considers the Final Issue Report on
the Current State of the UDRP.</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></TD></TR>
<TR>
<TD
style="BORDER-RIGHT: #dddddd 1pt solid; PADDING-RIGHT: 3.75pt; BORDER-TOP: medium none; PADDING-LEFT: 3.75pt; PADDING-BOTTOM: 3.75pt; BORDER-LEFT: #dddddd 1pt solid; PADDING-TOP: 3.75pt; BORDER-BOTTOM: #dddddd 1pt solid"
vAlign=top>
<P class=MsoNormal
style="MARGIN-BOTTOM: 3.75pt; LINE-HEIGHT: 13pt"><B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">RESOLVED
(D),</SPAN></B><SPAN class=apple-converted-space><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN></SPAN><SPAN
lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">prior to the
consideration of approval of the recommendation which states: "denial
reason #7 should be replaced by adding a new provision in a different
section of the IRTP on when and how domains may be locked or unlocked",
the GNSO Council requests ICANN Staff to provide a proposal for such a
new provision, taking into account the IRTP Part B WG deliberations in
relation to this issue (see IRTP Part B Final Report - (Recommendation
#9 - part 2). Upon review of the proposal, the GNSO Council will
consider whether to approve the recommendation.</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></TD></TR>
<TR>
<TD
style="BORDER-RIGHT: #dddddd 1pt solid; PADDING-RIGHT: 3.75pt; BORDER-TOP: medium none; PADDING-LEFT: 3.75pt; PADDING-BOTTOM: 3.75pt; BORDER-LEFT: #dddddd 1pt solid; PADDING-TOP: 3.75pt; BORDER-BOTTOM: #dddddd 1pt solid"
vAlign=top>
<P class=MsoNormal
style="MARGIN-BOTTOM: 3.75pt; LINE-HEIGHT: 13pt"><B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">RESOLVED
(E),</SPAN></B><SPAN class=apple-converted-space><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN></SPAN><SPAN
lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">prior to the
consideration of approval of the recommendation regarding the
standardizing and clarifying WHOIS status messages regarding Registrar
Lock status, the GNSO Council requests ICANN staff to provide a proposal
designed to ensure a technically feasible approach can be developed to
meet this recommendation. Staff should take into account the IRTP Part B
WG deliberations in relation to this issue (see IRTP Part B Final
Report). (IRTP Part B Recommendation #8). The goal of these changes is
to clarify why the Lock has been applied and how it can be changed. Upon
review of the proposed plan, the GNSO Council will consider whether to
approve the recommendation.</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></TD></TR>
<TR>
<TD
style="BORDER-RIGHT: #dddddd 1pt solid; PADDING-RIGHT: 3.75pt; BORDER-TOP: medium none; PADDING-LEFT: 3.75pt; PADDING-BOTTOM: 3.75pt; BORDER-LEFT: #dddddd 1pt solid; PADDING-TOP: 3.75pt; BORDER-BOTTOM: #dddddd 1pt solid"
vAlign=top>
<P class=MsoNormal
style="MARGIN-BOTTOM: 3.75pt; LINE-HEIGHT: 13pt"><B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Resolved
(F),</SPAN></B><SPAN class=apple-converted-space><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN></SPAN><SPAN
lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">the GNSO
Council will consider IRTP Part B Recommendation #3 concerning the
request of an Issue Report on the requirement of 'thick' WHOIS for all
incumbent gTLDs at its next meeting on 21 July.</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></TD></TR>
<TR>
<TD
style="BORDER-RIGHT: #dddddd 1pt solid; PADDING-RIGHT: 3.75pt; BORDER-TOP: medium none; PADDING-LEFT: 3.75pt; PADDING-BOTTOM: 3.75pt; BORDER-LEFT: #dddddd 1pt solid; PADDING-TOP: 3.75pt; BORDER-BOTTOM: #dddddd 1pt solid"
vAlign=top>
<P class=MsoNormal
style="MARGIN-BOTTOM: 3.75pt; LINE-HEIGHT: 13pt"><B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">RESOLVED
(G),</SPAN></B><SPAN class=apple-converted-space><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN></SPAN><SPAN
lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">the GNSO
Council requests an Issue Report on IRTP Part C, which should
include:<SPAN class=apple-converted-space> </SPAN><BR>- "Change of
Control" function, including an investigation of how this function is
currently achieved, if there are any applicable models in the
country-code name space that can be used as a best practice for the gTLD
space, and any associated security concerns. It should also include a
review of locking procedures, as described in Reasons for Denial #8 and
#9, with an aim to balance legitimate transfer activity and security.
(IRTP Part B Recommendation #4)<SPAN
class=apple-converted-space> </SPAN><BR>- Whether provisions on
time-limiting </SPAN><SPAN lang=EN-US> </SPAN><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Form Of
Authentification</SPAN><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> (FOA<SPAN
style="COLOR: #1f497d">)</SPAN>s should be implemented to avoid
fraudulent transfers out. For example, if a Gaining Registrar sends and
receives an FOA back from a transfer contact, but the name is locked,
the registrar may hold the FOA pending adjustment to the domain name
status, during which time the registrant or other registration
information may have changed.<SPAN
class=apple-converted-space> </SPAN><BR>- Whether the process could
be streamlined by a requirement that registries use IANA IDs for
registrars rather than proprietary IDs.</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></TD></TR></TBODY></TABLE>
<P class=MsoNormal style="MARGIN-BOTTOM: 3pt"><A
name=Motions22June2011-MOTION2.%26nbsp%3BRE.R></A><B><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">MOTION 2. RE.
REVISION OF THE GNSO COUNCIL OPERATING PROCEDURES RELATING TO PROXY
VOTING</SPAN></B><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Made by:
Wolf-Ulrich Knoben<BR>Seconded by: Stéphane van Gelder</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">WHEREAS,
the GNSO Council recently identified areas for improvement in the GNSO Council
Operating Procedures that would simplify and clarify the procedures relating
to proxy voting;</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">WHEREAS,
the GNSO Council tasked the Operations Steering Committee (OSC) with
completing a revision to improve the procedures relating to proxy
voting;</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">WHEREAS,
the OSC submitted to the GNSO Council on 14 June 2011 recommended
revisions</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><A
href="http://gnso.icann.org/drafts/osc-recommended-revisions-proxy-voting-14jun11-en.pdf"><SPAN
lang=EN-US
style="COLOR: windowtext">http://gnso.icann.org/drafts/osc-recommended-revisions-proxy-voting-14jun11-en.pdf</SPAN></A></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> to
the GNSO Council Operating Procedures to simplify and clarify the procedures
relating to proxy voting;</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">NOW
THEREFORE, BE IT:</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">RESOLVED, that the
GNSO Council acknowledges receipt of the recommended revisions submitted by
the OSC and directs Staff produce a redlined revision of the GNSO Council
Operating Procedures incorporating the recommended revisions and to post this
document for twenty-one (21) days in the ICANN Public Comment
Forum.</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 7.5pt; LINE-HEIGHT: 13pt"><SPAN
lang=EN-US style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">RESOLVED
FURTHER, that the GNSO Council shall take formal action on these
recommendations, including potential modification, as soon as possible after
the conclusion of the public comment period. </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Please let me know
if you have any questions.</SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Thank
you.</SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Kind
regards,</SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Glen</SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Glen de Saint
Géry</SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">GNSO
Secretariat</SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><A
href="mailto:gnso.secretariat@gnso.icann.org">gnso.secretariat@gnso.icann.org</A></SPAN><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"><A
href="http://gnso.icann.org">http://gnso.icann.org</A><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Consolas"> <o:p></o:p></SPAN></P></DIV></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>