Izumi Okutani (JPNIC) Terence Zhang (CNNIC)

Slides:



Advertisements
Similar presentations
Copyright (c) 2006 Japan Network Information Center Comments from JP on “End site allocation policy for IPv6” (prop-033-v001 ) Izumi Okutani Japan Network.
Advertisements

1 Overview of policy proposals Policy SIG Wednesday 26 August 2009 Beijing, China.
Draft Policy Tiny IPv6 Allocations for ISPs Advisory Council Shepherds: David Farmer and Chris Grundemann.
IPv6 Addressing – Status and Policy Report Paul Wilson Director General, APNIC.
2010-8: Rework of IPv6 Assignment Criteria David Farmer ARIN XXVI.
Draft Policy ARIN : Modification to Criteria for IPv6 Initial End-User Assignments.
Update on RIPE NCC Inter- RIR Transfer proposal Adam Gosling APNIC 38 Policy SIG Meeting 18 September 2014.
APNIC 33 AMM Policy SIG Report Andy Linton, Policy SIG Chair Thursday 2 March 2012.
Copyright (c) 2003 Japan Network Information Center NIR Voting and Fee Structures Izumi Okutani IP Address Section Japan Network Information Center Open.
Overview of policy proposals Policy SIG 27 February 2008 APNIC 25, Taipei.
Copyright © 2008 Japan Network Information Center JPNIC's review of IPv4 address transfer  Izumi Okutani  Japan Network Information.
Open Policy Hour Einar Bohlin, Policy Analyst. OPH Overview Draft Policy Preview Policy Experience Report Policy BoF.
POLICY EXPERIENCE REPORT Leslie Nobile. Review existing policies – Ambiguous text/Inconsistencies/Gaps/Effectiveness Identify areas where new or modified.
Skeeve Stevens APNIC 29, Kuala Lumpur Alternative criteria for subsequent IPv6 allocations Prop-083v002.
APNIC Policy Update 1 st TWNIC Open Policy Meeting 3 December, 2003 Taipei, Taiwan.
1 APNIC allocation and policy update JPNIC OPM July 17, Tokyo, Japan Guangliang Pan.
Copyright © 2007 Japan Network Information Center Global Policy for the Allocation of the remaining IPv4 Address Space  Japan Network Information Center.
A proposal to lower the IPv4 minimum allocation size and initial criteria in the AP region prop-014-v001 Policy SIG APNIC17/APRICOT 2004 Feb
Prop-080: Removal of IPv4 Prefix Exchange Policy Guangliang Pan Resource Services Manager, APNIC.
Policy Experience Report Leslie Nobile. Review existing policies – Ambiguous text/Inconsistencies/Gaps/Effectiveness Identify areas where new or modified.
ARIN Section 4.10 Austerity Policy Update.
Developing IPv6 Address Guidelines Izumi Okutani Japan Network Information Center Address Policy SIG Aug 2003, Seoul.
Separate Assignment Policies for End-Users and ISPs Izumi Okutani Japan Network Information Center.
Policy Implementation & Experience Report Leslie Nobile.
Copyright (c) 2006 Japan Network Information Center Survey results in JP on IPv6 assignment size Izumi Okutani Japan Network Information Center (JPNIC)
APNIC Policy SIG report: Open Policy Meeting Masato Yamanishi, Chair APNIC 40 Jakarta, Indonesia.
1 IPv6 Allocation Policy and Procedure Global IPv6 Summit in China 2007 April 13, 2007 Gerard Ross and Guangliang Pan.
Prop-097: Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA Alejandro Acosta, Nicolas Antoniello, S. Moonesamy, Douglas Onyango,
Izumi Okutani JPNIC IP Department NIR Meeting Feb 2004 JPNIC Open Policy Meeting Update.
Skeeve Stevens APNIC 31, Hong Kong Alternative criteria for subsequent IPv6 allocations Prop-083v003.
An Update to the IPv4 Guideline Yi Lee Digital United Inc. (Seednet) Mars Wei NCIC (Sparq*) By IPv4 Guideline Working Group.
Registration Services Feedback Andrea Cima RIPE NCC RIPE 67 - Athens.
Draft Policy Merge IPv4 ISP and End-User Requirements 59.
Prop-073 Automatic allocation/assignment of IPv6 Terry Manderson Andy Linton.
1 A Closer Look at the Final /8 Policy Sam Dickinson Senior Policy Specialist, APNIC Thursday, 26 August 2010.
1 IANA global IPv6 allocation policy [prop-005-v002] Policy SIG 1 Sept 2004 APNIC18, Nadi, Fiji.
A proposal for changing IPv6 per address fee Izumi Okutani Japan Network Information Center NIR 18, Fiji 31 August – 3 September, 2004.
Global IPv6 Address Interim Policy Draft Open Issues and Discussion Summary Address Policy SIG / 13 th APNIC Meeting Kosuke Ito Global IPv6 Interim Policy.
Prop-077: Proposal to supplement transfer policy of historical IPv4 addresses Wendy Zhao Wei, Jane Zhang & Terence Zhang Yinghao.
Policy SIG Report APNIC AGM Friday 29 August 2008 Christchurch, New Zealand 1.
1 Madison, WI 9 September Part 1 IPv4 Depletion Leslie Nobile Director, Registration Services.
1 IPv6 Allocation and Policy Update Global IPv6 Summit in China 2007 April 12, 2007 Guangliang Pan.
60 Recommended Draft Policy ARIN Reduce All Minimum Allocation/Assignment Units to /24.
Copyright (c) 2002 Japan Network Information Center Proposal for IPv6 Policy for Essential Infrastructure in the AP region Izumi Okutani IP Address Section.
Recommended Draft Policy ARIN David Farmer
NIR SIG Report Report to APNIC Member Meeting APNIC18, Nadi, Fiji
Policy Text Insert new section to NRPM to read as follows:
IPv6 Documentation Address Policy
ARIN Scott Leibrand / David Huberman
Prop-093: Reducing the minimum delegation size for the final /8
APNIC 29 Policy SIG report
Requiring aggregation for IPv6 subsequent allocations
Policy SIG Wednesday 3 March 2010
IPv6 Policy and Allocation Update
Izumi Okutani (JPNIC) Terence Zhang (CNNIC)
Policy SIG Open Action Items
Policy SIG Chair Report
Jane Zhang & Wendy Zhao Wei
Policy SIG Thursday 26 February Manila, Philippines
Prop-078-V002: IPv6 deployment criteria for IPv4 final /8 delegations
Randy Bush & Philip Smith
ARIN Inter-RIR Transfers
The Current Issues in IPv6 Policy
IPv4 Transfer Policy Amendments
Overview of policy proposals
Recommended Draft Policy ARIN : Transfers for new entrants
Status Report on Policy Implementation at the APNIC Secretariat
Proposal to Change IPv6 Initial Allocation Criteria
Removing aggregation criteria for IPv6 initial allocations
prop-081-v001: Eligibility for assignments from the final /8
Presentation transcript:

