<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Taking on data from an unaffiliated but accredited ppp
(privacy/proxy provider), we would know their data to be correct as
displayed. So we could just take their data. We do not know the
underlying data, of course, but that was never a requirement. It is
sufficient that the ppp knows. <br>
<br>
Te problem comes when ppp's have an issue with domains transferred
to registrars where they no longer have control or an agreement in
place.<br>
<br>
These are the complicated ones.<br>
<br>
Volker<br>
<br>
<br>
<div class="moz-cite-prefix">Am 28.01.2016 um 06:37 schrieb Holly
Raiche:<br>
</div>
<blockquote
cite="mid:AC56196B-1327-4BBD-8E45-242401B8FD87@internode.on.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Kathy/Mary<br>
<div><br>
</div>
<div>In a F2F (LA, I think) James talked through the problem.
Under the RAA, registrars are responsible for the accuracy of
the Whois (RDS) data. As yet, there isn’t a mechanism by which
a registrar, taking on a P/P customer from another from another
registrar, can be assured that the Whois data relating to that
new customer is accurate. So the short answer is that the new
registrar cannot now take at face value the custom of a P/P
customer without checking the accuracy of their Whois data. The
trouble with the recommendation below is that it fudges the
issue. What we should be asking is the extent to which a P/P
provider must verify new P/P data - and the extent to which that
data can remain confidential in the transfer process. (not the
best wording, but we need to accommodate two apparently
conflicting requirements: the confidentiality of the data of the
P/P customer, and the requirement on registrars for the accuracy
of the Whois data for all their customers.)</div>
<div><br>
</div>
<div>Holly</div>
<div><br>
</div>
<div><br>
<div>
<div>On 27 Jan 2016, at 3:45 am, Mary Wong <<a
moz-do-not-send="true" href="mailto:mary.wong@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:mary.wong@icann.org">mary.wong@icann.org</a></a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space: normal; widows:
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; font-size: 14px;
font-family: Calibri, sans-serif;">
<div>
<div>Hello Kathy and all,</div>
<div><br>
</div>
<div>Thanks for your note; it reminded that I should
have also included the further recommendation below in
my previous email that noted two specific WG
recommendations containing references to the IRTP.
This additional recommendation that I’m now pasting
came about as a result of the WG’s email and live
discussions, following the November email exchanges
which you and others are referring to today:</div>
<div><br>
</div>
<blockquote style="margin: 0px 0px 0px 40px; border:
none; padding: 0px;" type="cite"><i>“The next review
of the IRTP should include an analysis of the impact
on P/P service customers, to ensure that adequate
safeguards are in place as regards P/P service
protection when domain names are transferred
pursuant to an IRTP process. Where a P/P service
customer initiates a transfer of a domain name, the
WG recognizes that a registrar should have the same
flexibility that it has currently to reject incoming
transfers from any individual or entity, including
those initiated by accredited P/P services.
Nevertheless, the WG recommends that, in
implementing those elements of the P/P service
accreditation program that pertain to or that affect
domain name transfers and in addition to its
specific recommendations contained in this Final
Report, ICANN should perform a general
“compatibility check” of each proposed
implementation mechanism with the then-current
IRTP.”</i></blockquote>
<div><br>
</div>
<div>I believe the context for this – and the other two
IRTP-related recommendations approved in the Final
Report that I’d pasted in my earlier email – is the
WG’s recognition that the effect of the IRTP changes
on P/P services and their customers may need to be
more directly addressed in the next review of the
IRTP. This WG's final recommendations therefore
addressed particular situations for which specific
exceptions may be warranted due, e.g., to the need to
ensure continuing customer protection during the
deaccreditation of a P/P service provider.</div>
<div><br>
</div>
<div>Thanks and cheers</div>
<div>Mary</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE">
<div>Mary Wong</div>
<div>Senior Policy Director</div>
<div>Internet Corporation for Assigned Names and
Numbers (ICANN)</div>
<div>Email:<span class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="mailto:mary.wong@icann.org" style="color:
rgb(149, 79, 114); text-decoration: underline;"><a class="moz-txt-link-abbreviated" href="mailto:mary.wong@icann.org">mary.wong@icann.org</a></a></div>
<div>Telephone: +1-603-5744889</div>
<div><br>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family: Calibri; font-size: 12pt;
text-align: left; border-width: 1pt medium medium;
border-style: solid none none; padding: 3pt 0in 0in;
border-top-color: rgb(181, 196, 223);"><span
style="font-weight: bold;">From:<span
class="Apple-converted-space"> </span></span><<a
moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"
style="color: rgb(149, 79, 114); text-decoration:
underline;"><a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a></a>>
on behalf of Kathy Kleiman <<a
moz-do-not-send="true"
href="mailto:kathy@kathykleiman.com" style="color:
rgb(149, 79, 114); text-decoration: underline;"><a class="moz-txt-link-abbreviated" href="mailto:kathy@kathykleiman.com">kathy@kathykleiman.com</a></a>><br>
<span style="font-weight: bold;">Date:<span
class="Apple-converted-space"> </span></span>Tuesday,
January 26, 2016 at 23:08<br>
<span style="font-weight: bold;">To:<span
class="Apple-converted-space"> </span></span>"<a
moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"
style="color: rgb(149, 79, 114); text-decoration:
underline;"><a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a></a>" <<a
moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"
style="color: rgb(149, 79, 114); text-decoration:
underline;"><a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a></a>><br>
<span style="font-weight: bold;">Subject:<span
class="Apple-converted-space"> </span></span>Re:
[Gnso-ppsai-pdp-wg] PP transfer issue<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000">Tx Mary, but I
am still missing the impact of the discussion below
on our PPSAI recommendations. If I want to transfer
my domain name(s) from Registrar A to Registrar B,
both with Privacy and Proxy services, and to keep
the data private as the transfer takes place
(something we all agreed should happen) -- is there
a problem, a limitation, a barrier? If so, how can
we overcome it?<br>
<br>
Best,<span class="Apple-converted-space"> </span><br>
Kathy<br>
<br>
<div class="moz-cite-prefix">On 11/25/2015 2:04 PM,
Mary Wong wrote:<br>
</div>
<blockquote
cite="mid:D27B6CB5.1A945%25mary.wong@icann.org"
type="cite">
<div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;">Hello everyone,</div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;"><br>
</div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;">Just a quick note for those
WG members who may not be familiar with the
IRTP, the changes to IRTP-C, or the
implementation discussions – it may help to
note the following definition for the IRTP. I
believe that James is referring to the
registrar’s discretion in determining whether
the purported change is or is not
typographical in nature (see in particular the
words I’ve highlighted in bold and italics).
This is illustrated by the examples given:</div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;"><br>
</div>
<div>
<div><font face="Calibri,sans-serif">“Material
Change”<span class="Apple-converted-space"> </span><b><i>means
a non-typographical correction</i></b>.
The following will be considered material
changes:</font></div>
<div><font face="Calibri,sans-serif">(i) A
change to the Registered Name Holder’s
name or organization that does not appear
to be a merely a typographical correction;</font></div>
<div><font face="Calibri,sans-serif">(ii)
Any change to the Registered Name
Holder’s name or organization that is
accompanied by a change of address or
phone number;</font></div>
<div><font face="Calibri,sans-serif">(iii)
Any change to the Registered Name
Holder’s email address.</font></div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;"><br>
</div>
</div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;">
<div>The point about having discretion on this
matter can be significant because, under the
Policy, a Material Change to a registrant’s
name, organizational address or email
address<span class="Apple-converted-space"> </span><u>will</u><span
class="Apple-converted-space"> </span>be
considered a Change of Registrant and thus
trigger the 60-day lock. Hence,
disabling/removal of a proxy service would
trigger a lock – although the current Policy
contemplates another possible instance of
registrar discretion in such instances, i.e.
a registrar has the discretion (“may”) to
permit the Registered Name Holder to opt out
of the lock<span
class="Apple-converted-space"> </span><u>prior</u><span
class="Apple-converted-space"> </span>to
the Change of Registrant request.</div>
<div><br>
</div>
<div>I’m far from an expert on the IRTP, but
hopefully the above helps to explain the
current proposed recommendation in the Final
Report where, in referring to IRTP-C, the WG
is recommending that - in relation to
de-accreditation -<span
class="Apple-converted-space"> </span><i>"where
a Change of Registrant (as defined under
the IRTP) takes place during the process
of de-accreditation of a proxy service
provider, a registrar should lift the
mandatory 60-day lock at the express
request of the beneficial user, provided
the registrar has also been notified of
the de–accreditation of the proxy service
provider”</i>.</div>
</div>
</div>
<br>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;">Thanks and cheers</div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;">Mary</div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;"><br>
</div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;">
<div><font class="Apple-style-span"><font
class="Apple-style-span" face="Calibri">Mary
Wong</font></font></div>
<div><font class="Apple-style-span"><font
class="Apple-style-span" face="Calibri">Senior
Policy Director</font></font></div>
<div><font class="Apple-style-span"><font
class="Apple-style-span" face="Calibri">Internet
Corporation for Assigned Names &
Numbers (ICANN)</font></font></div>
<div><font class="Apple-style-span"><font
class="Apple-style-span" face="Calibri">Telephone:
+1 603 574 4889</font></font></div>
<div><font class="Apple-style-span"><font
class="Apple-style-span" face="Calibri">Email:<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:mary.wong@icann.org"
style="color: rgb(149, 79, 114);
text-decoration: underline;"><a class="moz-txt-link-abbreviated" href="mailto:mary.wong@icann.org">mary.wong@icann.org</a></a></font></font></div>
<div><br>
</div>
</div>
<div style="font-family: Calibri, sans-serif;
font-size: 14px;"><br>
</div>
<span id="OLK_SRC_BODY_SECTION"
style="font-family: Calibri, sans-serif;
font-size: 14px;">
<div style="font-family: Calibri; font-size:
11pt; text-align: left; border-width: 1pt
medium medium; border-style: solid none none;
padding: 3pt 0in 0in; border-top-color:
rgb(181, 196, 223);"><span style="font-weight:
bold;">From:<span
class="Apple-converted-space"> </span></span><<a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"
style="color: rgb(149, 79, 114);
text-decoration: underline;"><a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a></a>>
on behalf of "James M. Bladel" <<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"
style="color: rgb(149, 79, 114);
text-decoration: underline;"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>><br>
<span style="font-weight: bold;">Date:<span
class="Apple-converted-space"> </span></span>Wednesday,
November 25, 2015 at 11:24<br>
<span style="font-weight: bold;">To:<span
class="Apple-converted-space"> </span></span>Mike
Zupke <<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:Mike.Zupke@icann.org"
style="color: rgb(149, 79, 114);
text-decoration: underline;">Mike.Zupke@icann.org</a>>,
"Metalitz, Steven" <<a
moz-do-not-send="true"
href="mailto:met@msk.com" style="color:
rgb(149, 79, 114); text-decoration:
underline;"><a class="moz-txt-link-abbreviated" href="mailto:met@msk.com">met@msk.com</a></a>>, Volker
Greimann <<a moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
style="color: rgb(149, 79, 114);
text-decoration: underline;">vgreimann@key-systems.net</a>>,
"<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"
style="color: rgb(149, 79, 114);
text-decoration: underline;">gnso-ppsai-pdp-wg@icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"
style="color: rgb(149, 79, 114);
text-decoration: underline;">gnso-ppsai-pdp-wg@icann.org</a>>,
Amy Bivins <<a moz-do-not-send="true"
href="mailto:amy.bivins@icann.org"
style="color: rgb(149, 79, 114);
text-decoration: underline;">amy.bivins@icann.org</a>><br>
<span style="font-weight: bold;">Subject:<span
class="Apple-converted-space"> </span></span>Re:
[Gnso-ppsai-pdp-wg] PP transfer issue<br>
</div>
<div><br>
</div>
<blockquote
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
style="border-left-color: rgb(181, 196, 223);
border-left-width: 5px; border-left-style:
solid; padding: 0px 0px 0px 5px; margin: 0px
0px 0px 5px;" type="cite">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;
font-size: 14px; font-family: Calibri,
sans-serif;">
<div>Hi folks. Just responding to Mike’s
post from last Wednesday:</div>
<div><br>
</div>
<div>The question of P/P services triggering
the “Change of Registrant” policy was not,
IMO, sufficiently addressed by the IRTP
WG. It was, however, the subject of
extensive discussion by the Implementation
team, which ultimately determined that
Registrar’s should have the discretion to
determine whether or not this qualified as
a Change of Registrant. For example, a
Registrar may determine that
adding/removing an affiliated P/P service
does NOT trigger the change of registrant
policy, but that an unaffiliated P/P
service contains too many unknowns, so
explicit consent and a 60-day transfer
lock may be warranted.</div>
<div><br>
</div>
<div>There are a number of practical
scenarios where this flexibility is
needed, including dealing with transfers
as part of an aftermarket sale,
implementation of a UDRP decision, billing
or payment failures for the P/P service,
or termination due to a violation of the
P/P services terms. I would also caution
against recommendations of any particular
WG (PPSAI) explicitly reverse
recommendations or Implementation
decisions of prior WGs (IRTP-C) even
before they have been adopted.</div>
<div><br>
</div>
<div>I don’t think this should materially
affect the overall recommendations of
PPSAI, nor do I see any incompatibilities
with this and our recommendations. But
happy to discuss this point on our next
call.</div>
<div><br>
</div>
<div>Thanks—</div>
<div><br>
</div>
<div>J.</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family: Calibri;
font-size: 11pt; text-align: left;
border-width: 1pt medium medium;
border-style: solid none none; padding:
3pt 0in 0in; border-top-color: rgb(181,
196, 223);"><span style="font-weight:
bold;">From:<span
class="Apple-converted-space"> </span></span>Mike
Zupke <<a moz-do-not-send="true"
href="mailto:Mike.Zupke@icann.org"
style="color: rgb(149, 79, 114);
text-decoration: underline;">Mike.Zupke@icann.org</a>><br>
<span style="font-weight: bold;">Date:<span
class="Apple-converted-space"> </span></span>Wednesday,
November 18, 2015 at 7:10<span
class="Apple-converted-space"> </span><br>
<span style="font-weight: bold;">To:<span
class="Apple-converted-space"> </span></span>"Metalitz,
Steven" <<a moz-do-not-send="true"
href="mailto:met@msk.com"
style="color: rgb(149, 79, 114);
text-decoration: underline;">met@msk.com</a>>,
Volker Greimann <<a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net"
style="color: rgb(149, 79, 114);
text-decoration: underline;"><a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a></a>>,
James Bladel <<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"
style="color: rgb(149, 79, 114);
text-decoration: underline;"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>>,
PPSAI WG <<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"
style="color: rgb(149, 79, 114);
text-decoration: underline;">gnso-ppsai-pdp-wg@icann.org</a>>,
Amy Bivins <<a moz-do-not-send="true"
href="mailto:amy.bivins@icann.org"
style="color: rgb(149, 79, 114);
text-decoration: underline;">amy.bivins@icann.org</a>><br>
<span style="font-weight: bold;">Subject:<span
class="Apple-converted-space"> </span></span>RE:
[Gnso-ppsai-pdp-wg] PP transfer issue<br>
</div>
<div><br>
</div>
<div
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"
xmlns="http://www.w3.org/TR/REC-html40">
<div link="#0563C1" vlink="#954F72"
lang="EN-US">
<div class="WordSection1" style="page:
WordSection1;">
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);">Sorry
for the delayed reply. We
needed to consult with a few
others.<o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);"><o:p> </o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);">In
answer to Steve’s question
(“Could you clarify whether the
60-day lock provision is part of
the IRTP as a consensus policy,
or part of the implementation of
that policy?”), the lock was
included in the policy
recommendations of IRTP WG C,
which were adopted by the
Council and Board. There was no
mention of privacy or proxy
services in that part of the
recommendation. So our
implementation of the IRTP C
recommendations was done “to the
letter” of the recommendation,
so to speak. I.e., no exception
was made for privacy and proxy
services. <o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);"><o:p> </o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);">We
don’t believe the PPSAI working
group is necessarily precluded
from addressing questions about
how the to-be-created type of PP
registrations interact with the
Transfer Policy just because the
Transfer Policy is an existing
policy. PPSAI charter question
B-3 (here:<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="https://community.icann.org/x/ihLRAg"
style="color: rgb(149, 79,
114); text-decoration:
underline;"><a class="moz-txt-link-freetext" href="https://community.icann.org/x/ihLRAg">https://community.icann.org/x/ihLRAg</a></a>)
spoke to having the WG
“[c]larify how transfers,
renewals, and PEDNR policies
should apply.”<o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);"><o:p> </o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);">With
regard to the point James made,
during implementation of the
IRTP C recommendations, we
talked a good bit about how a
proxy (or the beneficial
customer) could disable a proxy
or privacy service in a world
where consent of the other party
would now be required in order
to make the change in Whois.
The solution to that question
was to allow use of “designated
agents” (see<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en#II"
style="color: rgb(149, 79,
114); text-decoration:
underline;"><a class="moz-txt-link-freetext" href="https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en#II">https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en#II</a></a><span
class="Apple-converted-space"> </span>at
1.1.2) to approve Changes of
Registrant. I don’t believe the
matter of exempting PP
registrations from the 60 day
lock was raised by the IRT or in
public comment, although I do
recall occasionally that people
would reference the work of this
WG as potentially being
necessary to addressing
interaction with accredited PP
service registrations and the
Transfer Policy. <o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);"><o:p> </o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);">Hope
that helps. <o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);"><o:p> </o:p></span></div>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style="color:
rgb(31, 73, 125);">Mike Zupke<o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style="color:
rgb(31, 73, 125);">Director,
Registrar Services<o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style="color:
rgb(31, 73, 125);">Internet
Corporation for Assigned Names
and Numbers<o:p></o:p></span></div>
</div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><span
style="color: rgb(31, 73, 125);"><o:p> </o:p></span></div>
<div>
<div style="border-style: solid
none none; border-top-color:
rgb(225, 225, 225);
border-top-width: 1pt; padding:
3pt 0in 0in;">
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><b>From:</b><span
class="Apple-converted-space"> </span><a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org" style="color: rgb(149,
79, 114); text-decoration:
underline;">gnso-ppsai-pdp-wg-bounces@icann.org</a><span
class="Apple-converted-space"> </span>[<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org" style="color: rgb(149,
79, 114); text-decoration:
underline;">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]<span
class="Apple-converted-space"> </span><b>On Behalf Of<span
class="Apple-converted-space"> </span></b>James
M. Bladel<br>
<b>Sent:</b><span
class="Apple-converted-space"> </span>Wednesday,
November 18, 2015 6:12 AM<br>
<b>To:</b><span
class="Apple-converted-space"> </span>Volker
Greimann <<a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:vgreimann@key-systems.net" style="color: rgb(149, 79, 114);
text-decoration: underline;"><a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a></a>>;<span
class="Apple-converted-space"> </span><a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"
style="color: rgb(149, 79,
114); text-decoration:
underline;">gnso-ppsai-pdp-wg@icann.org</a><br>
<b>Subject:</b><span
class="Apple-converted-space"> </span>Re:
[Gnso-ppsai-pdp-wg] PP
transfer issue<o:p></o:p></div>
</div>
</div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"><o:p> </o:p></div>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;">Agree,
and I thought this was also
the final determination of the
IRTP-C Implementation Review
Team. It came up several
times…<o:p></o:p></span></div>
</div>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;"><o:p> </o:p></span></div>
</div>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;">Thanks-<o:p></o:p></span></div>
</div>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;"><o:p> </o:p></span></div>
</div>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;">J.<o:p></o:p></span></div>
</div>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;"><o:p> </o:p></span></div>
</div>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;"><o:p> </o:p></span></div>
</div>
<div style="border-style: solid none
none; border-top-color: rgb(181,
196, 223); border-top-width: 1pt;
padding: 3pt 0in 0in;">
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><b><span style="">From:<span
class="Apple-converted-space"> </span></span></b><span style=""><<a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org" style="color: rgb(149,
79, 114); text-decoration:
underline;"><a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a></a>>
on behalf of Volker Greimann
<<a moz-do-not-send="true"
class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net"
style="color: rgb(149, 79,
114); text-decoration:
underline;">vgreimann@key-systems.net</a>><br>
<b>Date:<span
class="Apple-converted-space"> </span></b>Wednesday,
November 18, 2015 at 4:22<span
class="Apple-converted-space"> </span><br>
<b>To:<span
class="Apple-converted-space"> </span></b>PPSAI
WG <<a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:gnso-ppsai-pdp-wg@icann.org" style="color: rgb(149, 79,
114); text-decoration:
underline;"><a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a></a>><br>
<b>Subject:<span
class="Apple-converted-space"> </span></b>Re:
[Gnso-ppsai-pdp-wg] PP
transfer issue<o:p></o:p></span></div>
</div>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;"><o:p> </o:p></span></div>
</div>
<div>
<p class="MsoNormal"
style="margin: 0in 0in 12pt;
font-size: 11pt; font-family:
Calibri, sans-serif;"><span
style="font-size: 10.5pt;">In
all honesty, a removal of an
accredited privacy service
should not trigger the
transfer lock as it does not
imply an owner change. I am
therefore in favor of option
2)<br>
<br>
Best,<br>
<br>
Volker<o:p></o:p></span></p>
<div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;">Am
17.11.2015 um 19:01 schrieb
Amy Bivins:<o:p></o:p></span></div>
</div>
<blockquote style="margin-top:
5pt; margin-bottom: 5pt;"
type="cite">
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style="">Dear
PPSAI WG Members:<o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style=""> <o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style="">Here
is the issue you asked staff
to address by email today.
This came to our attention
after reflecting on the work
done Friday by the
“implementation issues”
sub-team.<o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style=""> <o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style="">In
short, disabling a proxy or
privacy service will trigger
the 60-day inter-registrar
transfer lock required by
IRTP C (which takes effect
on 1 August 2016,<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en"
style="color: rgb(149, 79,
114); text-decoration:
underline;"><a class="moz-txt-link-freetext" href="https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en">https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en</a></a><span
class="Apple-converted-space"> </span>). Although applicable generally,
this issue is of particular
concern following
de-accreditation of a
privacy or proxy service (if
transfer to another
registrar is required to
maintain privacy).<o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style=""> <o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style="">Here
are 3 things the WG could
consider doing to address
this:<o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style="">1.
Maintain the status quo and
leave the 60-day IRTP C lock
in place.<br>
2. Create an exception for
Privacy and Proxy Service
customers, so the 60 day
IRTP C (inter-registrar
transfer) lock doesn't apply
when/if the customer changes
or removes the PP service.<br>
3. Create an exception for
PP users only if a PP
service is de-accredited, so
the IRTP C (inter-registrar
transfer) lock can be lifted
by the beneficial user if
the registrar has been
notified of
de-accreditation.<o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="color: rgb(51, 51,
51); background-color:
white; background-position:
initial initial;
background-repeat: initial
initial;"> </span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="color: rgb(51, 51,
51); background-color:
white; background-position:
initial initial;
background-repeat: initial
initial;">Please let us know
if you’d like to us to
provide any further
background. </span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="color: rgb(51, 51,
51); background-color:
white; background-position:
initial initial;
background-repeat: initial
initial;"> </span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="color: rgb(51, 51,
51); background-color:
white; background-position:
initial initial;
background-repeat: initial
initial;">Thank you!</span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style=""> <o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><b><span
style="font-size: 10pt;">Amy
E. Bivins</span></b><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10pt;">Registrar
Policy Services Manager</span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><b><span
style="font-size: 10pt;">I</span></b><span
style="font-size: 10pt;">nternet<span
class="Apple-converted-space"> </span><b>C</b>orporation for<span
class="Apple-converted-space"> </span><b>A</b>ssigned<span
class="Apple-converted-space"> </span><b>N</b>ames and<span
class="Apple-converted-space"> </span><b>N</b>umbers
(ICANN)</span><span style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10pt;"><a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:amy.bivins@icann.org" style="color: rgb(149, 79, 114);
text-decoration:
underline;"><a class="moz-txt-link-abbreviated" href="mailto:amy.bivins@icann.org">amy.bivins@icann.org</a></a></span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10pt;"> </span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style=""><object
moz-do-not-send="true"
id="Picture_x0020_1"
alt="Description:
icann-logo"
data="cid:image001.jpg@01D121D3.B224FE80"
type="application/x-apple-msg-attachment" height="70" width="91"
border="0"></object><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><b><i><span
style="font-size: 10pt;
color: rgb(31, 73,
125);">One World. One
Internet.</span></i></b><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10pt;"> </span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10pt;">Direct:
+1 (202) 249-7551</span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10pt;">Fax:
+1 (202) 789-0104</span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10pt;">801
17<sup>th</sup><span
class="Apple-converted-space"> </span>Street
NW, Suite 400</span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10pt;">Washington,
DC 20006</span><span
style=""><o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span style=""> <o:p></o:p></span></div>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;"><br>
<br>
<br>
<o:p></o:p></span></div>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">_______________________________________________<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Gnso-ppsai-pdp-wg mailing list<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><a moz-do-not-send="true" href="mailto:Gnso-ppsai-pdp-wg@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;">Gnso-ppsai-pdp-wg@icann.org</a><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" style="color: rgb(149, 79, 114); text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><o:p></o:p></span></pre>
</blockquote>
<div style="margin: 0in 0in
0.0001pt; font-size: 11pt;
font-family: Calibri,
sans-serif;"><span
style="font-size: 10.5pt;"><br>
<br>
<o:p></o:p></span></div>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">-- <o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Mit freundlichen Grüßen,<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Volker A. Greimann<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">- Rechtsabteilung -<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Key-Systems GmbH<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Im Oberen Werk 1<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">66386 St. Ingbert<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Email: <a moz-do-not-send="true" href="mailto:vgreimann@key-systems.net" style="color: rgb(149, 79, 114); text-decoration: underline;">vgreimann@key-systems.net</a><o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Web: <a moz-do-not-send="true" href="http://www.key-systems.net/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.key-systems.net</a> / <a moz-do-not-send="true" href="http://www.rrpproxy.net/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.RRPproxy.net</a><a moz-do-not-send="true" href="http://www.domaindiscount24.com/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.domaindiscount24.com</a> / <a moz-do-not-send="true" href="http://www.brandshelter.com/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.BrandShelter.com</a><o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><a moz-do-not-send="true" href="http://www.facebook.com/KeySystems" style="color: rgb(149, 79, 114); text-decoration: underline;">www.facebook.com/KeySystems</a><a moz-do-not-send="true" href="http://www.twitter.com/key_systems" style="color: rgb(149, 79, 114); text-decoration: underline;">www.twitter.com/key_systems</a><o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Geschäftsführer: Alexander Siffrin<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Umsatzsteuer ID.: DE211006534<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Member of the KEYDRIVE GROUP<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><a moz-do-not-send="true" href="http://www.keydrive.lu/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.keydrive.lu</a> <o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">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.<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">--------------------------------------------<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Best regards,<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Volker A. Greimann<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">- legal department -<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Key-Systems GmbH<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Im Oberen Werk 1<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">66386 St. Ingbert<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Email: <a moz-do-not-send="true" href="mailto:vgreimann@key-systems.net" style="color: rgb(149, 79, 114); text-decoration: underline;">vgreimann@key-systems.net</a><o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Web: <a moz-do-not-send="true" href="http://www.key-systems.net/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.key-systems.net</a> / <a moz-do-not-send="true" href="http://www.rrpproxy.net/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.RRPproxy.net</a><a moz-do-not-send="true" href="http://www.domaindiscount24.com/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.domaindiscount24.com</a> / <a moz-do-not-send="true" href="http://www.brandshelter.com/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.BrandShelter.com</a><o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><a moz-do-not-send="true" href="http://www.facebook.com/KeySystems" style="color: rgb(149, 79, 114); text-decoration: underline;">www.facebook.com/KeySystems</a><a moz-do-not-send="true" href="http://www.twitter.com/key_systems" style="color: rgb(149, 79, 114); text-decoration: underline;">www.twitter.com/key_systems</a><o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">CEO: Alexander Siffrin<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">V.A.T. ID.: DE211006534<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">Member of the KEYDRIVE GROUP<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><a moz-do-not-send="true" href="http://www.keydrive.lu/" style="color: rgb(149, 79, 114); text-decoration: underline;">www.keydrive.lu</a> <o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style="">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.<o:p></o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=""><o:p> </o:p></span></pre>
</div>
</div>
</div>
</div>
</span></div>
</blockquote>
</span><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;">Gnso-ppsai-pdp-wg@icann.org</a><a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" style="color: rgb(149, 79, 114); text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></pre>
</blockquote>
<br>
</div>
</div>
</span>_______________________________________________<br>
Gnso-ppsai-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gnso-ppsai-pdp-wg@icann.org" style="color:
rgb(149, 79, 114); text-decoration: underline;">Gnso-ppsai-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg"
style="color: rgb(149, 79, 114); text-decoration:
underline;">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</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>