IP Address News

Providing you with a single site about IP Addresses News and Usage

IP Address News - Providing you with a single site about IP Addresses News and Usage

ARIN 34 & Nanog PPC Preview

arin34_logoNext week is the ARIN meeting in Baltimore.  There also will be a public policy consultation at Nanog 62 on Tuesday morning.  Here is my look ahead at the some of the nine policies being discussed at the meetings.  There is only one recommended draft that will be discussed, but lots of other draft policies are on the agenda and we will be looking for input on how to proceed.

2014-9 Resolve RSA & 8.2 Transfer Conflict

Policy Summary: This recommended draft policy removes two words (“aggregate” and “reclaim”) from the mergers and acquisitions section of the transfer policy.

Discussion: The current registration services agreement, the contract that governs the relationship between ARIN and resource holders, has language which prevents ARIN from reclaiming address space when it is underutilized.  However, the M&A transfer policy has language which prevents an organization from transferring their resource into their new name when they are underutilized.  Because of this, we end up with orphaned records which don’t really match the new organization who is the new resource holder.  Initially the draft policy had language in it which would have solved this problem, but this was removed because a number of critics of the policy believed that needs testing still should be performed and enforced for M&A transfers.

At this point, when IPv4 addresses are assets which can be transferred by sale to another organization, the limits in the M&A policy don’t make sense to me and only seem to create an environment where number resource records are not updated because current utilization rates may not be met across the new or combined organization.  Still this seems like a symbolic change that people have supported and will probably achieve consensus at the meetings.

2014-14 Remove Needs Test on Small Transfers

2014-20 Slow Start Transfer & Simplified Needs

Both of these policies are suggesting changes in the transfer policies due to the imminent run-out of the IPv4 free pool and the changing requirements of the transfer market.

2014-14 Policy Summary: This draft policy removes needs testing from blocks which are smaller than /16 and permits an organization to have one needs-free transfer per year.

2014-20 Policy Summary: This draft is a complex change to both the current IPv4 policy and its related transfer elements.  It seeks to significantly change how we look at the various aspects of obtaining addresses from ARIN or on the transfer market.

Discussion: I believe that changes are necessary for the transfer policy and the existing IPv4 policy as the free-pool is depleted.  How we address these changes is critical to the success of ARIN and its mission, but also the success of the transition to IPv6.  These two policies take different approaches toward the changes which are necessary after IPv4 depletion in the ARIN region.  I suspect there will be a lot of discussion about these two policies and the need to update the existing policy set in a post IPv4 depletion world.

2014-16 Section 4.10 Austerity Policy Update

Policy Summary: This draft policy creates a new subsection of the policy manual to provide an austerity pool of IPv4 resources for organizations which do not currently have any resources directly from ARIN.

I drafted this policy after a number of discussions at the last ARIN meeting in Chicago where it was noted that the current IPv4 policy has limitations inherent in it for new entrants.   This draft was modeled on the successful implementation of similar policies in the APNIC and RIPE regions.

Discussion: Most of the discussion about this draft has been about how to divide up the current /10 and the IANA reclaimed blocks between the existing transition technology pool and the new pool created by this policy.  Hopefully, it will become clear during our discussions if the community supports creating an austerity pool and how they wish to divide up the currently reserved /10 and the IANA reclaimed blocks for new organizations which do not currently have address blocks from ARIN.

2014-17 Change utilization requirements

Policy Summary: This draft policy changes how IPv4 utilization is calculated to deal with limitations on subsequent allocation for some organizations.

Issues:  The draft policy currently changes the utilization definition for all organizations.  The side effect of this is that large organizations could obtain large new blocks just from the implementation of this policy.  A few options to change the draft policy text are being discussed to deal with this issue.

Discussion: This policy fixes a known issue for smaller organizations which has occurred due to the smaller 3-month allocation model that is currently in use for subsequent allocations.  While this policy lowers the utilization bar and has the perceived negative effect noted above for large organizations, this policy as written now could be beneficial for the transfer market as it would make it easier for organizations to meet the utilization requirements for future transfers.

 

Routing table growth causes some hiccups

News reports have been circulating over the past couple of days that various service providers have hit the 512k route mark in their BGP tables on their routers and switches causing outages and other problems.  A number of hardware platforms, notably older Cisco hardware, have default limits in their configurations which limit route tables sizes to 512k routes.  When these limits are breached the older hardware slows down or otherwise stop functioning as expected. Cisco issued a bulletin in May to providers with workaround procedures for some platforms.

The growth in the global route table has been fairly stable over the past couple of years and this is growth has been expected for a long time and yet still Internet service providers were not prepared in time for this event.

Internet Touches Half Million Routes: Outages Possible Next Week

Internet routers hitting 512K limit, some become unreliable

The end of the internet predicted, news at 11

Echoes of Y2K: Engineers Buzz That Internet Is Outgrowing Its Gear

The internet broke yesterday

BGP Analysis Reports

 

LacNIC exhausts IPv4 free pool

LacNIC announced today that they have reached the equivalent of a /10 remaining in their free pool and have stopped regular allocations of IPv4 addresses to organizations in their region.  Organizations will now only receive a single /24 to /22 of address space every 6 months until the pool reaches a /11.  After the pool reaches a /11 only new members to LacNIC may receive a single /24 to /22.

No more IPv4 addresses in Latin America and the Caribbean

NANOG 61 PPC Recommended Draft Policy review

