[Gnso-ppsai-pdp-wg] A slightly revised proposed approachfor reviewing public comments

Tue Jul 21 13:42:02 UTC 2015

Hi Paul

While increasing numbers of policemen may be familiar with cybercrime,
etc, I would expect that it wouldbe dealt with by more specially
trained units within police forces.  It's not a tool I would expect
your average cop to use.

And ICANN is already carrying out an educational role in that space -
just talk to the SSAC members, who spend a lot of time on planes going
around the world training police forces.

My point is that I'd rather cases of fraud, misrepresentation etc are
dealt with by agencies designed to do so.

Holly 

----- Original Message -----
From: "McGrady Paul D." 
To:"h.raiche at internode.on.net" , "Volker Greimann" ,
"gnso-ppsai-pdp-wg at icannorg" 
Cc:
Sent:Tue, 21 Jul 2015 11:56:39 +0000
Subject:RE: [Gnso-ppsai-pdp-wg] A slightly revised proposed
approachfor reviewing public comments

	Hi Holly,

	Is there any data to back up the assertion that in today’s day and
age the police don’t know how to use WHOIS?  That might have been
the case 10 years ago, but with cybercrime on the rise along with
cyberbullying and other online offenses, I don’t think such is the
case anymore.  I bet these nice police know how to use WHOIS: 
https://portal.chicagopolice.org/portal/page/portal/ClearPath/Communities/Youth%20Services/Internet%20Safety1

	Even if it is true that some percentage of police don’t know how to
use WHOIS, it seems like an outreach & education need for ICANN rather
than for us to decide that the police are too ignorant to use WHOIS 
so we need to be concerned about noncommercial users of the
Internet.  

	Best,

	Paul

	FROM: h.raiche at internode.on.net [mailto:h.raiche at internode.on.net] 
SENT: Monday, July 20, 2015 8:29 PM
TO: Volker Greimann; McGrady, Paul D.; gnso-ppsai-pdp-wg at icann.org
SUBJECT: Re: [Gnso-ppsai-pdp-wg] A slightly revised proposed
approachfor reviewing public comments

	Hi Paul

 This is the very debate the ALAC has been having.  On the one hand,
non-commercial users and consumers do not want the miscreants being
able to hide behind a p/p service.  But earlier comments are also
correct - most consumers will not go to the Whois database to try to
track down the miscreant.  They will go to their consumer protection
agency (however named). And the truth is that if they go to their
local police station, that police station will also not be going to
the Whois database.  However, a consumer protection agency, or a
government agency that deals with consumer probably will have the
knowledge to check out the Whois database and use whatever other
resources (policy, law enforcement agencies) to track down the
miscreants.

 This is why we need to think through who should be given access to
Whois data of the registrant using a p/p service.  Should it just be
law enforcement agencies with a warrant, or others as well - as set
out in the Annex for rights holders. Agreed, the Whois data of
miscreants probably won't be correct, but it may assist law
enforcement and other agencies to track down the miscreants.

 Hope that moves this discussion along

 Holly

 ----- Original Message -----

	FROM:

	"Volker Greimann" 

	TO:

	"McGrady Paul D." , "gnso-ppsai-pdp-wg at icann.org [3]" 

	CC:

	SENT:

	Mon, 20 Jul 2015 19:24:40 +0200

	SUBJECT:

	Re: [Gnso-ppsai-pdp-wg] A slightly revised proposed approach for
reviewing public comments

 Hi Paul,

 I agree that non-commercial users and consumers may need protection
as well, but I am just not sure how this relates to privacy services
at all. How does knowing the underlying data of a privacy service help
a scam victim? If there is illegal use, odds are the underlying data
will not be of much value either. Criminals rarely leave their home
address on file anywhere near their crime scenes. 

 Surely preferred venue for addressing such abuse by consumers is
