[address-policy-wg] RIPE DB: disclosure of commertial information

On Thu, May 12, 2005 at 02:55:10PM +0200, Elmar K. Bins wrote:
> Well, if you have like, say, dialup customers, you may easily set aside
> a dialup-pool, enter this - registered to yourself (the ISP) - into the
> RIPE DB, and everything's fine.
> 
> (Dynamic-IP) Dialup access has always been done with pools; the documentation
> necessity begins with statically-assigned adresses or networks.

That's more-or-less what we do, the large part of our customers are put in
larger assignments which we hold full responsibillity for.

Even on the business side although we note the name or a short form of it,
we maintain responsible for the block and what they do with it, so unless
the customer asks for it and has good reasons, we refer to our own
admin-c and tech-c role objects. It's part of our service and I'm pretty
interested in any misbehaviour of them, I don't want the customer to use
it's own role to advertise his own address as abuse contact.

Further, I wonder how many people are actually using the ripe-db for these
kind of purposes (stealing customers as you call it), as there are other
ways to find out like traceroute, domain registrations vs (secondary)
nameservers or even a lookup of the in-addr.arpa zones.

The risk is minimal as I see it and it's the rule. So as other people
pointed out, if we everybody sticks to the procedure, we are all equal.

MarcoH
(on a sidenode, I'm referring to PA space here)