[consult] Call for Consultation: ARIN WHOIS Directory Services

[michael.c.loevner at verizon.com]

Heather -

I support all of your ideas other than:

-Mark 'invalid contact information' on whois records when it has been 
reported and confirmed by ARIN staff as such

and possibly not:

Clearly Mark Early Registration records with ERX as RIPE does - and 
remove the ERX marking when a resource is brought uptodate/under RSA

While I like the intent of the ideas, I have two objections:

1. I think marking invalid contact information can spur hijacking attempts 
on address blocks because it is like holding up a big flashing sign that 
says "vacant".  While I assume ARIN has safeguards to determine the proper 
registrant of the block, do we want to give more people the chance to try 
them out? 

2. Also, does a suggestion like this belong in the policy arena?  I know 
that I have seen policies in the past that have suggested marking invalid 
records, as well as the marking for the ERX - I think that suggestion goes 
beyond functionality into content, which would normally be determined by 
policy.

As far as the result of a query for 12.0.0.0/9 is concerned, it's nice for 
the WHOIS to return the address block the prefix is a part of, but what is 
the expected result when you do a query for a shorter prefix, like 
64.0.0.0/4?  That will give you every ARIN direct allocation and 
assignment over at least a four year period.  If CIDR queries alone must 
match a record exactly to display data, it prevents people from 
accidentally bringing up thousands of records.  I think showing multiple 
records, or the records that a prefix is part of should require a flag, 
like a - or + (although I know those are currently in use for other 
purposes).

-Mike




"Heather Schiller" <heather.schiller at verizonbusiness.com> 
Sent by: consult-bounces at arin.net
07/25/2007 05:09 PM

To
"Member Services" <info at arin.net>
cc
consult at arin.net
Subject
Re: [consult] Call for Consultation: ARIN WHOIS Directory Services







I support the existing suggestions of:
  -support for CIDR queries
  -Following rwhois referrals
  -method to login online and manage your swip records and other arin
   records (would be even better if the login method was with an RSA token
   or the like)
  -Most of Mike Loevner's post - except that searching for 12.0.0.0/9 
should return the  /8 (not nothing at all, because IMO, that would be 
misleading)


And would like to add the following suggestions:

-Whowas info - be able to search historical whois info enter a prefix and 
specify a date range or starting date with a default through the present. 
This would help in researching claims of hijacked blocks.

-Clearly Mark Early Registration records with ERX as RIPE does - and 
remove the ERX marking when a resource is brought uptodate/under RSA

-Mark 'invalid contact information' on whois records when it has been 
reported and confirmed by ARIN staff as such

-Be able to enter a POC handle and get a listing of the resources where 
that POC handle is a contact.

-Add the ability to prepend searches with * for wildcard
  to be able to do wildcard searches on the beginning instead of just the 
tail


--Heather

###############################################
  # Heather Schiller                          #
  # Customer Security & IP Address Management #
  # 800.900.0241                              #
  # security at mci.com                          #
###############################################

On Mon, 23 Jul 2007, Member Services wrote:

> ARIN received a suggestion to allow CIDR style queries to the ARIN WHOIS
> directory service. In addition to this enhancement, ARIN would like to
> explore other possible modifications that the community desires. ARIN
> requests that you provide specific feedback as to what additional WHOIS
> enhancements would benefit you and why they are needed.
>
> Discussion on this list will close at noon ET 27 July. A poll on the
> topic will be conducted beginning Tuesday, 31 July. Only subscribers on
> the consult at arin.net list when the poll opens will be eligible to
> participate. Poll results will be publicly available and will be used by
> the ARIN President to help determine what course of action, if any, ARIN
> should take regarding the subject.
>
> The ARIN Consultation and Suggestion Process documentation is available 
at:
> http://www.arin.net/about_us/corp_docs/acsp.html
>
> We welcome community-wide participation.  Please address any process
> questions to info at arin.net.
>
> Regards,
>
> Member Services
> American Registry for Internet Numbers (ARIN)
>
>
> _______________________________________________
> This message sent to you through the ARIN Consult Mailing List
> (consult at arin.net).
> Manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/consult
>
_______________________________________________
This message sent to you through the ARIN Consult Mailing List
(consult at arin.net).
Manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/consult