Send ARIN-PPML mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.arin.net/mailman/listinfo/arin-ppml
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-PPML digest..."


Today's Topics:

   1. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
      (John Curran)
   2. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for   ISPs
      (Michael Richardson)
   3. Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs (ARIN)
   4. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for   ISPs
      (Aaron Dudek)
   5. Re: The case against need based justification (Heather Schiller)


----------------------------------------------------------------------

Message: 1
Date: Mon, 8 Apr 2013 06:22:35 +0000
From: John Curran <[email protected]>
To: Steven Ryerse <[email protected]>
Cc: "[email protected] PPML" <[email protected]>
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-3: Tiny IPv6
        Allocations for ISPs
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

On Apr 7, 2013, at 11:02 PM, Steven Ryerse <[email protected]> wrote:

> Arin and this community could of course - rewrite the allocation polices like 
> the RIPE proposal http://www.ripe.net/ripe/policies/proposals/2013-03 and 
> make it easier and more straightforward to "qualify" for IP resources.  Then 
> organizations that have been denied allocations (like ours) or organizations 
> that haven't even bothered to apply to Arin for an allocation for fear of 
> being denied - could then get resources and be added to the community that 
> pays Arin fees.  
> 
> Then maybe Arin's board of directors wouldn't/won't have to approve fee 
> increases because there would be many more organizations paying fees and 
> Arin's total revenue would increase.  
> 
> Arin gets more revenue, Organizations get needed resources, Arin is 
> fulfilling its Mission, Organizations get lower costs. Sounds like a 
> win-win-win-win to me.  

Indeed.  ARIN has actually seen a significant increase in members
over time due to those receiving resources, but you are welcome to
suggest any specific changes to policy that would improve access 
to number resources.  You can find more information on the Policy 
Development Process here: 
   <https://www.arin.net/participate/how_to_participate.html>

Thanks!
/John

John Curran
President and CEO
ARIN



------------------------------

Message: 2
Date: Mon, 08 Apr 2013 08:45:07 -0400
From: Michael Richardson <[email protected]>
To: "[email protected]" <[email protected]>, Steven Noble
        <[email protected]>
Cc: John Curran <[email protected]>
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-3: Tiny IPv6
        Allocations for ISPs
Message-ID: <[email protected]>


>>>>> "Steven" == Steven Noble <[email protected]> writes:
    Steven> That is exactly my point, if ARIN says that someone
    Steven> requesting IPv6 will not have higher fees, then how does
    Steven> that work with a legacy holder?  Do we want people to adopt
    Steven> IPv6 or not?  A policy that makes it the same cost to
    Steven> request and hold IPv4 and IPv6 works both ways.  If I am
    Steven> charged the same as someone who has both IPv4 and IPv6
    Steven> resources, why would I not request IPv4 resources too? 

+1

And, given that I can get IPv4 for the same price, why go to the hassle
of doing anything with IPv6?   The business case for doing new things
with IPv6 should include "and the address space is essentially free,so
we wilkl do the network architecture correctly, rather than creating a
hack that supported IPv4 NAT/bridging"

Do you know how many layer-2 **hack** have been created because IPv4
subnets are a fixed quantity?  (particularly in the pre-CIDR days)

IPv6 allocations and especially end-user assignments, need to be
essentially free.  In the IPv4 time scale, this is 1989, when
enterprises just came to the table for address space, with *no
intention* of advertising that space.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     [email protected]  http://www.sandelman.ca/        |   ruby on rails    [ 
        


------------------------------

Message: 3
Date: Mon, 08 Apr 2013 11:12:23 -0400
From: ARIN <[email protected]>
To: [email protected]
Subject: [arin-ppml] Draft Policy ARIN-2013-3: Tiny IPv6 Allocations
        for ISPs
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Draft Policy ARIN-2013-3
Tiny IPv6 Allocations for ISPs

The text has been revised.

Draft Policy ARIN-2013-3 is below and can be found at:
https://www.arin.net/policy/proposals/2013_3.html

This draft will be presented at ARIN 31.

The ARIN Policy Development Process (PDP) can be found at:
https://www.arin.net/policy/pdp.html

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html

Regards,

Communications and Member Services
American Registry for Internet Numbers (ARIN)


## * ##


Draft Policy ARIN-2013-3
Tiny IPv6 Allocations for ISPs

Date: 8 April 2013

Problem Statement:

ARIN's fee structure provides a graduated system wherein organizations
pay based on the amount of number resources they consume.

