[arin-ppml] Clarification on AC Abandonment of Prop-176: Increasing Justification to 60 Months

jeffmehlenbacher at ipv4marketgroup.com jeffmehlenbacher at ipv4marketgroup.com
Mon Jul 30 10:13:20 EDT 2012


David / Scott,

Thanks for the background on the decision and your further thoughts on
the subject.

Jeff Mehlenbacher




-------- Original Message --------
Subject: Re: [arin-ppml] Clarification on AC Abandonment of Prop-176:
Increasing Justification to 60 Months
From: David Farmer <farmer at umn.edu>
Date: Fri, July 27, 2012 1:50 pm
To: Scott Leibrand <scottleibrand at gmail.com>
Cc: jeffmehlenbacher at ipv4marketgroup.com, "arin-ppml at arin.net"
<arin-ppml at arin.net>, David Farmer <farmer at umn.edu>

I'm also very interested in there being a discussion of this issue. 
However, I voted to abandon this proposal mostly to try to clam things 
down a bit, wanting to focus the discussion on what the proper next 
steps are and what the time table should be. Rather than arguing about 
the merits of this specific proposal especially its 60 month window 
which I'm highly skeptical of being able to achieve consensus.

There are a number of moving pieces here, 24 months only went into 
effect in February, Inter-RIR transfers should go into effect in the 
next week or so. While I generally support moving beyond 24 months, I 
would prefer to be cautious about when to do it. I supported 24 months 
last fall because while longer than ARIN had normally done, it is not 
without precedent in the RIR policy space, and it was clear to me that 
we needed a longer window than 12 months. I'm not aware on any RIR ever 
having a longer window than 24 months, so 24 months immediately and 
longer over time seemed like a reasonable but cautious path forward..

On the other I'm not saying that 60 months is complete out of the 
questions either, there are valid business reasons for that number too. 
 I fully support a 60 month planing horizon for IPv6, I'm just not 
convinced that 60 months is reasonable for IPv4 at this point in its 
life cycle.

I would like to suggest the proper focus for ARIN policy is not the 
success or failure of the IPv4 transfer market place, but the success or

failure or the Internet market place. I personally believe that they 
are not mutually exclusive, they are interdependent, but the short and 
long term health of the Internet market place is way more important than

the IPv4 transfer market place, not the other way around.

Thanks

On 7/27/12 09:22 CDT, Scott Leibrand wrote:
> Jeff,
>
> While the majority of the AC disagreed with my opinion that it would be
> best to have this proposal on the docket for discussion in October,
> everyone did seem to agree that this was an important issue to discuss.
> ARIN does report on registration and transfer activity at each
> meeting: I will be particularly interested to see how inter-RIR
> transfers play out over the first few months they're available. If/when
> you have any insight there, I'd like to hear it as well.
>
> -Scott
>
> On Fri, Jul 27, 2012 at 10:12 AM, <jeffmehlenbacher at ipv4marketgroup.com
> <mailto:jeffmehlenbacher at ipv4marketgroup.com>> wrote:
>
> Thank you Kevin. It will then be interesting to understand what metrics
> are being applied and monitored to determine whether 24 months is an
> appropriate duration for justification. The onus for change should not
> be on external parties, but rather, ARIN staff should produce statistics
> that support the AC's assertion that 24 months is appropriate.
>
> Jeff Mehlenbacher
>
> -------- Original Message --------
> Subject: RE: [arin-ppml] Clarification on AC Abandonment of Prop-176:
> Increasing Justification to 60 Months
> From: Kevin Blumberg <kevinb at thewire.ca ><mailto:kevinb at thewire.ca>>
> Date: Fri, July 27, 2012 9:45 am
> To: "jeffmehlenbacher at ipv4marketgroup.com
> <mailto:jeffmehlenbacher at ipv4marketgroup.com>"
> <jeffmehlenbacher at ipv4marketgroup.com
> <mailto:jeffmehlenbacher at ipv4marketgroup.com>>, "arin-ppml at arin.net
> <mailto:arin-ppml at arin.net>"
> <arin-ppml at arin.net ><mailto:arin-ppml at arin.net>>
>
> Jeff,
>
> It was a mistake on my part. I apologize. It should of read as:
>
> 176. "The ARIN Advisory Council voted not to accept onto the
> docket,ARIN-prop-176 "Increase Needs-Based Justification to 60 months".
> The AC feels that with the change to 24 month window in 8.3 having
> recently
> been implemented, it would be premature to increase the window of
> justification.
> As well there was concern over 60 month networking plans being
> speculative
> and difficult to evaluate."
>
> Thanks,
>
> Kevin Blumberg
>
> > -----Original Message-----
> > From: arin-ppml-bounces at arin.net
> <mailto:arin-ppml-bounces at arin.net>
> [mailto:arin-ppml-bounces at arin.net
> <mailto:arin-ppml-bounces at arin.net>] On
> > Behalf Of jeffmehlenbacher at ipv4marketgroup.com
> <mailto:jeffmehlenbacher at ipv4marketgroup.com>
> > Sent: Friday, July 27, 2012 7:58 AM
> > To: arin-ppml at arin.net <mailto:arin-ppml at arin.net>
> > Subject: [arin-ppml] Clarification on AC Abandonment of Prop-176:
> Increasing
> > Justification to 60 Months
> >
> > I wonder if a representative of the AC might clarify the
> following statement
> > relating to the abandonment of Prop-176:
> >
> > 176. "The ARIN Advisory Council voted not to accept onto the
> > docket,ARIN-prop-176 "Increase Needs-Based Justification to 60
> months".
> > The AC
> > feels that with the change to 24 month window in 8.3 having not
> yet been
> > implemented, it would be premature to increase the window of
> justification.
> > As well there was concern over 60 month networking plans being
> speculative
> > and difficult to evaluate."
> >
> > I actually do not understand the language above...24 months was
> approved
> > and implemented on February 10th, 2012.
> >
> > Any clarification would be appreciated.
> >
> > Jeff Mehlenbacher
> > IPv4 Market Group
> >
> > _______________________________________________
> > PPML
> > You are receiving this message because you are subscribed to the ARIN
> > Public Policy Mailing List (ARIN-PPML at arin.net
> <mailto:ARIN-PPML at arin.net>).
> > Unsubscribe or manage your mailing list subscription at:
> > http://lists.arin.net/mailman/listinfo/arin-ppml
> > Please contact info at arin.net <mailto:info at arin.net> if you
> experience any issues.
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net
> <mailto:ARIN-PPML at arin.net>).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net <mailto:info at arin.net> if you
> experience any issues.
>
>
>
>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>

-- 
===============================================
David Farmer Email:farmer at umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota 
2218 University Ave SE Phone: 612-626-0815
Minneapolis, MN 55414-3029 Cell: 612-812-9952
===============================================



More information about the ARIN-PPML mailing list