their local police station, who will initiate an investigation and can
get a court order if the substance of the case bears that out. Across
borders, legal assistance is available. A British law enforcement
official has proper venues to request legal assistance from his German
counterpart, for example.

 Which leaves us with the rights and interests of those that use these
services for legitimate reasons. We need to ensure their interests are
protected too. For reasons, go look at the hundreds of public comments
where users detail why they NEED strong protections of their privacy
that cannot be easily circumvented.

	Am 20.07.2015 um 18:53 schrieb McGrady, Paul D.:

	Thanks Volker.  For the benefit of the others on the list, I am
pulling up a copy of your original email to me so that I can be read
along with your additional thoughts below.

	Also, thank you for this statement in your post below:

	“I also think that the importance of the debate is of the essence
here, but that does not only include the interests of IP and trademark
rights holders but also those of those affected by anything we come up
with, i.e. civil society, private individuals and organizations, and
their rights and interests” 

	which appears to adopt my concern for the protection of
non-commercial users who are victims of scams, crime, etc.  While I
thought it was interesting that you attempted to bring in IP and
trademark rights holders into a conversation about non-commercial
user’s need to get access to information about criminals and others
abusing them and the DNS, I’m not sure that simply beating the
IP/Trademark Holder straw man is that same thing as putting forward
substantive ideas on how to balance in the concerns of non-commercial,
non-DNS customer consumers with the “mandatory litigation”
framework you are proposing.   I again welcome any substantive
comments you may have regarding how we protect those consumers –
even if they do not own a domain name or pay for P/P services –
within the mandatory litigation paradigm which would result in
months-long delay to get an order from the victim’s court served on
a P/P service countries away.  

	Thanks in advance for your substantive thoughts on how to balance
these interests.

	Best,

	Paul

	FROM: Volker Greimann [mailto:vgreimann at key-systems.net [5]] 
SENT: Monday, July 20, 2015 11:16 AM
TO: McGrady, Paul D.; gnso-ppsai-pdp-wg at icann.org [6]
SUBJECT: Re: [Gnso-ppsai-pdp-wg] A slightly revised proposed approach
for reviewing public comments

	Hi Paul,

 I intended to post to the list, apologies if I misclicked.

 I wanted to say that the truth is probably somewhere in the middle.
No one is served if the justice system takes months to process a
simple request, OTOH, this is not a reason for circumventing due
process. Slow justice is better than no justice or vigilantism.

 I also think that the importance of the debate is of the essence
here, but that does not only include the interests of IP and trademark
rights holders but also those of those affected by anything we come up
with, i.e civil society, private individuals and organizations, and
their rights and interests.

 Best,

 Volker 

	Am 20.07.2015 um 17:30 schrieb McGrady, Paul D.:

	Thanks Volker.  I don’t think your comment appreciates the
importance of the debate.  Is there a reason that it was sent only to
me and not to the list?  Any object to me posting it on the list? 
Thanks.

	FROM: Volker Greimann [mailto:vgreimann at key-systems.net [7]] 
SENT: Monday, July 20, 2015 10:26 AM
TO: McGrady, Paul D.
SUBJECT: Re: [Gnso-ppsai-pdp-wg] A slightly revised proposed approach
for reviewing public comments

	Hi Paul,

 it seems a good thing not to be in a common law country then, as over
here usually a different axiom applies: "justice hurried along is bad
justice". If a case is there, a court will be able to see that and
issue an order. Getting injunctive relief can take as little as half a
day. 

 Best,

 Volker

	Am 20.07.2015 um 17:15 schrieb McGrady, Paul D.:

	Thanks Volker.  I’m pretty sure it won’t do any good to get
drawn into a conversation about the consequences of service providers
being and permanently staying the RNH, since that is not what is
really being discussed.  The conversation has evolved well past that
point and a long, long time ago.  

	I would, however, appreciate your substantive thoughts on how we
