On Aug 13, 2010, at 11:32 PM, Randy Bush wrote:
If the allocation and reassignment of address space has no policy associated with it, then there's no doubt that most of the registry functions can be automated, and there's no need for the associated policy development process, public policy meetings, travel, conference calls. Quite a bit of savings available there, but the community first has to decide on permanent policy (or lack thereof :-) for that automated world before we can reap the savings.
when the 'community' is defined as those policy wannabes who do the flying, take the cruise junkets, ... this is a self-perpetuating steaming load that is not gonna change.
In theory, it's quite realistic to see it changing for IPv6 over time, since there is remarkable abundance even just the existing allocations made to date; we've no doubt already issues more IPv6 space that the entire Internet will need, and the only reason that an organization gets space from an RIR is the implication that such space will be routable. If ISPs were to hypothetically charge for use of a non-provider issues prefix and figure out a way to settle up for the routing impact, then there is already plenty of IPv6 space issued today, and one could seek an allocation from nearly anyone and know the cost for it be useable. Getting started via IPv6 would probably be easier than IPv4, but once running if shouldn't be too hard to make work for both. You can then completely eliminate routing driven constraints from the system, and get very close to vending machine with a pull handle for getting more addresses...
one start would be for arin to have the guts not to pay travel expenses of non-employees/contractors.
ARIN Suggestion process: <https://www.arin.net/participate/acsp/index.html> If you submit it, I will bring it to the Board for consideration. In fairness, I will tell you that I'll also recommend to the that we continue to pay for the travel for the Advisory Council, unless and until there is no need for a policy development process. /John