sig-policy September 2004

sig-policy@lists.apnic.net

6 participants
4 discussions

Final call for comments: [prop-021-v001] "Expansion of the initial allocation space for existing IPv6 address space holders"
by APNIC Secretariat 22 Sep '04

22 Sep '04

Dear colleagues APNIC welcomes comments, questions, and suggestions on the following policy proposal: ____________________ Final call for comments: [prop-021-v001] "Expansion of the initial allocation space for existing IPv6 address space holders" ____________________ This is the final call for comments on policy proposal [prop-021-v001] "Expansion of the initial allocation space for existing IPv6 address space holders". This is a proposal to allow existing IPv6 address holders to expand their initial allocation, using their existing IPv4 infrastructure to justify an allocation larger than a /32. The use of IPv4 infrastructure to justify a larger initial allocation was passed at APNIC 17 [prop-016-v002]. This current proposal allows networks that received an initial allocation before prop-0160-v001 to be given the same opportunity to recieve an initial allcoation greater than /32. This proposal was presented at APNIC 18 and the following consensus was reached: "to implement the proposal to expand IPv6 address space holdings for existing users without satisfying the subsequent allocation criteria." This proposal is now submitted to the sig-policy mailing list for an eight week discussion period. At the end of that period, if consensus appears to have been achieved, the Chair of the Policy SIG will ask the Executive Council to endorse the proposal for implementation. * Send all comments and questions to: <sig-policy(a)apnic.net> * Deadline for comments: 12 November 2004 _____________________________________________________________________ Proposal details _____________________________________________________________________ Introduction: I propose making it possible for existing IPv6 address holders with the initial allocation address space to expand their address space without clearing the subsequent allocation requirement. This proposal has reached a consensus at JPNIC Open Policy Meeting. Summary of the current problem: In the past, many of the organizations had requested for the minimum allocation size(/32) as an initial allocation due to the following reasons: + Based on the idea of the "slow start" in IPv4 policy, many organizations believed it would be difficult to justify all of their address requirements at an initial allocation. + It was difficult to estimate their needs as IPv6 network was not commercially developed. Many organizations requested for address space for a test service in order to kick off the commercial service, not for the commercial service itself. + `PROVISIONAL IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT' specified the initial allocation size as /35. LIRs which received allocations under this policy were only allowed an upgrade of their allocations to a /32. In recent days, most of the ISPs learned that /32 space is too small for the real scale service deployment if they cover their existing IPv4 users. Organizations currently requesting for initial allocations can simply request for a larger space as the RIRs actively emphasize to their communities that they are able to request for allocations greater than /32, which is already a common practice. However, ISPs with the default address space need to design the IPv6 service network within the small space untill they clear the subsequent allocation requirement (HD-Ratio) for more address space. This makes the real IPv6 service deployment difficult, especially for large ISPs. Situation in other RIRs: none. Details of your proposal: Existing IPv6 initial allocation address holders should be able to expand their address space without satisfying subsequent allocation criteria if they are able to demonstrate their concrete plan. The same criteria should apply as organizations requesting for an initial allocation larger than /32. This proposal does not intend to change the current policy but to apply the current allocation practice to existing IPv6 address holders. If it is possible to expand the address space under the current policy, it is desirable to be documented clearly (e.g. in the guidelines document). Advantages and disadvantages of adopting the proposed policy: Advantages: Existing IPv6 address holders will be possible to start their services under up-to-date situation. Disadvantages: none Effect on APNIC members: The expanded address space would be considered in the assessment of the APNIC membership tier of the organization, on the renewal of their membership. Effect on NIRs: NIRs providing IPv6 address allocation service should apply the same policy. ____________________ References ____________________ Proposal details including full text of proposal, presentations, links to relevant meeting minutes, and links to mailing list discussions are available at: http://www.apnic.net/docs/policy/proposals/prop-021-v001.html ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ______________________________________________________________________

3 3

Final call for comments: [prop-005-v004] "IANA global IPv6 allocation policy"
by APNIC Secretariat 18 Sep '04

18 Sep '04

Dear colleagues APNIC welcomes comments, questions, and suggestions on the following policy proposal: ____________________ Final call for comments: [prop-005-v004] "IANA global IPv6 allocation policy" ____________________ This is the final call for comments on policy proposal [prop-005-v004] "IANA global IPv6 allocation policy". This proposal was presented at APNIC 18 and the original proposal was modified to include the following: - Defined allocation unit (suggested size is /12) - All allocations should be in multiples of the minimum allocation size (suggested to be as a single CIDR block) - IANA allocations are made for a defined period (suggested as 36 months) - RIR qualifies for subsequent allocation when a defined amount is utilised by allocation or reservation (suggested amount is 50 percent) - IANA to process requests according to NRO and IANA agreed procedures - Communication by IANA to RIRs only. Based on the modified proposal, the following consensus was reached: "to adopt the proposal governing the allocation of IPv6 address space from the IANA to the Regional Internet Registries (RIRs)" This proposal is now submitted to the sig-policy mailing list for an eight week discussion period. At the end of that period, if consensus appears to have been achieved, the Chair of the Policy SIG will ask the Executive Council to endorse the proposal for implementation. * Send all comments and questions to: <sig-policy(a)apnic.net> * Deadline for comments: 12 November 2004 _____________________________________________________________________ Proposal details _____________________________________________________________________ This document describes the policy governing the allocation of IPv6 address space from the IANA to the Regional Internet Registries (RIRs). This document does not stipulate performance requirements in the provision of services by IANA to an RIR in accordance with the policy. Such requirements should be specified by appropriate agreements among the RIRs and ICANN. 1. Allocation principles --------------------------- 1.1 The unit of IPv6 allocation (and therefore the minimum IPv6 allocation) from IANA to an RIR is a /12; 1.2 Every IPv6 allocation from IANA to an RIR will comprise a single CIDR prefix. 1.3 The IANA will allocate sufficient IPv6 address space to each RIR to support its registration needs for at least a 36 month period; 1.4 The IANA will allow each RIR to apply its own respective chosen allocation and reservation strategies in order to ensure the efficiency and efficacy of its work. 2. IANA allocations to RIRs ------------------------------ 2.1 Initial allocations On inception of this policy, each current RIR shall receive an IPv6 allocation from the IANA. Any new RIR shall, on recognition by ICANN, receive an IPv6 allocation from the IANA. 2.2 Additional allocations - Eligibility A RIR is eligible to receive additional IPv6 address space from the IANA when it has utilised (allocated or reserved) more than 50% of its total IPv6 address space holdings. 2.3 Size of additional allocations Each additional allocation to an RIR will be a number (one or more) of /12 blocks, sufficient to ensure that the RIR holds at least 36 months' supply of IPv6 address space. 3. Announcement of IANA allocations -------------------------------------- When address space is allocated to a RIR, the IANA will send a detailed announcement to the receiving RIR. The IANA will also make announcements to all other RIRs, informing them of the recent allocation. The RIRs will coordinate announcements to their respective membership lists and any other lists they deem necessary. The IANA will make appropriate modifications to the "Internet Protocol V6 Address Space" page of the IANA website and may make announcements to its own appropriate announcement lists. The IANA announcements will be limited to which address ranges, the time of allocation and to which Registry they have been allocated. ____________________ References ____________________ Proposal details including full text of proposal, presentations, links to relevant meeting minutes, and links to mailing list discussions are available at: http://www.apnic.net/docs/policy/proposals/prop-005-v004.html ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ______________________________________________________________________

2 1

Summary report of APNIC 18 Policy-SIG
by Toshiyuki Hosaka 09 Sep '04

09 Sep '04

Dear All, Please find the summary report of APNIC 18 Policy-SIG as below. For those who could not attend the onsite meeting (and for those could also), the proposals/presentations are available on APNIC website. http://www.apnic.net/meetings/18/programme/sigs/policy.html The formal minutes that will be posted to this mailing list soon will contain the list of action items. Thanks and best regards, Toshi -- Toshiyuki Hosaka / JPNIC --------------------------------------------------------------------- APNIC 18 Policy SIG summary 1. Overview There were 3 sessions to cover 10 presentations including 4 proposals. 93 attendees in Session 1, 92 in Session 2, 70 in Session 3. Yong Wan Ju stepped down from co-chair, and Toshiyuki Hosaka was elected to the new co-chair. Several rough consensus were reached as described in section 2. in this summary. 2. Proposals (1) prop-023-v001: proposal to prevent the routing of "dark" address space - Proposal summary: To withdraw address space from LIR who routes "dark" prefix. - Consensus was not reached. (2) prop-020-v001: Application of the HD ratio to IPv4 - Proposal summary: To apply HD ratio as IPv4 subsequent allocation criteria. - There was no clear consensus. - Consensus is to keep this proposal open. APNIC secretariat and NIRs to do a small survey on ISP address management problems. (3) prop-021-v001: Expansion of the initial allocation space for existing IPv6 address space holders - Proposal summary: To expand IPv6 address space for existing IPv6 address holders without satisfying the subsequent allocation requirements, with IPv6 deployment plan and/or with IPv4 infrastructure information. - Consensus was reached. (4) prop-005-v003: Internet Assigned Numbers Authority (IANA) policy for allocation of IPv6 blocks to Regional Internet Registries - Proposal summary: IPv6 Policy from IANA to RIRs - Consensus reached for the revised proposal, with some flexibility of parameters. Flexibility is left for consensus of other regions - Specific number of parameters will be discussed in ML 3. Informational Presentations 6 informational presentations were made. - IPv6 address space management - IPv6 policy status from ARIN, LACNIC, RIPE and APNIC communities - Unique Local IPv6 unicast addresses - Large space IPv4 trial usage program for future IPv6 deployment activities update vol.7 - Status report on APNIC policy implementations from APNIC 17 - IPv6 address assignment size for end-users --------------------------------------------------------------------- -- Toshiyuki Hosaka <hosaka(a)nic.ad.jp>

1 0

Extended deadline: Call for volunteers - Cable/DSL guidelines
by APNIC Secretariat 08 Sep '04

08 Sep '04

Dear colleagues, The deadline for accepting volunteers to join the working group to review the criteria for Cable and DSL requests described in the IPv4 guidelines document is being extended until Friday 24th September. The original call for volunteers is appended below. If you have expertise in managing address space assigned to cable and DSL networks and some spare time your contribution would be appreciated. To volunteer please send email to <sig(a)apnic.net>. Kind regards, Anne APNIC Secretariat ________________________________________________________________________ New Working Group: Criteria for Cable and DSL requests ________________________________________________________________________ Action pol-17-007: Proposer to call for the creation of a working group and volunteers to develop modified guidelines for cable and DSL networks in the IPv4 guidelines document. At the 17th APNIC Open Policy Meeting, the Policy SIG decided to review the guidelines for IPv4 requests for cable and DSL networks. The intention of the review is to develop modified guidelines for cable and DSL networks in the light of operational experience of the policies. This is a call for volunteers to join the working group. Volunteers will be responsible for contributing to and reviewing document contents. If you have some spare time that you can contribute to this effort, please email <sig(a)apnic.net> by September 6th, to join the editorial team. A mailing list <wg-ipv4-guide(a)apnic.net> will be live and ready to go after this deadline. We look forward to hearing from you.

3 2

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

sig-policy September 2004