balance the need for consumers who are victims of scams and crime
(even if those consumers don’t happen to be domain name registrants
or P/P customers) within the “court order only” paradigm which on
its face is woefully inadequate to bring about a timely remedy.  It
is now axiomatic in common law jurisdictions that “Justice delayed
is justice denied.”

	I’m looking forward to your reply.  Thanks for your time.

	Best,

	Paul

	FROM: Volker Greimann [mailto:vgreimann at key-systems.net [8]] 
SENT: Monday, July 20, 2015 9:03 AM
TO: McGrady, Paul D.; James Gannon; gnso-ppsai-pdp-wg at icann.org [9]
SUBJECT: Re: [Gnso-ppsai-pdp-wg] A slightly revised proposed approach
for reviewing public comments

	Privacy or proxy services do not conflict with section 3.3.1.6 of the
RAA (nor RA) as formally, the service provider is the RNH in a proxy
form.

 Volker

	Am 20.07.2015 um 14:25 schrieb McGrady, Paul D.:

	Thanks James  The ship has already sailed on option a).  See
3.3.1.6 of the RA noting the mandatory requirement of the disclosure
of “The name and postal address of the Registered Name Holder.” 
What this team is discussing is how to develop an framework for
exceptions to 3.3.1.6 that does not create a safe haven for human
traffickers, cyber-bullies, and other nefarious types that would harm
non-commercial users of the Internet.  It is not within our remit to
undo 3.3.1.6, no matter how many form comments are posted asking that
we do so.  Our remit is finding what circumstances warrant the
exception through allowing WHOIS modification and which do not, the
means to communicate to someone who is legitimately using such WHOIS
modification services, and the terms upon which such allowable WHOIS
modification will be terminated if it is being used to abuse others.

	Even if abolishing 3.3.1.6 were a possibility and the DNS wasn’t
built on a series of contracts (which it is), I see no particular
upside to telling parents of children being bullied online, geriatric
victims of banking scams, and targets of pay-in-advance credit offers
that they have to wait months while their local court order requiring
disclosure makes its way through the Hague Convention service process
in order to  be effectuated by a far-away privacy service.  Although
we have heard much about protecting the rights of non-commercial users
of the Internet who happen to be domain name registrants as well and
who are using P/P services (and we should be concerned about them), we
also need to keep in mind the other non-commercial users of the
Internet who will also be affected – even if they have not
contributed financially to the system by purchasing a domain name.  

	I for one hope we can get back on track and discuss the substantive,
relevant comments and reach final consensus on the handful of
outstanding issues and get a report in to the GNSO that reflects a
sensible balance.

	Regards,

	Paul

	FROM: gnso-ppsai-pdp-wg-bounces at icann.org [10]
[mailto:gnso-ppsai-pdp-wg-bounces at icann.org [11]] ON BEHALF OF James
Gannon
SENT: Monday, July 20, 2015 5:51 AM
TO: Volker Greimann; gnso-ppsai-pdp-wg at icann.org [12]
SUBJECT: Re: [Gnso-ppsai-pdp-wg] A slightly revised proposed approach
for reviewing public comments

	Agreed Volker I would put my analysis in set A aswell.

	-James

	FROM: gnso-ppsai-pdp-wg-bounces at icann.org [13]
[mailto:gnso-ppsai-pdp-wg-bounces at icann.org [14]] ON BEHALF OF Volker
Greimann
SENT: Monday, July 20, 2015 11:37 AM
TO: gnso-ppsai-pdp-wg at icann.org [15]
SUBJECT: Re: [Gnso-ppsai-pdp-wg] A slightly revised proposed approach
for reviewing public comments

	Hi Steve,

 these comments can be read in different ways:

 a) ICANN should not implement policy that requires disclosure without
a court order, or
 b) no disclosure should be allowed without a court order. 

 I tend to interpret the comments as being in the a) column 

 Best,

 Volker

	Am 17.072015 um 21:42 schrieb Metalitz, Steven:

	No, James, we should certainly consider those concerns but not
