<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote
cite="mid:091f5915-e68a-d6c2-8d1f-652380dfe981@xs4all.nl"
type="cite">
<p> The resource records related to the RDAP service MUST be
signed with DNSSEC, and the DNSSEC chain of trust from the root
trust anchor to the name of the RDAP server MUST be valid at all
times.<br>
-Looks sensible, but I cannot find this in the RFC's mentioned,
is the above language a result of this?<br>
</p>
</blockquote>
Another case of "nice to have, so let's add it!"?<br>
<blockquote
cite="mid:091f5915-e68a-d6c2-8d1f-652380dfe981@xs4all.nl"
type="cite">
<p>The domain object in the RDAP response MUST contain entities
with the following roles. Exactly one entity per role MUST be
present in the response.<br>
-TG-Most gTLDs support more roles. Is there no support or does
the policy ends this support for more roles?<br>
</p>
</blockquote>
Better require a minimum of one entity per role to remain
consistent.<br>
<blockquote
cite="mid:091f5915-e68a-d6c2-8d1f-652380dfe981@xs4all.nl"
type="cite">
<p> -RDAP does not support a country code for a contact, rather
RDAP requires a full country name. <br>
-TG- This, is a mapping nightmare, not everyone supports the
official mapping, not sure how much work this is and will vary
from Registrar to Registrar. <br>
</p>
</blockquote>
RDAP requires full countryname in what language? Should we for
example put Deutschland, Duitsland, Germany, Allemangne, <span
class="st">德国 (</span><span class="st">Dégúo), </span>Tyskland,
ma Tosi, Đức, <span xml:lang="ko" lang="ko">독일 (Dogil), </span><span
xml:lang="ko" lang="ko"><span xml:lang="ja" lang="ja">ドイツ </span>(Doitsu),
or all of the above and more? Keeping the country code makes
sense, replacing it does not.<br>
Common sense should prevail over non-sense, or nonsense!<br>
</span>
<blockquote
cite="mid:091f5915-e68a-d6c2-8d1f-652380dfe981@xs4all.nl"
type="cite">
<p> If the queried domain name is allocated, the following
applies: If allocated variant domain names exist for the queried
domain name, or if the domain name is an allocated variant
domain name, the domain object in the RDAP response MUST contain
a variants member [RFC7483].<br>
-TG- We do not store this, and it seems to contradict the
following in the profile :"The purpose of this profile is to
specify the RDAP requirements that are in line with the current
Whois service requirements."</p>
</blockquote>
+1<br>
<br>
Best regards,<br>
<br>
Volker<br>
<blockquote
cite="mid:091f5915-e68a-d6c2-8d1f-652380dfe981@xs4all.nl"
type="cite">
<div class="moz-cite-prefix">On 24-9-2016 20:10, Dennis Chang
wrote:<br>
</div>
<blockquote
cite="mid:495B7396-8FF8-4957-AB29-4A47FBEA6A48@icann.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"맑은 고딕";}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:706226007;
mso-list-template-ids:-299753162;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1344673307;
mso-list-template-ids:2119488800;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Theo,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">This is
the first item on the agenda for the IRT meeting on
Tuesday.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Please
keep the questions coming.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">If you
could provide specifics on “irregularities within RDAP”
and “clarification on a few issues” in advance, that will
help us to prepare better for our team discussion.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black">Thanks<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black">Dennis Chang</span><span
style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span
style="color:black">theo geurts <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:gtheo@xs4all.nl"><gtheo@xs4all.nl></a><br>
<b>Date: </b>Thursday, September 22, 2016 at 1:16 AM<br>
<b>To: </b>"Anderson, Marc" <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:mcanderson@verisign.com"><mcanderson@verisign.com></a>,
Dennis Chang <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:dennis.chang@icann.org"><dennis.chang@icann.org></a>,
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:gnso-impl-thickwhois-rt@icann.org">"gnso-impl-thickwhois-rt@icann.org"</a>
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:gnso-impl-thickwhois-rt@icann.org"><gnso-impl-thickwhois-rt@icann.org></a><br>
<b>Subject: </b>Re: [Gnso-impl-thickwhois-rt] Proposed
Path Forward | Thick Whois CL&D Policy, RDAP and
RySG Request for Reconsideration<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman""><o:p> </o:p></span></p>
</div>
<p><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Dennis,<br>
<br>
This looks like the path forward, and I am supportive of the
proposed path forward as a Registrar.<br>
<br>
Perhaps I am jumping the gun here, but how would this
dialogue with the community take place? <br>
Furthermore, how do we address irregularities within RDAP?
Or get clarification on a few issues that I assume have not
been discussed yet?<br>
<br>
Thanks, <br>
<br>
Theo <br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">On 21-9-2016 19:58, Anderson, Marc
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D">Dennis,</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D">Thank you for the
excellent explanation and details. On behalf of
Verisign and as a member of the RySG I would like to
express my support for the revised CL&D policy and
the path forward you have laid out.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D">Thank you,</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D">Marc Anderson</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:Tahoma">From:</span></b><span
style="font-size:10.0pt;font-family:Tahoma"> <a
moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">mailto:gnso-impl-thickwhois-rt-bounces@icann.org</a>]
<b>On Behalf Of </b>Dennis Chang<br>
<b>Sent:</b> Wednesday, September 21, 2016 1:42 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br>
<b>Subject:</b> [Gnso-impl-thickwhois-rt] Proposed
Path Forward | Thick Whois CL&D Policy, RDAP and
RySG Request for Reconsideration</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Dear IRT members,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">As you know, on 7 February 2014, the
ICANN Board adopted GNSO consensus policy recommendations
regarding the provision of “Thick” Whois by all gTLD
registries.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">In consultation with the consensus
policy Implementation Review Team (IRT), the
implementation team identified two expected outcomes in
the policy development process (PDP) recommendations:<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l1 level1 lfo3">The
consistent labeling and display of WHOIS output for all
gTLDs <o:p></o:p></li>
<li class="MsoNormal" style="mso-list:l1 level1 lfo3">The
transition from Thin to Thick WHOIS for .COM, .NET and
.JOBS <o:p></o:p></li>
</ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The first outcome was published as a
consensus policy, the <a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_rdds-2Dlabeling-2Dpolicy-2D2016-2D07-2D26-2Den&d=DQMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=dqLP1wJqBvDSYLKrSEaAkCi_Kv0Mk5D_d32n29DHCN8&m=pkBrE3ogDYFgpWAATzOOdmRD93_Pz1PCrWtnSZN7Lg4&s=7mN42JF9avjgJDjFj4ZrjgmhMajcH8mgr2MOTxILGts&e=">Registry
Registration Data Directory Services Consistent Labeling
and Display Policy[icann.org]</a> (CL&D Policy), on
26 July 2016.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">In August 2016, the Registry
Stakeholder Group (RySG) submitted a <a
moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_reconsideration-2D16-2D10-2Drysg-2Drequest-2D2016-2D08-2D11-2Den&d=DQMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=dqLP1wJqBvDSYLKrSEaAkCi_Kv0Mk5D_d32n29DHCN8&m=pkBrE3ogDYFgpWAATzOOdmRD93_Pz1PCrWtnSZN7Lg4&s=f3NsGYRUd-AUuYr1fLckI0cksGxfF7ZbHmR82CBKyPg&e=">Request
for Reconsideration[icann.org]</a> (RfR) regarding the
CL&D Policy. The RfR objects to the inclusion of RDAP
as part of the Consensus Policy as RDAP was not
contemplated or referenced in the policy recommendations.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">To resolve this matter, ICANN proposes
the following path forward for the IRT:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">1. ICANN to issue a revised CL&D
Policy to all registry operators, removing provision 12.
For your reference, provision 12 states: “The
implementation of an RDAP service in accordance with the "<a
moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_rdap-2Dgtld-2Dprofile&d=DQMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=dqLP1wJqBvDSYLKrSEaAkCi_Kv0Mk5D_d32n29DHCN8&m=pkBrE3ogDYFgpWAATzOOdmRD93_Pz1PCrWtnSZN7Lg4&s=BEeCQrYK7JMscoggE25Woxu-0TdskrtCGjX6Sj6NVTo&e=">RDAP
Operational Profile for gTLD Registries and
Registrars[icann.org]</a>" is required for all gTLD
registries in order to achieve consistent labeling and
display.” Additionally, I have attached the proposed
revised CL&D Policy.<o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"> <o:p></o:p></p>
<p class="MsoNormal">2. Issue a revised notification to
registry operators regarding implementation of the
CL&D Policy, clearly indicating what has changed in
the revised CL&D Policy.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">3. Set the revised CL&D Policy
effective date to allow for full 6-month implementation
from the date of the revised notice.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">4. Update the published CL&D Policy
on the ICANN website, noting a change has been made. Note:
The revised CL&D Policy would <u>not</u> be subject
to another Public Comment process.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">5. Rescind the notification sent to
registrars to implement RDAP.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">ICANN intends to issue notices for
registries and registrars to implement RDAP after further
dialogue with the community.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Please let us know if you have comments
or concerns by responding to this list. Unless we hear
otherwise, we intend to move forward with the plan
outlined above on 4 October 2016.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black">— </span><o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black">Kind Regards,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black">Dennis S.
Chang</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black">GDD Services
& Engagement Program Director</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black">+1 213 293
7889</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black">Skype:
dennisSchang</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black"><a
moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DQMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=dqLP1wJqBvDSYLKrSEaAkCi_Kv0Mk5D_d32n29DHCN8&m=pkBrE3ogDYFgpWAATzOOdmRD93_Pz1PCrWtnSZN7Lg4&s=mPjnVw7nkrHEOvqo_pVRsOgcJA9nCei1CJcZWX0dYqs&e=">www.icann.org[icann.org]</a>
"One World, One Internet"</span><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times
New Roman""><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-impl-thickwhois-rt mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Dimpl-2Dthickwhois-2Drt&d=DQMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=dqLP1wJqBvDSYLKrSEaAkCi_Kv0Mk5D_d32n29DHCN8&m=pkBrE3ogDYFgpWAATzOOdmRD93_Pz1PCrWtnSZN7Lg4&s=4kbspuXnx6QwVFowMkdtINMgbQE8VDBSKEyWHfD8wDo&e=">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt[mm.icann.org]</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="font-family:"Times New
Roman""><br>
<br>
<o:p></o:p></span></p>
</div>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-impl-thickwhois-rt mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
</pre>
</body>
</html>