As some people seem to find it useful, I'll inject my own personal opinions on these inline...<br><br><div class="gmail_quote">On Tue, May 24, 2011 at 12:04 PM, ARIN <span dir="ltr"><<a href="mailto:info@arin.net">info@arin.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">In accordance with the ARIN Policy Development Process the ARIN Advisory<br>
Council (AC) held a meeting on 19 May 2011 and made decisions about<br>
several draft policies and proposals.<br>
<br>
The AC recommended the following draft policies to the ARIN Board for<br>
adoption:<br>
<br>
ARIN-2011-3: Better IPv6 Allocations for ISPs (revised)<br>
ARIN-2011-4: Reserved Pool for Critical Infrastructure<br>
ARIN-2011-5: Shared Transition Space for IPv4 Address Extension<br>
ARIN-2011-6: Returned IPv4 Addresses<br>
<br>
ARIN-2011-3 was revised. The renumbering requirement in 6.5.7 was<br>
removed. This was an oversight; it was something that was discussed<br>
before and during Last Call.<br></blockquote><div><br></div><div>IMO these were all pretty clearly supported by the community during Last Call, and are generally good ideas. I won't rehash any of the arguments here.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The following draft policy remains on the AC's docket (motions to send<br>
to last call and to abandon were unsuccessful):<br>
<br>
ARIN-2011-1: Globally Coordinated Transfer Policy<br></blockquote><div><br></div><div>There was quite a bit of concern around whether this one is ready to go to Last Call (based on solid consensus for the idea in principle), or whether the revisions since Puerto Rico have sufficiently addressed the community (and AC members') concerns with the original text (for which there was only a slight plurality of support in San Juan). I was in the minority who thought this was ready for last call, but in light of these concerns, I've started up another thread to discuss further revisions to text to address the concerns. I would encourage everyone to participate in those discussions so we can address them promptly. I am of the opinion that this proposal is somewhat urgent, as the longer we go without an inter-RIR transfer policy, the more likely we are to see interregional transfers occurring outside the RIR system.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The AC selected the following proposal as a draft policy for adoption<br>
discussion online and at the ARIN XXVIII Public Policy Meeting in<br>
Philadelphia in October. The draft policy will be posted shortly to the<br>
PPML.<br>
<br>
ARIN-prop-126 Compliance Requirement<br></blockquote><div><br></div><div>It sounds like we're leaning towards removing the "ARIN must remove rDNS after 60 days" requirement. Other than that I think this one is ready to get its formal staff and legal review, and if nothing else comes up, to be discussed in Philly. </div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The AC accepted the following proposals on to the AC's docket for<br>
development and evaluation:<br>
<br>
ARIN-prop-140 Business Failure Clarification<br>
ARIN-prop-141 Combined M&A and Specified Transfers<br>
ARIN-prop-144 Remove Single Aggregate requirement from Specified Transfer<br>
ARIN-prop-146 Clarify Justified Need for Transfers<br>
ARIN-prop-147 Set Transfer Need to 24 months and Clarify Exception<br></blockquote><div><br></div><div>I think all of these are worth discussing further, and am glad to see the author's revisions to address most of the issues identified with them thus far.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The AC abandoned the following proposal:<br>
<br>
ARIN-prop-139 No reassignment without network service<br>
ARIN-prop-142 Define RSA<br>
ARIN-prop-143 Clarify Specified Transfer RSA Requirement<br>
ARIN-prop-145 STLS Listing Immunity<br>
<br>
The AC chose to abandon prop-139 because the AC determined that there<br>
was a significant lack of support in the community based on its<br>
observations of the public policy mailing list. Reasons for the lack of<br>
support expressed on PPML included the perception that the problems<br>
addressed by the proposal are not a significant issue in the ARIN<br>
region, that it would disallow activity generally seen as beneficial,<br>
that such restrictions would be beyond ARIN's scope, and that the<br>
restriction may be difficult to enforce. The author of the proposal<br>
also suggested abandonment which further underscored the AC's conclusion.<br>
<br>
The AC abandoned prop-142 because the majority of the AC felt that the<br>
RSA is an adjunct document to the NRPM and its definition should not<br>
reside in policy.<br>
<br>
The Advisory Council of ARIN abandoned prop-143: Clarify Specified<br>
Transfer RSA Requirement. The AC believes that the content and terms of<br>
contracts between ARIN and holders of address space is an operational<br>
and legal issue. Prescribing that content is not an appropriate function<br>
of the ARIN Policy Development Process. The proper avenue for input<br>
regrading such issues is the ARIN Consultation and Suggestion Process<br>
(ACSP).<br>
<br>
The AC chose to abandon prop-145 because the AC agreed with ARIN staff<br>
that this is an issue for the terms of service for the STLS and as such<br>
is outside the scope of the PDP and NRPM. The AC also believes that<br>
except in cases of fraud, it is unlikely that ARIN staff would forcibly<br>
revoke resources that have already been approved to be on the STLS. The<br>
AC advises the community to use the ACSP if they would like to provide<br>
ARIN input on the terms of service for the STLS or the L/RSA.<br></blockquote><div><br></div><div>I think these summaries all speak fairly well for themselves, but if anyone has any questions about them I'll be happy to opine further.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The AC thanks the authors and the community for their continuing effort<br>
and contributions to these and all other policy considerations.<br></blockquote><div><br></div><div>In particular, I think Matthew Kaufman deserves a special thanks for his recent contributions.</div><div><br></div><div>
-Scott</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The AC abandoned proposals 139, 142, 143 and 144. Anyone dissatisfied<br>
with these decisions may initiate a petition. The petition to advance<br>
these proposals would be the "Discussion Petition." The deadline to<br>
begin a petition will be five business days after the AC's draft meeting<br>
minutes are published. For more information on starting and<br>
participating in petitions, see PDP Petitions at:<br>
<a href="https://www.arin.net/policy/pdp_petitions.html" target="_blank">https://www.arin.net/policy/pdp_petitions.html</a><br>
<br>
Draft Policy and Proposal texts are available at:<br>
<a href="https://www.arin.net/policy/proposals/index.html" target="_blank">https://www.arin.net/policy/proposals/index.html</a><br>
<br>
The ARIN Policy Development Process can be found at:<br>
<a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/pdp.html</a><br>
<br>
Regards,<br>
<br>
Communications and Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><br>