[arin-ppml] Lower End User IPv4 threshold to /24

[Kevin Kargel]

Pretty good Leo.  Can we build in the proviso to allow the user to keep the
space if ARIN issues a larger block that aggregates the existing space?  For
example I would hate to see someone because of policy wording have to return
1.0.0.0/24 within 12 months after ARIN gave them 1.0.0.0/23 ..

Kevin




From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
Behalf Of Owen DeLong
Sent: Monday, August 03, 2009 2:42 PM
To: policy at arin.net; ARIN PPML
Subject: [arin-ppml] Lower End User IPv4 threshold to /24

TEMPLATE: ARIN-POLICY-PROPOSAL-TEMPLATE-2.0

1.      Policy Proposal Name: /24 End User Minimum Allocation Unit
2.      Proposal Originator
        a.      name: Owen DeLong
        b.      email: owen at delong.com
        c.      telephone: 408-890-7992
        d.      organization: Hurricane Electric
3.      Proposal Version: 0.9
4.      Date: 8/3/09
5.      Proposal type: new
6.      Policy term: permanent
7.      Policy statement:

	Replace section 4.3.2.2 of the NRPM with the following:

	4.3.2.2 Multihomed Connection

	
For end-users who demonstrate an intent to announce the requested space in a
	
multihomed fashion to two or more distinct providers, the minimum block of I
P
	
address space assigned is a /24. If assignments smaller than a /24 are neede
d,
	
multihomed end-users should contact their upstream providers. When prefixes 
are
	
assigned which are longer than /20, they will be from a block reserved for t
hat
	purpose so long as that is feasible. End-users may not receive a
block smaller
	than /22 under this policy if they already have resources from ARIN,
except as
	specified in section 4.3.6.2.

	Renumber the existing paragraph under the 4.3.6 to 

	4.3.6.1 Utilization requirements for additional Assignment

	Add the following paragraph 4.3.6.2

	4.3.6.2	Replacement assignments for small multi-homers

	Any end-user that possesses an assignment smaller than /22 under any
part of
	section 4.3 shall not be able to get an additional assignment unless
they agree
	to return all existing assignments within 12 months of receiving a
new assignment.
	The new assignment shall be sized to accommodate their existing
utilization in
	addition to their justified additional growth space under section
4.3.6.1.
	The common cases for this are expected to be a /24 returned after
receipt of a /23,
	or a /23 returned after receipt of a /22.

8.      Rationale:

	
This policy attempts to incorporate the recent and historical discussions of
	
policy for multi-home users on PPML. The intent is to provide as fair a proc
ess
	
as possible for multi-homed organizations down to the smallest feasible size
	
while still preserving some control over growth in the routing table.

	
It has been repeatedly noted that /24 multi-homers exist today with PA space
	
and still occupy a routing table slot, so, it is unlikely that moving this
	boundary to /24 would significantly impact the routing table.

	
By requiring smaller assignments to renumber and return, rather than add mor
e
	
small blocks to their assignments, this policy seeks to further reduce the
	
chances of unnecessary growth in the routing table and encourage good aggreg
ation
	where possible.

9.      Timetable for implementation: Immediate

END OF TEMPLATE

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3224 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20090803/df9090e1/attachment.bin>