NANOG 61 wrapped up yesterday in Bellevue, Washington.  It is always different attending a conference in your home town; this was also the largest NANOG ever.  On Tuesday morning, ARIN held a public policy consultation.  Since I didn’t get a preview out before the meeting, here is my review of the discussion around the recommended draft policies.

2013-8 Subsequent Allocations for New Multiple Discrete Networks

Policy Summary: This recommended draft policy fixes an issue with the current policy which was highlighted by ARIN staff at an meeting last year.  This policy describes how ARIN should allocate blocks for new sites for organizations which use the multiple discrete networks policy.

Discussion: Previous issues in the policy draft centered around how ARIN should test if/when a site should receive an allocation.  The new text uses the phrase “has shown evidence of deployment.”  There have been no negative comments about this new text and I suspect the AC will move this policy toward last call at their next meeting.

2014-5 Remove 7.2 Lame Delegations

Policy Summary: This recommended draft policy removes section 7.2 which was formerly used when ARIN was conducting DNS lame delegation testing.

Review: This policy has not been in use for some time and the current policy carries some risk to operational DNS should it be implemented as currently written. Furthermore, the operator community has not asked ARIN to reinstate this monitoring service.  I believe consensus has been achieved on this policy and it will move forward to last call.

2014-12 Anti-hijack Policy

Policy Summary: This recommended draft policy adds language to the experimental allocation policy to restrict overlapping assignments.  This policy was created after multiple RIRs allowed an IPv6 research project to proceed by allowing an organization to obtain letters of agency permitting them to use overlapping address blocks.  ARIN has acknowledged that this action was a mistake and will not grant similar permission in the future.

Review:  This policy has been widely supported by the Internet operator community since its introduction.  Some editorial changes were made to the policy just prior to the meeting and the AC must discuss those changes to make sure they do not change the intent of the policy when it was previously moved to its current recommended state.  It seems likely that this policy will also be advanced to last call.

2014-13 Reduce All Minimum Allocation/Assignment Units to /24

Policy Summary: This recommended draft policy changes changes the minimum IPv4 allocation size to a /24 for both ISPs and end users.  This policy was rushed through the policy development process after a few organizations reported that their upstreams would not assign them /24 address blocks and they also could not qualify for an address block under current IPv4 policies.  This policy also fixes issues that ARIN staff highlighted with the shortly upcoming exhaustion of ARIN’s IPv4 free pool.

Review:  While the textual changes of this policy ended up being more complicated that many hoped, I believe the issue which triggered this policy draft will be resolved by this policy and that the additional simplification will also be beneficial.  The staff review raised an issue about the maximum initial allocation size for new entrants.  Current ARIN practice relies on a set of examples which are being removed by this update.  Some discussion was considered about adding an initial maximum, but no agreement could be made on those changes.  In the end, I suspect ARIN will continue with their current practice for block sizing, but an actual maximum would not be enumerated in policy.  I believe this policy will be advanced to last call by the advisory council shortly.

LacNIC reaches /9, triggering IANA reclaimed block distribution

On May 20th, LacNIC announced that it has reached the equivalent of a /9 remaining in its IPv4 free pool which has triggered the IANA to invoke its reclaimed IPv4 address space policy.  The IANA received a number of blocks from various RIRs under the reclaimed policy over the years.  Under the global policy for reclaimed blocks, each RIR is allocated 1/5th of the total pool.  Now that the first initial allocation has been made the IANA reclaimed free pool will be reevaluated every six months and appropriate distributions will then be made to each RIR.

LacNIC received the block (45.160.0.0/11) and will continue with its current allocation policies with some additional scrutiny until the free pool reaches a equivalent of a /10, then only blocks between /22 and /24 will be allocated.

APNIC has subsequently announced that they have received a /11 equivalent from the IANA as part of the reclaimed distribution.  Under APNIC policies, each APNIC member is eligible to receive up to a /22 of additional IPv4 address space from this specific block.

RIPE has sent an email to its member list which notes it has received 45.128.0.0/11 from IANA and has added this block to its free pool.  Under the current RIPE policy each LIR can receive a single /22 block.

ARIN has not yet announced that they have received an additional block, but the IANA registry notes they have received 45.32.0.0/11.  As ARIN does not have a specific policy for this block so it should be added to the available free pool.  ARIN’s current pool lists 0.86 /8s equivalent remaining on May 21st.

I have introduced a policy proposal (ARIN-2014-16) to the ARIN region which would designated IANA reclaimed blocks to be allocated under an austerity policy, but this policy is currently in only at the draft stage of discussion on the public policy mailing list.

ARIN & LacNIC close to the bottom of their IPv4 pools

ARIN announced this morning that they had reached the equivalent of a single /8 in the IPv4 free pool. (The ARIN countdown timer does not include reserved space for IPv4 blocks which are allocated under special policies.) With this level each request will be held under more review and will be processed in a first-in first-out basis. It could be only a matter of days or even weeks before the remaining free pool is exhausted depending on the outstanding demand already in ARIN’s queue especially if the request rate increases as organizations come back quickly for their last blocks from this pool.

Available ARIN IPv4 inventory

LacNIC is currently just above a single /9 equivalent in their inventory which includes a reserved /10 for an austerity policy. The Latin American region’s allocation of address space has really accelerated in the first 4 months of 2014 with the end of their pool drawing to a close. The LacNIC home page is currently predicting a runout by May 30th, 2014.

LacNIC’s IPv4 exhaustion policy

Geoff Huston’s IPv4 exhaustion prediction page