Need some opinions on what data to list

[William Leibzon]

On Tue, 14 Feb 2006, Kris Deugau wrote:

> I work for a growing ISP.  We're sloooowwwwwwly getting our IP space 
> assignments organized and tracked;  we have had a pretty much up-to-date 
> database for our internal use for a while now, and I've got a partial export 
> to a local rWHOIS server that's been running without apparent issues for some 
> time.
>
> However, we'd like to make this a fully-live rWHOIS server, and we need to 
> know what netblocks we should make public, and what to keep hidden in some 
> way.
>
> Currently, the export process I have running pushes out all customer 
> netblocks (whether real or just a set of contiguous IPs aligned along 
> netblock divisions from a PPP pool - business and residential are separate 
> pools) down to /30.  According to any documentation I've seen for SWIP, the 
> smallest netblock that should usually be listed is /29. Does this still apply 
> for rWHOIS?

Yes. The policy just says that /29 is smallest ip blocks that ISPs need 
to report and that reporting choices are SWIP and rwhois.

> (I haven't seen any indication of what size netblocks should or 
> should not be listed anywhere.)  We've got the better part of an aggregate 
> /21 used by /30 netblocks.

I don't think people will complain if you report smaller then /29.
But you don't have to if its too much extra work.

> Secondly, how do you decide what customer data to expose?

You're required to report customer name and address (except in case of
residential customers where you do not have to report and can substitute
"private residence - customer xyz" if customer asked you not to; this is
similar to not having your phone number listed in white pages).

There should also be at least one contact for person/role with working 
email/phone visible. Such contact can be your own NOC contact or can be 
customer contact or both. There can be multiple contacts, for example
many report separate noc and abuse.

> For some 
> assignments, the customer is actively using a medium-large chunk of IP space, 
> and they have their own IT services and should be listed as the tech and 
> abuse contacts for any bad things apparently originating from their network.

In that case reporting how to contact their IT services department seems 
like a must.

BTW - It would also be nice if you report date of when the data (i.e. 
customer info & contact info) was last changed as well as date when
your database as whole was last updated.

> -kgd
> _______________________________________________
> Rwhois mailing list
> Rwhois at rwhois.net
> https://lists.verisignlabs.com/mailman/listinfo/rwhois
>