nanog mailing list archives
Re: Important New Requirement for IPv4 Requests [re "impacting revenue"]
From: John Curran <jcurran () istaff org>
Date: Tue, 21 Apr 2009 12:01:26 -0400
On Apr 21, 2009, at 11:19 AM, Roger Marquis wrote:
Rich Kulawiec wrote:If the effort that will go into administering this went instead into reclaiming IPv4 space that's obviously hijacked and/or being used by abusive operations, we'd all benefit.But they can't do that without impacting revenue. In order to continue charging fees that are wholly out of proportion to their cost ARIN must:A) ignore all the unneeded legacy /16 allocations, even those owned byorganizations with fewer than 300 employees (like net.com) who could easily get by with a /24B) do nothing while IPv6 languishes due to the absence of a standard forone-to-many NAT and NAPT for v6 and v4/v6C) periodically raise fees and implement minimal measures like requiring someone to sign a statement of need, so they can at least appear to have been proactive when the impacts of this artificial shortage really beginto impact communicationsBottom line: it's about the money. Money and short-term self- interest,same as is causing havoc in other sectors of the economy. Nothing new here.
Roger - A few nits: A) ARIN's not ignoring unneeded legacy allocations, but can't take action without the Internet community first making some policyon what action should be taken... Please get together with folks
of similar mind either via PPML or via Public Policy meeting at the the Open Policy Bof, and then propose a policy accordingly.B) Technical standards for NAT & NAPT are the IETF's job, not ARIN's.
C) We've routinely lowered fees since inception, not raised them. Thanks, /John John Curran Acting CEO ARIN
Current thread:
- Re: Important New Requirement for IPv4 Requests, (continued)
- Re: Important New Requirement for IPv4 Requests Robert E. Seastrom (Apr 23)
- Re: Important New Requirement for IPv4 Requests Carl Ford (Apr 20)
- Re: Important New Requirement for IPv4 Requests Rich Kulawiec (Apr 21)
- Re: Important New Requirement for IPv4 Requests John Curran (Apr 21)
- Re: Important New Requirement for IPv4 Requests Joel Jaeggli (Apr 21)
- Re: Important New Requirement for IPv4 Requests Ricky Beam (Apr 21)
- Re: Important New Requirement for IPv4 Requests Leo Bicknell (Apr 21)
- Re: Important New Requirement for IPv4 Requests Kevin Graham (Apr 23)
- Re: Important New Requirement for IPv4 Requests Edward Lewis (Apr 22)
- Re: Important New Requirement for IPv4 Requests Roger Marquis (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] John Curran (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Chris Owen (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Roger Marquis (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Owen DeLong (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Fred Baker (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Jo Rhett (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Roger Marquis (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] John Curran (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Shane Ronan (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Kevin Loch (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Brandon Galbraith (Apr 21)
- Re: Important New Requirement for IPv4 Requests [re "impacting revenue"] Shane Ronan (Apr 21)