Izumi Okutani (JPNIC) Terence Zhang (CNNIC) Alternative criteria to renumbering in initial allocation after the final /8 phase Izumi Okutani (JPNIC) Terence Zhang (CNNIC)

Introduction We would like to share the implications of keeping the renumbering requirement in initial allocation criteria after the final /8 phase Would like to make a conscious decision as the forum even if we are going to keep the requirement as it is

Intention of the last /8 block In principle, it should be used to enable IPv4 and IPv6 dual stack environment during the transition phase/interim measure to face IPv4 address pool run out It is not intended for expansions of existing IPv4 service

Who are eligible and how Each LIR is eligible to receive a single IPv4 block of minimum size New LIRs Must meet the Initial Allocation Criteria Existing LIRs Must meet the Subsequent Allocation Criteria

Current Initial Allocation Criteria To be eligible to obtain an initial allocation, an LIR must: have used a /24 from their upstream provider or demonstrate an immediate need for a /24; have complied with applicable policies in managing all address space previously allocated to it (including historical allocations); demonstrate a detailed plan for use of a /23 within a year; and commit to renumber from previously deployed space into the new address space within one year. The purpose is aggregation into allocation block(s), Not reclamation

Renumbering Criteria in Initial Allocation Before the final /8,APNIC could make allocations to new LIRs to compensate for IPv4 assignment(s) returned to the upstream After the final /8, APNIC can no longer compensate for IPv4 assignment(s) returned to the upstream The renumbering requirement in practice will result in reclamation of a new LIR's IPv4 address holding used for its existing network This will affect over 95% of new LIRs

Issue with renumbering requirement after the final /8 phase APNIC The allocation from the last /8 Existing LIR T= IPv6/IPv4 Translation Function IPv4 from the last /8 Return assignments T Existing IPv4 NW IPv4 assignments From upstream A New LIR must return IPv4 block(s) used in its existing network in order to receive IPv4 block required for IPv6/IPv4 translation function in its network

Keeping the renumbering requirement in initial allocation New LIR (no IPv4) IPv4 from the last /8 Newly built IPv6 NW T Affects over 95% of new LIRs IPv6 allocation(s) b) New LIR (IPv4 from upstream) Existing IPv4 NW IPv4 from the last /8 T Existing IPv4 assignment(s) Upstream LIR return Existing IPv4 NW IPv4 from the last /8 c) Existing LIR T Existing IPv4 allocation(s) T= IPv6/IPv4Translation Function

Summary of the issues Keeping the renumbering requirement in initial allocation after the final /8 phase will in practice mean a reclamation of a new LIR’s IPv4 holdings for existing network to receive necessary IPv4 block for IPv6/IPv4 translation It will affect over 95% of new LIRs Difficult to provide a rationale reason why existing LIRs are allowed to keep their past allocation but not new LIRs

Proposed Change in Initial Allocation Criteria Keep the justification requirement as it is in the current initial allocatation criteria Provide an alternative option the renumbering criteria Demonstrate 80%(*) usage of the past assignments * 80% is consistent with the % utilization required in subsequent allocations

Initial allocation criteria a.f./8 (prop-094) To be eligible to obtain an initial allocation, an LIR must: have used a /24 from their upstream provider or demonstrate an immediate need for a /24; have complied with applicable policies in managing all address space previously allocated to it (including historical allocations); demonstrate a detailed plan for use of a /23 within a year; and commit to renumber from previously deployed space into the new address space within one year. OR Demonstrate that the usage rate of previous IPv4 address space holding from their upstream provider(s) reached 80% Prop-094 suggests to add this alternative

Additional Note Even if this proposal doesn’t reach consensus, we would like to propose to at least share the implications to new LIRs when applying for initial allocation they must return their existing IPv4 address holdings to its upstream LIR, if they wish to receive IPv4 block from the last /8