necessarily change the report. 

	The single concern raised more often than any other, I am positive,
is that proxy services should not be permitted to disclose any
information on their customer without a court order.   That is not a
standard that your service or any other that I know of can meet.  We
can change our report to make that a requirement for privacy/proxy
service providers.  Should we?  

	Steve 

	FROM: James M. Bladel [mailto:jbladel at godaddy.com [16]] 
SENT: Friday, July 17, 2015 3:35 PM
TO: Metalitz, Steven
CC: Kathy Kleiman; gnso-ppsai-pdp-wg at icann.org [17]
SUBJECT: Re: [Gnso-ppsai-pdp-wg] A slightly revised proposed approach
for reviewing public comments

	Steve:

	With respect, if several thousand commenters raised issues that
concern them, but are not addressed by our report, the our focus
should be on changing the report, not discounting the comments 

 Thank you, 

	J.

	____________

	James Bladel

	GoDaddy

 On Jul 17, 2015, at 21:20, Metalitz, Steven  wrote:

	I am all in favor of people identifying topics they believe need to
be addressed by the WG.  However, Kathy, I have to disagree with your
premise, which is that the ten thousand plus comments reflect
responses to our questions or even statements of agreement or
disagreement to our consensus positions or report proposals A much
smaller (though still significant) number of comments do that, and
those should be our top priority for review and response.  But the
vast majority of comments clearly are not responses to our report. 
These mass comments raise a very limited number of issues, which I
don’t think we will that much difficulty dealing with once we have
addressed the responses to our questions and the reasoned statements
of agreement or disagreement with specific proposals we have made. 

	Let’s get started on the more substantive comments, starting with
the questions we did pose.  We have subteams forming to start to
tackle that, and the staff (and Graeme!) are providing some tools to
try to help facilitate that.    For those who don’t wish to join
subteams, again, I agree it would be useful to identify (as you put
it) the “major issues and concerns” that you find in the comments,
with citations to those comments that you believe raise those major
issues and concerns.

	Steve  

	FROM: gnso-ppsai-pdp-wg-bounces at icann.org [19]
[mailto:gnso-ppsai-pdp-wg-bounces at icann.org [20]] ON BEHALF OF Kathy
Kleiman
SENT: Thursday, July 16, 2015 6:34 PM
TO: gnso-ppsai-pdp-wg at icann.org [21]
SUBJECT: [Gnso-ppsai-pdp-wg] A slightly revised proposed approach for
reviewing public comments

	Hi Don, Steve, Graeme, Mary and all WG members, 
 I would like recommend that we take a slightly different approach. We
received over ten thousand comments, many coming from those who do not
ordinarily participate in the ICANN process. They wrote to us us not
only in response to our specific questions, but also to share
agreement (and disagreement) to our consensus positions/report
proposals, and to explain why proxy/privacy registrations are
important to them. There has been a huge outpouring particularly on
the last issue.

 While a few topics for cataloging these comments were presented on
the call, with great respect, I do not think we have dealt with or
cataloged all of the major issues and concerns raised by the comments
yet. Before we leap forward to subteams and analysis, shouldn't we ask
further, in writing, and with the whole of the WG participating --
have we gotten the topics right?  Have we created sufficient topics
to allow us to catalog the broad range of information, concerns and
comments shared with us by so many commenters? 

 I would like to request that we be able to take big breath, and a
slightly (only slightly!) different approach.  In preparation for
Tuesday's call, could we all skim the comments -- with our array of
expertise, insight, knowledge of aspects of our commenter base -- to
come up with topics that we think the WG should evaluate in tour
review?  Perhaps if we can circulate the topics online, and then
discuss them on Tuesday.

 Then we discuss how these topics/this substance might be overlaid on
the subteam process laid out below and shared for the first time on
last week's call. We will then have both substance and process! And we
will know that we have considered all of the major issues arising from
these important comments.

 If we go forward now without this evaluation, I fear we may be
