prop-064-v002 Change to assignment policy for AS numbers

Slides:



Advertisements
Similar presentations
LACNIC Policy Update Roque Gagliano LACNIC. Current Policies Proposals - LACNIC As a result of the Open Policy Forum at LACNIC XI four policy proposals.
Advertisements

IPv4 Address Transfer proposal APNIC prop-050-v002 Geoff Huston.
Proposal-062: Use of Final /8 Jonny Martin, Philip Smith & Randy Bush Policy APNIC 26 28th August 2008 Christchurch, New Zealand.
Policy SIG report 29 February 2008 APNIC 25, Taipei Toshiyuki Hosaka Randy Bush Jian Zhang.
1 IP Policy update - comparative status in all RIR regions Policy SIG 7 Sep 2006 APNIC 22, Kaohsiung, Taiwan Save Vocea.
Copyright (c) 2006 Japan Network Information Center Comments from JP on “End site allocation policy for IPv6” (prop-033-v001 ) Izumi Okutani Japan Network.
APNIC update ARIN XX 17 October 2007 Srinivas Chendi.
1 Overview of policy proposals Policy SIG Wednesday 26 August 2009 Beijing, China.
1 Change in the Minimum Allocation Criteria Policy Proposal Proposed by Rajesh Chharia, President – ISPAI Presented by Kusumba S Vice President - ISPAI.
IPv6 Addressing – Status and Policy Report Paul Wilson Director General, APNIC.
APNIC Update The state of IP address distribution and its impact to business operations 1 Elly Tawhai Senior Internet Resource Analyst/Liaison Officer,
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.
APNIC Last /8 Policy Implementation Report Sanjaya Services Area Director.
Policy Documentation Adam Gosling APNIC 38 Policy SIG Meeting 18 September 2014.
Overview of policy proposals Policy SIG 27 February 2008 APNIC 25, Taipei.
Skeeve Stevens APNIC 29, Kuala Lumpur Alternative criteria for subsequent IPv6 allocations Prop-083v002.
Policy implementation and document status report Address Policy SIG APNIC 15, Taipei, Taiwan 27 February 2003.
Address Policy SIG, APNIC Policy meeting, February 27th, 2003 (1) IPv6 Policy in action Feedback from other RIR communities David Kessens Chairperson RIPE.
APNIC Depletion of the IPv4 free address pool – IPv6 deployment The day after!! 8 August 2008 Queenstown, New Zealand In conjunction with APAN Cecil Goldstein,
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.
1 TWNIC Update Sheng Wei Kuo, TWNIC NIR SIG, 28 th APNIC OPM.
1 The Status of 4-byte AS number in Taiwan Sheng Wei Kuo, TWNIC NIR SIG, 27 th APNIC OPM.
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.
Policy Implementation & Experience Report Leslie Nobile.
Prop-065-v001 Format for delegation and recording of 4-byte AS numbers APNIC26 - Christchurch NZ.
Skeeve Stevens APNIC 31, Hong Kong Alternative criteria for subsequent IPv6 allocations Prop-083v003.
Policies for ASN Management in the Asia Pacific Region – Revised Draft Address Policy SIG APNIC14, Kitakyushu, Japan 4 Sept 2002.
ARIN Allow Inter-RIR ASN Transfers. Problem Statement We already allow transfer of ASNs within the ARIN region. Recently APNIC implemented a policy.
1 Application of the HD ratio to IPv4 [prop-020-v001] Policy SIG 1 Sept 2004 APNIC18, Nadi, Fiji.
Current Policy Topics Emilio Madaio RIPE NCC RIPE November 2010, Rome.
APNIC 32 AMM Policy SIG Report Andy Linton Thursday 1 September 2011.
Registration Services Feedback Andrea Cima RIPE NCC RIPE 67 - Athens.
IPv4 IXP Address Policy APNIC Policy SIG Meeting Taipei, August 2001 Philip Smith.
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 Welcome to the Policy SIG Policy SIG 1 March 2007 APNIC 23, Bali, Indonesia Kenny Huang.
1 Transition to IPv6: Should ISPs consider it now? PITA 11th AGM Meeting 2007 Tahiti, French Polynesia 24 April 2007.
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.
ARIN Update John Curran President and CEO, ARIN Focus IPv4 to IPv6 Transition Awareness – Targeting ISPs and Content Providers Continued enhancements.
September, 2003 Bill Woodcock Packet Clearing House
ARIN XXVIII 13 October 2011 Philadelphia Geoff Huston, APNIC
Prop-093: Reducing the minimum delegation size for the final /8
APNIC 29 Policy SIG report
Prop-50 IP Address Transfers
RIPE October 2005 Geoff Huston APNIC
IPv6 Policy and Allocation Update
A view from ARIN, LACNIC & RIPE Communities Laura Cobley
Izumi Okutani (JPNIC) Terence Zhang (CNNIC)
News from APNIC ARIN XXII 16 October 2008.
Policy SIG Open Action Items
Jane Zhang & Wendy Zhao Wei
Nurani Nimpuno On behalf of Geoff Huston APNIC 25 May 2006
Policy SIG Thursday 26 February Manila, Philippines
Permitted Uses of space reserved under NRPM 4.10
4-Byte AS number registry Policy Proposal [LACNIC Proposal ]
Prop-078-V002: IPv6 deployment criteria for IPv4 final /8 delegations
Randy Bush & Philip Smith
Policy Development Process
Overview of policy proposals
Overview of policy proposals
IPv6 Address Space Management A follow up to RIPE-261
Status Report on Policy Implementation at the APNIC Secretariat
Database SIG APNIC19 24 February 2005, Kyoto, Japan
IPv6 Policy Update ~ APNIC community ~
prop-081-v001: Eligibility for assignments from the final /8
Policy Development Process
Presentation transcript:

