Draft Policy 2012-2 IPv6 Subsequent Allocations Utilization Requirement.

Slides:



Advertisements
Similar presentations
62 Recommended Draft Policy ARIN Resolve Conflict Between RSA and 8.2 Utilization Requirements.
Advertisements

Draft Policy Clarifying Requirements for IPv4 Transfers.
Draft Policy GPP Network IP Resource Policy Advisory Council Shepherds: Scott Leibrand and Rob Seastrom.
Draft Policy Tiny IPv6 Allocations for ISPs Advisory Council Shepherds: David Farmer and Chris Grundemann.
Improving 8.4 Anti-Flip Language. Problem Statement Current policy prevents an organization that receives BLOCK A in the previous 12 months from.
Recommended Draft Policy Section 8.4 Inter-RIR Transfer of ASNs.
Advisory Council Shepherds: Scott Leibrand & Stacy Hughes Remove Single Aggregate requirement from Specified Transfer.
60 Recommended Draft Policy ARIN Anti-hijack Policy.
IPv6 Addressing – Status and Policy Report Paul Wilson Director General, APNIC.
2010-8: Rework of IPv6 Assignment Criteria David Farmer ARIN XXVI.
Customer Confidentiality Draft Policy Origin (Proposal 95)9 June 2009 Draft Policy (successfully petitioned) 2 February 2010 Aaron Wendel has.
Open Policy Hour Einar Bohlin, Policy Analyst. OPH Overview Draft Policy Preview Policy Experience Report Policy BoF.
Getting Internet Number Resources from ARIN Community Use Slide Deck Courtesy of ARIN May 2014.
Standardize IP Reassignment Registration Requirements Draft Policy
Recommended Draft Policy ARIN Out of Region Use.
Policy Experience Report Leslie Nobile. Review existing policies – Ambiguous text/Inconsistencies/Gaps/Effectiveness Identify areas where new or modified.
Draft Policy Revising Section 4.4 C/I Reserved Pool Size.
Simplified M&A transfer policy Draft Policy
ARIN Out of Region Use Tina Morris. Problem Statement Current policy neither clearly forbids nor clearly permits out of region use of ARIN registered.
Recommended Draft Policy ARIN Remove Operational Reverse DNS Text.
Draft Policy Transfers & Multi-National Networks Kevin Blumberg.
AC On-Docket Proposals Report John Sweeting AC Chair.
Draft Policy ARIN “Out of Region Use”. Problem statement (summary) Current policy neither clearly forbids nor clearly permits out of region use.
Policy Implementation & Experience Report Leslie Nobile.
Draft Policy Returned IPv4 Addresses 1.History including origin & shepherds 2.Summary 3.Status at other RIRs 4.Staff/legal assessment 5.PPML discussion.
Draft Policy Preview ARIN XXVII. Draft Policies Draft Policies on the agenda: – ARIN : Globally Coordinated Transfer Policy – ARIN : Protecting.
Recommended Draft Policy ARIN Remove Web Hosting Policy.
Draft Policy IPv6 Subsequent Allocations Utilization Requirement.
ARIN Change Utilization Requirements from last-allocation to total-aggregate.
Draft Policy Allocation of IPv4 and IPv6 Address Space to Out-of-region Requestors 59.
Draft Policy Protecting Number Resources 1.History including origin & shepherds 2.Summary 3.Status at other RIRs 4.Staff/legal assessment 5.PPML.
ARIN Revising Section 4.4 C/I Reserved Pool Size Bill Sandiford ARIN AC.
Skeeve Stevens APNIC 31, Hong Kong Alternative criteria for subsequent IPv6 allocations Prop-083v003.
Waiting List For Unmet IPv4 Requests Draft Policy
ARIN Allow Inter-RIR ASN Transfers. Problem Statement We already allow transfer of ASNs within the ARIN region. Recently APNIC implemented a policy.
Draft Policy Return to 12 Month Supply and Reset Trigger to /8 in Free Pool.
Draft Policy Globally Coordinated Transfer Policy 1.History including origin & shepherds 2.Summary 3.Status at other RIRs 4.Staff/legal assessment.
Draft Policy ARIN Modify 8.4 (Inter-RIR Transfers to Specified Recipients) Authors: David Huberman and Tina Morris AC Shepherds: Cathy Aronson and.
Policy Experience Report Leslie Nobile. Review existing policies – Ambiguous text/Inconsistencies/Gaps/Effectiveness Identify areas where new or modified.
Rework of IPv6 Assignment Criteria Draft Policy
Draft Policy Aligning 8.2 and 8.3 Transfer Policy.
Draft Policy IPv6 Subsequent Allocations Utilization Requirement.
Draft Policy Reassignments for Third Party Internet Access (TPIA) over Cable.
Allocation of IPv4 Blocks to Regional Internet Registries (Global Proposal) Draft Policy
Draft Policy Removal of Renumbering Requirement for Small Multihomers.
Recommended Draft Policy RIR Principles 59.
60 Draft Policy ARIN Improving 8.4 Anti-Flip Language.
60 Recommended Draft Policy ARIN Reduce All Minimum Allocation/Assignment Units to /24.
60 Draft Policy ARIN NRPM 4 (IPv4) Policy Cleanup.
Prop 182 Update Residential Customer Definition to Not Exclude Wireless as Residential Service.
Draft Policy Compliance Requirement History 1.Origin: ARIN-prop-126 (Jan 2011) 2.AC Shepherds: Chris Grundemann, Owen DeLong 3.AC selected.
Draft Policy Better IPv6 Allocations for ISPs 1.History including origin & shepherds 2.Summary 3.Status at other RIRs 4.Staff/legal assessment 5.PPML.
59 Draft Policy Allocation of IPv4 and IPv6 Address Space to Out-of-region Requestors.
Recommended Draft Policy ARIN David Farmer
Returned IPv4 Addresses
Required Resource Reviews
Recommended Draft Policy ARIN : Post-IPv4-Free-Pool-Depletion Transfer Policy Staff Introduction.
IPv6 Subsequent Allocation
Draft Policy ARIN Cathy Aronson
Draft Policy Shared Transition Space for IPv4 Address Extension
ARIN New MDN allocation based on past utilization
Recommended Draft Policy ARIN Change timeframes for IPv4 requests to 24 months Tina Morris.
Recommended Draft Policy ARIN : Eliminate HD-Ratio from NRPM
Requiring aggregation for IPv6 subsequent allocations
A view from ARIN, LACNIC & RIPE Communities Laura Cobley
Permitted Uses of space reserved under NRPM 4.10
ARIN Inter-RIR Transfers
Recommended Draft Policy ARIN : Modify 8
Recommended Draft Policy ARIN : Transfers for new entrants
Removing aggregation criteria for IPv6 initial allocations
Presentation transcript:

