Y

On Saturday, January 22, 2022, Scott Leibrand <[email protected]>
wrote:

> 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.
>
> Scott
>
> On Jan 22, 2022, at 3:23 AM, Mattapally Technologies <
> [email protected]> wrote:
>
> -1
>
> On Friday, January 21, 2022, Owen DeLong via ARIN-PPML <[email protected]>
> wrote:
>
>> 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.
>>
>> Owen
>>
>>
>> On Jan 21, 2022, at 09:58 , Fernando Frediani <[email protected]>
>> wrote:
>>
>> 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.
>>
>> I would also like to understand it better.
>>
>> Regards
>> Fernando
>> On 21/01/2022 14:18, Scott Leibrand wrote:
>>
>> Are 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.
>>
>> 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”.
>>
>> Scott
>>
>> On Jan 21, 2022, at 7:42 AM, ARIN <[email protected]> <[email protected]> wrote:
>>
>> Inter-regional transfers of IPv4 number resources and ASNs
>>
>>
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List ([email protected]).
>> Unsubscribe or manage your mailing list subscription 
>> at:https://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact [email protected] if you experience any issues.
>>
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List ([email protected]).
>> Unsubscribe or manage your mailing list subscription at:
>> https://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact [email protected] if you experience any issues.
>>
>>
>> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
>
>
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to