At the very bottom end of the scale, it is presently not possible to be
an XX-Small ISP with an IPv6 allocation because the minimum allocation
size of /36 automatically promotes one into X-Small ISP status,
resulting in a doubling of annual fees.

While tiny in absolute terms, the extra costs incurred represent a
disincentive to IPv6 deployment.

To the author's knowledge, it has never been possible for an LIR/ISP to
get a /40 allocation direct from ARIN; such assignments have been
limited to organizations that qualify as end sites or /48s for critical
infrastructure.  It is understood there is an expected correction of the
XX-Small fee category to "/40 or smaller".

Policy statement:

Part 1: In subsection 6.5.2. Initial Allocation Size, insert "or /40" at
the end of the first sentence of subsection 6.5.2.1 clause (b), and add
a new clause (g), resulting in;

b. In no case shall an LIR receive smaller than a /32 unless they
specifically request a /36 or /40.  In no case shall an ISP receive more
than a /16 initial allocation.

...

g. An LIR that requests a smaller /36 or /40 allocation is entitled to
expand the allocation to any nibble aligned size up to /32 at any time
without renumbering or additional justification.  Such expansions are
not considered subsequent allocations.  However, any expansions beyond
/32 are considered subsequent allocations, and must conform to section
6.5.3.

Part 2: Add a new subsection to section 6 "IPv6";

6.12 Reduction or Return

ARIN will accept the return of whole or partial block(s) allowing an
organization to reduce their holdings as long as:

a. The resulting number of retained aggregate blocks does not increase.

b. Whole blocks are returned to the extent practicable.

c. Partial block(s) retained must conform to current applicable
allocation or assignment policies, as to size, alignment, etc?

d. Block(s) retained are within a single reserved space or aggregate set
aside for the organization in the ARIN database to the extent practicable.

e. All block(s) returned are not in use by the organization or its
customers.

Comments:

The author acknowledges the shortcomings of providing an ISP with an
allocation of a size that is more traditionally associated with end
sites. In order to avoid possible bad effects on the routing table, the
author encourages ARIN staff to adopt the same sparse allocation
practice as currently exists for larger allocations, ideally even
reserving a block as large as the /28 that is reserved for /32s
currently.  Note the policy intent of part 1 requires a minimum of a /32
be reserved.

Part 1 brings ARIN's allocation policies in line with the upcoming fee
schedule, with the addition of an expected correction of the XX-Small
fee category to "/40 or smaller".  This makes it possible to qualify for
each ISP fee category while holding IPv6 number resources and allows
expansion up to /32 without renumbering or additional justification as a
subsequent allocation.  The selection of a /32, /36 or /40 allocation is
only driven by an ISP's own internal business justifications.

Part 2 codifies and expands upon current practice for selective return
in the manner described by John Curran on the arin-discuss mailing list
(7-Mar-2013 in
[email protected] ). It
specifies the generic requirements that should be met for such returns.

A more practical approach might to figure out a way to apply graduated
fees to ISPs at the very small end of the scale using some metric other
than prefix size. Fee schedules are outside of the purview of the Policy
Development Process; such responsibility lies with the Board should they
choose to take it up.

Summary of community discussion:

The fundamental argument against this draft policy is that the primary
problem being solved is a billing or fee structure issue and not a
number resource policy issue in itself.  A significant minority are
adamant on this issue to the extent they oppose this policy. The
majority of the community recognizes this issue, and would prefer /32 be
the sole minimum allocation size for ISPs and other LIRs.  However, the
majority are willing to accept the tradeoffs incorporated into this
policy.  As there are too many ISPs that fit into the /32 allocation
category for the fee level associated with the XX-Small category to be
fiscally responsible and sustainable for ARIN. Furthermore, there are no
obvious solutions to this problem within the fee structure domain that
are fiscally responsible and sustainable for ARIN, especially in the
long-term.

Everyone agrees making /36 or /40 allocations to ISPs seems less than
ideal from a number resource policy perspective.  However, this is
mitigated by ensuring that all ISPs have a /32 available to them without
renumbering or additional justification and from a number resource
policy perspective the selection of /36 or /40 allocations is completely
voluntary.  This allows each ISP to make the decision to select from a
/32, /36 or /40 initial allocation based solely on their own internal
business justifications, and eliminates structural disincentives in the
fee schedule for IPv6 adoption.  This seems like the best balance
available at this time of number resource policy, fiscal responsibility
and sustainability for both ARIN and the ISPs that it serves.

