[arin-ppml] Advisory Council Meeting Results - March 2012
owen at delong.com
Tue Mar 13 17:33:46 EDT 2012
On Mar 13, 2012, at 1:09 PM, Scott Leibrand wrote:
> On Tue, Mar 13, 2012 at 12:37 PM, ARIN <info at arin.net> wrote:
> In accordance with the ARIN Policy Development Process, the ARIN Advisory Council (AC) held a meeting on 8 March 2012 and made decisions about several proposals.
> The AC selected the following proposals as draft policies for adoption
> discussion online and at the ARIN XXIX Public Policy Meeting in
> Vancouver in April. The draft policies will be posted shortly to the PPML.
> ARIN-prop-157 Section 8.3 Simplification
> This is a revised version that the AC also retitled to "ASN transfers". The revised draft policy text is short enough to post here:
> In NRPM 8.3, replace "IPv4 number resources" with "IPv4 number resources and ASNs".
> I personally feel that while there is not a compelling need to be able to transfer ASNs as there was/is with IPv4 addresses, that there are legitimate use cases, and very few downsides that I can see to allowing it.
Scott has not yet been able to articulate to me use cases that I consider particularly legitimate, so, community input in that regard would be helpful.
Personally, I don't feel that there is a compelling need for this. Further, given the number of problems we have already created by opening up a market in IPv4 number resources, I really feel that it is imprudent to expand this strategy before we've had time to better understand the ramifications of such a transfer policy and work out some of the policy kinks.
There was urgency and a necessity for implementing an IPv4 resource transfer policy and process. I see no such urgency for ASN transfers and I don't think we need to be creating more headaches for staff and more policy problems for ourselves at this time.
I supported the motion to discuss this with the community, but, as it currently stands, I do not support the draft policy.
> ARIN-prop-162 Redefining request window in 22.214.171.124
> This was also re-titled to "Return to 12 Month Supply and Reset Trigger to /8 in Free Pool".
> In my opinion we have (perhaps unintentionally) achieved somewhat of a "soft landing" with the current policy that allows for 3 month allocations from the free pool and 24 months worth of space via transfer. I don't think moving back to a 12 month free pool supply will be helpful, but I voted to put this on the agenda for Vancouver because I think we need to have a full discussion on it.
It is my opinion that we missed the target on the soft landing we were trying to achieve and we have actually caused quite a bit of harm in the process. When we passed the soft landing proposal, we did not realize that there would be a significant difference between the time that ARIN received its last /8 from IANA and the time that ARIN would be starting to consume that last /8 for address allocations.
It was much easier to codify the IANA date than the ARIN free pool based date which resulted in policy that was easier to read and understand. Unfortunately, since the dates ended up being far apart, it is having significant impact to a number of organizations in the ARIN constituency and I believe we should correct this mistake post haste. On the other hand, if we debate the issue long enough, it will become moot in 1-2 policy cycles.
> The AC abandoned the following proposal:
> ARIN-prop-165 Eliminate Needs-Based Justification on 8.3 Specified Transfers
> The AC provided the following statement about prop-165:
> "Based on significant community opposition to the removal of the needs
> requirement in 8.3 transfers, the AC chose to abandon proposal 165. While the author has brought to light privately additional issues, most of them are procedural in nature and would require a complete rewrite of both the policy and rationale text well beyond the original proposal's intent. The AC feels that there is merit in the discussion of these issues, and suggests that the author look at more specific issues outside of removal of needs, that could be applied to new proposal submissions."
> I was in the minority here, largely because I think this is an important issue that should be discussed at the public policy meeting. (I was not in favor of putting this particular text up for adoption discussion, and in any event, it was received too late to make the timeline for Vancouver).
> Given that the majority of the AC (and the community) opposed this particular text, I would agree with the statement above that "The AC feels that there is merit in the discussion of these issues, and suggests that the author look at more specific issues outside of removal of needs, that could be applied to new proposal submissions." I look forward to having such discussion at upcoming meeting(s) and working towards a consensus proposal for how to assess needs basis on transfers, particularly after the free pool is empty.
It might be an important issue. However, it is an issue that has been discussed, re-discussed, and discussed again. The community each and every time this has come up has resoundingly responded with opposition to eliminating needs basis. Further, we structured our response to inter-RIR transfers to say "agree to needs basis or go play in your own sandbox
without access to resources from the ARIN community". That was almost the only aspect of inter-RIR transfers that had
really wide community consensus from the start.
I'm not saying we shouldn't discuss it further, but, this proposal in anything remotely resembling its current form had such overwhelming community opposition that I felt any action other than abandonment would have been disingenuous to the community and to the author.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARIN-PPML