Draft Policy IPv6 Subsequent Allocations Utilization Requirement

History 1.Origin: ARIN-prop-159 (Nov 2011) 2.AC Shepherds: Heather Schiller, Cathy Aronson 3.Presented at ARIN 29 – needed more work 4.Presented at ARIN 30 – needed more work 5.Text and assessment online & in Discussion Guide 2

– ARIN Staff Summary The intent of this proposal is to allow ISPs (that have begun using IPv6 but may not have sufficiently planned for longer term growth) to receive an additional allocation. 3

– Status at other RIRs No similar proposals/discussions. 4

– Staff Assessment Staff Comments: Issues/Concerns? We believe that the intent of this policy is to allow ISPs who have allocated at least 90% of their space to serving sites to qualify for an additional allocation as long as the block size allocated to each serving site is justified based on the number of customers at the largest single serving site. However, we find the new policy text, "Has allocated more than 90% of their serving site blocks to serving sites, and has sufficient actual utilization at their serving sites to continue to justify the block size being utilized for all serving sites as specified in section " to be unclear and confusing. Staff suggests that the text be modified to: "has allocated more than 90% of their total address space to serving sites, with the block size allocated to each serving site being justified based on the criteria specified in section 6.5.2" This would allow block size to be based on the same criteria used to determine block size for the initial allocation. 5

– Legal Assessment This policy does not create significant legal issues. 6

Draft Policy IPv6 Subsequent Allocations Utilization Requirement

Problem Statement Current IPv6 allocation policy contains artifacts of IPv4 scarcity/slow-start thinking. This proposal attempts to mitigate that by allowing a longer term planning window for IPv6 number resources. 8

Text Part One Section 2.14 Serving Site When applied to IPv6 policies, the term serving site shall mean a location where an ISP terminates or aggregates customer connections, including, but, not limited to Points of Presence (POPs), Datacenters, Central or Local switching office or regional or local combinations thereof. It does not require the implementation of such aggregation in routing, only the implementation of an addressing plan that is subnetted along these topological boundaries to support the ability to aggregate. [Bold text is new] 9

Text Part Two Section Subsequent Allocations to LIRs a. Where possible ARIN will make subsequent allocations by expanding the existing allocation. b. An LIR qualifies for a subsequent allocation if they meet any of the following criteria: – Shows utilization of 75% or more of their total address space – Shows utilization of more than 90% of any serving site – Has allocated more than 90% of their serving site blocks to serving sites, and has sufficient actual utilization at their serving sites to continue to justify the block size being utilized for all serving sites as specified in section [Bold text is new] 10