On Wed, 6 Jun 2018 08:01:35 +0300, Hank Nussbacher
may have written:
> "The European Commission has insisted it is *not subject to the strict
> new data protection law* that it has imposed across Europe after it was
> revealed the personal information of hundreds of people had been leaked
> on
On 31/05/2018 08:14, Badiei, Farzaneh wrote:
Gotta love the EU logic:
https://inews.co.uk/news/uk/gdpr-eu-commission-not-compliant/
The European Commission is not GDPR compliant even though it was
responsible for the new GDPR law
"The European Commission has insisted it is *not subject to the
peering DB has a sole purpose of disseminating names, phone
numbers and email addresses.
Mack
From: Rubens Kuhl [mailto:rube...@gmail.com]
Sent: Tuesday, June 05, 2018 1:41 PM
To: McBride, Mack
Cc: Daniel Corbe ; Baldur Norddahl
; nanog@nanog.org
Subject: Re: ICANN GDPR lawsuit
On Tue, Jun 5
On Tue, Jun 5, 2018 at 4:31 PM, McBride, Mack
wrote:
> PeeringDB is already 100% opt-in.
>
Domain registration is also opt-in, and still registrars, registries and
ICANN have to change things to comply with GDPR.
Rubens
PeeringDB is already 100% opt-in.
Mack
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Daniel Corbe
Sent: Monday, June 04, 2018 12:56 PM
To: Baldur Norddahl
Cc: nanog@nanog.org
Subject: Re: ICANN GDPR lawsuit
at 2:40 PM, Baldur Norddahl wrote:
> man
at 2:40 PM, Baldur Norddahl wrote:
man. 4. jun. 2018 17.31 skrev McBride, Mack :
GDPR doesn't play well with directory listing services.
BUT since providing contact information is exactly what a directory
listing service does,
It is safe to assume that this is 'essential' under GDPR.
No it
PM
To: nanog@nanog.org
Subject: Re: ICANN GDPR lawsuit
In article you write:
>http://www.circleid.com/posts/20180527_icann_files_legal_action_against_domain_registrar_whois_data/
Elliot said that if he had to choose between fighting ICANN and
fighting governments, he'd fight ICANN. I can't
On June 4, 2018 at 17:01 ra...@psg.com (Randy Bush) wrote:
> once upon a time, when one received what had yet to be called spam, or
> logs showed an attack, one wrote to the owner of the source ip to tell
> them their system had been hacked. dunno about everyone else, but i
> stopped doing
On Mon, Jun 4, 2018 at 9:34 PM, Dan Hollis wrote:
> On Mon, 4 Jun 2018, Rubens Kuhl wrote:
>
>> On Fri, Jun 1, 2018 at 1:56 AM, Hank Nussbacher
>> wrote:
>> Usually, identifying attackers at other online services is a duty on RIR
>> directories, and even the RIPE one is not suffering that many
On Mon, 4 Jun 2018, Rubens Kuhl wrote:
On Fri, Jun 1, 2018 at 1:56 AM, Hank Nussbacher
wrote:
Usually, identifying attackers at other online services is a duty on RIR
directories, and even the RIPE one is not suffering that many changes due
to GDPR.
Also, GDPR doesn't prevent law enforcement
once upon a time, when one received what had yet to be called spam, or
logs showed an attack, one wrote to the owner of the source ip to tell
them their system had been hacked. dunno about everyone else, but i
stopped doing that sometime in the '80s.
randy
_ //` `\
_,-"\% //
Subject: Re: ICANN GDPR lawsuit
> On Jun 3, 2018, at 22:44 , Baldur Norddahl wrote:
>
>>
>>
>>
>> Yeah, what Niels is really leaving out here is the open question of
>> whether or not GDPR will eventually lead to the destruction of Peering D
man. 4. jun. 2018 20.56 skrev Daniel Corbe :
>
> It occurs to me that operators might want to opt-in to have their data
> published through PeeringDB. From a purely pragmatic standpoint, I won’t
> peer with anyone I can’t reach out to and if you don’t have a 24/7 NOC
> chances are good that
man. 4. jun. 2018 20.58 skrev Owen DeLong :
>
>
> Much of the information in Peering DB is people. In fact, IIRC, peering DB
> doesn’t really have “role” accounts.
>
> Peering DB is unrelated to whois.
>
> Owen
>
No actually I just checked and peeringdb has none of my personal
information. It
On Fri, Jun 1, 2018 at 1:56 AM, Hank Nussbacher
wrote:
> On 31/05/2018 21:44, John Peach wrote:
> > On 05/31/2018 02:37 PM, Dan Hollis wrote:
> >> On Thu, 31 May 2018, b...@theworld.com wrote:
> >>> FWIW a German court has just ruled against ICANN's injunction and in
> >>> favor of Tucows/EPAG.
nor contradict any regulatory requirement (which covers cyber attacks).
>
> Mack
>
> -Original Message-
> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Johnny Eriksson
> Sent: Monday, June 04, 2018 12:24 PM
> To: nanog@nanog.org
> Subject: Re: ICA
> On Jun 3, 2018, at 22:44 , Baldur Norddahl wrote:
>
>>
>>
>>
>> Yeah, what Niels is really leaving out here is the open question of
>> whether or not GDPR will eventually lead to the destruction of Peering DB.
>>
>> Owen
>>
>
>
> Of course it will not. We just need to accept that
man. 4. jun. 2018 17.31 skrev McBride, Mack :
> GDPR doesn't play well with directory listing services.
> BUT since providing contact information is exactly what a directory
> listing service does,
> It is safe to assume that this is 'essential' under GDPR.
>
No it is very clear that publishing
Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Johnny Eriksson
Sent: Monday, June 04, 2018 12:24 PM
To: nanog@nanog.org
Subject: Re: ICANN GDPR lawsuit
Hank Nussbacher wrote:
> The entire whois debacle will only get resolved when some hackers
> attack www.eugd
Hank Nussbacher wrote:
> The entire whois debacle will only get resolved when some hackers attack
> www.eugdpr.org, ec.europa.eu and some other key .eu sites. When the
> response they get will be "sorry, we can't determine who is attacking
> you since that contravenes GDPR", will the EU light
03, 2018 10:00 PM
To: Rodney Joffe
Cc: NANOG
Subject: Re: ICANN GDPR lawsuit
> On Jun 3, 2018, at 14:17 , Rodney Joffe wrote:
>
>
>
>> On Jun 1, 2018, at 10:21 AM, niels=na...@bakker.net wrote:
>>
>> * l...@satchell.net (Stephen Satchell) [Fri 01 Jun 2018,
[mailto:nanog-boun...@nanog.org] On Behalf Of Rodney Joffe
Sent: Sunday, June 03, 2018 3:17 PM
To: NANOG
Subject: Re: ICANN GDPR lawsuit
> On Jun 1, 2018, at 10:21 AM, niels=na...@bakker.net wrote:
>
> * l...@satchell.net (Stephen Satchell) [Fri 01 Jun 2018, 14:51 CEST]:
>> How
>
>
>
> Yeah, what Niels is really leaving out here is the open question of
> whether or not GDPR will eventually lead to the destruction of Peering DB.
>
> Owen
>
Of course it will not. We just need to accept that only roles not people
are published. Those people will change job anyway and
> On Jun 3, 2018, at 14:17 , Rodney Joffe wrote:
>
>
>
>> On Jun 1, 2018, at 10:21 AM, niels=na...@bakker.net wrote:
>>
>> * l...@satchell.net (Stephen Satchell) [Fri 01 Jun 2018, 14:51 CEST]:
>>> How does your shop, Niels, go about making contact with an operator that is
>>> hijacking
> On Jun 1, 2018, at 10:21 AM, niels=na...@bakker.net wrote:
>
> * l...@satchell.net (Stephen Satchell) [Fri 01 Jun 2018, 14:51 CEST]:
>> How does your shop, Niels, go about making contact with an operator that is
>> hijacking one of your netblocks, or is doing something weird with routing
On 06/01/2018 09:37 AM, McBride, Mack wrote:
> For routing whois information there aren't going to be many individuals and
> it would seem
> that the corporations who employee individuals should be the ones protecting
> those individuals
> work emails by providing a generic contact email
:24 AM
To: l...@satchell.net
Cc: nanog@nanog.org
Subject: Re: ICANN GDPR lawsuit
On Fri, Jun 1, 2018 at 8:47 AM, Stephen Satchell wrote:
> In other words, how do you do your job in light of the GDPR
> restrictions on accessing contact information for other network operators?
>
> Please
On Fri, Jun 1, 2018 at 8:47 AM, Stephen Satchell wrote:
> In other words, how do you do your job in light of the GDPR restrictions
> on accessing contact information for other network operators?
>
> Please be specific. A lot of NOC policies and procedures will need to
> be updated.
Publish role
* l...@satchell.net (Stephen Satchell) [Fri 01 Jun 2018, 14:51 CEST]:
How does your shop, Niels, go about making contact with an operator
that is hijacking one of your netblocks, or is doing something weird
with routing that is causing your customers problems, or has broken
BGP?
The same as
On 06/01/2018 08:47 AM, Stephen Satchell wrote:
On 06/01/2018 05:24 AM, niels=na...@bakker.net wrote:
* h...@efes.iucc.ac.il (Hank Nussbacher) [Fri 01 Jun 2018, 06:56 CEST]:
The entire whois debacle will only get resolved when some hackers attack
www.eugdpr.org, ec.europa.eu and some other key
On 06/01/2018 05:24 AM, niels=na...@bakker.net wrote:
> * h...@efes.iucc.ac.il (Hank Nussbacher) [Fri 01 Jun 2018, 06:56 CEST]:
>> The entire whois debacle will only get resolved when some hackers attack
>> www.eugdpr.org, ec.europa.eu and some other key .eu sites. When the
>> response they get
On 01/06/2018 15:24, niels=na...@bakker.net wrote:
> * h...@efes.iucc.ac.il (Hank Nussbacher) [Fri 01 Jun 2018, 06:56 CEST]:
>> The entire whois debacle will only get resolved when some hackers attack
>> www.eugdpr.org, ec.europa.eu and some other key .eu sites. When the
>> response they get will
* h...@efes.iucc.ac.il (Hank Nussbacher) [Fri 01 Jun 2018, 06:56 CEST]:
The entire whois debacle will only get resolved when some hackers attack
www.eugdpr.org, ec.europa.eu and some other key .eu sites. When the
response they get will be "sorry, we can't determine who is attacking
you since
On 31/05/2018 21:44, John Peach wrote:
> On 05/31/2018 02:37 PM, Dan Hollis wrote:
>> On Thu, 31 May 2018, b...@theworld.com wrote:
>>> FWIW a German court has just ruled against ICANN's injunction and in
>>> favor of Tucows/EPAG.
>>> https://www.icann.org/news/announcement-4-2018-05-30-en
>>
>>
whoisnt
On Thu, May 31, 2018 at 2:37 PM, Dan Hollis wrote:
> On Thu, 31 May 2018, b...@theworld.com wrote:
>>
>> FWIW a German court has just ruled against ICANN's injunction and in
>> favor of Tucows/EPAG.
>> https://www.icann.org/news/announcement-4-2018-05-30-en
>
>
> Welcome to
On 05/31/2018 02:37 PM, Dan Hollis wrote:
On Thu, 31 May 2018, b...@theworld.com wrote:
FWIW a German court has just ruled against ICANN's injunction and in
favor of Tucows/EPAG.
https://www.icann.org/news/announcement-4-2018-05-30-en
Welcome to contact-free whois?
-Dan
Already been
On Thu, 31 May 2018, b...@theworld.com wrote:
FWIW a German court has just ruled against ICANN's injunction and in
favor of Tucows/EPAG.
https://www.icann.org/news/announcement-4-2018-05-30-en
Welcome to contact-free whois?
-Dan
FWIW a German court has just ruled against ICANN's injunction and in
favor of Tucows/EPAG.
https://www.icann.org/news/announcement-4-2018-05-30-en
--
-Barry Shein
Software Tool & Die| b...@theworld.com | http://www.TheWorld.com
Purveyors to the Trade | Voice: +1
In article you write:
>http://www.circleid.com/posts/20180527_icann_files_legal_action_against_domain_registrar_whois_data/
Elliot said that if he had to choose between fighting ICANN and
fighting governments, he'd fight ICANN. I can't blame him.
39 matches
Mail list logo
