Job, I mostly agree with you.

There is, however, one issue with the way ARIN does things.

On ARIN whois records, there is a field for “Origin AS”.

In the event that an organization transfers out an AS that is listed on
their blocks as “Origin AS”, you’d like to think that the organization
in question would clean that up, but my bet is it’s an opportunity for
database degradation and if we can somehow automate safety checks on
that, I think it’s worth while.

I think the right answer is probably for ARIN to implement business
logic that does not permit the transfer of an ASN that is listed
on any block as an “Origin AS” unless that block is also simultaneously
being transferred to the same entity.

Owen

> On Feb 1, 2018, at 10:29 , Job Snijders <j...@instituut.net> wrote:
> 
> On Thu, Feb 01, 2018 at 06:21:06PM +0000, Roberts, Orin wrote:
>> You could, but then IPv6 routing/fragmentation becomes an issue.
> 
> How so?
> 
>> Unless when an ASN is transferred from ARIN all IP networks associated
>> to that ASN are revoked/removed/deleted from ARIN.  ie. I can acquire
>> an ASN that currently exists at ARIN minus any associated IP networks,
>> move it to APNIC/RIPE, then associate IP networks from APNIC/RIPE.
>> 
>> ~the same for the reverse.
>> 
>> A proviso would then be, only a clean(ed) ASN can be transferred in/out.
> 
> Why would one delete networks when an ASN is transferred? The IPs were
> assigned according to whatever policy was applicable at that moment. IP
> prefixes and ASNs are assigned independently from each other, according
> to different policices, and as such it is logical that they are
> transferable independently from each other.
> 
> Kind regards,
> 
> Job
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact i...@arin.net if you experience any issues.

_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.

Reply via email to