missing much of what the comments have to offer.

 Best and tx,
 Kathy

FROM: gnso-ppsai-pdp-wg-bounces at icann.org [22]
[mailto:gnso-ppsai-pdp-wg-bounces at icann.org [23]] ON BEHALF OF Mary
Wong

	SENT: 14 July 2015 23:50
TO: gnso-ppsai-pdp-wg at icann.org [24]
SUBJECT: [Gnso-ppsai-pdp-wg] A proposed approach for reviewing public
comments

	Dear WG members,

	Following from the WG call earlier today, the co-chairs and staff
after some consultation would like to propose the following approach
for your consideration:

	1. Use of Sub Teams for Specific Topics:

	* Sub-teams comprising a few WG volunteers each can be formed to do
the initial review of public comments received on the three topics
suggested by Steve on the call, i.e. (1) Section 1.3.2 of the Initial
Report (on escalation of relay requests and the handling of
disclosure/publication requests from third parties other than IP
rights holders); (2) Section 1.3.3 (on the open question regarding
online financial transactions); and (3) Annex E (the Illustrative
Disclosure Framework).

	* To assist the WG evaluate the usefulness of sub teams, a sub team
for Section 1.3.2 can be formed first and serve as a “test case”
for the exercise.

	* As outlined on the call, a sub team will do a “first pass”
through a template, based on the Public Comment Review Tool, that
staff will populate with all the input received on that particular
issue. The sub team will report back to the full WG in a timely
fashion, including suggesting a WG response and/or proposed action in
relation to the comments received.

	* Sub teams may elect to do their work via email and online tools
(e.g. Google Docs or a wiki page), with or without supplemental
conference calls. Any calls will be recorded and transcribed for
transparency purposes, and drafts and other documents prepared using
online tools will also be made available to the full WG. (Do note,
however, that depending on call scheduling and timing, staff support
may not be available for all requested calls if several sub teams are
used concurrently.)

	PLEASE VOLUNTEER FOR SUB TEAM 1.3.2 IF YOU ARE INTERESTED IN
ASSISTING WITH THIS INITIAL REVIEW. Staff will endeavor to provide the
template tool for 1.3.2 to the sub team as soon as possible, hopefully
by Monday.

	2. Full WG Review of Other Comments to Continue in Parallel:

	* Staff will “collapse” (per James’ suggestion on the call) all
those template responses received that were simply a Yes or No answer
to a question, without any further comment added – these will be
reflected in the Public Comment Review Tool accordingly, as a single
collective entry. The current Tool (covering Preliminary
Recommendations 1 through 9) will be updated in time for the WG to
begin this review on the next call.

	3. Collated Information:

	* In addition to the updated spreadsheet just circulated by Graeme,
we can also send you archived mail files of the contributions received
to the public comment forum, should you or your group wish to conduct
searches through each comment yourselves.

	We hope the above will be helpful in facilitating good progress on
the work to be done in preparation for the Final Report.

	Thanks and cheers

	Mary

	Mary Wong

	Senior Policy Director

	Internet Corporation for Assigned Names & Numbers (ICANN)

	Telephone: +1 603 574 4889

	Email: mary.wong at icann.org [25]

-------------------------

	Confidentiality Notice
 This message is being sent by or on behalf of a lawyer. It is
intended exclusively for the individual or entity to which it is
addressed. This communication may contain information that is
proprietary, privileged or confidential or otherwise legally exempt
from disclosure. If you are not the named addressee, you are not
authorized to read, print, retain, copy or disseminate this message or
any part of it. If you have received this message in error, please
notify the sender immediately by e-mail and delete all copies of the
message.

	_______________________________________________

	Gnso-ppsai-pdp-wg mailing list

	Gnso-ppsai-pdp-wg at icann.org [26]

	https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg [27]

	_______________________________________________
 Gnso-ppsai-pdp-wg mailing list
