Re: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean
Making the decision that having an RDS (WHOIS or something else) is essential may have to happen later? Chuck, did you mean make the decision to get a NEW RDS? Because it is bizarre to discuss the purposes of an RDS but deny there should even be an RDS. If an RDS has even one valid purpose, there logically should be an RDS. Can we imagine if this WG reported back to the world that we should no longer have WHOIS or any successor system? That people would no longer even be able to look up what domains are registered and which are not? I am interested if anyone can show how the publication of thin data is harmful, and then that the harm outweighs the benefits. For example, no, IP numbers are not sensitive in this scenario. First, anyone can find out the A record of a resolving domain by performing a DNS lookup (dig). This is baked into how the DNS itself works. An IP address MUST be submitted to the relevant registry in order for a valid nameserver record to exist, and thereby allow one or more associated domain names to resolve. IP addresses are considered PII in some places (such as Europe) but if and only if they can be connected back to an individual. The use case there is usually: can we identify a person by their _origin_ (the IP of the computer they are using). Such as law enforcement trying to figure out what individual visited a web site from traffic logs of users' IP addresses. This involves the origin of an Internet user, not where a domain name resolves to. All best, --Greg -----Original Message----- From: Gomes, Chuck [mailto:cgomes@verisign.com] Sent: Wednesday, December 7, 2016 6:16 PM To: Greg Aaron <gca@icginc.com>; ajs@anvilwalrusden.com; gnso-rds-pdp-wg@icann.org Subject: RE: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Please see my thoughts below. Chuck -----Original Message----- From: gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org] On Behalf Of Greg Aaron Sent: Wednesday, December 07, 2016 5:24 PM To: Andrew Sullivan <ajs@anvilwalrusden.com>; gnso-rds-pdp-wg@icann.org Subject: [EXTERNAL] Re: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Dear Mike: Thanks. And I think Andrew gets what I'm saying. "Should gTLD registration data be accessible for any purpose or only for specific purposes?" The question assumes we're talking about contact data. With thin data, I suggest that the question doesn't matter much -- none of that data's sensitive. The question only really matters when we're talking about contact data (PII). [Gomes, Chuck] I don't think I agree that the question assumes we are talking about contact data or that thin data is never sensitive. I believe that Andrew suggested the same thing. For example, is it possible for IP numbers to be sensitive? I also think that we may have to examine 'Other Data' (Data that is not thin or contact data). I would like to think that thin data and other data may be easier but we may still have to work on them. Note what I said: "This is not a proposal to publish thin data only." I'm simply wondering if everyone can agree that having an RDS is essential, and that publishing at least the thin data via it is essential for many valid and public purposes. Thin data may not satisfy all valid purposes, but requiring the world to get along without thin data seems untenable. Agreeing to this would be a step forward for the WG. Progress has been hard to find here, nearly a year in.... [Gomes, Chuck] I suspect that making the decision that having an RDS is essential may have to happen later. Don't get me wrong, it would be nice if we could agree on that now, but it may be premature to do that. We should certainly agree on what the valid and public purposes are first. I wouldn't be surprised if we came to conclusion that getting 'along without thin data seems untenable' but I believe we will have to specifically come to that conclusion in our deliberation. I do like Andrew's suggestion that we should start by focusing on think data. Then would come the more difficult discussion about contact data. Your observations do not invalidate my approach. I don't think my idea favors or endangers anyone's ability to argue their positions about the collection and publication of contact data (PII), nor does it endangers future innovation as far as I am aware. FWIW, I agree with you that the legal construct upon which the domain name system is based recognizes the Registrant and the Registrant Data that it provides. Let's not get too hung up on trademark, nexus, reseller, etc. data. These miscellaneous fields exist and we should be aware of them, and that future innovation (like inventing more) is possible. But also 99.5% of gTLD domains don't employ those extra fields at this time, and they're not a reason to torpedo anything at this stage. The general categories are useful. If we want to think of it as PII data versus not-PII data, that's a way to think of it too. Anyway, we are good engineers, and good engineers are aware of the corner cases while also keeping the big picture in mind. [Gomes, Chuck] The more immediate focus should be on the 99.5% but I think we will still have to cover the corner cases at least in a general sense. All best, --Greg ********************************** -----Original Message----- From: gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org] On Behalf Of Andrew Sullivan Sent: Wednesday, December 7, 2016 4:35 PM To: gnso-rds-pdp-wg@icann.org Subject: Re: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Hi Michael, On Wed, Dec 07, 2016 at 04:13:01PM -0500, Michael D. Palage wrote:
I appreciate Greg's historical context of Whois data primarily being for purposes of "contacting" the registrant of a domain name using those data fields with personally identifying information. However, I think introducing/relying upon the concept of "CONTACT DATA" as proposed by Greg while well intentioned will only lead to greater confusion.
If instead of "contact data" we want to call it "the flying monkey all-singing-and-dancing circus data", I don't care. I think Greg's point is that there are several different kinds of data here, and we could start with the little set that is unambiguously related to the domain _qua_ domain, and hammer out some agreement there. That would have the salubrious effects that we would have found some common ground, it would allow us to close coversations on some parts of the data, and it would allow us to acknowledge that there are at least two classes of data here. For that reason,
First Greg acknowledges that not ALL data other than the thin technical data falls within his CONTACT DATA definition
we might well acknowledge that there are at least two kinds of data we're talking about, and start with the first class. Then we could work on a second class. At some point, we'll run out of classes that people will be able to mention; we don't need to know in advance exactly how many there are. They're surely fewer than 30.
Second, the use of this terminology ignores the reality in the marketplace that Registrant data is widely relied upon to make legal determinations
What these different classes of data are used _for_ is an entirely different problem from what kinds of data they are. Those potential uses, indeed, are something we need to consider when asking under what circumstances a given datum may be disclosed, and to whom. But the use is not part of the definition of the kind of data.
"ICANN's WHOIS Lookup gives you the ability to lookup any generic domains, such as "icann.org" to find out the registered domain owner."
I do not believe one can argue from the premise that this is how things have always been done to the conclusion that it is how things _should_ be done.
So I think we stick to one of the first things I learned as a young engineer. Keep It Simple Stupid (KISS)
Agreed. And for that reason, we should start with the simple cases and forge some consensus there before we start with the hard cases. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
Greg, Can you please explain what you mean by the origin of an Internet user?Such as law enforcement trying to figure out what individual visited a web site from traffic logs of users' IP addresses. This involves the origin of an Internet user, not where a domain name resolves to.If law enforcement has the IP address, the time of use and traffic analysis log, it can always trace the IP address to an individual, can it not? Nathalie On Wednesday, December 7, 2016 7:19 PM, Greg Aaron <gca@icginc.com> wrote: Making the decision that having an RDS (WHOIS or something else) is essential may have to happen later? Chuck, did you mean make the decision to get a NEW RDS? Because it is bizarre to discuss the purposes of an RDS but deny there should even be an RDS. If an RDS has even one valid purpose, there logically should be an RDS. Can we imagine if this WG reported back to the world that we should no longer have WHOIS or any successor system? That people would no longer even be able to look up what domains are registered and which are not? I am interested if anyone can show how the publication of thin data is harmful, and then that the harm outweighs the benefits. For example, no, IP numbers are not sensitive in this scenario. First, anyone can find out the A record of a resolving domain by performing a DNS lookup (dig). This is baked into how the DNS itself works. An IP address MUST be submitted to the relevant registry in order for a valid nameserver record to exist, and thereby allow one or more associated domain names to resolve. IP addresses are considered PII in some places (such as Europe) but if and only if they can be connected back to an individual. The use case there is usually: can we identify a person by their _origin_ (the IP of the computer they are using). Such as law enforcement trying to figure out what individual visited a web site from traffic logs of users' IP addresses. This involves the origin of an Internet user, not where a domain name resolves to. All best, --Greg -----Original Message----- From: Gomes, Chuck [mailto:cgomes@verisign.com] Sent: Wednesday, December 7, 2016 6:16 PM To: Greg Aaron <gca@icginc.com>; ajs@anvilwalrusden.com; gnso-rds-pdp-wg@icann.org Subject: RE: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Please see my thoughts below. Chuck -----Original Message----- From: gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org] On Behalf Of Greg Aaron Sent: Wednesday, December 07, 2016 5:24 PM To: Andrew Sullivan <ajs@anvilwalrusden.com>; gnso-rds-pdp-wg@icann.org Subject: [EXTERNAL] Re: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Dear Mike: Thanks. And I think Andrew gets what I'm saying. "Should gTLD registration data be accessible for any purpose or only for specific purposes?" The question assumes we're talking about contact data. With thin data, I suggest that the question doesn't matter much -- none of that data's sensitive. The question only really matters when we're talking about contact data (PII). [Gomes, Chuck] I don't think I agree that the question assumes we are talking about contact data or that thin data is never sensitive. I believe that Andrew suggested the same thing. For example, is it possible for IP numbers to be sensitive? I also think that we may have to examine 'Other Data' (Data that is not thin or contact data). I would like to think that thin data and other data may be easier but we may still have to work on them. Note what I said: "This is not a proposal to publish thin data only." I'm simply wondering if everyone can agree that having an RDS is essential, and that publishing at least the thin data via it is essential for many valid and public purposes. Thin data may not satisfy all valid purposes, but requiring the world to get along without thin data seems untenable. Agreeing to this would be a step forward for the WG. Progress has been hard to find here, nearly a year in.... [Gomes, Chuck] I suspect that making the decision that having an RDS is essential may have to happen later. Don't get me wrong, it would be nice if we could agree on that now, but it may be premature to do that. We should certainly agree on what the valid and public purposes are first. I wouldn't be surprised if we came to conclusion that getting 'along without thin data seems untenable' but I believe we will have to specifically come to that conclusion in our deliberation. I do like Andrew's suggestion that we should start by focusing on think data. Then would come the more difficult discussion about contact data. Your observations do not invalidate my approach. I don't think my idea favors or endangers anyone's ability to argue their positions about the collection and publication of contact data (PII), nor does it endangers future innovation as far as I am aware. FWIW, I agree with you that the legal construct upon which the domain name system is based recognizes the Registrant and the Registrant Data that it provides. Let's not get too hung up on trademark, nexus, reseller, etc. data. These miscellaneous fields exist and we should be aware of them, and that future innovation (like inventing more) is possible. But also 99.5% of gTLD domains don't employ those extra fields at this time, and they're not a reason to torpedo anything at this stage. The general categories are useful. If we want to think of it as PII data versus not-PII data, that's a way to think of it too. Anyway, we are good engineers, and good engineers are aware of the corner cases while also keeping the big picture in mind. [Gomes, Chuck] The more immediate focus should be on the 99.5% but I think we will still have to cover the corner cases at least in a general sense. All best, --Greg ********************************** -----Original Message----- From: gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org] On Behalf Of Andrew Sullivan Sent: Wednesday, December 7, 2016 4:35 PM To: gnso-rds-pdp-wg@icann.org Subject: Re: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Hi Michael, On Wed, Dec 07, 2016 at 04:13:01PM -0500, Michael D. Palage wrote:
I appreciate Greg's historical context of Whois data primarily being for purposes of "contacting" the registrant of a domain name using those data fields with personally identifying information. However, I think introducing/relying upon the concept of "CONTACT DATA" as proposed by Greg while well intentioned will only lead to greater confusion.
If instead of "contact data" we want to call it "the flying monkey all-singing-and-dancing circus data", I don't care. I think Greg's point is that there are several different kinds of data here, and we could start with the little set that is unambiguously related to the domain _qua_ domain, and hammer out some agreement there. That would have the salubrious effects that we would have found some common ground, it would allow us to close coversations on some parts of the data, and it would allow us to acknowledge that there are at least two classes of data here. For that reason,
First Greg acknowledges that not ALL data other than the thin technical data falls within his CONTACT DATA definition
we might well acknowledge that there are at least two kinds of data we're talking about, and start with the first class. Then we could work on a second class. At some point, we'll run out of classes that people will be able to mention; we don't need to know in advance exactly how many there are. They're surely fewer than 30.
Second, the use of this terminology ignores the reality in the marketplace that Registrant data is widely relied upon to make legal determinations
What these different classes of data are used _for_ is an entirely different problem from what kinds of data they are. Those potential uses, indeed, are something we need to consider when asking under what circumstances a given datum may be disclosed, and to whom. But the use is not part of the definition of the kind of data.
"ICANN's WHOIS Lookup gives you the ability to lookup any generic domains, such as "icann.org" to find out the registered domain owner."
I do not believe one can argue from the premise that this is how things have always been done to the conclusion that it is how things _should_ be done.
So I think we stick to one of the first things I learned as a young engineer. Keep It Simple Stupid (KISS)
Agreed. And for that reason, we should start with the simple cases and forge some consensus there before we start with the hard cases. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
The computer you use to access the Internet has an IP address. That is your origin. The place you want to visit – say a web site on a domain name – has a different IP address. That is your destination. From: nathalie coupet [mailto:nathaliecoupet@yahoo.com] Sent: Wednesday, December 7, 2016 7:24 PM To: Greg Aaron <gca@icginc.com>; Gomes, Chuck <cgomes@verisign.com>; ajs@anvilwalrusden.com; gnso-rds-pdp-wg@icann.org Subject: Re: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Greg, Can you please explain what you mean by the origin of an Internet user?Such as law enforcement trying to figure out what individual visited a web site from traffic logs of users' IP addresses. This involves the origin of an Internet user, not where a domain name resolves to. If law enforcement has the IP address, the time of use and traffic analysis log, it can always trace the IP address to an individual, can it not? Nathalie On Wednesday, December 7, 2016 7:19 PM, Greg Aaron <gca@icginc.com<mailto:gca@icginc.com>> wrote: Making the decision that having an RDS (WHOIS or something else) is essential may have to happen later? Chuck, did you mean make the decision to get a NEW RDS? Because it is bizarre to discuss the purposes of an RDS but deny there should even be an RDS. If an RDS has even one valid purpose, there logically should be an RDS. Can we imagine if this WG reported back to the world that we should no longer have WHOIS or any successor system? That people would no longer even be able to look up what domains are registered and which are not? I am interested if anyone can show how the publication of thin data is harmful, and then that the harm outweighs the benefits. For example, no, IP numbers are not sensitive in this scenario. First, anyone can find out the A record of a resolving domain by performing a DNS lookup (dig). This is baked into how the DNS itself works. An IP address MUST be submitted to the relevant registry in order for a valid nameserver record to exist, and thereby allow one or more associated domain names to resolve. IP addresses are considered PII in some places (such as Europe) but if and only if they can be connected back to an individual. The use case there is usually: can we identify a person by their _origin_ (the IP of the computer they are using). Such as law enforcement trying to figure out what individual visited a web site from traffic logs of users' IP addresses. This involves the origin of an Internet user, not where a domain name resolves to. All best, --Greg -----Original Message----- From: Gomes, Chuck [mailto:cgomes@verisign.com<mailto:cgomes@verisign.com>] Sent: Wednesday, December 7, 2016 6:16 PM To: Greg Aaron <gca@icginc.com<mailto:gca@icginc.com>>; ajs@anvilwalrusden.com<mailto:ajs@anvilwalrusden.com>; gnso-rds-pdp-wg@icann.org<mailto:gnso-rds-pdp-wg@icann.org> Subject: RE: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Please see my thoughts below. Chuck -----Original Message----- From: gnso-rds-pdp-wg-bounces@icann.org<mailto:gnso-rds-pdp-wg-bounces@icann.org> [mailto:gnso-rds-pdp-wg-bounces@icann.org<mailto:gnso-rds-pdp-wg-bounces@icann.org>] On Behalf Of Greg Aaron Sent: Wednesday, December 07, 2016 5:24 PM To: Andrew Sullivan <ajs@anvilwalrusden.com<mailto:ajs@anvilwalrusden.com>>; gnso-rds-pdp-wg@icann.org<mailto:gnso-rds-pdp-wg@icann.org> Subject: [EXTERNAL] Re: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Dear Mike: Thanks. And I think Andrew gets what I'm saying. "Should gTLD registration data be accessible for any purpose or only for specific purposes?" The question assumes we're talking about contact data. With thin data, I suggest that the question doesn't matter much -- none of that data's sensitive. The question only really matters when we're talking about contact data (PII). [Gomes, Chuck] I don't think I agree that the question assumes we are talking about contact data or that thin data is never sensitive. I believe that Andrew suggested the same thing. For example, is it possible for IP numbers to be sensitive? I also think that we may have to examine 'Other Data' (Data that is not thin or contact data). I would like to think that thin data and other data may be easier but we may still have to work on them. Note what I said: "This is not a proposal to publish thin data only." I'm simply wondering if everyone can agree that having an RDS is essential, and that publishing at least the thin data via it is essential for many valid and public purposes. Thin data may not satisfy all valid purposes, but requiring the world to get along without thin data seems untenable. Agreeing to this would be a step forward for the WG. Progress has been hard to find here, nearly a year in.... [Gomes, Chuck] I suspect that making the decision that having an RDS is essential may have to happen later. Don't get me wrong, it would be nice if we could agree on that now, but it may be premature to do that. We should certainly agree on what the valid and public purposes are first. I wouldn't be surprised if we came to conclusion that getting 'along without thin data seems untenable' but I believe we will have to specifically come to that conclusion in our deliberation. I do like Andrew's suggestion that we should start by focusing on think data. Then would come the more difficult discussion about contact data. Your observations do not invalidate my approach. I don't think my idea favors or endangers anyone's ability to argue their positions about the collection and publication of contact data (PII), nor does it endangers future innovation as far as I am aware. FWIW, I agree with you that the legal construct upon which the domain name system is based recognizes the Registrant and the Registrant Data that it provides. Let's not get too hung up on trademark, nexus, reseller, etc. data. These miscellaneous fields exist and we should be aware of them, and that future innovation (like inventing more) is possible. But also 99.5% of gTLD domains don't employ those extra fields at this time, and they're not a reason to torpedo anything at this stage. The general categories are useful. If we want to think of it as PII data versus not-PII data, that's a way to think of it too. Anyway, we are good engineers, and good engineers are aware of the corner cases while also keeping the big picture in mind. [Gomes, Chuck] The more immediate focus should be on the 99.5% but I think we will still have to cover the corner cases at least in a general sense. All best, --Greg ********************************** -----Original Message----- From: gnso-rds-pdp-wg-bounces@icann.org<mailto:gnso-rds-pdp-wg-bounces@icann.org> [mailto:gnso-rds-pdp-wg-bounces@icann.org<mailto:gnso-rds-pdp-wg-bounces@icann.org>] On Behalf Of Andrew Sullivan Sent: Wednesday, December 7, 2016 4:35 PM To: gnso-rds-pdp-wg@icann.org<mailto:gnso-rds-pdp-wg@icann.org> Subject: Re: [gnso-rds-pdp-wg] key concepts: say "contact data" when that is what we mean Hi Michael, On Wed, Dec 07, 2016 at 04:13:01PM -0500, Michael D. Palage wrote:
I appreciate Greg's historical context of Whois data primarily being for purposes of "contacting" the registrant of a domain name using those data fields with personally identifying information. However, I think introducing/relying upon the concept of "CONTACT DATA" as proposed by Greg while well intentioned will only lead to greater confusion.
If instead of "contact data" we want to call it "the flying monkey all-singing-and-dancing circus data", I don't care. I think Greg's point is that there are several different kinds of data here, and we could start with the little set that is unambiguously related to the domain _qua_ domain, and hammer out some agreement there. That would have the salubrious effects that we would have found some common ground, it would allow us to close coversations on some parts of the data, and it would allow us to acknowledge that there are at least two classes of data here. For that reason,
First Greg acknowledges that not ALL data other than the thin technical data falls within his CONTACT DATA definition
we might well acknowledge that there are at least two kinds of data we're talking about, and start with the first class. Then we could work on a second class. At some point, we'll run out of classes that people will be able to mention; we don't need to know in advance exactly how many there are. They're surely fewer than 30.
Second, the use of this terminology ignores the reality in the marketplace that Registrant data is widely relied upon to make legal determinations
What these different classes of data are used _for_ is an entirely different problem from what kinds of data they are. Those potential uses, indeed, are something we need to consider when asking under what circumstances a given datum may be disclosed, and to whom. But the use is not part of the definition of the kind of data.
"ICANN's WHOIS Lookup gives you the ability to lookup any generic domains, such as "icann.org" to find out the registered domain owner."
I do not believe one can argue from the premise that this is how things have always been done to the conclusion that it is how things _should_ be done.
So I think we stick to one of the first things I learned as a young engineer. Keep It Simple Stupid (KISS)
Agreed. And for that reason, we should start with the simple cases and forge some consensus there before we start with the hard cases. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com<mailto:ajs@anvilwalrusden.com> _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org<mailto:gnso-rds-pdp-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org<mailto:gnso-rds-pdp-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org<mailto:gnso-rds-pdp-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
Can we imagine if this WG reported back to the world that we should no longer have WHOIS or any successor system?
Sounds like a perfectly valid final conclusion to me, if a _little_ unlikely.
That people would no longer even be able to look up what domains are registered and which are not?
What has the ability to look up what domains are registered (or not) got to do with RDS/WHOIS ? whois (or any replacement of it) is the wrong tool for that task Rob
Well, there are ccTLD registries out there that publish next to no registrant information. For example nic.io only publishes a handle like NIC-123456 for all registration contacts. Who is to say that is not the better solution? Note that this only means no data is published. the data is still held and stored by the registry. Volker Am 08.12.2016 um 02:53 schrieb Rob Golding:
Can we imagine if this WG reported back to the world that we should no longer have WHOIS or any successor system?
Sounds like a perfectly valid final conclusion to me, if a _little_ unlikely.
That people would no longer even be able to look up what domains are registered and which are not?
What has the ability to look up what domains are registered (or not) got to do with RDS/WHOIS ?
whois (or any replacement of it) is the wrong tool for that task
Rob _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org 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.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP 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.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP 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.
participants (4)
-
Greg Aaron -
nathalie coupet -
Rob Golding -
Volker Greimann