1 / 9

2012-3: ASN Transfers

2012-3: ASN Transfers. Advisory Council Shepherds : Scott Leibrand and Bill Sandiford. Problem Statement. Some organizations would like a low-numbered or memorable ASN. Some organizations have ASNs they’re no longer using and would like to transfer. Draft Policy Text.

hina
Download Presentation

2012-3: ASN Transfers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 2012-3: ASN Transfers Advisory Council Shepherds: Scott Leibrand and Bill Sandiford

  2. Problem Statement • Some organizations would like a low-numbered or memorable ASN. • Some organizations have ASNs they’re no longer using and would like to transfer.

  3. Draft Policy Text • In NRPM 8.3, replace "IPv4 number resources" with "IPv4 number resources and ASNs". • (Yes, this is a two word change.)

  4. Benefits • Organizations who would prefer a low-numbered or memorable ASN could get one. • Makes it easier for peers to remember their ASN and configure their sessions • When the 2-byte ASN pool is exhausted, having a way to get unused ASNs back into use may help organizations with a technical need for 2-byte ASNs. • Bankruptcy courts seeking to dispose of ASNs could do so without conflicting with ARIN policy.

  5. Potential Drawbacks • Concerns that some organizations may be able to acquire another company’s reputation and use it for nefarious purposes. • RPKI concerns... • Perhaps we should work out problems with existing IPv4 transfers first. • Is this really necessary?

  6. Staff & Legal Assessment • “24‐month utilization requirement in 8.3 would not apply to ASN requests” • “This creates no legal concerns and may actually facilitate any bankruptcy proceedings where ASNs are involved.” - ARIN General Counsel

  7. Discussion?

  8. Appendix – Current NRPM 8.3 • 8.3. Transfers to Specified Recipients • In addition to transfers under section 8.2, IPv4 number resources within the ARIN region may be released to ARIN by the authorized resource holder, in whole or in part, for transfer to another specified organizational recipient. Such transferred number resources may only be received under RSA by organizations that are within the ARIN region and can demonstrate the need for such resources in the amount which they can justify under current ARIN policies showing how the addresses will be utilized within 24 months.

  9. Appendix – NRPM 8.3 w/ 2012-3 • 8.3. Transfers to Specified Recipients • In addition to transfers under section 8.2, IPv4 number resources and ASNs within the ARIN region may be released to ARIN by the authorized resource holder, in whole or in part, for transfer to another specified organizational recipient. Such transferred number resources may only be received under RSA by organizations that are within the ARIN region and can demonstrate the need for such resources in the amount which they can justify under current ARIN policies showing how the addresses will be utilized within 24 months.

More Related