<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:NewCenturySchlbk;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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";}
h1
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:14.0pt;
font-family:NewCenturySchlbk;
font-weight:bold;}
h2
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:12.0pt;
font-family:NewCenturySchlbk;
font-weight:normal;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{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";}
p.SPCI-503Report, li.SPCI-503Report, div.SPCI-503Report
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level1 lfo1;
font-size:14.0pt;
font-family:NewCenturySchlbk;
font-weight:bold;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:888152470;
mso-list-type:hybrid;
mso-list-template-ids:1337115686 -1630604664 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-style-link:"SPCI-503 Report";
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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 vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Wes<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>The simple answer is that regardless of
how we try to prevent it; our computing environment gets built into our
applications. In short, although IPv6 makes re-addressing easy, it cannot
fix the parts of an entity’s infrastructure that get built into code,
scripts, or configs. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Thus re-addressing after even a year or
two present huge potential issues for the entity contemplating changing ISPs
and thus getting new addresses. Outages of any magnitude scare even the
CIO’s of small businesses.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>It is the same thing we are seeing trying
to migrate entities into “cloud computing”; they still have to take
the risk that some number of your apps will fail in the transition because the
apps have “the current computing environment” embedded in their
code.<o:p></o:p></span></font></p>
<div>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>Take care</span></font><font color=navy><span
style='color:navy'> <br>
</span></font><font size=2 color=navy face=Arial><span style='font-size:10.0pt;
font-family:Arial;color:navy'>Terry</span></font><font color=navy><span
style='color:navy'> <o:p></o:p></span></font></p>
<p><font size=3 color=navy face="Times New Roman"><span style='font-size:12.0pt;
color:navy'>PS: And for larger enterprises, Sarbanes-Oxley may even come into
play as to whether they can accept PA space.<o:p></o:p></span></font></p>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
arin-ppml-bounces@arin.net [mailto:arin-ppml-bounces@arin.net] <b><span
style='font-weight:bold'>On Behalf Of </span></b>George, Wes E [NTK]<br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, May 29, 2009 1:26 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Stacy Hughes; <st1:PersonName
w:st="on">arin-ppml@arin.net</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [arin-ppml] Policy
Proposal: Open Access To IPv6</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>I agree with Leo's comments regarding the
risks to deaggregation and routing table size with no sizable benefit.</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>The comment was made in <st1:City w:st="on"><st1:place
w:st="on">San Antonio</st1:place></st1:City> when we were
discussing relaxing standards for community networks, and I'll
echo/paraphrase it here...</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>I need to see some level of justification
as to why provider independent space is a requirement and provider-allocated
space will not work for a non-multihomed network. Otherwise I'm not convinced
that there's sufficient reason to loosen the requirements for direct
allocations simply on the basis that it discriminates against those who
can't/won't multihome or don't have a network of a specific size.</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>While I can see how innovation might be
chilled by overly stringent allocation policies, I don't see how innovation or
adoption is chilled by having to use PD allocations, and I echo
the statement that if policy was the only reason why IPv6 wasn't widely
deployed, we'd be in FAR better shape right now. </span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Yes, in the short term while there are
ISPs that don't have their collective "stuff" together on an IPv6
deployment and it is not possible to *get* IPv6 service (and therefore also an
allocation) from one's upstream, this would be a problem. However, that is
going to be self-correcting for a lot of reasons, and if it's a deal-breaker,
the entity in question will find another ISP that is able to meet their needs.</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>If it's a block size issue, I would expect
that this will go similarly to the way that it does in IPv4, either an ISP has
enough space to allocate the requested block size to their customer, or they go
to Arin to get more space using this as the justification.</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>That said, as IPv4 space is getting harder
to come by, ISPs have tightened up their justification requirements. It would
be good to ensure that ISPs are being more open in their allocations of IPv6 by
comparison in order to ensure that we aren't preventing people who want IPv6
space from getting it. If that falls beyond ARIN's purview and this is an
attempt to solve that, I'm not sure that it's the best solution.</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><!-- Converted from text/rtf format -->Thanks,</span></font>
<br>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Wes</span></font>
<o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
arin-ppml-bounces@arin.net [mailto:arin-ppml-bounces@arin.net] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Stacy Hughes<br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, May 29, 2009 1:49 PM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">arin-ppml@arin.net</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [arin-ppml] Policy
Proposal: Open Access To IPv6</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> A multihoming requirement discriminates against networks that
either cannot or do not want to multihome. <o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I oppose this modification.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Stacy <o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Fri, May 29, 2009 at 10:42 AM, Leo Bicknell <<a
href="mailto:bicknell@ufp.org">bicknell@ufp.org</a>> wrote:<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>In a message written on
Fri, May 29, 2009 at 11:14:45AM -0400, <st1:PersonName w:st="on">Member
Services</st1:PersonName> wrote:<br>
> 1) Remove ?by advertising that connectivity through its single<br>
> aggregated address allocation? from article 3 of section 6.5.1.1<br>
><br>
> 2) Remove article 4 of section 6.5.1.1, ?be an existing, known ISP in<br>
> the ARIN region or have a plan for making at least 200 end-site<br>
> assignments to other organizations within 5 years? in its entirety.<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I fear the way this is written may be confusing. Section 6.5.1.1
is at<br>
<a href="https://www.arin.net/policy/nrpm.html#six511" target="_blank">https://www.arin.net/policy/nrpm.html#six511</a><br>
<br>
If these changes were made, I believe the section would then read:<br>
<br>
6.5.1.1. Initial allocation criteria<br>
<br>
To qualify for an initial allocation of IPv6 address space, an<br>
organization must:<br>
<br>
1. be an LIR;<br>
2. not be an end site;<br>
3. plan to provide IPv6 connectivity to organizations to which it<br>
will assign IPv6 address space.<br>
<br>
I would like to make two comments as a result.<br>
<br>
Criteria #1 doesn't make a lot of sense. If you were a new participant<br>
(no IPv4 or IPv6 resources at all) and going only for IPv6 then you<br>
aren't an LIR yet, indeed, you are trying to become one. I think,<br>
but cannot be sure, that the LIR reference has to do with fee/membership<br>
structures of other RIR's.<br>
<br>
The result of this policy is basically you get an allocation if you<br>
want one and can show you will provide IPv6 to another entity and<br>
are willing to pay the fees. This is too loose of a standard.<br>
While I believe we should be giving out IPv6 relatively easily and<br>
there is no danger in running out of the numbers that does not mean<br>
we don't still have the issue of routing slots, staff to deal with<br>
the number of requests, and other issues.<br>
<br>
To that end, I would like to suggest a new criteria:<br>
<br>
- Plan to announce the IPv6 address space provided to at least<br>
two other autonomous systems.<br>
<br>
Basically, setting the bar at being multi-homed to BGP speaking<br>
networks. No number of sites requirement, you only need 1 customer<br>
to meet the customer requirement.<br>
<font color="#888888"><span style='color:#888888'><br>
--<br>
Leo Bicknell - <a href="mailto:bicknell@ufp.org">bicknell@ufp.org</a>
- CCIE 3440<br>
PGP keys at <a href="http://www.ufp.org/~bicknell/"
target="_blank">http://www.ufp.org/~bicknell/</a><br>
</span></font><br>
_______________________________________________<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" target="_blank">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></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p class=MsoNormal><font size=1 color=gray face=Arial><span style='font-size:
7.5pt;font-family:Arial;color:gray'>This e-mail may contain Sprint Nextel
Company proprietary information intended for the sole use of the recipient(s).
Any use by others is prohibited. If you are not the intended recipient, please
contact the sender and delete all copies of the message.</span></font><o:p></o:p></p>
</div>
</div>
</body>
</html>