Frank Bulk (iname.com)
frnkblk at iname.com
Mon May 27 02:05:04 UTC 2013
Here's a few more resources:
From: shawn wilson [mailto:ag4ve.us at gmail.com]
Sent: Saturday, May 25, 2013 11:27 PM
To: info at cymru.com
Cc: North American Network Operators Group
Subject: Re: Geoip lookup
If anyone is interrested, here's a little Perl CLI util to lookup what
countries registered networks within a block. There's no documentation
yet, it's a .pl where it should probably be a command with a makefile
installer, and Net::CIDR overlaps Net::IP. At any rate, hopefully it
is useful to someone.
PS - do note the -mask option (where you can define say, a 20 or 21 or
22) so that you're not sitting there banging on their DNS looking up
tons of /32s for blocks CYMRU doesn't have any information on.
On Sat, May 25, 2013 at 6:44 AM, John Curran <jcurran at arin.net> wrote:
> On May 24, 2013, at 10:47 AM, David Conrad <drc at virtualized.org> wrote:
>> I replied privately to Owen, but might as well share:
>> On May 23, 2013, at 11:57 PM, Owen DeLong <owen at delong.com> wrote:
>>>>>> True, according to (at least some of) the RIRs they reside in regions...
>>>>> Really? Which ones? I thought they were only issued to organizations that had operations in regions.
>>> That was exactly my point, Bill... If you have operations in RIPE and ARIN regions, it is entirely possible for you to obtain addresses from RIPE or ARIN and use them in both locations, or, obtain addresses from both RIPE and ARIN and use them in their respective regions, or mix and match in just about any imaginable way. Thus, IP addresses don't reside in regions, either. They are merely issued somewhat regionally.
>> A direct quote from a recent interaction with ARIN (this was requested by ARIN staff as part of the back and forth for requesting address space):
>> "Please reply and verify that you will be using the requested number resources within the ARIN region and announcing all routing prefixes of the requested space from within the ARIN region. In accordance with section 2.2 of the NRPM, ARIN issues number resources only for use within its region. ARIN is therefore only able to provide for your in-region numbering needs."
>> I believe AfriNIC and LACNIC have similar limitations on use but am too lazy to look it up (and I don't really care all that much: just thought it was amusing).
> Indeed. This was covered in more detail in the Policy Experience Report
> given at the ARIN 31, in which it was noted that we are seeing an increase
> in requests for IPv4 address space from parties who have infrastructure in
> the region, but for customers entirely from outside the region. This has
> resulted in a significant change in the issuance rate and therefore any
> estimates for regional free pool depletion. ARIN has sought guidance from
> the community regarding what constitutes appropriate in-region use, should
> this be based on infrastructure or served customers, and whether incidental
> use outside the region is appropriate. (This topic was also on this list on
> 26 April 2012 - see attached email from that thread) Policy proposals in
> this area to bring further clarity in address management are encouraged.
> John Curran
> President and CEO
> Begin forwarded message:
>> From: John Curran <jcurran at arin.net>
>> Subject: Re: "It's the end of the world as we know it" -- REM
>> Date: April 26, 2013 10:43:51 AM EDT
>> To: "nanog at nanog.org Group" <nanog at nanog.org>
>> On Apr 26, 2013, at 10:23 AM, Chris Grundemann <cgrundemann at gmail.com> wrote:
>>> One interesting twist in all of this is that several of these new
>>> "slow-start" players in the ARIN region seem to be servicing customers
>>> outside of the region with equipment and services hosted here inside
>>> the ARIN region (see slide 12 on the ARIN 31 "Policy Implementation
>>> and Experience Report"
>> NANOG Folks -
>> Please read this slide deck, section noted by Chris. It explains the
>> "situation"... (I would not call the sudden acceleration in IP address
>> issuance a problem, per se, as that is an judgement for the community
>> either way.)
>> John Curran
>> President and CEO
More information about the NANOG