<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19046">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>
<DIV><FONT size=4 face=Fixedsys>Hi list,</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>I tried to put together a proposal to end needs
requirements for transfers and I used the APNIC policy as a
framework.</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys>The problem is that as the proposal is
structured below, there is a problem with the application of ARIN Resource
Review policies in section 12.</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys>Even if the transfer happens without regard to
need, since the transferred resources would be received by an ARIN account
holder and would be subject to ARIN's policies, then ARIN could feasibly do a
resource review immediately post transfer to effectively retain a needs
requirement.</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>My intent is that ARIN resource reviews continue
to happen for purposes other than need.</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys>So for fraud, for hijackings, for failure to pay
ARIN's bills, I support resource review and recovery.</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys>But not for need.</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys>I was hoping not to have to mess with section 12
of the NRPM. Can somebody suggest a way to modify my draft proposal to effect my
intent in a graceful manner which doesn't require modifications to section
12?</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>Thanks for any help you can offer on this matter
or any other issues related to this draft.</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>Regards,</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>Mike</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>1. Policy Proposal Name: New IPv4 Transfer
policy</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>2. Proposal Originator:</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys> a. Name: Mike
Burns</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys> b. Email:
</FONT><A href="mailto:mike@sum.net"><FONT size=4
face=Fixedsys>mike@sum.net</FONT></A></DIV>
<DIV><FONT size=4 face=Fixedsys> c. Phone:
1-863-494-7692 x105</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys> d. Organization:
Nationwide Computer Systems</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>3. Proposal Version: 1</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>4. Date: May 5th, 2011</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>5. Proposal type: modify</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>6. Policy term: permanent</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>7. Policy statement:</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>Replace Section 8 with </FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>8.ARIN will process and record IPv4 address
transfer requests.</FONT></DIV>
<DIV><BR><FONT size=4 face=Fixedsys>Conditions on the IPv4 address
block:<BR><BR> - The minimum transfer size is a
/24<BR><BR> - The address block must be in the range of
addresses administered<BR>
by ARIN</FONT></DIV>
<DIV><FONT size=4 face=Fixedsys></FONT> </DIV>
<DIV><FONT size=4 face=Fixedsys>Conditions on source of the
transfer:<BR><BR> - The source entity must be the current
rights holder of the<BR> IPv4 address resources,
and not be involved in any dispute as to<BR> the
status of those resources.<BR><BR> - The source entity will be
ineligible to receive any further IPv4<BR> address
allocations or assignments from ARIN for a period of
12<BR> months after the transfer, or until the
exhaustion of ARIN's<BR> IPv4 space, whichever
occurs first.<BR><BR> Conditions on recipient of the
transfer:<BR><BR> - The recipient entity must be a current
ARIN account holder.<BR><BR> - The recipient entity of the
transferred resources will be subject<BR> to
current ARIN policies. In particular, in any subsequent ARIN</FONT></DIV>
<DIV><FONT face=Fixedsys><FONT size=4> IPv4
address allocation request, the recipient will be
required<BR> to account for the efficient
utilization of all IPv4 address<BR> space held,
including all transferred resources.<BR><BR></FONT><FONT size=2>8. Rationale:
</FONT></FONT></DIV>
<DIV><FONT face=Fixedsys>Current ARIN policies relating to the registration of
transfer of<BR>address holdings limit the eligibility of registration of
transfers to<BR>those relating to mergers and acquisitions of entities that
are<BR>administering an operational network, or to those who agree to
</FONT></DIV>
<DIV><FONT face=Fixedsys>sign either an RSA or LRSA with ARIN and subject the
buyer</FONT></DIV>
<DIV><FONT face=Fixedsys>to needs analysis and the seller to a potential ARIN
audit.<BR><BR>It is currently anticipated that the IPv4 unallocated address
pool<BR>will be exhausted within a couple of years at ARIN, and earlier
</FONT></DIV>
<DIV><FONT face=Fixedsys>than that in other regions, and the transition to
IPv6-based service delivery<BR>is likely to take longer than the remaining
period of unallocated<BR>address availability. Accordingly, it is likely that
demand for IPv4<BR>addresses will continue beyond the time of unallocated
address pool<BR>exhaustion, leading to a period of movement of IPv4 address
blocks<BR>between address holders to meet such continuing demand for
IPv4<BR>address blocks.<BR><BR>The underlying proposition behind this policy
proposal is that the<BR>registry of IPv4 addresses operated by ARIN is of
general utility and<BR>value only while it accurately describes the current
state of address<BR>distribution. If a class of address movement transactions
are excluded<BR>from being entered in the registry, then the registry will
have<BR>decreasing value to the broader community, and the integrity of
the<BR>network itself is thereby compromised. This proposal's central aim
is<BR>to ensure the continuing utility and value of the ARIN address<BR>registry
by allowing the registry to record transactions where IPv4<BR>addresses are
transfered between ARIN account holders.<BR><BR>It proposes that ARIN will
recognise and register a transfer of<BR>addresses where the parties to the
transfer are 'known' to ARIN and<BR>that the address block being transferred is
part of ARIN's current address set.<BR><BR>The proposal does not prescribe
how such transfers may occur, nor<BR>impose any further constraints on the
transfer or on the parties<BR>involved other than those described in this
proposal.</FONT></DIV>
<DIV><FONT face=Fixedsys></FONT> </DIV>
<DIV><FONT size=2 face=Fixedsys>9. Timetable for implementation:
immediate.</FONT></DIV>
<DIV><FONT size=2 face=Fixedsys></FONT> </DIV>
<DIV><FONT face=Fixedsys></FONT> </DIV>
<DIV><FONT face=Fixedsys><BR><BR></FONT></DIV></DIV></BODY></HTML>