1 / 8

2011-10 Remove Single Aggregate requirement from Specified Transfer

2011-10 Remove Single Aggregate requirement from Specified Transfer. Advisory Council Shepherds: Scott Leibrand & Stacy Hughes. Problem Statement. ARIN has received a number of legitimate transfer requests that involve multiple IPv4 netblocks .

tyanne
Download Presentation

2011-10 Remove Single Aggregate requirement from Specified Transfer

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. 2011-10 Remove Single Aggregate requirement from Specified Transfer Advisory Council Shepherds: Scott Leibrand & Stacy Hughes

  2. Problem Statement • ARIN has received a number of legitimate transfer requests that involve multiple IPv4 netblocks. • Some of these transfers were ordered by bankruptcy court. • ARIN has interpreted 8.3’s “single aggregate” requirement to apply to the justification, not to the transfer.

  3. Draft Policy Text Modify last sentence of 8.3: "can demonstrate the need for such resources, as a single aggregate, in the exact amount which they can justify under current ARIN policies.”

  4. Benefits • Allows otherwise legitimate transfers involving multiple netblocks to occur as a single transaction. • Avoids putting ARIN policy at odds with legal requirements. • Simplifies policy and reduces possible confusion over interpretation of “single aggregate” language.

  5. Drawbacks • By allowing transfers of multiple smaller netblocks instead of a larger one, may result in additional routes being announced into the DFZ.

  6. Staff & Legal Assessment • This would eliminate possible confusion and align the text with current implementation whereby transfers can involve multiple discontiguous IPv4 address ranges (in a single transaction with ARIN). • Counsel affirmatively supports this suggested change. We do not see it as creating any additional legal liability. Given the myriad of factual situations that may arise, a single aggregate requirement could prove to be too rigid and could prohibit an overall good policy result.

  7. Discussion?

  8. Appendix – 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, as a single aggregate, in the exact amount which they can justify under current ARIN policies.

More Related