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
(Steven Noble)
2. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(John Curran)
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
(Steven Ryerse)
----------------------------------------------------------------------
Message: 1
Date: Sun, 7 Apr 2013 10:44:58 -0700
From: Steven Noble <[email protected]>
To: John Curran <[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
Hi John,
On Apr 7, 2013, at 10:35 AM, John Curran <[email protected]> wrote:
>>
> Steve -
>
> The prior fee was $100 per year for all your resources;
> I am uncertain why you felt it was $30?
I registered my ASN in 2000, at that time I was charged a $30 maintenance fee
for the ASN.
>
> The revised fee schedule changes this for end-users and
> legacy holders to $100 per year per resource record.
Which is again higher than the $30 that I originally paid before the
"consolidated" fee.
>
>> Why not make a sliding scale? Those who consume more resources as a single
>> ORG pay more: $30 for first ASN, $60 for second, etc.
>
> It is a sliding scale under the revised fee schedule for
> end-users and legacy holders, but at $100 per record not
> $30 per record as you suggest.
A sliding scale would start small for 1 ASN and then get larger (more than +n)
for each ASN after that. If someone holds 1 ASN, they would pay $30, if
someone holds 2, they would pay $90, 3 ASNs would be $210, that type of a
sliding scale.
>>
>> I believe it will allow for more IPv6 deployment which is the end goal. I
>> can debate in my head paying $500 to have IPv6 PI space, I cannot justify
>> paying $1000+ yearly.
>
> That is helpful to know - Thank you!
No problem, obviously lower costs help push adoption. If the cost of getting
IPv6 is less than requesting both IPv4 and IPv6 it makes sense to me.
------------------------------
Message: 2
Date: Sun, 7 Apr 2013 17:55:10 +0000
From: John Curran <[email protected]>
To: Steven Noble <[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 10:44 AM, Steven Noble <[email protected]>
wrote:
> Hi John,
>
> On Apr 7, 2013, at 10:35 AM, John Curran <[email protected]> wrote:
>
>>>
>> Steve -
>>
>> The prior fee was $100 per year for all your resources;
>> I am uncertain why you felt it was $30?
>
> I registered my ASN in 2000, at that time I was charged a $30 maintenance fee
> for the ASN.
Now I understand... Thank you.
>> It is a sliding scale under the revised fee schedule for
>> end-users and legacy holders, but at $100 per record not
>> $30 per record as you suggest.
>
> A sliding scale would start small for 1 ASN and then get larger (more than
> +n) for each ASN after that. If someone holds 1 ASN, they would pay $30, if
> someone holds 2, they would pay $90, 3 ASNs would be $210, that type of a
> sliding scale.
I'd like to see the fee per record be reduced to $75 (or even
lower) over time but we need to use care in doing so and cannot
head that direction until we understand long-term if ISP and
end-user fees are to be harmonized or kept distinct (while the
services are very similar, arguing for similar fees, there is
a argument to be made that the end-users do not benefit "as a
business" in the ways that the ISPs do, and hence should always
have a distinct lower fee schedule.)
Thanks!
/John
John Curran
President and CEO
ARIN
------------------------------
Message: 3
Date: Sun, 7 Apr 2013 18:03:53 +0000
From: John Curran <[email protected]>
To: cb.list6 <[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="iso-8859-1"
On Apr 7, 2013, at 10:30 AM, "cb.list6"
<[email protected]<mailto:[email protected]>> wrote:
Generally speaking we need to move away from conservation as goal for both ipv4
and ipv6
Structurally there is no need in v6 and the market will force it in v4
conservation at the rir level creates costly externalities in routing and other
areas such as system design.
Ripe is on the right track http://www.ripe.net/ripe/policies/proposals/2013-03
CB -
Could you be a little more specific with regards to whether you support
"Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs"? It would
provide an option for ISPs who wish to be issued IPv6 allocations of
/40, which is smaller than present policy allows. The referenced RIPE
policy proposal is with regards to IPv4 allocation policy, not IPv6, so
it is hard to discern whether you support allowing ISPs to request a
smaller allocation if they wish to.
Thanks!
/John
John Curran
President and CEO
ARIN
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130407/a07da1fc/attachment-0001.html>
------------------------------
Message: 4
Date: Sun, 7 Apr 2013 19:33:26 +0000
From: Steven Ryerse <[email protected]>
To: cb.list6 <[email protected]>, Matthew Kaufman
<[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-3: Tiny IPv6
Allocations for ISPs
Message-ID:
<5b9e90747fa2974d91a54fcfa1b8ad12012f5cc...@eni-mail.eclipse-networks.com>
Content-Type: text/plain; charset="utf-8"
I agree with Mathew and CB. We do need to move away from conservation at the
RIR level as a goal for both ipv4 and ipv6. Ripe is definitely on the right
track with http://www.ripe.net/ripe/policies/proposals/2013-03 and I strongly
support that. The same changes should happen for the Arin RIR.
The IPv6 pricing issue is a difficult one in a world that is still IPv4
oriented. We purchased an IPv6 block in the Small category (/32) from Arin
last year for $2250 less the 25% discount of $562.50 for a total of $1687.50.
At the time I felt that was expensive since less than 5% of Internet traffic
runs on IPv6 - but that was the cost so I made a business decision to pay it.
We run BGP with IPv4 and we wanted to also run BGP with IPv6 which is why we
purchased the block. To my surprise ? only one of my upstream providers has
implemented IPv6 and of course we are in a 3 year agreement with them for their
Metro-E line. They are a CLEC and they tell me that they have only had about 6
inquires about running IPv6.
So now just today I received my renewal bill for our IPv6 block and it is again
for $1687.50. Now I have to make a business decision on whether to pay it and
hope I can twist our CLEC?s arm to support IPv6 - or let it lapse and wait
until the end of our contract and switch upstream providers - and pay for
another IPv6 allocation at that time.
My preference would be to renew but not using an assigned IPv6 block for two
years will costs me $3375 (even in the Small category) and if I can?t use it
then I get no benefit for it. This is the real world of IPv6 and I am
definitely for less expensive blocks for IPv6 and for allocations of extra
small blocks of the Tiny size to further Arin?s Mission.
I am for a Tiny IPv6 option for small ISP?s - but at an attractive price -
because that is in line with Arin?s mission of allocating resources. I think
even with the 25% discount all of the current IPv6 prices are too high for the
current value being received from them. The price should be at least somewhat
in line with the value that can be derived from the IPv6 resource. Adoption of
IPv6 needs to be a high priority and the best way to make that happen is to
allocate IPv6 of all sizes at a maybe 50% or more discount until the adoption
is at a higher percentage ? maybe 15%-20% or more. I do think the entire fee
Arin fee schedule needs to be enough for Arin to pay its bills.
P.S. The email I just received says at the bottom of it that the Board
approved a new fee schedule in January effective July. Maybe I missed
something but I didn?t see any discussion of a totally new fee schedule
discussed in this forum. While I acknowledge that Arin?s Board has the right
and responsibility to set fees independent of this forum ? as there are a
number of smart experienced folks participating in this forum ? this
community?s input might have helped develop a better outcome for all. I?m
guessing there would have been a lot of constructive feedback provided ? just
like there has been on the fees portion of the Tiny IPv6 policy.
Steven L Ryerse
President
100 Ashford Center North, Suite 110, Atlanta, GA 30338
770.656.1460 - Cell
770.399.9099 - Office
770.392-0076 - Fax
[Description: Description: Description: Eclipse Networks Logo_small.png]?
Eclipse Networks, Inc.
Conquering Complex Networks?
From: [email protected] [mailto:[email protected]] On Behalf
Of cb.list6
Sent: Sunday, April 07, 2013 1:31 PM
To: Matthew Kaufman
Cc: [email protected]
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-3: Tiny IPv6 Allocations forISPs
On Apr 6, 2013 10:14 PM, "Matthew Kaufman"
<[email protected]<mailto:[email protected]>> wrote:
>
> On 4/6/2013 12:00 PM, Michael Sinatra wrote:
>>
>> 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.
>
>
> Worse, we're creating a messy IPv6 situation downstream... as Owen points
> out, this type of financial pressure towards false conservation is going to
> give us things like /64-per-household instead of something sensible that lets
> the thermostat be on a different subnet than the Xbox.
>
> We should be telling ISPs of all sizes "IPv6 is huge... come get a /32 or
> bigger... do sensible things when you make your addressing plans... do
> sensible things when you sell service to your customers" and not "here's a
> way to save a buck by pretending IPv6 is like IPv4"
>
> You're right (in the part below that I deleted)... the bug is the fee
> structure and there's absolutely no reason to try to muck with the policy,
> which can't possibly fix the real problem.
>
> Matthew Kaufman
>
Generally speaking we need to move away from conservation as goal for both ipv4
and ipv6
Structurally there is no need in v6 and the market will force it in v4
conservation at the rir level creates costly externalities in routing and other
areas such as system design.
Ripe is on the right track http://www.ripe.net/ripe/policies/proposals/2013-03
CB.
> _______________________________________________
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130407/811dcd36/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1473 bytes
Desc: image001.jpg
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130407/811dcd36/attachment.jpg>
------------------------------
_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml
End of ARIN-PPML Digest, Vol 94, Issue 17
*****************************************