Gnso-ppsai-pdp-wg at icann.org [28]
https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg [29]

	_______________________________________________

	Gnso-ppsai-pdp-wg mailing list

	Gnso-ppsai-pdp-wg at icann.org [30]

	https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg [31]

	-- 

	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: vgreimann at key-systems.net [32]

	Web: www.key-systems.net [33] / www.RRPproxy.net [34]

	www.domaindiscount24.com [35] / www.BrandShelter.com [36]

	Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:

	www.facebook.com/KeySystems [37]

	www.twitter.com/key_systems [38]

	Geschäftsführer: Alexander Siffrin

	Handelsregister Nr.: HR B 18835 - Saarbruecken 

	Umsatzsteuer ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [39] 

	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: vgreimann at key-systems.net [40]

	Web: www.key-systems.net [41] / www.RRPproxy.net [42]

	www.domaindiscount24.com [43] / www.BrandShelter.com [44]

	Follow us on Twitter or join our fan community on Facebook and stay
updated:

	www.facebook.com/KeySystems [45]

	www.twitter.com/key_systems [46]

	CEO: Alexander Siffrin

	Registration No.: HR B 18835 - Saarbruecken 

	V.A.T. ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [47] 

	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.

 The contents of this message may be privileged and confidential.
Therefore, if this message has been received in error, please delete
it without reading it. Your receipt of this message is not intended to
waive any applicable privilege. Please do not disseminate this message
without the permission of the author. 

	-- 

	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: vgreimann at key-systems.net [48]

	Web: wwwkey-systems.net [49] / www.RRPproxy.net [50]

	www.domaindiscount24.com [51] / www.BrandShelter.com [52]

	Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:

	www.facebook.com/KeySystems [53]

	www.twitter.com/key_systems [54]

	Geschäftsführer: Alexander Siffrin

	Handelsregister Nr.: HR B 18835 - Saarbruecken 

	Umsatzsteuer ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [55] 

	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: vgreimann at key-systems.net [56]

	Web: www.key-systems.net [57] / www.RRPproxy.net [58]

	www.domaindiscount24.com [59] / www.BrandShelter.com [60]

	Follow us on Twitter or join our fan community on Facebook and stay
updated:

	www.facebook.com/KeySystems [61]

	www.twitter.com/key_systems [62]

	CEO: Alexander Siffrin

	Registration No.: HR B 18835 - Saarbruecken 

	V.A.T. ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [63] 

	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

 The contents of this message may be privileged and confidential.
Therefore, if this message has been received in error, please delete
it without reading it. Your receipt of this message is not intended to
waive any applicable privilege. Please do not disseminate this message
without the permission of the author. 

	-- 

	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: vgreimann at key-systemsnet [64]

	Web: www.key-systems.net [65] / www.RRPproxy.net [66]

	www.domaindiscount24.com [67] / www.BrandShelter.com [68]

	Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:

	www.facebook.com/KeySystems [69]

	www.twitter.com/key_systems [70]

	Geschäftsführer: Alexander Siffrin

	Handelsregister Nr.: HR B 18835 - Saarbruecken 

	Umsatzsteuer ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [71] 

	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: vgreimann at key-systems.net [72]

	Web: www.key-systemsnet [73] / www.RRPproxy.net [74]

	www.domaindiscount24.com [75] / www.BrandShelter.com [76]

	Follow us on Twitter or join our fan community on Facebook and stay
updated:

	www.facebook.com/KeySystems [77]

	www.twitter.com/key_systems [78]

	CEO: Alexander Siffrin

	Registration No.: HR B 18835 - Saarbruecken 

	V.A.T. ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [79] 

	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.

 The contents of this message may be privileged and confidential.
