[120176] in North American Network Operators' Group
RE: Is there anyone from ASPEWS on this list?
daemon@ATHENA.MIT.EDU (Alex Lanstein)
Fri Dec 11 12:56:31 2009
From: Alex Lanstein <ALanstein@FireEye.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Fri, 11 Dec 2009 09:55:46 -0800
In-Reply-To: <1260520619.4148.99.camel@petrie>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
>>>Also, the fact that Atrivo is *dead* and this
>>>stuff is still listed means that anyone who gets
>>>those blocks from ARIN next are basically screwed
Why would you say Atrivo is dead?
root@localhost --- {~} nslookup www.googleadservices.com 85.255.114.83
Server: 85.255.114.83
Address: 85.255.114.83#53
Name: www.googleadservices.com
Address: 67.210.14.113
root@localhost --- {~}
root@localhost --- {~} nslookup www.googleadservices.com 8.8.4.4
Server: 8.8.4.4
Address: 8.8.4.4#53
Non-authoritative answer:
www.googleadservices.com canonical name =3D adservices.google.com.
adservices.google.com canonical name =3D adservices.l.google.com.
Name: adservices.l.google.com
Address: 74.125.19.96
Regards,
Alex Lanstein
FireEye, Inc.
________________________________________
From: William Pitcock [nenolod@systeminplace.net]
Sent: Friday, December 11, 2009 3:36 AM
To: nanog@nanog.org
Subject: Is there anyone from ASPEWS on this list?
Hi,
ASPEWS is listing 216.83.32.0/20 as being associated with the whole
Atrivo incident of 2008. My memory does not recall 216.83.32.0/20 being
involved, nor the provider that belongs to.
So it'd be cool if I could you know, talk to someone who has involvement
with that, because frankly, I do not see why it is listed as having any
involvement with Atrivo. Also, the fact that Atrivo is *dead* and this
stuff is still listed means that anyone who gets those blocks from ARIN
next are basically screwed. Which kind of sucks.
William
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
