<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19046"><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Tahoma","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US link=blue bgColor=white vLink=purple>
<DIV><FONT size=2 face=Arial>Hi Frank,</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Don't you think that every purchaser will have the
same impetus towards aggregation (slimmer table)?</FONT></DIV>
<DIV><FONT size=2 face=Arial>And the network operator community has the same
desire (slimmer table).</FONT></DIV>
<DIV><FONT size=2 face=Arial>(The network community which maintains
routers also does request blocks, I think that they will probably be among
the most active buyers and sellers.)</FONT></DIV>
<DIV><FONT size=2 face=Arial>So why create policy whose effect in this area is
unproven, despite evidence that it does not work well in certain
scenarios?</FONT></DIV>
<DIV><FONT size=2 face=Arial>By that I mean some who need now will have to wait,
some who want to sell will keep addresses on the sideline, etc.</FONT></DIV>
<DIV><FONT size=2 face=Arial>My argument is that our primary responsibilty is
maintaining an accurate Whois registry, and these increasing complex mechanisms
work against that responsibility by incentivizing off-the-books
transfers.</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</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=frnkblk@iname.com href="mailto:frnkblk@iname.com">Frank Bulk -
iName.com</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=mike@nationwideinc.com
href="mailto:mike@nationwideinc.com">'Mike Burns'</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> ; <A
title=scottleibrand@gmail.com href="mailto:scottleibrand@gmail.com">'Scott
Leibrand'</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, May 31, 2011 11:57
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [arin-ppml] ARIN-prop-153
Correct erroneous syntax in NRPM 8.3</DIV>
<DIV><BR></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt">Rather
than let my transit and peering providers summarize routes for me, I prefer to
have the IPv4 tables be as slim as possible.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt">Those
who request blocks are not those who maintain and purchase routers.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt">If
we find out that disaggregation is not an issue we can always eliminate those
policies.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt">Frank<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Mike Burns
[mailto:mike@nationwideinc.com] <BR><B>Sent:</B> Tuesday, May 31, 2011 10:50
AM<BR><B>To:</B> <A href="mailto:frnkblk@iname.com">frnkblk@iname.com</A>;
'Scott Leibrand'<BR><B>Cc:</B> <A
href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A><BR><B>Subject:</B> Re:
[arin-ppml] ARIN-prop-153 Correct erroneous syntax in NRPM
8.3<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">This is all an
unnecessary and needlessly confusing set of rules whose only purpose is to
attempt to impose some restriction on the downwards slide towards
disaggregation which will happen whatever policies we
prescribe.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">In a fluid transfer
market, nobody will purposely select to fill their needs with a smattering of
smaller netblocks, they will by nature attempt to acquire the largest block to
suit their purchase requirements, if only to relieve them of configuration
complexity.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">In fact, my guess
is that people will tend to round up, to allow for a little more room to grow
within a contiguous block, bounded of course by the cost of
holding unused inventory of addresses. </SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Larger netblocks
are more likely to be routed everywhere than smaller ones, and this alone will
drive consumers towards aggregation.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Creating a new and
confusing set of rules related to timeframes for allowed purchases, tracking
original registration sizes through potentially multiple transactions,
restricting sellers from selling off chunks of their holdings, these things
are exactly what would be wrong in putting the steward's lightest touch on
things.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Because they would
inevitably lead to buyers with a real need not getting addresses in a timely
fashion, additional listing requirements (like original allocation size), and
of course, lots more transactions happening off the books and leading to a
decay in Whois accuracy and representing a failure of our primary stewardship
role.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">And where is the
evidence that this will serve as an actual check on disaggregation, and where
is the evidence that we are BGP-table bound, in any real
sense?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">The check on the
growth of the table will not come from the RIR's, in a post-exhaust world, it
will come from the decisions of the network operator group about what the
minimum routable block size is.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">I oppose the
policy.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Regards,</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Mike</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: black 1.5pt solid; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0in">
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">----- Original
Message ----- <o:p></o:p></SPAN></P></DIV>
<DIV>
<P style="BACKGROUND: #e4e4e4" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"> <A
title=frnkblk@iname.com href="mailto:frnkblk@iname.com">Frank Bulk</A>
<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">To:</SPAN></B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"> <A
title=scottleibrand@gmail.com href="mailto:scottleibrand@gmail.com">'Scott
Leibrand'</A> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Cc:</SPAN></B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"> <A
title=arin-ppml@arin.net
href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A>
<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Sent:</SPAN></B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"> Tuesday, May 31,
2011 8:10 AM<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Subject:</SPAN></B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"> Re: [arin-ppml]
ARIN-prop-153 Correct erroneous syntax in NRPM
8.3<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">As
long as everyone works within the ARIN transfer policy, attaching the limits
on the recipients would seem sufficient. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Echoing
previous posters’ concerns, those who fall under the “3 month” needs
demonstration may create more disaggregation if they have to get small
chunks every time rather than a chunk two or three times larger.
Ideally they’re buying the chunks contiguously. I don’t know if we
can/should incent them to do that, or if having a contiguous block and not
having to find a new seller each time is incentive enough. I mean, if
they really think they’re going to grow, they’ll likely want to create a
contract from the same seller to buy more chunks.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Frank<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Scott Leibrand
[mailto:scottleibrand@gmail.com] <BR><B>Sent:</B> Tuesday, May 31, 2011
12:27 AM<BR><B>To:</B> frnkblk@iname.com<BR><B>Cc:</B> Owen DeLong;
arin-ppml@arin.net<BR><B>Subject:</B> Re: [arin-ppml] ARIN-prop-153 Correct
erroneous syntax in NRPM 8.3<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal>ARIN deaggregates /8s into
/22s and /20s today, so that's not really much different. It seems that any
restriction needs to be on the recipient getting a bunch of deaggregates,
not on a large block holder transferring to lots of smaller
recipients. <o:p></o:p></P>
<DIV>
<P class=MsoNormal>Scott<o:p></o:p></P></DIV></DIV>
<DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><BR>On May 30, 2011, at 7:16
PM, "Frank Bulk" <<A
href="mailto:frnkblk@iname.com">frnkblk@iname.com</A>>
wrote:<o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt">
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">That’s
a good goal, but how does this policy manage disaggregation where a larger
block owner has the opportunity to sell to different buyers? For
example, the owner of a /8 that has an unused /10 could sell /12’s to four
different buyers. On one hand there’s a desire to minimize
disaggregation, on the other hand if there’s unused space that others with
a validated need could use, why not.</SPAN><o:p></o:p></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </SPAN><o:p></o:p></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Frank</SPAN><o:p></o:p></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </SPAN><o:p></o:p></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Owen DeLong
[mailto:<A href="mailto:owen@delong.com">owen@delong.com</A>]
<BR><B>Sent:</B> Monday, May 30, 2011 11:28 AM<BR><B>To:</B> <A
href="mailto:frnkblk@iname.com">frnkblk@iname.com</A><BR><B>Cc:</B> <A
href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A><BR><B>Subject:</B>
Re: [arin-ppml] ARIN-prop-153 Correct erroneous syntax in NRPM
8.3</SPAN><o:p></o:p></P></DIV></DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal> <o:p></o:p></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>If they can find two /15s that started out as /15s, then
there's no problem. The issue comes if they, for example,<o:p></o:p></P>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>find someone with a /8 and want to get two disparate /15s
from within that /8. The intent here is to require<o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>the /8 holder to renumber enough to make a contiguous /14
available rather than transferring two disparate<o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>/15s and disaggregating them.<o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>Owen<o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal> <o:p></o:p></P>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>On May 29, 2011, at 9:34 PM, Frank Bulk
wrote:<o:p></o:p></P></DIV>
<P style="MARGIN-BOTTOM: 12pt; mso-margin-top-alt: auto"
class=MsoNormal><o:p> </o:p></P>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I’m
confused. If an organization can demonstrate need for a /14 and they
can only find a /15 in the market today, why should they have to wait a
whole year if they can find another /15 just a few months later? Why
should we penalize them for the fact that the supply at the time of need
is low? Is it because you want someone else with demonstrable need
to get that second /15? If that’s the case, won’t that be based on
who’s willing to pay top dollar for that
/15? </SPAN><o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </SPAN><o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Frank</SPAN><o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </SPAN><o:p></o:p></P></DIV>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
class=apple-converted-space><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> </SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"><A
href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</A><SPAN
class=apple-converted-space> </SPAN>[mailto:<A
href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</A>]<SPAN
class=apple-converted-space> </SPAN><B>On Behalf Of<SPAN
class=apple-converted-space> </SPAN></B>Owen
DeLong<BR><B>Sent:</B><SPAN
class=apple-converted-space> </SPAN>Sunday, May 29, 2011 10:46
PM<BR><B>To:</B><SPAN class=apple-converted-space> </SPAN>Brett
Frankenberger<BR><B>Cc:</B><SPAN
class=apple-converted-space> </SPAN><A
href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A><BR><B>Subject:</B><SPAN
class=apple-converted-space> </SPAN>Re: [arin-ppml] ARIN-prop-153
Correct erroneous syntax in NRPM 8.3</SPAN><o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> </SPAN><o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="COLOR: #1f497d"><snip></SPAN><o:p></o:p></P></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </SPAN><o:p></o:p></P></DIV></DIV></DIV>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>What I would think makes more sense as policy would
be:<o:p></o:p></P></DIV></DIV>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal> <o:p></o:p></P></DIV></DIV>
<BLOCKQUOTE style="MARGIN: 5pt 0in 5pt 30pt">
<DIV>
<DIV>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>Organizations may transfer multiple address blocks
but<o:p></o:p></P></DIV></DIV></DIV></DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>no organization shall receive more than one address
block<o:p></o:p></P></DIV></DIV>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>per year where said address block is
smaller<o:p></o:p></P></DIV></DIV></DIV></DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal>than its original registered
size.<o:p></o:p></P></DIV></DIV></DIV></DIV></BLOCKQUOTE>
<DIV>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal> <o:p></o:p></P></DIV></DIV></DIV>
<DIV>
<DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="COLOR: #1f497d"><snip></SPAN><o:p></o:p></P></DIV></DIV></DIV>
<DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal> <o:p></o:p></P></DIV></DIV></DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal> <o:p></o:p></P></DIV></DIV></DIV></BLOCKQUOTE>
<BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt">
<DIV>
<P
class=MsoNormal>_______________________________________________<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">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">http://lists.arin.net/mailman/listinfo/arin-ppml</A><BR>Please
contact <A href="mailto:info@arin.net">info@arin.net</A> if you experience
any issues.<o:p></o:p></P></DIV></BLOCKQUOTE>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center>
<HR align=center SIZE=2 width="100%">
</DIV>
<P
class=MsoNormal>_______________________________________________<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">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">http://lists.arin.net/mailman/listinfo/arin-ppml</A><BR>Please
contact <A href="mailto:info@arin.net">info@arin.net</A> if you experience
any issues.<o:p></o:p></P></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>