prop-064-v002 Change to assignment policy for AS numbers APNIC26 - Christchurch NZ

prop-064-v002 A change to APNIC-094 “Policies for Autonomous System number management in the Asia Pacific region” http://www.apnic.net/policy/asn-policy.html

prop-064-v002 The policy seeks to create awareness earlier within the community for the need to support 4-byte AS numbers without mandating an absolute final adoption of 4-byte AS numbers.

prop-064-v002 Current policy 1 January 2007 APNIC assigns two-byte AS numbers by default. APNIC assigns four-byte AS numbers on request. 1 January 2009 APNIC assigns four-byte AS numbers by default APNIC assigns two-byte AS numbers on request. 1 January 2010 APNIC ceases to make any distinction between two- and four-byte AS numbers. APNIC assigns from an undifferentiated four-byte AS number pool.

prop-064-v002 Problem Specific jump from “must request 2byte” to general 4byte Providers are likely to continue to request 2byte Lack of pressure to Vendors/Service Providers

prop-064-v002 Seeks to create feedback by involving the Provider/Peer in the resource request. CUSTOMER -> LIR -> PROVIDER -> VENDOR

prop-064-v002 Details of the Proposal From 01/07/09 an LIR requesting a 2-Byte AS number would need to demonstrate they cannot announce a 4- Byte AS

prop-064-v002 Proposed policy 1 January 2007 APNIC assigns two-byte AS numbers by default APNIC assigns four-byte AS numbers on request. 1 January 2009 APNIC assigns four-byte AS numbers by default. APNIC assigns two-byte AS numbers on request. 1 July 2009 APNIC assigns four-byte AS numbers by default. APNIC assigns two-byte AS numbers if a four-byte AS number is demonstrated to be unsuitable 1 January 2010 APNIC ceases to make any distinction between two-and four-byte AS numbers. APNIC assigns from an undifferentiated four-byte AS number pool.

prop-064-v002 Key Benefits - Makes more service providers aware of the requirement to support 4Byte AS numbers - Information on the status of support will be documented - Providers will put pressure on Vendors - Increases the chance of orderly transition

prop-064-v002 Key Disadvantages - Will create more work per AS assignment for APNIC staff

prop-064-v002 Mailing List feedback - positive support - request for APNIC to publish providers lacking support - suggestion it would be interesting to raise at ARIN - suggestion to remove “request 2byte” stage (1/1/09) - suggestion to push default allocation out till exhaustion

prop-064-v002 Questions/Comments ?