<br><br>Hi Dan,<br><br>The current PDP that we are operating under with respect to this proposal says that:<br><br>"The Advisory Council evaluates policy proposals and develops them into
technically sound and useful draft policies that, if adopted, will make
a positive contribution to the Number Resource Policy Manual. "<br><br>This proposal is technically sound; I believe that you would agree that we did address the technical concerns which were what the majority of what the opposition was on mailing list. The proposal is useful to the Internet technical community; it allows network operators to choose and was additionally noted to be useful by ARIN's outside legal counsel further benefiting the ARIN community.<br>
<br>2 in favor vs. every one opposed) is a much wider margin of consensus than many other proposals that we've passed of late (See 2011-1 for example). Consensus is not a good challenge for this proposal.<br>
<br>With Section 8.3 and 2011-1 opening the door for transfer at-large, it would make sense for ASN's to be included in this as well and as such, the AC overwhelmingly adopted this proposal 10 in favor, 4 opposed, an even wider margin than the public support. <br>
<br>In favor..<br><br>Best,<br><br>Martin Hannigan<br>Elected Advisory Council Member<br><br><br><br><br><div class="gmail_quote">
On Wed, May 2, 2012 at 3:32 PM, Alexander, Daniel <span dir="ltr"><<a href="mailto:Daniel_Alexander@cable.comcast.com" target="_blank">Daniel_Alexander@cable.comcast.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I will probably get flamed for this one, but I wanted to try and explain<br>
why I voted against this proposal during the AC meeting.<br>
<br>
If I borrow some wording from the proposed PDP, when the AC has to<br>
determine consensus we have to determine whether the proposed change has<br>
substantially more support than opposition in the community active in the<br>
discussion. (56 PPML posts: 6 for, 3 against)(106 people in the room of<br>
the Public Policy Meeting: 27 for, 11 against) We also have to consider<br>
that the specific concerns expressed have been considered. This last part<br>
is one of the reasons I voted against this proposal.<br>
<br>
I think that 2012-3 breaks new ground in that it has no technical need as<br>
a foundation. This proposal allows a part of the community to do something<br>
they want to do, rather than technically need to do. Bear with me here<br>
before this splinters into days of argument. To be clear, I am not<br>
suggesting this should not be allowed, rather question what is the<br>
appropriate level of dissent or support for such a change.<br>
<br>
Some policy debates have to move past the dissenting opinions because the<br>
implications may outweigh the result of not making a change. If, however<br>
there are no technical downside, then similar consideration has to be<br>
given to both opinions of the community. One cannot dismiss the personal<br>
opinions of those who object to the change when those in dissent are<br>
supposed to accept the opinions of those who want it for no other reason.<br>
We need a serious debate over what is the appropriate level of support for<br>
a non-technical proposal.<br>
<br>
Because of this, I do not feel that appropriate consensus has been reached<br>
and this proposal warrants further discussion. Not only for the merits of<br>
the proposal itself but for the implications that this change has on how<br>
we are referred to as the "Internet Technical Community".<br>
<br>
Dan Alexander<br>
AC Member<br>
<div><div><br>
<br>
On 4/30/12 1:19 PM, "ARIN" <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>> wrote:<br>
<br>
>The ARIN Advisory Council (AC) met on 25 April 2012 and decided to<br>
>send the following draft policy to last call:<br>
><br>
> ARIN-2012-3: ASN Transfers<br>
><br>
>Feedback is encouraged during the last call period. All comments should<br>
>be provided to the Public Policy Mailing List. Last call for 2012-3 will<br>
>expire on 14 May 2012. After last call the AC will conduct their last<br>
>call review.<br>
><br>
>The draft policy text is below and available at:<br>
><a href="https://www.arin.net/policy/proposals/" target="_blank">https://www.arin.net/policy/proposals/</a><br>
><br>
>The ARIN Policy Development Process is available 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>
>Draft Policy ARIN-2012-3<br>
>ASN Transfers<br>
><br>
>Date: 14 March 2012<br>
><br>
>Policy statement:<br>
><br>
>In NRPM 8.3, replace "IPv4 number resources" with "IPv4 number resources<br>
>and ASNs".<br>
><br>
>Rationale:<br>
><br>
>There are legitimate use cases for transferring ASNs, and no significant<br>
>downsides (identified to date) of allowing it.<br>
><br>
>Timetable for implementation: Immediate<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>
<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>
</div></div></blockquote></div><br>