Therefore, if this message has been received in error, please delete
it without reading it. Your receipt of this message is not intended to
waive any applicable privilege. Please do not disseminate this message
without the permission of the author. 

	-- 

	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: vgreimann at key-systems.net [80]

	Web: www.key-systems.net [81] / www.RRPproxy.net [82]

	www.domaindiscount24.com [83] / www.BrandShelter.com [84]

	Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:

	www.facebook.com/KeySystems [85]

	www.twitter.com/key_systems [86]

	Geschäftsführer: Alexander Siffrin

	Handelsregister Nr.: HR B 18835 - Saarbruecken 

	Umsatzsteuer ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [87] 

	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: vgreimann at key-systems.net [88]

	Web: www.key-systems.net [89] / www.RRPproxy.net [90]

	www.domaindiscount24.com [91] / www.BrandShelter.com [92]

	Follow us on Twitter or join our fan community on Facebook and stay
updated:

	www.facebook.com/KeySystems [93]

	www.twitter.com/key_systems [94]

	CEO: Alexander Siffrin

	Registration No.: HR B 18835 - Saarbruecken 

	V.A.T. ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [95] 

	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.

 The contents of this message may be privileged and confidential.
Therefore, if this message has been received in error, please delete
it without reading it. Your receipt of this message is not intended to
waive any applicable privilege. Please do not disseminate this message
without the permission of the author. 

	-- 

	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: vgreimann at key-systems.net [96]

	Web: www.key-systems.net [97] / www.RRPproxy.net [98]

	www.domaindiscount24.com [99] / www.BrandShelter.com [100]

	Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:

	www.facebook.com/KeySystems [101]

	www.twittercom/key_systems [102]

	Geschäftsführer: Alexander Siffrin

	Handelsregister Nr.: HR B 18835 - Saarbruecken 

	Umsatzsteuer ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [103] 

	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: vgreimann at key-systems.net [104]

	Web: www.key-systems.net [105] / wwwRRPproxy.net [106]

	www.domaindiscount24.com [107] / www.BrandShelter.com [108]

	Follow us on Twitter or join our fan community on Facebook and stay
updated:

	www.facebook.com/KeySystems [109]

	www.twitter.com/key_systems [110]

	CEO: Alexander Siffrin

	Registration No.: HR B 18835 - Saarbruecken 

	V.A.T. ID.: DE211006534

	Member of the KEYDRIVE GROUP

	www.keydrive.lu [111] 

	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

The contents of this message may be privileged and confidential.
Therefore, if this message has been received in error, please delete
it without reading it. Your receipt of this message is not intended to
waive any applicable privilege. Please do not disseminate this message
without the permission of the author. 

