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
(Owen DeLong)
2. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(Owen DeLong)
3. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(Seth Mattinen)
4. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(David Farmer)
5. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(Seth Mattinen)
6. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(Kevin Kargel)
7. Re: Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs
(William Herrin)
----------------------------------------------------------------------
Message: 1
Date: Fri, 5 Apr 2013 08:58:22 -0700
From: Owen DeLong <[email protected]>
To: David Farmer <[email protected]>
Cc: ARIN 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
How about "...expand the allocation to any nibble aligned size up to /32
without renumbering or additional..."
Owen
On Apr 5, 2013, at 06:45 , David Farmer <[email protected]> wrote:
> On 4/5/13 08:31 , William Herrin wrote:
>> On Fri, Apr 5, 2013 at 8:23 AM, David Farmer <[email protected]> wrote:
>>> g. An LIR that requests a smaller /36 or /40 allocation is entitled to
>>> expand the allocation to /32 or /36 at any time without renumbering or
>>> additional justification.
>>
>> Hi David,
>>
>> This could be misread to mean "/32 or /36 respectively" instead of
>> "either /32 or /36 as the registrant chooses."
>
> That's was bugging me too, but I wasn't sure how to fix it. How about;
>
> g. An LIR that requests a smaller /36 or /40 allocation is entitled to expand
> the allocation to either /32 or /36 at any time without renumbering or
> additional justification. ...
>
> Does that cover it without getting to wordy?
>
>>> e. All returned block(s) must not be in use by the organization or its
>>> customers.
>>
>> This verbiage is a little clumsy. I'm not sure how to word it better.
>
> How about;
>
> e. All block(s) returned must not be in use by the organization or its
> customers.
>
> Not a big change but it read a little better.
>
>
> --
> ================================================
> David Farmer Email: [email protected]
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE Phone: 1-612-626-0815
> Minneapolis, MN 55414-3029 Cell: 1-612-812-9952
> ================================================
> _______________________________________________
> 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.
------------------------------
Message: 2
Date: Fri, 5 Apr 2013 09:07:07 -0700
From: Owen DeLong <[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=windows-1252
> a. The end result is not an increase in the number of aggregatable blocks
> held by the organization.
>
This is problematic. This would allow an increase in the number of
non-aggregatable blocks. While I'm not 100% sure that it is possible to create
such a situation, I would rather see us express the direct intent. How about:
a. The resulting number of aggregate retained blocks must 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 returned block(s) must not be 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 of the community
> would prefer /32 be the sole minimum allocation size for ISPs and other LIRs,
> and they feel there is no need for smaller /36 or /40 allocations. They
> would prefer to solve the problem with changes in the fee structure rather
> than contorting number resource policy to solve the problem. However, there
> are to 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.
I would not call this "A significant minority". Rather, I would say that a
significant minority are adamant to the extent they oppose this policy. I
believe the vast majority of the community would prefer to see /32 be the sole
minimum, but that most are willing to accept the tradeoffs incorporated into
this policy. I believe that if we had an effective way to solve the problem
through fee structure changes that was acceptable to the vast majority, it
would be the preferred solution. I encourage anyone who has ideas of such a
solution to please make them known to the community either here or on
arin-discuss. While fees are outside of the policy process, at the point we
start contorting policy to address problems with the fee structure, I certainly
think it is appropriate to discuss the problems with the fee structure directly
in that context.
> 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 ISPs to make the decision to select from a /32, /36 or /40 initial
> allocation based solely on their own internal business justifications, and
> eliminating 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 servers.
I would rather see the reservation set to a minimum of /28, personally, but /32
is better than smaller.
Is there anyone in the community that objects to a minimum /28 reservation
(which is the current situation for recipients of /32s)?
Owen
------------------------------
Message: 3
Date: Fri, 05 Apr 2013 09:24:50 -0700
From: Seth Mattinen <[email protected]>
To: [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; format=flowed
On 4/4/13 3:53 PM, David Farmer wrote:
>
> If the lower ones go a way then, as was said no one in their right mind
> would choose /36 or /40. I can't imagine anything smaller, I just don't
> see room for more changes one the smaller side. At least without
> changing the IPv6 architecture and the /64 subnet standard, and that
> would be a big enough change that a whole bunch of assumptions need to
> change not just this one.
I would want to see verbiage in the policy that would immediately
revoke/revert it if any fee schedule changes are made. If we're going to
start making policy based on the fees then we should have to rerun them
through the them the PDP anytime the fees they are based on change.
~Seth
------------------------------
Message: 4
Date: Fri, 05 Apr 2013 11:31:53 -0500
From: David Farmer <[email protected]>
To: Seth Mattinen <[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; format=flowed
On 4/5/13 11:24 , Seth Mattinen wrote:
> On 4/4/13 3:53 PM, David Farmer wrote:
>>
>> If the lower ones go a way then, as was said no one in their right mind
>> would choose /36 or /40. I can't imagine anything smaller, I just don't
>> see room for more changes one the smaller side. At least without
>> changing the IPv6 architecture and the /64 subnet standard, and that
>> would be a big enough change that a whole bunch of assumptions need to
>> change not just this one.
>
> I would want to see verbiage in the policy that would immediately
> revoke/revert it if any fee schedule changes are made. If we're going to
> start making policy based on the fees then we should have to rerun them
> through the them the PDP anytime the fees they are based on change.
I'm not going to include that right now but I will raise that question
at the Barbados meeting.
--
================================================
David Farmer Email: [email protected]
Office of Information Technology
University of Minnesota
2218 University Ave SE Phone: 1-612-626-0815
Minneapolis, MN 55414-3029 Cell: 1-612-812-9952
================================================
------------------------------
Message: 5
Date: Fri, 05 Apr 2013 09:37:13 -0700
From: Seth Mattinen <[email protected]>
To: [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; format=flowed
On 4/5/13 9:31 AM, David Farmer wrote:
> On 4/5/13 11:24 , Seth Mattinen wrote:
>> On 4/4/13 3:53 PM, David Farmer wrote:
>>>
>>> If the lower ones go a way then, as was said no one in their right mind
>>> would choose /36 or /40. I can't imagine anything smaller, I just don't
>>> see room for more changes one the smaller side. At least without
>>> changing the IPv6 architecture and the /64 subnet standard, and that
>>> would be a big enough change that a whole bunch of assumptions need to
>>> change not just this one.
>>
>> I would want to see verbiage in the policy that would immediately
>> revoke/revert it if any fee schedule changes are made. If we're going to
>> start making policy based on the fees then we should have to rerun them
>> through the them the PDP anytime the fees they are based on change.
>
> I'm not going to include that right now but I will raise that question
> at the Barbados meeting.
>
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
------------------------------
Message: 6
Date: Fri, 5 Apr 2013 11:41:41 -0500
From: Kevin Kargel <[email protected]>
To: "[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"
I am still trying to figure out how having one *additional* database entry
costs $1000/year.
Kevin
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Seth Mattinen
Sent: Friday, April 05, 2013 11:37 AM
To: [email protected]
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for
ISPs
On 4/5/13 9:31 AM, David Farmer wrote:
> On 4/5/13 11:24 , Seth Mattinen wrote:
>> On 4/4/13 3:53 PM, David Farmer wrote:
>>>
>>> If the lower ones go a way then, as was said no one in their right
>>> mind would choose /36 or /40. I can't imagine anything smaller, I
>>> just don't see room for more changes one the smaller side. At least
>>> without changing the IPv6 architecture and the /64 subnet standard,
>>> and that would be a big enough change that a whole bunch of
>>> assumptions need to change not just this one.
>>
>> I would want to see verbiage in the policy that would immediately
>> revoke/revert it if any fee schedule changes are made. If we're going
>> to start making policy based on the fees then we should have to rerun
>> them through the them the PDP anytime the fees they are based on change.
>
> I'm not going to include that right now but I will raise that question
> at the Barbados meeting.
>
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
_______________________________________________
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.
------------------------------
Message: 7
Date: Fri, 5 Apr 2013 12:45:04 -0400
From: William Herrin <[email protected]>
To: Kevin Kargel <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-3: Tiny IPv6
Allocations for ISPs
Message-ID:
<cap-gugu2ky82mgn5fm7ktzwp3k2-5fpoxb778ghub10cv-o...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Fri, Apr 5, 2013 at 12:41 PM, Kevin Kargel <[email protected]> wrote:
> I am still trying to figure out how having one *additional* database entry
> costs $1000/year.
Registration in the database: $25/year
Your share of the overhead costs of running a registry: $975/year
Regards,
Bill Herrin
--
William D. Herrin ................ [email protected] [email protected]
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
------------------------------
_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml
End of ARIN-PPML Digest, Vol 94, Issue 10
*****************************************