[gnso-rds-pdp-wg] Legal basis vs. lawful
Michael Palage
michael at palage.com
Tue Feb 13 17:56:46 UTC 2018
Bradley,
I would respectfully push back on your representation that ICANN.org has not raised concerns regarding the efficacy of the current conflicts procedure. Please refer to the following excerpt from Cyrus Namazi, Vice President, Domain Name Services & Industry Engagement made during the intercessional meeting with the non-contracting parties that occurred in LA on 2-Feb-2018
Thank you Steve. This is Cyrus. So just to level set on the reason for the existence of this procedure the primary goal here behind this procedure was to ensure that all of our contracted parties have a mechanism to comply with their local jurisdictions laws in contrast with the ICANN contract so if the ICANN contract by any chance actually exposes some contracted party to end up having in the course of fulfilling up their obligations under the contract being in violation of their local law this law, this is the mechanism for them to come back to ICANN and essentially engage in a conversation to get a waiver or the provisions that the contract that are engaged in law. So this is sort of the overarching goal for this procedure.
Now there are two ways that this mechanism, this procedure can be invoked. And our difficulty on the staff side on the GDD and org side has been that the bar has been set so high that in fact no one, no contracted party has actually been able to effectively successfully invoke this with one exception, the recent exception I can talk to that.
And these trigger mechanisms are either whether you’re actually being prosecuted by your local law enforcement or you get a letter from your local the data protection authority and neither one of which has proven to be realistically feasible for an operator to really do. And I quite frankly sympathize with our contracted parties. So twice we have actually opened this procedure and taken it to the community in hopes of making it more realistic, more doable, more feasible.
Best regards,
Michael
From: gnso-rds-pdp-wg [mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Silver, Bradley via gnso-rds-pdp-wg
Sent: Tuesday, February 13, 2018 11:35 AM
To: Ayden Férdeline <icann at ferdeline.com>
Cc: RDS PDP WG <gnso-rds-pdp-wg at icann.org>
Subject: Re: [gnso-rds-pdp-wg] Legal basis vs. lawful
That’s incorrect Ayden: an array of views were been expressed by stakeholders in the public comment period about the WHOIS Conflicts Procedure – some in support, some not. ICANN the organization most definitely has not taken a position on the efficacy of the procedure. To the contrary, ICANN’s general counsel, John Jeffrey’s recently suggested invoking the procedure in response to the input from Dutch DPA’s regarding data protection compliance: “this letter enables [the .frl and .amsterdam registries] to invoke the community’s Whois Conflicts Procedure, which I encourage them to do.” <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_jeffrey-2Dto-2Dsprey-2D01nov17-2Den.pdf&d=DwMF-g&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=AZGJ0aXoaBD93o5lG7tXdJGhVOKkOSAKTUktNxuwbic&s=rvMJJZb6K4DexAEVKkwmQIuXRA8ogrwoZsv1uga6NGE&e=> https://www.icann.org/en/system/files/correspondence/jeffrey-to-sprey-01nov17-en.pdf
From: Ayden Férdeline [mailto:icann at ferdeline.com]
Sent: Tuesday, February 13, 2018 11:15 AM
To: Silver, Bradley
Cc: Dotzero; Volker Greimann; RDS PDP WG
Subject: Re: [gnso-rds-pdp-wg] Legal basis vs. lawful
There is not a process that works. Its inadequacy, I felt, was widely acknowledged both within the ICANN community and by ICANN the organisation.
Ayden
-------- Original Message --------
On 13 February 2018 5:09 PM, Silver, Bradley via gnso-rds-pdp-wg <gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org> > wrote:
I agree, Michael – any single jurisdiction should not dictate the framework. We should of course take into account legal norms – including regulations such as the GDPR. We should also recall that to the extent any registrar or registry wishes to deviate from their contractual WHOIS obligations (or whatever takes their place in a future RDS), because of a conflict with local privacy laws, there is a process for them to do so.
From: gnso-rds-pdp-wg [ <mailto:gnso-rds-pdp-wg-bounces at icann.org> mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Dotzero
Sent: Tuesday, February 13, 2018 11:04 AM
To: Volker Greimann
Cc: RDS PDP WG
Subject: Re: [gnso-rds-pdp-wg] Legal basis vs. lawful
Volker, you assert that "it would be sensible to take GDPR as a basis and start from there". Perhaps sensible from your perspective and easier from your perspective but ICANN is an international organization - primarily dealing with technical/administrative issues - and it MUST take an approach that, as best it can, accommodates the laws and practices of various jurisdictions around the world. Your proposed approach, quite simply does not do that.
Michael Hammer
On Tue, Feb 13, 2018 at 10:54 AM, Volker Greimann <vgreimann at key-systems.net <mailto:vgreimann at key-systems.net> > wrote:
I think that it would be sensible to take the GDPR as a basis and start from there. Obviously, where it conflicts with other applicable laws, we should make sure to accomodate those as well, but as the EU Commission and others have pointed out is that compliance with GDPR does not preclude providing certain access levels to certain parties. What those levels would be and who those parties could be should be the main focus of our work.
Am 13.02.2018 um 15:41 schrieb Chuck:
Volker,
Are you saying that you think that RDS policies should be designed to comply with European regulations and then applied to all other jurisdictions in the world?
Chuck
From: Volker Greimann [mailto:vgreimann at key-systems.net]
Sent: Tuesday, February 13, 2018 5:58 AM
To: Chuck <mailto:consult at cgomes.com> <consult at cgomes.com>; 'Michael Palage' <mailto:michael at palage.com> <michael at palage.com>
Cc: gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>
Subject: Re: [gnso-rds-pdp-wg] Legal basis vs. lawful
I am afraid that if we create different policies for different regions, we will break the model, encourage forum shopping and encourage firewalling of entire geographic sections of the net. I hope that is not what we are doing here.
GDPR will cause some breakage of this and I see it as our mission to fix this breakage of the standard by proposing a unified model once again.
Ultimately, if this solution does what the EU has been asking for, e.g. protect legitimate use cases of registration data as well as the rights of the data subjects, there is no reason why it should not be universally applicable.
Best,
Volker
Am 13.02.2018 um 00:04 schrieb Chuck:
Volker,
The WG could recommend policies that are ‘universally applicable to all registrations’ but I seriously doubt that will happen in today’s world. That would be much simpler than policies that vary by region and users, but is it realistic?
Chuck
From: gnso-rds-pdp-wg [mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Volker Greimann
Sent: Monday, February 12, 2018 2:30 PM
To: Michael Palage <mailto:michael at palage.com> <michael at palage.com>
Cc: gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>
Subject: Re: [gnso-rds-pdp-wg] Legal basis vs. lawful
Michael is right. ICANN iOS based on the thought of “One World; one Internet”. This also means that the policies it creates should be universally applicable to all registrations, if possible. IF we start creating policy that diverges, that would only lead to further fragmentation and undermine the founding ideal of ICANN itself. Our aim should be to create one policy that can be applied to all or most registrations and that can be implemented by all registrars alike.
While we will likely have a certain amount of fragmentation following May 25 as each contracted party applies its own solution, it should be our goal to overcome this and present a new unified policy that works for all contracted parties.
Volker
On 12. Feb 2018, at 20:27, Michael Palage <michael at palage.com <mailto:michael at palage.com> > wrote:
Greg/John,
I will respectfully push back on your legal over simplification of the GDPR.
The exterritorial aspect of the GDPR set forth in Article 3 is NOT just limited to EU residents/citizens. As Michele has noted in the past, the GDPR requires BlackKnight as an Irish legal entity to protect all of its customers data (EU/Non-EU) in compliance with GDPR, as well as US entities that target and conduct business within the EU.
Now your points about the distinction between natural and legal persons is a fair one and one that has been noted in EU and Art 29 communications. Could you please share the basis of your proposition that 97% of all domain name registrations are registered by legal entities.
As I have note previously the long term viability of the ICANN multi-stakeholder model is at risk as national governments continue to pass national laws that impact the operation of the Internet. However, the European Union is NOT alone in advancing Privacy Legislation, in fact data localization is perhaps the next biggest lurking threat to the domain name system.
Best regards,
Michael
From: gnso-rds-pdp-wg [mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of John Horton via gnso-rds-pdp-wg
Sent: Monday, February 12, 2018 1:22 PM
To: Greg Aaron <gca at icginc.com <mailto:gca at icginc.com> >
Cc: gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>
Subject: Re: [gnso-rds-pdp-wg] Legal basis vs. lawful
I think Greg is right on. There's simply no justification to force a law that is only intended to apply to a) EU residents/citizens that are b) natural persons not using the domain name for commercial purposes, to the remaining...what? 97% - 99% of the world's registrant population? That would be a balanced way to implement all of this.
John Horton
President and CEO, LegitScript
Follow LegitScript: <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_legitscript-2Dcom&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=ZNlsL3HkOUSrj6H3HaiIqByBxK3JHOO_sDEF4RRfYx4&e=> LinkedIn | <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_LegitScript&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=NrJSqdWXyZVQSooolT5KCtughhUc00tyGB583zV_XzQ&e=> Facebook | <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_legitscript&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=S7NF-0yuAMS4-JN0VdpG8FrfMsQdQQAHMgS1v_JkYLg&e=> Twitter | <https://urldefense.proofpoint.com/v2/url?u=http-3A__blog.legitscript.com_&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=iW2nS0CscTIzmxUkn9jT-JGdeGGgEn_MJniVHKoROLE&e=> Blog | <https://urldefense.proofpoint.com/v2/url?u=http-3A__go.legitscript.com_Subscription-2DManagement.html&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=TaiTEl9U6Gyw1XTcQjwYmtQhBwVYNEwf_DBQ6dM3l7A&e=> Newsletter
On Mon, Feb 12, 2018 at 9:57 AM, Greg Aaron < <mailto:gca at icginc.com> gca at icginc.com> wrote:
I don’t know if we arrive at the same place.
GDPR is based on one principle. It states what is legal. It's explicit about what you _are allowed to do_; granted there’s some flexibility and room for interpretation. It’s like saying what’s inside a box.
U.S. law is one based on different principles. AFAIK U.S. consumer protection law does not enumerate specifically what is lawful. Instead it tends to state what is illegal, what you are _not allowed to do_. It’s like saying what’s outside the box. The U.S. doesn’t have something like GDPR that spells out legal bases for collecting data, i.e. the enumerated allowable reasons. Instead the trade and consumer protection laws basically say: entities have the right to form contracts between themselves, they should live up to the contract, don’t surprise people, don’t do certain dishonest things.
Here's the problem: if one makes the GDPR principle the ICANN standard and you apply it to all registrations, then practices that are allowable in one place under the law (like the U.S.) would no longer be allowed there by ICANN policy. ICANN would be choosing one legal approach or regime for everyone in the world.
The alternative is to apply the GDRP only to those that it is designed to protect: registrants in the EU.
For example, there’s nothing in U.S. law that prohibits a U.S. registrar from having a contract that says publication of full contact data in WHOIS is a condition of registering a domain name if you are a registrant in the U.S.
See <https://urldefense.proofpoint.com/v2/url?u=https-3A__iapp.org_news_a_explaining-2Dthe-2Dgdpr-2Dto-2Dan-2Damerican_&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=HR7E74IbLN2-Xhfn1tX5fkjRdhqvSFbEexgHkr8K64Y&e=> https://iapp.org/news/a/explaining-the-gdpr-to-an-american/ for more.
From: gnso-rds-pdp-wg [ <mailto:gnso-rds-pdp-wg-bounces at icann.org> mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Silver, Bradley via gnso-rds-pdp-wg
Sent: Friday, February 9, 2018 2:54 PM
To: Volker Greimann < <mailto:vgreimann at key-systems.net> vgreimann at key-systems.net>; <mailto:gnso-rds-pdp-wg at icann.org> gnso-rds-pdp-wg at icann.org
Subject: Re: [gnso-rds-pdp-wg] Legal basis vs. lawful
It is true that the GDPR is prescriptive, although also rather open-ended (hence our current pickle). But regardless of the term we use, don’t we arrive at the same place: which is that if something that requires a legal basis is done without one, it will be unlawful? Using Kathy’s example, if data is processed without complying with minimization or purpose principles, will such processing not run afoul of the law, and hence be unlawful?
There are important distinctions between the meaning of “legal basis” which implies that a law requires something to be affirmatively present, versus “lawful”, which means that something is not prohibited by law. Ultimately though, isn’t “lawfulness”, the same end point, regardless?
From: gnso-rds-pdp-wg [ <mailto:gnso-rds-pdp-wg-bounces at icann.org> mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Volker Greimann
Sent: Friday, February 09, 2018 11:27 AM
To: <mailto:gnso-rds-pdp-wg at icann.org> gnso-rds-pdp-wg at icann.org
Subject: Re: [gnso-rds-pdp-wg] Legal basis vs. lawful
I do not see how. Kathy's analysis seems sound. The flexibility within the GDPR still only allows processing in very specific cicumstances, all of which are listed in the GDPR.
Am 09.02.2018 um 16:45 schrieb Victoria Sheckler:
Kathy’s analysis breaks down on a practical level when one looks at the GDPR and what it says about when data can be processed. The GDPR allows for flexibility for what can be processed and when, and kathy’s analysis overlooks that point.
From: gnso-rds-pdp-wg [ <mailto:gnso-rds-pdp-wg-bounces at icann.org> mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Kathy Kleiman
Sent: Thursday, February 8, 2018 7:07 PM
To: <mailto:gnso-rds-pdp-wg at icann.org> gnso-rds-pdp-wg at icann.org
Subject: Re: [gnso-rds-pdp-wg] Legal basis vs. lawful
Tx for the invitation to join, Chuck, and following up on the discussion of Sam and Tapani, let me add that criteria for processing must be clearer than something broadly within ICANN's mission statement and something permissible somewhere. The requirements under law are express and concrete.
Specifically, GDPR Article 5(1)(b and c) states:
Personal data shall be:
2. "collected for specified, explicit and legitimate purposes and not further processed in a manner that is incompatible with those purposes" (the "purpose limitation") AND
3. "adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed" (the "data minimisation" requirement). [underline added]
Thus, our first criteria of "consistent with ICANN's mission," is only the first step and we need to go further than even the 3 criteria we are discussing..
Second, lawful and legal enter us into a debate over words and I have to agree with Sam and Tapani's analysis and let me add some of my own.
"Legal" is the term we use for actions expressly allowed under law. How we process personal data under the GDRP falls into this category -- of processing expressly allowed under law. Whereas the term lawful is used for a much broader category of actions which are generally permissible and allowable.
The term "legal" is much more consistent with our criteria statement because the processing of personal data by ICANN must clearly have a valid legal basis as expressly defined by data protection laws.
Best regards,
Kathy
On 2/7/2018 10:53 AM, Sam Lanfranco wrote:
Thanks Tapani,
I will extract from your longer message.
I deliberately kept my brief and less technical.
I think we are in agreement here and I support your position.
On 2/7/2018 1:07 AM, Tapani Tarvainen wrote:
The key distinction, as I understand it, is that "lawful" would be
defined by the negative, everything that some law does not prohibit,
where as "legal basis" is defined by the positive, only things whose
justification can be explicitly derived from law.
<......>
So I would prefer "legal basis" specifically in this sense: that any processing
would have to be explicitly based on one of the criteria, or bases, as listed
in GDPR Article 6, or similar explicit justification in other data protection legislation.
_______________________________________________
gnso-rds-pdp-wg mailing list
<mailto:gnso-rds-pdp-wg at icann.org> gnso-rds-pdp-wg at icann.org
<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dwg&d=DwMDaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=fOG1O9n2_DhDKrVj0wrojDKlYIsDeLHzwtDlEi-f9Ng&s=GditP_BvWvjE7xFIYot7e5akySiL4RPKaCgA_X_fyTE&e=> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
_______________________________________________
gnso-rds-pdp-wg mailing list
<mailto:gnso-rds-pdp-wg at icann.org> gnso-rds-pdp-wg at icann.org
<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dwg&d=DwMDaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=fOG1O9n2_DhDKrVj0wrojDKlYIsDeLHzwtDlEi-f9Ng&s=GditP_BvWvjE7xFIYot7e5akySiL4RPKaCgA_X_fyTE&e=> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
_____
Reminder: Any email that requests your login credentials or that asks you to click on a link could be a phishing attack. If you have any questions regarding the authenticity of this email or its sender, please contact the IT Service Desk at <tel:%28212%29%20484-6000> 212.484.6000 or via email at <mailto:ITServices at timewarner.com> ITServices at timewarner.com
_____
This message is the property of Time Warner Inc. and is intended only for the use of the addressee(s) and may be legally privileged and/or confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, he or she is hereby notified that any dissemination, distribution, printing, forwarding, or any method of copying of this information, and/or the taking of any action in reliance on the information herein is strictly prohibited except by the intended recipient or those to whom he or she intentionally distributes this message. If you have received this communication in error, please immediately notify the sender, and delete the original message and any copies from your computer or storage system. Thank you.
_______________________________________________
gnso-rds-pdp-wg mailing list
<mailto:gnso-rds-pdp-wg at icann.org> gnso-rds-pdp-wg at icann.org
<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dwg&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=jczIBTjLgtBVtedOnmeMW-_WPUnlE6ODNOmjhfCPQEg&e=> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
_______________________________________________
gnso-rds-pdp-wg mailing list
<mailto:gnso-rds-pdp-wg at icann.org> gnso-rds-pdp-wg at icann.org
<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dwg&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=jczIBTjLgtBVtedOnmeMW-_WPUnlE6ODNOmjhfCPQEg&e=> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
--
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.: <tel:+49%206894%209396901> +49 (0) 6894 - 9396 901
Fax.: <tel:+49%206894%209396851> +49 (0) 6894 - 9396 851
<mailto:vgreimann at key-systems.net> Email: vgreimann at key-systems.net
Web: <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.key-2Dsystems.net&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=CeKGpwgO5g-PqUpTecoaY2MesyVLXofYokNSOoMtIEs&e=> www.key-systems.net / <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.RRPproxy.net&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=ZotVwb6plvRA3lWht6N0XemQhIw-3PV46y48UPiVRXk&e=> www.RRPproxy.net
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.domaindiscount24.com&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=l2IpMUVNZeAJOszlpCL6MYuASFfGe5BthPZd5PyvMxo&e=> www.domaindiscount24.com / <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.BrandShelter.com&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=wj-fuEXWJZvM-LH0jCTP89edjW3_Q6biBN_DDdQPSl0&e=> www.BrandShelter.com
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_KeySystems&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=fHTJbGWZ2pcEi_6Rg636HtapV9W0oQkqVnJOk4dBmCs&e=> www.facebook.com/KeySystems
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_key-5Fsystems&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=ReaeT_WpYTz-xf-2RdG64TM9Pbz86iHJlblZYmROuuc&e=> www.twitter.com/key_systems
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.keydrive.lu&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=WzTdZzwmUxHqvCqLkFd_v6jMK9gd7QDpRVA-yS_AYEE&e=> www.keydrive.lu
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.: <tel:+49%206894%209396901> +49 (0) 6894 - 9396 901
Fax.: <tel:+49%206894%209396851> +49 (0) 6894 - 9396 851
Email: <mailto:vgreimann at key-systems.net> vgreimann at key-systems.net
Web: <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.key-2Dsystems.net&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=CeKGpwgO5g-PqUpTecoaY2MesyVLXofYokNSOoMtIEs&e=> www.key-systems.net / <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.RRPproxy.net&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=ZotVwb6plvRA3lWht6N0XemQhIw-3PV46y48UPiVRXk&e=> www.RRPproxy.net
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.domaindiscount24.com&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=l2IpMUVNZeAJOszlpCL6MYuASFfGe5BthPZd5PyvMxo&e=> www.domaindiscount24.com / <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.BrandShelter.com&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=wj-fuEXWJZvM-LH0jCTP89edjW3_Q6biBN_DDdQPSl0&e=> www.BrandShelter.com
Follow us on Twitter or join our fan community on Facebook and stay updated:
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_KeySystems&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=fHTJbGWZ2pcEi_6Rg636HtapV9W0oQkqVnJOk4dBmCs&e=> www.facebook.com/KeySystems
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_key-5Fsystems&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=ReaeT_WpYTz-xf-2RdG64TM9Pbz86iHJlblZYmROuuc&e=> www.twitter.com/key_systems
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.keydrive.lu&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=WzTdZzwmUxHqvCqLkFd_v6jMK9gd7QDpRVA-yS_AYEE&e=> www.keydrive.lu
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.
_______________________________________________
gnso-rds-pdp-wg mailing list
gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg <https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drds-2Dpdp-2Dwg&d=DwMFaQ&c=tq9bLrSQ8zIr87VusnUS92RmR2KtbW6AiQIx78dtRmA&r=TAA3GKe6tpWdv3RbCks6TRrjaTx9d0J3KzemA65KYpA&m=MnL0DaGK44Xa9WEHXtgiJa-Dsa_2TZ5RCXN75zMQ6c0&s=jczIBTjLgtBVtedOnmeMW-_WPUnlE6ODNOmjhfCPQEg&e=>
_____
Reminder: Any email that requests your login credentials or that asks you to click on a link could be a phishing attack. If you have any questions regarding the authenticity of this email or its sender, please contact the IT Service Desk at 212.484.6000 or via email at <mailto:ITServices at timewarner.com> ITServices at timewarner.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20180213/95250ace/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 426 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20180213/95250ace/image004-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 453 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20180213/95250ace/image005-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 460 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20180213/95250ace/image006-0001.jpg>
More information about the gnso-rds-pdp-wg
mailing list