<!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 content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19328">
<STYLE><!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:"Gill Sans MT";
panose-1:2 11 5 2 2 1 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Arial","sans-serif";}
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.SingleSpace, li.SingleSpace, div.SingleSpace
{mso-style-name:"Single Space";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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=EN-US link=blue vLink=purple>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=758441615-14102012>FYI</SPAN></FONT></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=de><FONT size=2 face="Courier New">Wolf-Ulrich Knoben
</FONT></SPAN></P>
<DIV> </DIV><BR>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px" dir=ltr>
<DIV dir=ltr lang=de class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>Von:</B> Winterfeldt, Brian
[mailto:bwinterfeldt@steptoe.com] <BR><B>Gesendet:</B> Sonntag, 14. Oktober
2012 11:13<BR><B>An:</B> Stéphane Van Gelder
(stephane.vangelder@indom.com)<BR><B>Cc:</B> Neuman, Jeff
(Jeff.Neuman@neustar.us); Knoben, Wolf-Ulrich<BR><B>Betreff:</B> FW:
Suggestions for Compromise re WHOIS RT Final Report -- PROPOSED
DRAFT<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="COLOR: black; FONT-SIZE: 11pt">FYI<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: black; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><B><SPAN style="COLOR: black; FONT-SIZE: 9pt">Brian J.
Winterfeldt <o:p></o:p></SPAN></B></P>
<P class=MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 9pt">Partner
<o:p></o:p></SPAN></P>
<P style="MARGIN-BOTTOM: 7pt" class=MsoNormal><A
href="mailto:bwinterfeldt@steptoe.com"><SPAN
style="FONT-SIZE: 9pt">bwinterfeldt@steptoe.com</SPAN></A><SPAN
style="COLOR: #971b2f; FONT-SIZE: 9pt"><o:p></o:p></SPAN></P>
<P style="MARGIN-BOTTOM: 1pt" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Georgia','serif'; LETTER-SPACING: -1pt; COLOR: #971b2f; FONT-SIZE: 20pt">Steptoe<o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'"> Winterfeldt, Brian
<BR><B>Sent:</B> Sunday, October 14, 2012 11:08 AM<BR><B>To:</B> Wendy Seltzer
(wendy@seltzer.com)<BR><B>Subject:</B> Suggestions for Compromise re WHOIS RT
Final Report -- PROPOSED DRAFT<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=SingleSpace><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'">Dear
Wendy,<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'"><BR>Please
find below the beginning of a working draft I put together last night to try
to suggest were both of our groups can possibly compromise. Please
review with your SG and let me know if you think there is room for negotiation
on any of the below points. <o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'">Many
thanks for your time to try to reach some additional consensus before
reporting to the Board. I appreciate the opportunity to work with you on
this.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'">Best,<BR><BR>Brian<o:p></o:p></SPAN></P>
<P style="TEXT-ALIGN: center" class=SingleSpace align=center><B><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></B></P>
<P style="TEXT-ALIGN: center" class=SingleSpace align=center><B><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></B></P>
<P style="TEXT-ALIGN: center" class=SingleSpace align=center><B><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'">WHOIS
RT Final Report<o:p></o:p></SPAN></B></P>
<P style="TEXT-ALIGN: center" class=SingleSpace align=center><B><SPAN
style="FONT-VARIANT: small-caps; FONT-FAMILY: 'Gill Sans MT','sans-serif'">Suggestions
for Compromise – Implementation vs. Policy
Development<o:p></o:p></SPAN></B></P>
<P style="TEXT-ALIGN: center" class=SingleSpace align=center><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P style="TEXT-ALIGN: justify; TEXT-INDENT: 0.5in" class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">At its Board Meeting on
October 18, 2012, the ICANN Board is scheduled to vote as to how to move
forward with the 16 recommend<A name=Verdatum></A>ations contained in the
WHOIS Review Team Final Report. To date, despite the Board’s request for
input, the GNSO Council has been unable to provide cohesive advice due to a
disparity among constituencies and stakeholder groups as to which
recommendations should require a PDP and which may be implemented without a
PDP. In order to ensure that the Council has the opportunity to provide
meaningful input to the Board, it appears a compromise would be necessary on
this point. This document sets forth suggestions for compromise from
both the NCSG and IPC and/or BC in order to allow the Council to provide
guidance to the Board on as many of the RT’s recommendations as
possible.<o:p></o:p></SPAN></P>
<P style="TEXT-ALIGN: justify; TEXT-INDENT: 0.5in" class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><B><U><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">Existing Full Consensus that
PDP Needed – No Compromise Required</SPAN></U></B><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">:<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">10a. The Review Team
recommends that ICANN should initiate processes to regulate and oversee
privacy and proxy service providers.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">10b. The Review Team
considers that one possible approach to achieving this would be to establish,
through the appropriate means, an accreditation system for all proxy/privacy
service providers. As part of this process, ICANN should consider the merits
(if any) of establishing or maintaining a distinction between privacy and
proxy services.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">10c. The goal of this
process should be to provide clear, consistent and enforceable requirements
for the operation of these services consistent with national laws, and to
strike an appropriate balance between stakeholders with competing but
legitimate interests. At a minimum, this would include privacy, data
protection, law enforcement, the industry around law enforcement and the human
rights community.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">10d. ICANN could, for
example, use a mix of incentives and graduated sanctions to encourage
proxy/privacy service providers to become accredited, and to ensure that
registrars do not knowingly accept registrations from unaccredited
providers.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">10e. ICANN could
develop a graduated and enforceable series of penalties for proxy/privacy
service providers who violate the requirements, with a clear path to
de-accreditation for repeat, serial or otherwise serious
breaches.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">10f. In considering the
process to regulate and oversee privacy/proxy service providers, consideration
should be given to the following objectives: . . .<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><B><U><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">Suggestions for NCSG To
Consider Possibly Compromising on position that No PDP Needed (I am of course
not suggesting that you compromise necessarily on all these points - but
thought it might be helpful to identify ones to focus your review on from my
analysis of the various positions and points at issue)</SPAN></U></B><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">:<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><I><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">Please note that these
recommendations generally relate to ICANN data/report generation and other
administrative functions to be completed by ICANN
staff.<o:p></o:p></SPAN></I></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">1. It is recommended
that WHOIS, in all its aspects, should be a strategic priority for ICANN the
organization. It should form the basis of staff incentivization and published
organizational objectives.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">3. ICANN should ensure
that WHOIS policy issues are accompanied by cross-community outreach,
including outreach to the communities outside of ICANN with a specific
interest in the issues, and an ongoing program for consumer
awareness.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">4. ICANN should act to
ensure that its compliance function is managed in accordance with best
practice principles . . .<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">5. ICANN should ensure
that the requirements for accurate WHOIS data are widely and pro-actively
communicated, including to current and prospective Registrants, and should use
all means available to progress WHOIS accuracy, including any
internationalized WHOIS data, as an organizational objective. <I>(note: NCSG
position not included on recommendation chart)<o:p></o:p></I></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">7. ICANN shall produce
and publish an accuracy report focused on measured reduction in WHOIS
registrations that fall into the accuracy groups Substantial Failure and Full
Failure, on an annual basis.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">9a. The ICANN Board
should ensure that the Compliance Team develop, in consultation with relevant
contracted parties, metrics to track the impact of the annual WHOIS Data
Reminder Policy (WDRP) notices to registrants. Such metrics should be used to
develop and publish performance targets, to improve data accuracy over
time.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">11. It is recommended
that the Internic Service is overhauled to provide enhanced usability for
consumers, including the display of full registrant data for all gTLD domain
names (whether those gTLDs operate thin or thick WHOIS services) in order to
create a one stop shop, from a trusted provider, for consumers and other users
of WHOIS services.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">12. ICANN should task a
working group within six months of publication of this report, to determine
appropriate internationalized domain name registration data requirements and
evaluate available solutions (including solutions being implemented by
ccTLDs). At a minimum, the data requirements should apply to all new gTLDs,
and the working group should consider ways to encourage consistency of
approach across the gTLD and (on a voluntary basis) ccTLD space. The working
group should report within a year of being tasked.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">16. ICANN should
provide at least annual written status reports on its progress towards
implementing the recommendations of this WHOIS Review Team. The first of these
reports should be published one year, at the latest, after ICANN publishes the
implementation plan mentioned in recommendation 15, above. Each of these
reports should contain all relevant information, including all underlying
facts, figures and analyses.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><B><U><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">Suggestions for IPC and/or BC
Compromise that a PDP Can or Should be Conducted</SPAN></U></B><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">:<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">6. ICANN should take
appropriate measures to reduce the number of WHOIS registrations that fall
into the accuracy groups Substantial Failure and Full Failure (as defined by
the NORC Data Accuracy Study, 2009/10) by 50% within 12 months and by 50%
again over the following 12 months.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">9b. If this
[development of certain metrics] is unfeasible with the current system, the
Board should ensure that an alternative, effective policy is developed (in
accordance with ICANN’s existing processes) and implemented in consultation
with registrars that achieves the objective of improving data quality, in a
measurable way.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">13. The final data
model, including (any) requirements for the translation or transliteration of
the registration data, should be incorporated in the relevant Registrar and
Registry agreements within 6 months of adoption of the working group’s
recommendations by the ICANN Board. If these recommendations are not finalized
in time for the next revision of such agreements, explicit placeholders for
this purpose should be put in place in the agreements for the new gTLD program
at this time, and in the existing agreements when they come up for
renewal.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><B><U><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">Further Analysis Necessary –
No Clear Majority Position and/or Clarifications Needed from One or More
Constituencies or Stakeholder Groups</SPAN></U></B><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">:<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">2. The ICANN Board
should oversee the creation of a single WHOIS policy document, and reference
it in subsequent versions of agreements with Contracted
Parties.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">8. ICANN should ensure
that there is a clear, unambiguous and enforceable chain of contractual
agreements with registries, registrars, and registrants to require the
provision and maintenance of accurate WHOIS data. As part of these agreements,
ICANN should ensure that clear, enforceable and graduated sanctions apply to
registries, registrars and registrants that do not comply with its WHOIS
policies. These sanctions should include de-registration and/or
de-accreditation as appropriate in cases of serious or serial
non-compliance.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">14. In addition,
metrics should be developed to maintain and measure the accuracy of the
internationalized registration data and corresponding data in ASCII, with
clearly defined compliance methods and targets, as per the details in
Recommendations 5-9 in this document.<o:p></o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=SingleSpace><SPAN
style="FONT-FAMILY: 'Gill Sans MT','sans-serif'">15. ICANN should
provide a detailed and comprehensive plan within 3 months after the submission
of the Final WHOIS Review Team report that outlines how ICANN will move
forward in implementing these recommendations.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><B><SPAN style="FONT-SIZE: 9pt">Brian J. Winterfeldt
<o:p></o:p></SPAN></B></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">Partner <o:p></o:p></SPAN></P>
<P style="MARGIN-BOTTOM: 7pt" class=MsoNormal><A
href="mailto:bwinterfeldt@steptoe.com"><SPAN
style="FONT-SIZE: 9pt">bwinterfeldt@steptoe.com</SPAN></A><SPAN
style="COLOR: #971b2f; FONT-SIZE: 9pt"><o:p></o:p></SPAN></P>
<P style="MARGIN-BOTTOM: 1pt" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Georgia','serif'; LETTER-SPACING: -1pt; COLOR: #971b2f; FONT-SIZE: 20pt">Steptoe<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt"><o:p> </o:p></SPAN></P>
<TABLE style="BORDER-COLLAPSE: collapse" class=MsoNormalTable border=0
cellSpacing=0 cellPadding=0>
<TBODY>
<TR style="HEIGHT: 50.8pt">
<TD
style="PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; WIDTH: 113.4pt; PADDING-RIGHT: 0in; HEIGHT: 50.8pt; PADDING-TOP: 0in"
vAlign=top width=151>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">+1 202 429 6260
direct<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">+1 202 903 4422
mobile<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">+1 202 429 3902
fax<o:p></o:p></SPAN></P></TD>
<TD
style="PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; WIDTH: 252.4pt; PADDING-RIGHT: 0in; HEIGHT: 50.8pt; PADDING-TOP: 0in"
vAlign=top width=337>
<P class=MsoNormal><B><SPAN style="FONT-SIZE: 9pt">Steptoe & Johnson
LLP - DC<o:p></o:p></SPAN></B></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">1330 Connecticut Avenue,
NW<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">Washington, DC
20036<o:p></o:p></SPAN></P>
<P class=MsoNormal><A href="http://www.steptoe.com/"><SPAN
style="FONT-SIZE: 9pt">www.steptoe.com</SPAN></A><SPAN
style="COLOR: #971b2f; FONT-SIZE: 9pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 9pt"><o:p> </o:p></SPAN></P></TD></TR>
<TR style="HEIGHT: 50.8pt">
<TD
style="PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; WIDTH: 113.4pt; PADDING-RIGHT: 0in; HEIGHT: 50.8pt; PADDING-TOP: 0in"
vAlign=top width=151>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">+1 212.506.3935
direct<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">+1 212.506.3950
fax<o:p></o:p></SPAN></P></TD>
<TD
style="PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; WIDTH: 252.4pt; PADDING-RIGHT: 0in; HEIGHT: 50.8pt; PADDING-TOP: 0in"
vAlign=top width=337>
<P class=MsoNormal><B><SPAN style="FONT-SIZE: 9pt">Steptoe & Johnson
LLP – New York<o:p></o:p></SPAN></B></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">1114 Avenue of the
Americas<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">New York, NY
10036<o:p></o:p></SPAN></P></TD></TR></TBODY></TABLE>
<P class=MsoNormal><SPAN style="FONT-SIZE: 8pt">This message and any attached
documents contain information from the law firm Steptoe & Johnson LLP that
may be confidential and/or privileged. If you are not the intended recipient,
please do not read, copy, distribute, or use this information. If you have
received this transmission in error, please notify the sender immediately by
reply e-mail and then delete this message.<o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BLOCKQUOTE></BODY></HTML>