<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23580">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Hi Bill,</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>I will answer as the author.</FONT></DIV>
<DIV><FONT size=2 face=Arial>I chose /16 as a starting point for discussion, at
least, because my experience as a broker demonstrates a distinction in buyers
and sellers around that size.</FONT></DIV>
<DIV><FONT size=2 face=Arial>I suppose we could go by ARIN billing policy which
has different definitions, but I think a /16 is a medium size.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Most transactions have been at or below this
number.</FONT></DIV>
<DIV><FONT size=2 face=Arial>There is a complete record of transfers available
at APNIC and ARIN, including the sizes of all transferred blocks.</FONT></DIV>
<DIV><FONT size=2 face=Arial>APNIC's list is a little cluttered with
quasi-internal transfers to National Internet Registries, but is available
here:</FONT></DIV>
<DIV><FONT size=2 face=Arial><A
href="ftp://ftp.apnic.net/public/transfers/apnic/">ftp://ftp.apnic.net/public/transfers/apnic/</A></FONT></DIV>
<DIV><FONT size=2 face=Arial>ARIN here:</FONT></DIV>
<DIV><FONT size=2 face=Arial><A
href="https://www.arin.net/knowledge/statistics/transfers.html">https://www.arin.net/knowledge/statistics/transfers.html</A></FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Regards,</FONT></DIV>
<DIV><FONT size=2 face=Arial>Mike Burns</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=billdarte@gmail.com href="mailto:billdarte@gmail.com">Bill Darte</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=springer@inlandnet.com
href="mailto:springer@inlandnet.com">John Springer</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=arin-ppml@arin.net
href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, April 29, 2014 7:59
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [arin-ppml] ARIN-prop-204
Removing Needs Test from Small IPv4 Transfers (fwd)</DIV>
<DIV><BR></DIV>
<DIV dir=ltr>Hi John,
<DIV><BR>
<DIV>Couple of questions..... could the solution for staff effort be solved
more directly by modifying the protocol that establishes team testing for each
and every request through exhaustion? I wonder about the need for these
extraordinary measures.</DIV>
<DIV><BR></DIV>
<DIV>Is /16 small? Did you consider a different boundary....say,
/20?</DIV>
<DIV>How much of a record do we have for transfer requests yet? Until
exhaustion we don't know what the run rate will be or the average size block
request. Though I believe the that those metrics should mimic
pre-exhaustion as I see nothing magic affecting network build out and business
demands in the pre-post time frames.</DIV>
<DIV><BR></DIV>
<DIV>So, I neither support, nor oppose this proposal but hope to inform the
discussion through my questions.</DIV>
<DIV><BR></DIV>
<DIV>bd</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV></DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Tue, Apr 29, 2014 at 12:35 AM, John Springer <SPAN
dir=ltr><<A href="mailto:springer@inlandnet.com"
target=_blank>springer@inlandnet.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Hi All,<BR><BR>The following timely policy proposal is
presented for your consideration, discussion and comment. Will you please
comment?<BR><BR>As always, expressions of support or opposition (and their
reasons) are given slightly more weight than reasons why you might be in
neither condition.<BR><BR>John Springer<BR><BR><BR>ARIN-prop-204 Removing
Needs Test from Small IPv4 Transfers<BR><BR>Date: 16 April 2014<BR>Problem
Statement:<BR>ARIN staff, faced with a surge in near-exhaust allocations and
subsequent transfer requests and a requirement for team review of these, is
spending scarce staff time on needs testing of small transfers. This
proposal seeks to decrease overall ARIN processing time through elimination
of that needs test.<BR>Policy statement:<BR>Change the language in NRPM 8.3
after Conditions on the recipient of the transfer: from "The recipient must
demonstrate the need for up to a 24-month supply of IP address resources
under current ARIN policies and sign an RSA." to "For transfers larger than
a /16 equivalent, the recipient must demonstrate the need for up to a
24-month supply of IP address resources under current ARIN policies and sign
an RSA."<BR>Change the language in the third bullet point in NRPM 8.4 after
Conditions on the recipient of the transfer: from "Recipients within the
ARIN region must demonstrate the need for up to a 24-month supply of IPv4
address space." to "For transfers larger than a /16 equivalent, recipients
in the ARIN region must demonstrate the need for up to a 24-month supply of
IP address resources under current ARIN policies and sign an
RSA."<BR>Comments:<BR>Needs testing has been maintained for transfers
largely because the community wishes to ensure protection against hoarding
and speculation in the IPv4 market. This proposal seeks a middle ground
between the elimination of needs tests for transfers altogether, and the
continuance of needs tests for every transfer. This should help ARIN staff
to reduce transfer processing time, since most transfers have been smaller
than /16.<BR>Timetable for implementation:
Immediate<BR><BR>______________________________<U></U>_________________<BR>PPML<BR>You
are receiving this message because you are subscribed to<BR>the ARIN Public
Policy Mailing List (<A href="mailto:ARIN-PPML@arin.net"
target=_blank>ARIN-PPML@arin.net</A>).<BR>Unsubscribe or manage your mailing
list subscription at:<BR><A
href="http://lists.arin.net/mailman/listinfo/arin-ppml"
target=_blank>http://lists.arin.net/mailman/<U></U>listinfo/arin-ppml</A><BR>Please
contact <A href="mailto:info@arin.net" target=_blank>info@arin.net</A> if
you experience any issues.<BR></BLOCKQUOTE></DIV><BR></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>PPML<BR>You are
receiving this message because you are subscribed to<BR>the ARIN Public Policy
Mailing List (ARIN-PPML@arin.net).<BR>Unsubscribe or manage your mailing list
subscription at:<BR>http://lists.arin.net/mailman/listinfo/arin-ppml<BR>Please
contact info@arin.net if you experience any issues.</BLOCKQUOTE></BODY></HTML>