[arin-ppml] Fraud or not?
Mark Kosters
markk at arin.net
Fri Feb 18 13:09:35 EST 2011
On 2/16/11 4:05 PM, "Owen DeLong" <owen at delong.com> wrote:
>Output, sure. However, the web-based one is much stricter and less
>intelligent about parsing queries and THAT is the primary problem I'm
>having.
>
>Instead of realizing that the old "AS10912" query means the same
>thing to the user as the new arcane syntax "a 10912" (which the
>old version did just fine), the new version neither fails nor works
>consistently (or at least the behavior appears very inconsistent
>until you begin to understand an additional arcane set of rules).
Owen
Legacy whois service has had a very interesting search properties. It
depends on clients if you have a hit or miss depending on the format of
another field or how "smart" the whois client tries to be. The directory
service works consistently if do the "A <as number>" => matches on As
number. The directory service works consistently doing "AS<Number>" if
"AS<Number>" is the handle. Both will come back with hits.
Here is an example for querying an AS number registered as a range
(701-705).
Whois -h whois.arin.net <http://whois.arin.net/> "AS701" works (matches
the handle)
Whois h whois.arin.net <http://whois.arin.net/> "a 701" works matches
the as number
Whois h whois.arin.net <http://whois.arin.net/> "AS702" fails (no handle).
Whois h whois.arin.net <http://whois.arin.net/> "a 702" works matches
on the as number.
ARIN was very careful to replicate most of the functionality in the legacy
whois service including some of the oddities. Differences were
documented and placed on the website at
https://www.arin.net/resources/whoisrws/whois_diff.html.
If you prefer to move away from that, you are welcome to use the RESTful
interface. In this case, the answer would be (using xmllint to create a
nice output):
xmllint --format http://whois.arin.net/rest/asn/<AS NUMBER> .
For example, finding the AS 694 would be:
xmllint --format http://whois.arin.net/rest/asn/693
Feel free to ask additional questions to arin-tech-discuss at arin.net.
Regards,
Mark Kosters
ARIN CTO
>
>The actual result is:
>
> 1. Some command line clients do the translation for you.
> (good for them, but, not universal)
>
> 2. If you query ASnnnnn, then, whether you get a good
> result back or not depends on whether or not ASnnnnn
> is the handle for the resource. If I were to create
> an AS Number record, for example, named AS105,
> but, which was actually AS693, then, I would get
> the following odd mixture:
>
> Query Result
> AS105 Record for AS693
> AS693 Nothing
> a 105 Record for AS105
> a 693 Record for AS693
>
> (Assuming that my client doesn't alter my queries
> unexpectedly).
>
>I shouldn't have to become an expert in whois arcana to survive
>navigating whois for simple everyday queries.
>
>Owen
>
>On Feb 16, 2011, at 10:10 AM, Ted Mittelstaedt wrote:
>
>> So do I - but, I will say that once they finally get their web-based one
>> to work, it should not be too difficult to write a command line Perl
>> script that talks to their web server and outputs like the older
>>command line tool did.
>>
>> Ted
>>
>> On 2/15/2011 11:41 PM, Owen DeLong wrote:
>>> I really wish ARIN would make the command line whois work as well as
>>> it used to instead of focusing all their energy on the (much less
>>>convenient
>>> much higher overhead from the user perspective) web-based one.
>>>
>>> Owen
>>>
>>> On Feb 15, 2011, at 9:03 PM, Scott Leibrand wrote:
>>>
>>>> On Tue, Feb 15, 2011 at 8:48 PM, Ronald F. Guilmette
>>>> <rfg at tristatelogic.com <mailto:rfg at tristatelogic.com>> wrote:
>>>>
>>>>
>>>> www.robtex.com <http://www.robtex.com/> says that AS10912 belongs
>>>> to Internap.
>>>>
>>>> whois.arin.net <http://whois.arin.net/> says that there ain't no
>>>> such AS.
>>>>
>>>> So, should I file a formal report charging Internap with fradulent
>>>>use
>>>> of resources that are not actually assigned to them? Or is it more
>>>> likely that ARIN has simply (and entirely) misplaced the WHOIS
>>>>record
>>>> for AS10912?
>>>>
>>>>
>>>> It looks like it's only the traditional whois tool that is failing.
>>>> The web tool at arin.net <http://arin.net/> reports it as part of
>>>> INTERNAP-BLK, which covers ASNs 10910 - 10913.
>>>>
>>>> http://whois.arin.net/rest/asn/AS10910/pft
>>>>
>>>> I suspect your message will be enough to get ARIN to fix the whois
>>>> port 43 service shortly. :-)
>>>>
>>>> -Scott
>>>> _______________________________________________
>>>> PPML
>>>> You are receiving this message because you are subscribed to
>>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net
>>>> <mailto:ARIN-PPML at arin.net>).
>>>> Unsubscribe or manage your mailing list subscription at:
>>>> http://lists.arin.net/mailman/listinfo/arin-ppml
>>>> Please contact info at arin.net if you experience any issues.
>>>
>>>
>>>
>>> _______________________________________________
>>> PPML
>>> You are receiving this message because you are subscribed to
>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>>> Unsubscribe or manage your mailing list subscription at:
>>> http://lists.arin.net/mailman/listinfo/arin-ppml
>>> Please contact info at arin.net if you experience any issues.
>>
>> _______________________________________________
>> PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net if you experience any issues.
>
>_______________________________________________
>PPML
>You are receiving this message because you are subscribed to
>the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>Unsubscribe or manage your mailing list subscription at:
>http://lists.arin.net/mailman/listinfo/arin-ppml
>Please contact info at arin.net if you experience any issues.
More information about the ARIN-PPML
mailing list