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-2: 3GPP Network IP Resource Policy
(Andrew Dul)
2. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(Michael Sinatra)
3. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(John Curran)
4. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(John Curran)
----------------------------------------------------------------------
Message: 1
Date: Sat, 06 Apr 2013 11:51:00 -0700
From: Andrew Dul <[email protected]>
To: [email protected], [email protected]
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-2: 3GPP Network IP
Resource Policy
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Inline
On 3/27/2013 11:32 AM, Scott Leibrand wrote:
> As one of the AC shepherds for the policy, I am hoping to have a
> discussion, both here on PPML at at the upcoming ARIN meeting, to
> cover a few key points:
>
> - Is the problem statement clear to the community? Do you have any
> questions on the problem the proposal is attempting to solve?
My read of the problem is that wireless operators have been using space
beyond RFC 1918 (such as 1.0.0.0/8) to solve their addressing needs and
now that this is becoming part of the "Internet" they need to move off
of that space.
>
> - Do you feel that it is an important problem to try to solve? Do
> you have any reasons you can share that we should or shouldn't do so?
>
With ARIN's /8 inventory currently at approximately 2.5, I'm skeptical
that any policy using global IPv4 unicast space can actually solve this
problem. Even if we were to give a whole /8 to this problem, I'm
doubtful that is enough address space to solve this problem.
Class E space is available...and so is IPv6 :)
One could also use 100.64.0.0/10
> - If so, how would you prefer we approach solving it? Some
> suggestions are outlined in the proposal below, but we'll need to
> decide on an approach and write and discuss actual policy text in
> order to move this Draft Policy forward. This proposal will *not* be
> eligible for last call after ARIN 31 in Barbados, but we will be
> discussing it there.
>
> So if you have any input now, please speak up. We'll be locking down
> the version of the Draft Policy that will be printed in the ARIN 31
> discussion guides by April 5th, so please provide any input you can
> before then.
I currently don't see any "policy text" as we've normally come to
expect. I'm certainly open to a discussion, but at this point we seem
to be discussing concepts and a method to work the problem rather than
specifically policy to solve the problem. It would be good to have some
strawman text to discuss rather than just the concepts.
>
> Thanks,
> Scott
>
>
> On Wed, Mar 27, 2013 at 11:20 AM, ARIN <[email protected]
> <mailto:[email protected]>> wrote:
>
> Draft Policy ARIN-2013-2
> 3GPP Network IP Resource Policy
>
> On 21 March 2013 the ARIN Advisory Council (AC) accepted
> "ARIN-prop-184 3GPP Network IP Resource Policy" as a Draft Policy.
>
> Draft Policy ARIN-2013-2 is below and can be found at:
> https://www.arin.net/policy/proposals/2013_2.html
>
> You are encouraged to discuss the merits and your concerns of
> Draft Policy 2013-2 on the Public Policy Mailing List. 2013-2 will
> also be on the agenda at the upcoming ARIN Public Policy Meeting
> in Barbados. The AC will evaluate the discussion in order to
> assess the conformance of this draft policy with ARIN's Principles
> of Internet Number Resource Policy as stated in the PDP.
> Specifically, these principles are:
>
> * Enabling Fair and Impartial Number Resource Administration
> * Technically Sound
> * Supported by the Community
>
> 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-2
> 3GPP Network IP Resource Policy
>
> Date: 27 March 2013
>
> Problem Statement:
>
> Current 3GPP architectures consist of hierarchical aggregation,
> from cell site up to anchor nodes, approximately one per NFL city.
> Anchor nodes are the point where IP addresses are assigned and
> topologically positioned in the network. Generally an anchor node
> must be provisioned with enough addresses to handle all
> simultaneously attached users, plus enough headroom to handle
> failover from an adjacent anchor node in the event of an outage.
> Capacity planning generally ensures that all anchor nodes have
> approximately the same number of attached users at steady state.
> Moving addresses between anchor nodes would require significant
> renumbering effort and substantial increases in operational
> complexity, so cannot be performed during an outage. Generally
> addresses are not renumbered between anchor nodes: instead,
> aggregation nodes can be rehomed as needed to balance steady state
> capacity levels. Because of the 3GPP architecture's failover and
> capacity planning requirements, all cellular networks target
> approximately 50% simultaneous usage of each anchor node's IP
> addresses. However, even at 50% usage, the total number of
> subscribers generally exceeds the number of addresses needed.
>
> Currently, a number of mobile networks are using non-RIR-assigned
> space internally to meet customer demand. However, there is
> insufficient private space (RFC1918, etc.) available for internal
> use, so other unassigned space is currently being used. As this
> unassigned space is brought into service via reclamation, returns,
> and transfers, it is no longer possible to use it internally, so
> globally unique space must be used instead. As a result, most of
> the need for additional RIR-assigned space is to serve existing
> customers, not to accommodate future growth.
>
> Policy statement:
>
> I can see two possible approaches to address this need. One
> approach would be to continue counting simultaneously attached
> users to measure IP needs, and apply a 50% usage requirement to
> justify allocations. Another approach would be to instead count
> total subscribers (rather than simultaneously attached users), and
> apply a much higher threshold, such as 80% or even 90%, to justify
> allocations.
>
> Timetable for implementation: ASAP
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]
> <mailto:[email protected]>).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] <mailto:[email protected]> if you
> experience any issues.
>
>
>
>
> _______________________________________________
> 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/20130406/9fcb66d4/attachment-0001.html>
------------------------------
Message: 2
Date: Sat, 06 Apr 2013 12:00:53 -0700
From: Michael Sinatra <[email protected]>
To: David Farmer <[email protected]>
Cc: [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=ISO-8859-1
On 03/27/13 17:45, David Farmer wrote:
> On 3/27/13 18:00 , Michael Sinatra wrote:
>
>> Or, to put more bluntly, if ARIN's fee structure is itself creating
>> disincentives for proper IPv6 adoption, then let's go back and (re-)fix
>> that problem.
>>
>> Oppose 2013-3.
>
> Michael and others opposed,
>
> What about modifying the proposal to /40, require a minimum reservation
> of /32 (or maybe /28) be held for ISPs that elect for /40 or /36
> allocations, allow subsequent allocations to expansion from /40 to /36
> and then to /32 without evaluating there current IPv6 usage. Thereby
> ensuring they can grow their allocation in place and allowing policy
> flexibility that enables the fee structure equity that the new xx-small
> category seems to provided.
Sorry to be responding to an earlier part of the thread, but I was on
vacation and lost track of this thread, and you did ask me a direct
question. I owe you the courtesy of an answer.
The answer to your question is no. If I start out with a /40 or /36 and
then rapidly grow into a /32 (and can justify the fees), then I am going
to end up with a largely organic addressing plan. We're giving
incentives for people to cram all of their addressing into a corner of
the total space that they should be using and it will create a really
messy IPv6 deployment.
Again, when did we decide that ARIN should encourage parsimonious *IPv6*
adoption?
One thing that I understand from 19 years working at a large state
university is a phenomenon called "ignoring the obvious solution." It's
like the doctor who keeps prescribing more drugs to a patient to deal
with the side effects of the drugs the patient is already on, rather
than finding the one drug that will solve the patient's problem with
minimal side-effects. When we face a big problem that should be tackled
head on, we instead try to work around it.
The big problem is that the fee schedule doesn't make sense. A
university with 5 /16s (IPv4) and 1 /32 (IPv6) is an "X-Large" in IPv4
and "Small" in IPv6. (Note that such a fee schedule will definitely not
encourage (L)RSA uptake, BTW.) It's increasingly hard to cut this new
fee schedule in a way that treats ISPs or end users consistently across
the two address families. This policy doesn't solve that problem, since
a big part of the problem is on the IPv4 side.
The second issue is that it's not even clear what the goals of the fee
schedule are. Are we trying to provide incentives for IPv6 uptake? For
IPv4 return? Are we trying to charge ISPs and end sites based on their
size? On their profits? (Address space allocations measure neither.)
[snip]
> Finally, even if you continue to not support the proposal would you
> support making the changes to the text about for the text to discuss at
> the PPM?
I couldn't quite parse this statement, but I think my answer is "yes."
I really appreciate the original author's work on this and your work as
shepherd, and I think the policy needs to be discussed. Still, I can't
support a policy that simply codifies the bad incentives that inhere in
the fee schedule.
michael
------------------------------
Message: 3
Date: Sun, 7 Apr 2013 02:31:21 +0000
From: John Curran <[email protected]>
To: Michael Sinatra <[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="Windows-1252"
On Apr 6, 2013, at 12:00 PM, Michael Sinatra <[email protected]> wrote:
> The second issue is that it's not even clear what the goals of the fee
> schedule are.
<https://www.arin.net/fees/faq_fee_schedule.html>
"
ARIN adopted the new Fee Schedule in order to:
? Ensure members receiving comparable services are paying comparable
fees where feasible
? Meet the community's expectations for new and future services such as
RPKI
? Maintain and reduce, where possible, cost for smaller ISPs
? Provide a revenue model based on long-term expenses
"
(This is also very similar to the information in community
consultation held in October 2012 on the Revised Fee schedule.)
Note that the present fee schedule does not provide an xx-small
size category at all, and the fees associated with the current
x-small category are also lowered by the Revised Fee schedule.
> Are we trying to provide incentives for IPv6 uptake? For IPv4 return?
We're trying to provide more more uniform fee categories and
introduce lower fees for both x-small and xx-small ISPs as
noted in the Revised Fee schedule faq.
> Are we trying to charge ISPs and end sites based on their size?
> On their profits?
> (Address space allocations measure neither.)
ARIN has always had fees based on relative size of organizations,
generally based on the total address space held. This is the case
with both the present fee schedule and the Revised Fee Schedule.
FYI,
/John
John Curran
President and CEO
ARIN
------------------------------
Message: 4
Date: Sun, 7 Apr 2013 02:58:23 +0000
From: John Curran <[email protected]>
To: Seth Mattinen <[email protected]>
Cc: "[email protected]" <[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 5, 2013, at 9:37 AM, Seth Mattinen <[email protected]> wrote:
> I see no reason to have a policy motivated strictly by fees to remain after
> fee changes that may or may not negate it, and to determine that it should go
> back through the PDP. Otherwise we're just cluttering the NRPM with
> irrelevant policy.
Seth -
The ARIN Board has often lowered the fee schedule as the
financial circumstances allow, and in general this has been
independent of number resource policy changes.
The Revised Fee schedule is much improved over the existing
fee schedule with respect to organizations being able to
cost-effectively make use of IPv6 (as it is lower than the
existing fee schedule's smallest IPv6 category today.)
If the community does not support 2013-3, then smaller ISPs
will still have the current option of receiving a /36 of IPv6
(if they wish); this will put them in the x-small fee category
of $1000 per year.
If the community supports 2013-3, then some very small ISPs will
gain an option of taking a /40 allocation of IPv6 space, which
will put them in the xx-small fee category with fees of $500 per
year.
If very small ISPs receiving /40 of IPv6 space does not make good
technical sense, then the community should not support the draft
policy... it's that simple. (These ISPs will still have lower fees
under the Revised Fee schedule, just not as low as they might have
had otherwise...)
Thanks!
/John
John Curran
President and CEO
ARIN
------------------------------
_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml
End of ARIN-PPML Digest, Vol 94, Issue 13
*****************************************