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: Justifying an ISP /22 (Jimmy Hess)
2. Re: Justifying an ISP /22 (Randy Carpenter)
3. Re: Justifying an ISP /22 (Owen DeLong)
----------------------------------------------------------------------
Message: 1
Date: Wed, 17 Apr 2013 19:14:18 -0500
From: Jimmy Hess <[email protected]>
To: Randy Carpenter <[email protected]>
Cc: [email protected]
Subject: Re: [arin-ppml] Justifying an ISP /22
Message-ID:
<caaawwbxnol+ldent-4cz15u8mwjam+_qlgsyd4detdm8bkd...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 4/16/13, Randy Carpenter <[email protected]> wrote:
[snip]
> 3. Have upstream ISPs that refuse to hand out any more PA space (which
> appears to be the rule rather than the exception now) (I'm not sure how one
> would go about proving this, but I have seen situations where the upstream
> would likely write a letter of support)
[snip]
So the concern is... if ARIN adopts a policy allowing additional IP
addresses to be acquired specifically if the ISP refuses to allocate
them to satisfy the justified need; ARIN could essentially be
encouraging the ISP to collude with the subscriber, and refuse to
allocate.
Because the service provider's benefits of refusing increase then;
they can still provide the subscriber service, after refusing them IP
addresses (thanks to the subscriber's suddenly gained ability to get
addresses through ARIN).
The subscriber receives benefit of (1), the space they want, and (2)
the addresses in PI format, which is more desirable.
The benefit the ISP receives is (1) they conserve what PA space they
still have available, for use with higher evenue, or applications
where the allocation requirement cannot be offloaded. (2) they
might still in some cases be "inadvertently" using that subscriber's
service to justify certain future allocations.
--
-JH
------------------------------
Message: 2
Date: Wed, 17 Apr 2013 20:51:56 -0400 (EDT)
From: Randy Carpenter <[email protected]>
To: Jimmy Hess <[email protected]>
Cc: [email protected]
Subject: Re: [arin-ppml] Justifying an ISP /22
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> On 4/16/13, Randy Carpenter <[email protected]> wrote:
> [snip]
> > 3. Have upstream ISPs that refuse to hand out any more PA space (which
> > appears to be the rule rather than the exception now) (I'm not sure how one
> > would go about proving this, but I have seen situations where the upstream
> > would likely write a letter of support)
> [snip]
Yeah, that part is a little too specific, and I would say unnecessary, provided
proper re-working of the other parts. (lowering to a /22 from a /20 is the big
one)
> So the concern is... if ARIN adopts a policy allowing additional IP
> addresses to be acquired specifically if the ISP refuses to allocate
> them to satisfy the justified need; ARIN could essentially be
> encouraging the ISP to collude with the subscriber, and refuse to
> allocate.
I think there is almost the same incentive for collusion now:
Upstream: "I'll give you a /20 for a month (just log enough for you to get PI
space from ARIN)"
ISP: "Sounds good. I'll put it in production on some dynamic IP customers, for
which changing is easy"
Upstream: "Here ya go."
ISP: "Thanks, I'm now done with it"
Upstream: Rinse, repeat.
This is all perfectly within the policies of the NRPM as far as I can tell.
I have been party to very similar conversations before. I have always looked
(and continue to) for ways of accomplishing the desired result without
resorting to such a situation.
-Randy
------------------------------
Message: 3
Date: Wed, 17 Apr 2013 21:38:09 -0600
From: Owen DeLong <[email protected]>
To: "Otis L. Surratt, Jr." <[email protected]>
Cc: [email protected]
Subject: Re: [arin-ppml] Justifying an ISP /22
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Apr 17, 2013, at 3:41 PM, "Otis L. Surratt, Jr." <[email protected]> wrote:
> Jumping on ppml late..
>
> Randy,
>
>> 1. Be an ISP with *any* amount of space from an upstream
>
> I'm not so sure this would be advisable? Wouldn't it be better to have
> at least a /24? Or is this what you had in mind?
>
In at least one case, part of the problem is he can't even get a /24 from his
upstreams. This will become a more and more prevalent problem as runout
continues to progress.
>> 2. Be able to justify a 3-month need for a /22
>> 3. Have upstream ISPs that refuse to hand out any more PA space (which
> appears to be the rule rather than the exception now) (I'm not sure how
> one would go about proving this, but I have seen situations where the
> upstream would likely write a letter of support)
I'm not sure we need to include this as a criteria anyway.
>> 4. Be forced to take an automatic IPv6 allocation (at whatever
> NRPM-supported size is appropriate (preferably /32 min.))
I'm not sure I buy this, either. As much as I support IPv6 and favor increased
IPv6 rollout (the sooner we're off v4 the better we will all be), I don't
believe
that inflicting IPv6 allocations on people that aren't ready to ask for them
does
anything other than skew statistics.
Owen
>
------------------------------
_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml
End of ARIN-PPML Digest, Vol 94, Issue 38
*****************************************