Timetable for implementation: Immediate


------------------------------

Message: 4
Date: Mon, 8 Apr 2013 11:15:06 -0400
From: Aaron Dudek <[email protected]>
To: Michael Richardson <[email protected]>
Cc: John Curran <[email protected]>, "[email protected]"
        <[email protected]>
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-3: Tiny IPv6
        Allocations for ISPs
Message-ID:
        <CAA0LXWXA=Yzv9dtEOCikqf8x==pqhbdywot3pg4da22nd1c...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Because IPv4 is disappearing.
At some point in the near future it will cost more to do IPv4, specifically
to acquire addresses, then IPv6.

Nice reference to 1989. Where did that get us now?


On Mon, Apr 8, 2013 at 8:45 AM, Michael Richardson <[email protected]> wrote:

>
> >>>>> "Steven" == Steven Noble <[email protected]> writes:
>     Steven> That is exactly my point, if ARIN says that someone
>     Steven> requesting IPv6 will not have higher fees, then how does
>     Steven> that work with a legacy holder?  Do we want people to adopt
>     Steven> IPv6 or not?  A policy that makes it the same cost to
>     Steven> request and hold IPv4 and IPv6 works both ways.  If I am
>     Steven> charged the same as someone who has both IPv4 and IPv6
>     Steven> resources, why would I not request IPv4 resources too?
>
> +1
>
> And, given that I can get IPv4 for the same price, why go to the hassle
> of doing anything with IPv6?   The business case for doing new things
> with IPv6 should include "and the address space is essentially free,so
> we wilkl do the network architecture correctly, rather than creating a
> hack that supported IPv4 NAT/bridging"
>
> Do you know how many layer-2 **hack** have been created because IPv4
> subnets are a fixed quantity?  (particularly in the pre-CIDR days)
>
> IPv6 allocations and especially end-user assignments, need to be
> essentially free.  In the IPv4 time scale, this is 1989, when
> enterprises just came to the table for address space, with *no
> intention* of advertising that space.
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        | network
> architect  [
> ]     [email protected]  http://www.sandelman.ca/        |   ruby on rails
>    [
>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130408/b7a65176/attachment-0001.html>

------------------------------

Message: 5
Date: Mon, 8 Apr 2013 11:34:11 -0400
From: Heather Schiller <[email protected]>
To: "cb.list6" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-ppml] The case against need based justification
Message-ID:
        <CADricwqBsFSn3Tc+O8EAB8RYhm_Hv0q=a5KaR=dzmab5mcw...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

 I find much of your argument flawed -- you seem to have chosen a
conclusion and then tried to wrap theories around it.

Re-read the nrpm... for a transfer to be recognized by ARIN, the criteria
of justified need still applies.  The "substantial market buys" you
referenced still had justified need applied to them ---- the only
difference between getting space directly from ARIN and getting it on the
secondary market [aside from cost] is the window of time you can justify
need for.  Directly from ARIN you can get 3 months justified need and on
the secondary market you can request up to 24 months need.

Unless you participated in the engineering and design of each of the
networks you reference, you can not have first hand knowledge of how
addressing policy affected their decisions.  You are making guesses from
the outside, based on the size of their customer base and what you see
today.  In atleast one mobile provider you reference, I can say -with
direct knowledge- that your conclusion is wrong.  The move to CGN has
nothing to do with justified need and everything to do with whether it is
financially responsible to continue investing in a finite resource.  Sure
providers could buy up space on the secondary market for another year or 2
- and then what?  The price for v4 could rise exorbitantly, to the point
where the cost of an address becomes a significant cost toward offering the
service.  You will be stuck in the same place and out a bunch of cash.  Or
you can have multiple customers share an address, recover a bunch of space
and continue to grow your business without investing in the secondary
market.  Its the expense of the secondary market itself, that makes CGN
more appealing.

With regard to use of RFC1918 space - again - unless you were involved in
making the decision at those companies - you can not authoritatively say
why they made the decision they did.  You are speculating that they chose
to use 1918 space because they were unable or unwilling to justify need -
and that is very unlikely to be the case.  Network Engineers tend to be
reasonable, logical folks who give great thought to where public address
space is necessary and where it isn't, as well as the pros and cons of
using both.  They may have chosen to respect a shared resource and conserve
space, or been unsure how large the network would grow, or been unable to
justify [to their mgr, themselves or whoever] the additional ARIN fees for
being in a larger allocation category.

