[120109] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: Arrogant RBL list maintainers

daemon@ATHENA.MIT.EDU (Frank Bulk)
Wed Dec 9 22:09:14 2009

From: "Frank Bulk" <frnkblk@iname.com>
To: "'Michael Holstein'" <michael.holstein@csuohio.edu>
In-Reply-To: <4B20141D.9090906@csuohio.edu>
Date: Wed, 9 Dec 2009 21:08:07 -0600
Cc: nanog@nanog.org
Reply-To: frnkblk@iname.com
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Michael:

I've seen their form, too.  I think you're reading too much into their
policies/requests.

Does it matter if they label your non e-mail server IPs as dynamic space,
and therefore put it on their DUL?  

Frank

-----Original Message-----
From: Michael Holstein [mailto:michael.holstein@csuohio.edu] 
Sent: Wednesday, December 09, 2009 3:18 PM
To: Ken Chase
Cc: nanog@nanog.org
Subject: Re: Arrogant RBL list maintainers


> To be clear: because the legitimate mailserver with a proper non-generic
> reverse was in a block with other generic reverses, they blacklisted you?
>   

Their initial email said :

[snip]
Trend Micro Notification: 137.148.0.0/16 added to DUL
[snip]

and then went on to say :

[snip]
To work with us, please generate the following three lists:

 
1) TOTAL ALLOCATED SPACE - in CIDR format
     Please include all information for the space you announce. 
     The total of Static and Dynamic space must equal the 
     Total Allocated Space.
2) DYNAMIC SPACE LIST - in CIDR format
3) STATIC SPACE LIST - in CIDR Format
[snip]


Which was, of course, impossible .. since trunking a VLAN across the
core just to have all the printers in the same /22 would be silly.

After some arguing back-and-forth .. they (Trend) said :

[snip]

Also we don't see the IP address as static as we see the generic naming
convention of 
*csuohio.edu* as dynamic and the WHOIS information doesn't indicate that the
space is static.
[snip]

Seriously .. we're a college campus, not a colo. Org-Abuse roles is defined
(and valid) and real people read the RFC2142 required addresses. What more
do these people want?

(Note: they did eventually say "okay, we see the MXs as static so those
aren't listed" .. but not without some discussion).

Cheers,

Michael Holstein
Cleveland State University



home help back first fref pref prev next nref lref last post