<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div>Since the RDAP comment period has been extended I can't attribute the opinions below to the whole SG, but let me just say that a significant number of registries agree on the following:<div class=""><br class=""></div><div class=""><div class=""><br class=""></div><div class="">
<!--[if gte mso 9]><xml>
<o:DocumentProperties>
<o:Revision>0</o:Revision>
<o:TotalTime>0</o:TotalTime>
<o:Pages>1</o:Pages>
<o:Words>2321</o:Words>
<o:Characters>13230</o:Characters>
<o:Company>Nic.br</o:Company>
<o:Lines>110</o:Lines>
<o:Paragraphs>31</o:Paragraphs>
<o:CharactersWithSpaces>15520</o:CharactersWithSpaces>
<o:Version>14.0</o:Version>
</o:DocumentProperties>
</xml><![endif]-->
<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>JA</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
<w:UseFELayout/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="--"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="276">
<w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" Priority="39" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" Name="toc 9"/>
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
</w:LatentStyles>
</xml><![endif]-->
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:Calibri;
color:black;
mso-ansi-language:EN-US;
mso-fareast-language:EN-US;}
</style>
<![endif]-->
<!--StartFragment--><p class="MsoNormal" align="center" style="margin-bottom:0cm;margin-bottom:.0001pt;
text-align:center;line-height:normal"><br class=""></p>
<div style="mso-element:para-border-div;border:none;border-top:solid windowtext 1.0pt;
mso-border-top-alt:solid windowtext .5pt;padding:1.0pt 0cm 0cm 0cm" class=""><p class="MsoNormal" style="border:none;mso-border-top-alt:solid windowtext .5pt;
padding:0cm;mso-padding-alt:1.0pt 0cm 0cm 0cm"><span lang="EN-US" class=""> </span></p>
</div><p class="MsoNormal" style="text-indent:36.0pt"><a name="h.c8dknkjvpiit" class=""></a><a name="h.gjdgxs" class=""></a><span lang="EN-US" class="">We welcome the work being done by ICANN to
develop a proposal for the many features of the Registration Data Access
Protocol (“RDAP”) that require agreement between clients and server operators
to develop interoperable implementations. We are, however, concerned that the
RDAP Operational Profile for gTLD Registries and Registrars” (the “Operational
Profile”) that has been proposed is specifically designed to produce
implementations of RDAP that are intended to meet the WHOIS requirements found
in the Registration Data Directory Service (“RDDS”) specifications in the gTLD
Registry Agreement, the 2013 Registrar Accreditation Agreement, the Additional
Whois Information Policy, and the RDDS Clarification Advisory. <o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">These documents
were written to describe requirements that can be (and are being) met using the
current WHOIS protocols. They do not consider the new capabilities available
through features specified in RDAP, and are thus incomplete. Any RDAP
implementation that is functionally equivalent to WHOIS remains functionally
deficient and fundamentally flawed from a policy standpoint. Since the creation of ICANN, work to update
WHOIS has been an ongoing process. Many constituencies and cross-constituency
groups within ICANN have worked diligently to address the many operational
issues associated with using the 33-year old WHOIS protocol to publish and
access domain registration metadata. <o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">On the policy
front, ICANN formed the Expert Working Group (EWG) on gTLD Directory Services
in early 2013 to "define the purpose of collecting and maintaining gTLD
registration data, and consider how to safeguard the data" and to
"provide a proposed model for managing gTLD directory services that
addresses related data accuracy and access issues, while taking into account
safeguards for protecting data."
The EWG’s final report, issued in June 2014, recommended that "a
new approach be taken for registration data access, abandoning entirely
anonymous access by everyone to everything in favor of a new paradigm that
combines public access to some data with gated access to other data." <o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class=""> </span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">Following the
EWG Final Report, the GNSO completed an Issues Report (submitted in October
2015) and has approved a motion for a Charter for the Next-Generation gTLD
Registration Directory Service (RDS) to replace WHOIS (Next-Gen RDS) PDP
WG. While adoption of this draft
Operational Profile is premature, it should prove to be useful for the
registries and registrars to consider during this policy work which is just
getting underway but is a long way from being complete.<o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">On the
technology front, the Internet Engineering Task Force (IETF) published a series
of RFC documents (RFCs 7480 - 7485) in March 2015 that specify RDAP, and
consistent with the EWG on gTLD Directory Services’ recommendation, the IETF’s
work on RDAP was focused on finding <i class="">new</i>
ways to provide registration data directory services by <i class="">replacing</i> WHOIS. For
instance, RFC 7482 describes the following significant WHOIS protocol
deficiencies: <o:p class=""></o:p></span></p><div style="margin: 0cm 0cm 0.0001pt 36pt; text-indent: -18pt;" class=""><!--[if !supportLists]--><span lang="EN-US" class="">1.<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Lack of standardized command
structures<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt 36pt; text-indent: -18pt;" class=""><!--[if !supportLists]--><span lang="EN-US" class="">2.<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Lack of standardized output and
error structures<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt 36pt; text-indent: -18pt;" class=""><!--[if !supportLists]--><span lang="EN-US" class="">3.<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Lack of support for
internationalization and localization<o:p class=""></o:p></span></div><p class="MsoNormalCxSpMiddle" style="margin-left:36.0pt;mso-add-space:auto;
text-indent:-18.0pt;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span lang="EN-US" class="">4.<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Lack of support for user
identification, authentication and access control.<o:p class=""></o:p></span></p><p class="MsoNormal"><span lang="EN-US" class=""> </span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">As currently
specified in the IETF RFC’s, RDAP addresses all of these deficiencies. The RFCs
also describe a number of options for use in different operating environments,
so there are many instances of decisions that need to be made by implementers
to meet specific operating requirements. One specific example associated with
deficiency #4 is found in the client authentication options described in RFC
7481. RDAP can be used with all of the authentication options supported by the
Hypertext Transfer Protocol (HTTP), but not all of these options will work well
in the domain registration operating environment. Additional specifications
need to be written and additional decisions need to be made to implement and
deploy a usable solution. Another specific example is that the domain status
values described in RDAP do not map consistently to the domain status values
defined in the Extensible Provisioning Protocol (EPP). Work needs to be done to
develop a mapping of status values between the protocols to maintain
consistency of interpretation.<o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">RDAP was
designed to address the WHOIS deficiencies and the EWG on gTLD Directory
Services’ recommendations, but as currently proposed, the Operational Profile
only provides the benefits of standardized command, output and error structures
(deficiencies 1 and 2 above). The proposed Operational Profile fails to address
internationalization and localization of contact information (deficiency 3) and
also fails to include support for RDAP's user identification, authentication
and access control features (deficiency 4). As noted by the EWG, these features
are needed to provide data privacy by restricting data access to appropriately
authorized users. As currently written, the Operational Profile continues the
practice of exposing personally identifiable information to anyone who asks. <o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class=""> </span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">An approach that
does not include support for RDAP's internationalization and data privacy
supporting features and fails to address the most significant issues with WHOIS
turns unsolved WHOIS problems into unsolved RDAP problems, and our industry’s
history of failure to resolve WHOIS deficiencies will be repeated.<o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">For example,
Section 1.4.1 of the Operational Profile is inconsistent with the guidance
given in RFC 7482 regarding processing of RDAP queries containing a mixture of
IDN A-labels and U-labels. Per RFC 7482, “IDNs SHOULD NOT be represented as a
mixture of A-labels and U-labels; that is, internationalized labels in an IDN
SHOULD be either all A-labels or all U-labels”. Section 1.4.1 of the proposed
Operational Profile requires that “The RDAP server MUST support
Internationalized Domain Name (IDN) RDAP lookup queries using A-label or
U-label format [RFC 5890] for domain name and name server objects. The RDAP
server MUST accept a mixture of the two (i.e. A-label and U-label format) in
the same RDAP lookup query”. This requirement is not only inconsistent with RFC
7482, it is also counter to the consensus of the IETF community regarding
appropriate processing of IDN queries.<o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">To provide
another example, Section 1.4.11 of the proposed Operational Profile says that
“If permitted or required by an ICANN agreement provision, waiver, or Consensus
Policy, an RDAP response may contain redacted registrant, administrative,
technical and/or other contact information”. While this is useful in the
context of providing differentiated access to data for some top-level domains
that include a relatively small number of registered domains, it fails to
address the data privacy issue associated with open, public access to
Personally Identifiable Information (PII) associated with domain name
registration. One technology that can be used to provide differentiated access
in RDAP exists today and has been documented as a Standards Track Internet
Draft titled “<a href="https://datatracker.ietf.org/doc/draft-hollenbeck-weirds-rdap-openid/" class=""><span style="color:blue" class="">Federated Authentication for the Registration Data Access
Protocol (RDAP) using OpenID Connect</span></a>”. What's missing are the
policies associated with determining appropriate levels of access based on a
user's identity and their "need to know", or stated query purpose.
This gap in policy development should be addressed expeditiously and <i class="">before</i> the RDAP requirements are
finalized to take full advantage of the capabilities available in RDAP to
address internationalization, localization and privacy.<o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">Section 3 of the
Operational Profile describes implementation requirements for registrars. The
requirements for registrar implementation should be consistent with the 2013
Registrar Accreditation Agreement. This
implementation requirement will require registrars to commit significant
resources to develop, deploy, and operate a software service that will
ultimately end up being discarded when and if all gTLD registries are required
to provide thick services themselves. This is not a commercially reasonable
requirement.<o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">Further to
reasonable commercial considerations, with regard to 1.3.6 of the profile,
which states: <o:p class=""></o:p></span></p><div style="margin: 0cm 0cm 0.0001pt 36pt; line-height: normal;" class=""><span lang="EN-US" style="mso-bidi-font-family:Helvetica;color:windowtext" class="">"RDAP extensions,
if used, MUST be registered in the IANA's RDAP Extensions registry (</span><span lang="EN-US" class=""><a href="https://www.iana.org/assignments/rdapextensions/rdap-extensions.xhtml" class=""><span style="mso-bidi-font-family:Helvetica;color:#114EE6" class="">https://www.iana.org/assignments/rdapextensions/rdap-extensions.xhtml</span></a></span><span lang="EN-US" style="mso-bidi-font-family:Helvetica;color:windowtext" class="">), as
defined in RFC7480. Deployment of RDAP extensions in gTLD Registries operated
under agreement with ICANN, are subject to approval by ICANN via the RSEP
process."<o:p class=""></o:p></span></div><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
normal;mso-pagination:none;mso-layout-grid-align:none;text-autospace:none"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;color:windowtext" class=""> </span></p><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;text-indent:
36.0pt;line-height:normal;mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;
color:windowtext" class="">If the extensions are RFC standards applicable to domain name
registration services, it may be unnecessary for every registry to submit an
RSEP. If an RSEP is not approved, is the registry thus in violation of
its contract with ICANN, which requires adoption of the new RFCs? It is
not commercially viable to submit to the RSEP process for every TLD to adopt an
RFC standard that is required per the contract.<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;text-indent:
36.0pt;line-height:normal;mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;
color:windowtext" class=""> </span></p><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;text-indent:
36.0pt;line-height:normal;mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;
color:windowtext" class="">With regard to section 2.6.1., which states: “Specification 3
of the RA specifies the format and content of the monthly reporting for
Registry operators. The following rows are added to the Registry Functions
Activity Report under section 2:<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;text-indent:
36.0pt;line-height:normal;mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;
color:windowtext" class="">40 rdap-queries Number of RDAP queries during the
period. <o:p class=""></o:p></span></p><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;text-indent:
36.0pt;line-height:normal;mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;
color:windowtext" class="">41 rdap-rate-limit Number of RDAP queries refused due to rate
limiting for the period. <o:p class=""></o:p></span></p><div style="margin: 0cm 0cm 0.0001pt 36pt; line-height: normal;" class=""><span lang="EN-US" style="mso-bidi-font-family:Helvetica;color:windowtext" class="">42 rdap-redirects
Number of HTTP redirects for the period. 42 rdap-authenticated Number of
authenticated RDAP queries for the period. <o:p class=""></o:p></span></div><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;text-indent:
36.0pt;line-height:normal;mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;
color:windowtext" class="">43 rdap-search-domain Number of RDAP domain search queries
for the period. <o:p class=""></o:p></span></p><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;text-indent:
36.0pt;line-height:normal;mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;
color:windowtext" class="">44 rdap-search-entity Number of RDAP entity search queries
for the period. <o:p class=""></o:p></span></p><div style="margin: 0cm 0cm 0.0001pt 36pt; line-height: normal;" class=""><span lang="EN-US" style="mso-bidi-font-family:Helvetica;color:windowtext" class="">45
rdap-truncatedauthorization Number of RDAP responses truncated due to
authorization. Includes both results and object truncation events. <o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt 36pt; line-height: normal;" class=""><span lang="EN-US" style="mso-bidi-font-family:Helvetica;color:windowtext" class="">46 rdap-truncated-load
Number of RDAP responses truncated due to server load. Includes both results
and object truncation events.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt 36pt; line-height: normal;" class=""><span lang="EN-US" style="mso-bidi-font-family:Helvetica;color:windowtext" class="">47
rdap-truncatedunexplainable Number of RDAP responses truncated due to
unexplainable reasons. Includes both results and object truncation”<o:p class=""></o:p></span></div><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
normal;mso-pagination:none;mso-layout-grid-align:none;text-autospace:none"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;color:windowtext" class=""> </span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" style="mso-bidi-font-family:Helvetica;color:windowtext" class="">These are new
requirements for monthly reports, and represent a change to the Registry
Agreement and thus should be negotiated with registries and not be part of an
operational profile. The applicable Registry Agreements do not provide
ICANN the latitude to add required outputs. For instance, according to
the 2012 New gTLD RA: "ICANN may request in the future that the reports be
delivered by other means and using other formats." This (and similar
language in other gTLD RAs) does not provide ICANN the specific right to
unilaterally require additional fields.</span><span lang="EN-US" class=""><o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">Appendix A of
the Operational Profile notes that additional protocol specifications are
needed to map Extensible Provisioning Protocol (EPP) domain status codes to
RDAP status codes and extend RDAP to include events that describe the registrar
expiration date (which also requires an EPP extension) and the date of the most
recent database update. As of today only the domain status mappings are
described in an Internet-Draft. The requirement to include these features adds
a dependency on the IETF’s standards development process that adds scope and
schedule risk. Another significant concern with the Operational Profile is in
understanding how it fits into all of the other WHOIS-related work that is
currently under way. The profile fails to describe how we will ever realize a
fully functional RDAP service that addresses all of the known WHOIS
deficiencies, and it fails to describe how the profile relates to other
WHOIS-related activities taking place in ICANN. A comprehensive,
well-articulated plan that describes how all of the existing work fits into a
larger strategic effort would go a long way towards mitigating the risks of
contracted parties having to implement multiple incomplete solutions. This plan
should be developed through a community-based process such as the Thick WHOIS
Implementation Review Team that is in progress. <o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">We are also
concerned about the approach being taken to develop the profile itself<a href="#_ftn1" name="_ftnref1" title="" class=""><sup class=""><!--[if !supportFootnotes]--><sup class=""><span lang="EN-US" style="font-size:11.0pt;line-height:115%;font-family:Calibri;
mso-fareast-font-family:Calibri;mso-bidi-font-family:Calibri;color:windowtext;
mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA" class="">[1]</span></sup><!--[endif]--></sup></a>.
The IETF has a long tradition of documenting protocol implementation profiles
using the Internet-Draft and Informational RFC publication process. Here are a
few recent examples: <o:p class=""></o:p></span></p><div style="margin: 0cm 0cm 0.0001pt 36pt; text-indent: -18pt;" class=""><!--[if !supportLists]--><span lang="EN-US" style="font-family:Arial;mso-fareast-font-family:Arial" class="">●<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Adobe's RTMFP Profile for Flash
Communication (RFC 7425)<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt 36pt; text-indent: -18pt;" class=""><!--[if !supportLists]--><span lang="EN-US" style="font-family:Arial;mso-fareast-font-family:Arial" class="">●<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Suite B Profile for Transport
Layer Security (TLS) (RFC 6460)<o:p class=""></o:p></span></div><p class="MsoNormalCxSpMiddle" style="margin-left:36.0pt;mso-add-space:auto;
text-indent:-18.0pt;mso-list:l2 level1 lfo3"><!--[if !supportLists]--><span lang="EN-US" style="font-family:Arial;mso-fareast-font-family:Arial" class="">●<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Suite B Profile of Certificate
Management over CMS (RFC 6403)<o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">The registration
industry used the IETF process to develop the RDAP protocol specifications. We
should use the same IETF process to document an RDAP implementation profile and
gain consensus for the proposals.<o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">While it may not
be feasible to expect that the implementation of RDAP should be dependent on a
complete solution that addresses every shortfall or potential enhancement, the
community must consider the inefficiency and unnecessary churn of a piecemeal
implementation plan that is a replication of the current systems without
clearly articulated benefits. There is significant risk to RDAP becoming yet
another failed attempt to replace WHOIS unless there is a clear understanding
of the logical sequence of steps that must be taken to address each and every
WHOIS deficiency recognized by the community as a whole. As proposed, the
Operational Profile does not do this.<o:p class=""></o:p></span></p><p class="MsoNormal" style="text-indent:36.0pt"><span lang="EN-US" class="">In summary, we
believe that the following things need to be done before useful, efficient
implementations of RDAP can be developed and deployed to provide maximum
benefit to both users and operators:<o:p class=""></o:p></span></p><div style="margin: 0cm 0cm 0.0001pt 36pt; text-indent: -18pt;" class=""><!--[if !supportLists]--><span lang="EN-US" class="">1.<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Policy development work should
be completed before production implementations are required.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt 36pt; text-indent: -18pt;" class=""><!--[if !supportLists]--><span lang="EN-US" class="">2.<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Needed protocol specifications
(EPP status mapping, new EPP extensions, federated authentication, etc.) should
be completed before production implementations are required.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt 36pt; text-indent: -18pt;" class=""><!--[if !supportLists]--><span lang="EN-US" class="">3.<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Operators should be given the
opportunity to deploy experimental pilots, prototypes, and reference
implementations to inform the development of policies and production services.
This will also give ICANN an opportunity to test SLA monitoring interfaces and
prototypes in parallel so they can be fully supported by operators when
production services are deployed.<o:p class=""></o:p></span></div><p class="MsoNormalCxSpMiddle" style="margin-left:36.0pt;mso-add-space:auto;
text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span lang="EN-US" class="">4.<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">A clear statement of direction
that ties the multitude of policy efforts together should be developed and
approved by the ICANN community.<o:p class=""></o:p></span></p><p class="MsoNormalCxSpMiddle" style="margin-left:36.0pt;mso-add-space:auto;
text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span lang="EN-US" class="">5.<span style="font-size: 7pt; line-height: normal; font-family: 'Times New Roman';" class="">
</span></span><!--[endif]--><span lang="EN-US" class="">Replacing WHOIS with RDAP now,
even though it won't take advantage of key RDAP features, would likely require
rework of the RA and RAA 2013 and therefore lead to the necessity of contract
modifications prior to implementation of RDAP by all ROs & Registrars later
after the policy and standards work is done.<o:p class=""></o:p></span></p><p class="MsoNormal"><span lang="EN-US" class=""> </span></p><p class="MsoNormal"><span lang="EN-US" class="">Thank you for your consideration.<o:p class=""></o:p></span></p>
<div class=""><!--[if !supportFootnotes]--><br clear="all" class="">
<hr align="left" size="1" width="33%" class="">
<!--[endif]-->
<div id="ftn1" class=""><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
normal"><a href="#_ftnref1" name="_ftn1" title="" class=""><sup class=""><span lang="EN-US" class=""><!--[if !supportFootnotes]--><sup class=""><span lang="EN-US" style="font-size:11.0pt;line-height:115%;font-family:Calibri;
mso-fareast-font-family:Calibri;mso-bidi-font-family:Calibri;color:windowtext;
mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA" class="">[1]</span></sup><!--[endif]--></span></sup></a><span lang="EN-US" class=""> Proceeding to implementation now based on the Operational Profile
creates potential contractual issues, as the obligations to implement a
successor protocol to WHOIS found in the applicable Registry Agreements and in
the 2013 Registrar Accreditation Agreement do not contemplate compliance with a
“profile” developed by ICANN staff, but rather a “standard” developed by the
IETF. Moreover, given the unfinished
work, it would appear the Profile cannot be implemented on a “commercially
reasonable” basis, also a contractual requirement.<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:
normal"><span lang="EN-US" class=""> </span></p>
</div>
</div>
<!--EndFragment--><div><blockquote type="cite" class=""><div class="">Em 16 de fev de 2016, à(s) 18:37:000, Marika Konings <<a href="mailto:marika.konings@icann.org" class="">marika.konings@icann.org</a>> escreveu:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">Dear All,</div>
<div class=""><br class="">
</div>
<div class="">On behalf of my colleague Francisco Arias from the GGD Team, please find attached the requested briefing paper on the Registry Data Access Protocol (RDAP) to help inform you deliberations on this topic per item 7 on the GNSO Council Agenda for Thursday’s
meeting (Item 7: Briefing & Discussion – RDAP Implementation). </div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class=""><br class="">
</div>
<div class="">Marika</div>
</div>
<span id="cid:F340F167BF98E741B4247F9AA1F3EDD0@pexch112.icann.org"><Briefing to GNSO on the Migration to RDAP - 16 February 2016.pdf></span></div></blockquote></div><br class=""></div></div></body></html>