Links:
------
[1] mailto:vgreimann at key-systems.net
[2] mailto:PMcGrady at winston.com
[3] mailto:gnso-ppsai-pdp-wg at icann.org
[4] mailto:gnso-ppsai-pdp-wg at icann.org
[5] mailto:vgreimann at key-systems.net
[6] mailto:gnso-ppsai-pdp-wg at icann.org
[7] mailto:vgreimann at key-systems.net
[8] mailto:vgreimann at key-systems.net
[9] mailto:gnso-ppsai-pdp-wg at icann.org
[10] mailto:gnso-ppsai-pdp-wg-bounces at icann.org
[11] mailto:gnso-ppsai-pdp-wg-bounces at icann.org
[12] mailto:gnso-ppsai-pdp-wg at icann.org
[13] mailto:gnso-ppsai-pdp-wg-bounces at icann.org
[14] mailto:gnso-ppsai-pdp-wg-bounces at icann.org
[15] mailto:gnso-ppsai-pdp-wg at icann.org
[16] mailto:jbladel at godaddy.com
[17] mailto:gnso-ppsai-pdp-wg at icannorg
[18] mailto:met at msk.com
[19] mailto:gnso-ppsai-pdp-wg-bounces at icann.org
[20] mailto:gnso-ppsai-pdp-wg-bounces at icann.org
[21] mailto:gnso-ppsai-pdp-wg at icann.org
[22] mailto:gnso-ppsai-pdp-wg-bounces at icann.org
[23] mailto:gnso-ppsai-pdp-wg-bounces at icann.org
[24] mailto:gnso-ppsai-pdp-wg at icann.org
[25] mailto:mary.wong at icann.org
[26] mailto:Gnso-ppsai-pdp-wg at icannorg
[27] https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
[28] mailto:Gnso-ppsai-pdp-wg at icann.org
[29] https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
[30] mailto:Gnso-ppsai-pdp-wg at icann.org
[31] https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
[32] mailto:vgreimann at key-systems.net
[33] http://wwwkey-systems.net
[34] http://www.RRPproxy.net
[35] http://www.domaindiscount24.com
[36] http://www.BrandShelter.com
[37] http://www.facebook.com/KeySystems
[38] http://www.twitter.com/key_systems
[39] http://www.keydrive.lu
[40] mailto:vgreimann at key-systems.net
[41] http://www.key-systems.net
[42] http://www.RRPproxy.net
[43] http://www.domaindiscount24.com
[44] http://www.BrandSheltercom
[45] http://www.facebook.com/KeySystems
[46] http://www.twitter.com/key_systems
[47] http://www.keydrive.lu
[48] mailto:vgreimann at key-systems.net
[49] http://www.key-systems.net
[50] http://www.RRPproxy.net
[51] http://www.domaindiscount24.com
[52] http://www.BrandShelter.com
[53] http://www.facebook.com/KeySystems
[54] http://www.twitter.com/key_systems
[55] http://www.keydrive.lu
[56] mailto:vgreimann at key-systems.net
[57] http://www.key-systems.net
[58] http://www.RRPproxy.net
[59] http://www.domaindiscount24.com
[60] http://www.BrandShelter.com
[61] http://www.facebook.com/KeySystems
[62] http://www.twitter.com/key_systems
[63] http://www.keydrive.lu
[64] mailto:vgreimann at key-systems.net
[65] http://www.key-systems.net
[66] http://www.RRPproxy.net
[67] http://www.domaindiscount24.com
[68] http://www.BrandShelter.com
[69] http://www.facebook.com/KeySystems
[70] http://www.twitter.com/key_systems
[71] http://www.keydrive.lu
[72] mailto:vgreimann at key-systems.net
[73] http://www.key-systems.net
[74] http://www.RRPproxy.net
[75] http://www.domaindiscount24.com
[76] http://www.BrandShelter.com
[77] http://www.facebook.com/KeySystems
[78] http://www.twitter.com/key_systems
[79] http://www.keydrive.lu
[80] mailto:vgreimann at key-systems.net
[81] http://www.key-systems.net
[82] http://www.RRPproxy.net
[83] http://www.domaindiscount24.com
[84] http://www.BrandShelter.com
[85] http://www.facebook.com/KeySystems
[86] http://wwwtwitter.com/key_systems
[87] http://www.keydrive.lu
[88] mailto:vgreimann at key-systems.net
[89] http://www.key-systems.net
[90] http://www.RRPproxynet
[91] http://www.domaindiscount24.com
[92] http://www.BrandShelter.com
[93] http://www.facebook.com/KeySystems
[94] http://www.twitter.com/key_systems
[95] http://www.keydrive.lu
[96] mailto:vgreimann at key-systems.net
[97] http://www.key-systems.net
[98] http://www.RRPproxy.net
[99] http://www.domaindiscount24.com
[100] http://www.BrandShelter.com
[101] http://www.facebook.com/KeySystems
[102] http://www.twitter.com/key_systems
[103] http://www.keydrive.lu
[104] mailto:vgreimann at key-systems.net
[105] http://www.key-systems.net
[106] http://www.RRPproxy.net
[107] http://www.domaindiscount24.com
[108] http://www.BrandShelter.com
[109] http://www.facebook.com/KeySystems
[110] http://www.twitter.com/key_systems
[111] http://www.keydrive.lu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-ppsai-pdp-wg/attachments/20150721/56f9ea30/attachment-0001.html>