[arin-ppml] Draft Policy 2012-3: ASN Transfers

[Tom Vest]

There are lots of compelling reasons to support ASN transfers, depending on what one hopes to accomplish:

1. Entities that already expect to enjoy a long profitable run as IPv4 brokers will be able to command even higher prices for the bundled lease/sales of "lightly used" IPv4 prefixes along with their associated origin-ASes.

2.  Entities that aspire to further extend their profitable run as IPv4 brokers will have an easier time power-washing their more roughly used Pv4 by repackaging soiled prefixes with a different origin-AS between each new lease transaction.

3. Entities that would not be unhappy to see SIDR/RPKI fail absolutely and/or to succeed primarily in turning the current industry pecking order into a perpetual, insurmountable reputation hierarchy -- where no amount of good of behavior can ever be truly reassuring (if you're a new entrant), and no instance of bad behavior need ever tarnish one's own reputation (if you're an incumbent operator) -- would have everything they require to achieve those goals.

4. Ditto (3), but for ASN32.

5. Peering game players and associated suppliers/enablers/profiteers would be able to extend the current round of AS-centered games indefinitely into the future -- or at least until someone determines the next new realm into which the game will be extended.

Oh, and the vanity number-thing.

Given the adverse impact that this proposed change is very very likely to have just *within* this industry, there shouldn't be any need to speculate about the numerous layer 8+ implications of each of the above -- but I encourage anyone who has any lingering doubts to think each threat vector through on their own.

Opposed (!),

TV

On Mar 14, 2012, at 11:07 AM, ARIN wrote:

> Draft Policy ARIN-2012-3
> ASN Transfers
> 
> On 8 March 2012 the ARIN Advisory Council (AC) selected "ASN Transfers" as a  draft policy for adoption discussion on the PPML and at the Public Policy Meeting in Vancouver in April.
> 
> The draft was developed by the AC from policy proposal "ARIN-prop-157 Section 8.3 Simplification." Per the Policy Development Process the AC submitted text to ARIN for a staff and legal assessment prior to its selection as a draft policy. Below the draft policy is the ARIN staff and legal assessment, followed by the text that was submitted by the AC.
> 
> Draft Policy ARIN-2012-3 is below and can be found at:
> https://www.arin.net/policy/proposals/2012_3.html
> 
> You are encouraged to discuss Draft Policy 2012-3 on the PPML prior to
> the April Public Policy Meeting. Both the discussion on the list and
> at the meeting will be used by the ARIN Advisory Council to determine
> the community consensus for adopting this as policy.
> 
> The ARIN Policy Development Process can be found at:
> https://www.arin.net/policy/pdp.html
> 
> Draft Policies and Proposals under discussion can be found at:
> https://www.arin.net/policy/proposals/index.html
> 
> Regards,
> 
> Member Services
> American Registry for Internet Numbers (ARIN)
> 
> 
> ## * ##
> 
> 
> Draft Policy ARIN-2012-3
> ASN Transfers
> 
> Date: 14 March 2012
> 
> Policy statement:
> 
> In NRPM 8.3, replace "IPv4 number resources" with "IPv4 number resources and ASNs".
> 
> Rationale:
> 
> There are legitimate use cases for transferring ASNs, and no significant downsides (identified to date) of allowing it.
> 
> Timetable for implementation: Immediate
> 
> 
> ##########
> 
> 
> ARIN STAFF ASSESSMENT
> 
> Draft Policy:  Proposal 157 “ASN Transfers”
> Date of Assessment:  23 Feb 2012
> 
> 1.  Proposal Summary (Staff Understanding)
> 
> This proposal would allow organizations to transfer ASNs in addition to IPv4 address space in an 8.3 transfer to specified recipients.
> 
> 2. Comments
> 
> A.	ARIN Staff Comments
> 
> •	If implemented as written, the 24-month utilization requirement in 8.3 would not apply to ASN requests since 8.3 clearly says “how the addresses will be utilized in 24 months”.  Staff would apply the current ASN policy, which requires an organization to be multi-homed or to immediately become multi-homed.
> 
> B. ARIN General Counsel
> 
> This creates no legal concerns and may actually facilitate any bankruptcy proceedings where ASNs are involved.
> 
> 3. Resource Impact
> 
> This policy would have minimum resource impact from an implementation aspect.  It is estimated that implementation would occur within 3 months after ratification by the ARIN Board of Trustees. The following would be needed in order to implement:
> 
> •	Updated guidelines
> •	Staff training
> 
> 4. Proposal Text
> 
> Policy statement:
> 
> In NRPM 8.3, replace "IPv4 number resources" with "IPv4 number resources and ASNs".
> 
> Rationale:
> There are legitimate use cases for transferring ASNs, and no significant downsides (identified to date) of allowing it.
> Timetable for implementation: Immediate
> 
> 
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.