[ppml] A proposal to modify proposal 2003-9 (WHOIS and INADDR access)

[william at elan.net]

On Tue, 10 Jun 2003, John M. Brown wrote:

> because that URL does not provide complete data and
> is only for a specific project, per richardj (6-6-03).
> 
> research the allocated space as listed at 
> http://www.iana.org/assignments/ipv4-address-space
> 
> and you will find the ftp site is missing a good chuck
> of space.

Fine, lets get ARIN to listen and provide the data for all other /8 blocks!

Still the question is do we need a policy for this? If we do should it 
actually require authentication similar to bulk whois to get the data or 
is current system of getting it by ftp enough?

In my opinion adding in-addr to bulk-whois proposal is both not approriate
as whois data is a lot more complex and has rather specific privacy issues,
its unnecessory and it sounds bad as far as you wrote it (i.e. what you 
proposed - "arin whois inaddr aup"). 

First I think we need to ask ARIN if they are willing to get all the 
inaddr data out on their ftp site on their own based on current polices 
and procedures (they do after all provide entire ASN list including all
those ASNs they inherited from Internic, so why is it so different for 
inaddr?). If they do not want to do it, then propose a simple policy:
"ARIN will provide public access to complete INADDR data for all ip 
blocks in its database for public download by ftp"

> > -----Original Message-----
> > From: owner-ppml at arin.net [mailto:owner-ppml at arin.net] On 
> > Behalf Of william at elan.net
> > Sent: Monday, June 09, 2003 11:44 PM
> > To: John M. Brown
> > Cc: ppml at arin.net
> > Subject: Re: [ppml] A proposal to modify proposal 2003-9 
> > (WHOIS and INADDR access)
> > 
> > 
> > Why do you need policy for providing in-addr data as bulk? I 
> > think ARIN 
> > already provides this all publicly as it, see 
> > ftp://ftp.arin.net/pub/zones
> > 
> > Do you need something more then 
> > that?
> > 
> > On Mon, 9 Jun 2003, John M. Brown wrote:
> > 
> > > 3. A policy for bulk WHOIS and or ARIN INADDR access will 
> > be published 
> > > on
> > >    ARIN website as follows:
> > > 
> > > "Access to the entire WHOIS or ARIN INADDR database or 
> > large portion 
> > > of
> > > it may be obtained by any organization or individual 
> > provided that this 
> > > organization or individual agrees in writing to ARIN WHOIS/INADDR
> > > Acceptable 
> > > Use Policy. WHOIS or ARIN INADDR data provided under bulk 
> > WHOIS access 
> > > will not include any information that is marked as private.
> > > 
> > > Access to WHOIS/INADDR data may be by way of:
> > > 
> > > Individual WHOIS/DNS queries
> > > 
> > > FTP or other type of download
> > > 
> > > Hard media distribution (such as CDROM)
> > > 
> > > 
> > > -----
> > > 
> > > Given that ARIN now has policy  2002-1 Lame In-addr, 
> > providing access 
> > > to the in-addr view that ARIN has would be useful for the internet 
> > > operational and research community, and help reduce lame 
> > issues.  This 
> > > access would allow service providers access to the IN-ADDR tree and 
> > > allow them to self verify what deligations they are listed as 
> > > authoritative for.  It would allow the research community a better 
> > > source of data for research and other activities.
> > > 
> > > 
> > > respectfully,
> > > 
> > > john brown
> >