Fair does not mean that every organization gets the same thing.  The NEEDS
of every organization are different.  This is why ARIN takes the time to
read through the request and help ensure that what the organization gets,
meets their needs... not their competitor or neighbor's needs.

http://imbloghoppin.blogspot.com/2011/08/power-of-bandaid.html


Where I do empathize with you, is the problem you described about getting
v6 address space from your provider for a lab and they wouldn't give you
more than a /56.  However, that is a business decision by your ISP.  As of
today, there is no mandatory minimum IPv6 assignment size for ISP's to
their customers, only a small reference to a recommendation.  In fact,
justified need is not a requirement in making reallocations to customers in
IPv6, so abolishing justified need would not affect the v6 assignment size
your ISP offers.   If you would like to see that changed - then read up on
how we got there and submit a proposal to change it (
https://www.arin.net/policy/pdp_appendix_b.html)  Otherwise, it is an issue
between you and your provider and should be taken up with them directly.

--Heather



On Mon, Apr 8, 2013 at 1:13 AM, cb.list6 <[email protected]> wrote:

> Need-based justification is being reviewed in RIPE [1]
>
> That spurred me to review need based justification in ARIN for both
> IPv4 and IPv6.
>
> I would like to present some facts for review so that the ARIN
> community can judge the success of need-based justification and
> consider the role it will have in future policy.
>
> First, as of this writing, ARIN still has  2.47 /8s free [2].
> Excluding the last /8 which is locked in a way by policy, that leaves
> approximately 24 Million addresses in the free pool.  Assuming a free
> market cost of $10 per IPv4 address, that is $240 million worth of
> IPv4 cost off-set from which one would have to pay the free ipv4
> market for those addresses.  This is a relevant sum on nearly any
> balance sheet.  So, it is not acceptable to say folks are turning away
> from it because ARIN is offering that space in a fair way.  The free
> pool is relevant.
>
> There is a case that the need-based policy has done well, and it has
> done well for some.  Comcast, for example, has 18 million subscribers
> and 70 Million IPv4 addresses [3].  For simple math, we can call that
> 3.8 addresses for every 1 customer.  Then, you have a network like
> Metro PCS who has 9 million subscribers (2.2 million of which are LTE)
> [4] on what i can tell is 1,024 IPv4 addresses.  Which is a
> 0.000113778 IPv4 addresses per subscriber from ARIN.  I do not speak
> for Metro PCS, i just found their case interesting.
>
> So, there are winners and losers in need-based.  Winners puts more
> time and money into the process, losers are busy optimizing other
> parts of their business instead of working the ARIN system.  Looking
> back at [3],  winners are also big companies with a lot of resource
> and ... they probably send people to ARIN meetings and ... maybe they
> even send lawyers to ARIN meetings.  I don't know, i have never been
> to an ARIN meeting myself.
>
> So far, i hope we have seen that the free pool as of today is relevant
> and that need-based is not strictly "fair" in how the distribution
> happens, and that there are winners and losers.  Winners invest more
> time and effort, and sometimes time and effort is from lawyers not
> engineers.
>
> Now, there is more.  Many organizations have found ARIN unsuitable for
> their address needs.  We know that in 2011 when the free pool was much
> larger than it is now (4+ /8s?), Microsoft bought IPv4 space from  a
> bankruptcy court [6].  Amazon among others has also made substantial
> market buys.  These companies are obviously not getting what they want
> from a need-based policy, and i assume they made cogent business case
> to close these deals.  The difference is they have the money to work
> the policy like Comcast, but instead they worked a different angle
> also applying money.  But, need-based is not a about money.  Is it?
> It is about justified need, or the appearance of such.  It would
> appear that Amazon and Microsoft could justify need, but the
> need-based policy does not appear to work for them.  I am aware of the
> transfer policy and how need is, for some reason, a different standard
> there.
>
> So, that is open market end of things, organizations pay millions of
> dollars instead of thousands of dollars to not use a need-based policy
> of the ARIN free pool.  Seems like the symptom of something broken.
>
> Here is another symptom of something broken.  The largest internet
> growth engine is mobile.  Mobile contributes a huge amount of traffic,
> growth, and "stuff" on the Internet.  If Zuck does not mention mobile
> 20 times in an earnings call, FB stock dives.  AT&T wireless and
> Verizon Wireless both have close to a 100 million subscribers each.
> And, just about every one of those subscribers uses RFC 1918 space.
> What about those 2 smaller players, Sprint and T-Mobile.  Both of them
> use squat space.  Despite spending time and money on outreach, this
> HUGE part of the internet is not part of the ARIN numbering system
> (unless you count the ARIN addresses on the CGN).  At least, not part
> of ARIN's need-based policy.   Mobile uses CGN because ARIN's policies
> have not and will not fit with the growth of these networks and their
> architectures.  Not today, but also not in 2003.  I would like that
> that to change [7].  Speaking for myself, what i saw was a network was
> designed to best fit the business needs.  That network design did not
> fit ARIN policies for efficiency, and so ARIN would not provide
> addresses and CGNs were rolled in to close the gap between the best
> network design and the ARIN policies.
>
> Speaking more for myself, in 2000 i worked for an ISP, and one of my
> job roles was assigning addresses to T1 and T3 customers of the ISP.
> It was a painful process for me and my customers.  We lived in world
> where people just wanted a /24 to turn up their LAN, but i could not
> just give it to them.  It was a world of scarcity of addresses, emails
> full of made up justifications, and that persist today.
>
> In fact, last year i tried to get a /48 of address space for a lab
> network attached to a T3 from TWT.  They would not give me more than a
> /56.  I heard from another guy that Internap would only give him a
> /64.  Need-based is a trickled down disease on network design.
>
> It is not just mobile doing CGN.  AT&T has deployed CGN to landline
> DSL [8], and now Verizon DSL too [9]
>
> As previously noted, the ARIN free pool is a non-trivial sum of 24
> million IPv4 addresses.  Yet, companies continue to buy addresses and
> / or deploy CGN.  And they do it at massive scale.  We are talking
> about the biggest cloud and access network providers can't seem to get
> what they need from ARIN whether it be IPv4 addresses or effective
> IPv6 deployment advocacy.
>
> My conclusion from all this is that need-based policy did not help
> IPv4 and is actively hurting IPv6.
>
> NRPM and ARIN should get out of the business of telling people how to
> number their networks, it has not helped the businesses or the
> internet.  I say this because "we" did not transition to IPv6 and the
> market for IPv4 and the technology known as CGN is seen as more
> effective solution than ARIN or IPv6
>
> That brings me to policy changes that i would like feedback on.
>
> 1. Should ARIN continue to administer need-based policy now and after
> run-out?  Please note the discussion of winners and loser with data
> points [3] and [5]. Who is ARIN serving with the need-based policy?
>
> 2.  I have made the claim that ARIN's need-based policy has negatively
> impacted system design, the specific system being the internet.  The
> squat / CGN internet that is on your phone [7] and coming to your DSL
> [8],[9].
>
> 3.  By moving away from need based policy from ipv4, we accept reality
> that the market rules [6].  IPv4 addresses are part of the means of
> production in a capitalist society.  IPv4 addresses should not be
> acquired by playing some logic game with people  via ARIN tickets or
> intellectual thumb-wrestling and posturing on PPML.
>
> 4.  IPv6 is designed without need in mind, there is no reason for ARIN
> to import the notion that need is factor when each LAN is given 2^64
> addresses.  Organizations that want PI should get an ASN (existing
> policy) and a minimum /32 and be done. End of story.  There is no
> logic for conservation of a limitless resource (in this case, it is
> bounded by ASN).  Growth beyond a /32 should just be a simple written
> justification, not gear and subscriber logs showing 80% use.
>
> 5.  These simplifications can be reflected in a rate structure that
> results from such simplification.
>
>
> [1] https://www.ripe.net/ripe/policies/proposals/2013-03/
> [2] https://www.arin.net/resources/request/ipv4_countdown.html
> [3]
> http://www.nanog.org/meetings/nanog57/presentations/Tuesday/tue.lightning3.howard.ipv4%20buyers.pdf
> [4]
> http://investor.metropcs.com/phoenix.zhtml?c=177745&p=irol-newsArticle&ID=1789168&highlight=
> [5] http://whois.arin.net/rest/net/NET-65-91-116-0-1.html
> [6] http://www.bbc.co.uk/news/technology-12859585
> [7] https://www.arin.net/policy/proposals/2013_2.html
> [8]
> http://www.broadbandreports.com/forum/r27139468-Uverse-wants-me-to-change-my-network-address-
> [9]
> https://www22.verizon.com/support/residential/internet/highspeed/networking/troubleshooting/portforwarding/123897.htm
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130408/d23827a6/attachment.html>

------------------------------

_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml

End of ARIN-PPML Digest, Vol 94, Issue 26
*****************************************

Reply via email to