* a RESTful Web Service (RWS) * a NICNAME/WHOIS port 43 service * a user-friendly [...]]]> ARIN is pleased to announce that it will deploy its Whois-RWS service on
17 July 2010. We have corrected the issues that impacted the first
release and are now able to bring you the following services that
provide the general public with access to ARIN’s registration data:

* a RESTful Web Service (RWS)
* a NICNAME/WHOIS port 43 service
* a user-friendly web site (http://whois.arin.net)

When using the Whois-RWS you will notice some differences in behavior
for certain queries and corresponding result sets on the NICNAME/WHOIS
port 43 service. The detailed documentation on these differences has
been updated and is now available at:

https://www.arin.net/resources/whoisrws/whois_diff.html

ARIN?s Directory Service for registration data has used the
NICNAME/WHOIS protocol since its inception. The limitations of the
NICNAME/WHOIS protocol are well known and documented in RFC3912.
Whois-RWS was created as an alternative to the ARIN Whois and will
provide much richer functionality and capability to the community.

ARIN is pleased to announce that it plans to deploy an improved Whois service called Whois-RWS on 26 June 2010. Included in the deployment are the following services that provide the general public with access to ARIN’s registration data.

* a RESTful Web Service (RWS) * a NICNAME/WHOIS port 43 service * a user-friendly web site (http://whois.arin.net)

A demo of this service [...]]]> From ARIN:

ARIN is pleased to announce that it plans to deploy an improved Whois
service called Whois-RWS on 26 June 2010. Included in the deployment are
the following services that provide the general public with access to
ARIN’s registration data.

When using Whois-RWS you will notice some differences in behavior for
certain queries and corresponding result sets on the NICNAME/WHOIS port
43 service. ARIN will make a separate announcement on 11 June when it
publishes detailed documentation on these differences along with the
demonstration service update.

//

“We will run out of IPv4 address space and the real difficult part is that there is no flag date. It’s a real moving date [...]]]> At the ARIN XXV policy meetings held here this week, ARIN CIO Richard Jimmerson explained how the organization expects to know when the final IPv4 address is gone.

“We will run out of IPv4 address space and the real difficult part is that there is no flag date. It’s a real moving date based on demand and the amount of address space we can reclaim from organizations,” Jimmerson told InternetNews.com. “If things continue they way they have, ARIN will for the very first time, sometime between the middle and end of next year, receive a request for IPv4 address space that is justified and meets the policy. However, ARIN won’t have the address space. So we’ll have to say no for the very first time.”

Many ISPs, bandwidth providers, and other groups out there think we can never run out of IPV4 space.  There are many organizations who have no plans of moving to IPv6, think NAT is evil, and generally don’t care.  I wonder what will happen when ARIN denies their application or tells them it will be some outrageous amount.  I believe IPV4 space will be like radio spectrum, at least until people convert to IPV6.  There will be large auctions bringing ARIN big amounts of money. IPV4 space will become a huge commodity that is sold by those who have excess.  Groups like MIT & HP who have /8 blocks will capitalize on the market.

http://www.enterprisenetworkingplanet.com/news/article.php/3878391

With the distribution of two /8 blocks to APNIC, the Number Resource Organization (NRO) today announced that less than ten percent of available IPv4 addresses remain unallocated.

The router at [...]]]> As IPV4 space becomes more and more scarce small operators are faced how to make their IP space stretch as far as they can.  One way to do this in a routed WISP environment is to do NAT translation on a per pop basis.  I have put together a Visio diagram to illustrate this.

The router at each POP in this simplified diagram is doing the nat translation for the customers behind the single public IP address.  If you have any customers who truly need a non-shared IP you can simply route an appropriate netblock to that POP and assign public IPs out that way.  You method of assignment may vary (Static, PPPoE, DHCP, etc.). Most customers will not need a true public IP address. The XBOX Live, Playstation live, and people who want to run servers will be the main ones.

The above example is a nice compromise between assigning public IPs to everyone and being able to track customers.  If you entire network is behind a single IP address you are more prone to getting blacklisted, and having issues tracking customers from the outside.