Great I agree your policy. <br><br>On Saturday, January 22, 2022, Scott Leibrand <<a href="mailto:scottleibrand@gmail.com">scottleibrand@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">You answered an either-or question with a Y. I’m not on the AC, but if I were the shepherd on this proposal I would not be able to incorporate your opinion into my assessment of community consensus for or against this policy proposal. If you want your opinion to be considered, you might want to express it in English. <br><br><div dir="ltr"><div>Scott</div></div><div dir="ltr"><br><blockquote type="cite">On Jan 22, 2022, at 12:16 PM, Mattapally Technologies <<a href="mailto:technologiesmattapally@gmail.com" target="_blank">technologiesmattapally@gmail.<wbr>com</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">Y<br><br>On Saturday, January 22, 2022, Scott Leibrand <<a href="mailto:scottleibrand@gmail.com" target="_blank">scottleibrand@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Are you disagreeing with Owen, or objecting to some part of the proposed changes from 2021-4? If the latter, which change, and why? Despite my initial concerns, it doesn’t appear that it actually changes policy with regard to inter-region ASN transfers, which have been allowed for years. <br><br><div dir="ltr"><div>Scott</div></div><div dir="ltr"><br><blockquote type="cite">On Jan 22, 2022, at 3:23 AM, Mattapally Technologies <<a href="mailto:technologiesmattapally@gmail.com" target="_blank">technologiesmattapally@gmail.<wbr>com</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">-1<br><br>On Friday, January 21, 2022, Owen DeLong via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">There’s a valid argument to be made that there is no longer any (technical) valid reason to treat 16 and 32-bit ASNs differently… ASNs are ASNs today.<div><br></div><div>Owen</div><div><br><div><br><blockquote type="cite"><div>On Jan 21, 2022, at 09:58 , Fernando Frediani <<a href="mailto:fhfrediani@gmail.com" target="_blank">fhfrediani@gmail.com</a>> wrote:</div><br><div>
<div><p>I tend to think that transfers originally exists due to IPv4
exhaustion and that is justified. IPv6 and 32-bit ASN don't have
the same justification, only 16-bit ASN.</p><p>I would also like to understand it better.</p><p>Regards<br>
Fernando<br>
</p>
<div>On 21/01/2022 14:18, Scott Leibrand
wrote:<br>
</div>
<blockquote type="cite">
Are <span style="font-family:Calibri,sans-serif;font-size:14.666666984558105px;background-color:rgb(255,255,255)">Inter-regional transfers
of ASNs allowed via policy today? If not, this is a substantive
change on that topic, and the draft policy should be retitled
accordingly. </span>
<div><font face="Calibri, sans-serif"><span style="font-size:14.666666984558105px;background-color:rgb(255,255,255)"><br>
</span></font></div>
<div><font face="Calibri, sans-serif"><span style="font-size:14.666666984558105px;background-color:rgb(255,255,255)">I have no objections
to allowing inter-regional ASN transfers, but would like to
see an explicit argument if we are proposing to change
whether it is allowed, even if that’s as simple as “some
orgs want to do it”.<br>
</span></font><br>
<div dir="ltr">
<div>Scott</div>
</div>
<div dir="ltr"><br>
<blockquote type="cite">On Jan 21, 2022, at 7:42 AM, ARIN
<a href="mailto:info@arin.net" target="_blank"><info@arin.net></a> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">Inter-regional transfers of IPv4 number
resources and ASNs</div>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>______________________________<wbr>_________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman<wbr>/listinfo/arin-ppml</a>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
</div>
______________________________<wbr>_________________<br>ARIN-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="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman<wbr>/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></blockquote></div><br></div></div></blockquote>
<span>______________________________<wbr>_________________</span><br><span>ARIN-PPML</span><br><span>You are receiving this message because you are subscribed to</span><br><span>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).</span><br><span>Unsubscribe or manage your mailing list subscription at:</span><br><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman<wbr>/listinfo/arin-ppml</a></span><br><span>Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.</span><br></div></blockquote></div></blockquote>
</div></blockquote></div></blockquote>