1 / 8

Draft Policy 2011-10 Remove Single Aggregate requirement from Specified Transfer

This proposed policy aims to eliminate the requirement for transfers to be done as a single aggregate, allowing the transfer of multiple prefixes simultaneously under NRPM 8.3. The change intends to reduce confusion and align with current implementation practices at ARIN. The staff assessment indicates minimal resource impact and updated guidelines within three months post-implementation, while legal counsel supports the amendment with no additional legal liabilities foreseen. The PPML discussion saw limited activity, with only a few posts supporting the original proposal.

golding
Download Presentation

Draft Policy 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. Draft Policy 2011-10Remove Single Aggregate requirement from Specified Transfer

  2. 2011-10 - History Origin: ARIN-prop-144 (May 2011) AC Shepherds: Scott Leibrand, Stacy Hughes AC selected as Draft Policy (Aug 2011) Current version: 24 Aug 2011 Text and assessment online & in Discussion Guide https://www.arin.net/policy/proposals/2011_10.html

  3. 2011-10 – Summary This proposed policy would remove the phrase, "as a single aggregate” from the existing NRPM 8.3 policy thus allowing the transfer of multiple prefixes during an 8.3 transfer.

  4. 2011-10 – Status at other RIRs Nothing similar at the other RIRs

  5. 2011-10 – Staff Assessment Staff Comments: Issues/Concerns? This would eliminate possible confusion and align the text with current implementation whereby transfers can involve multiple discontiguousIPv4 address ranges (in a single transaction with ARIN). Implementation: Resource Impact? – Minimal (3 mos.) Updated guidelines Staff training

  6. 2011-10 – Legal Assessment 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. 2011-10 – PPML Discussion Little discussion of Draft Policy A couple posts in support of the original proposal, one against.

  8. Draft Policy 2011-10Remove Single Aggregate requirement from Specified Transfer

More Related