sig-policy March 2013

sig-policy@lists.apnic.net

2 participants
5 discussions

IMPORTANT: Correction on status of Prop 105 - returned to the mailing list
by Andy Linton 05 Mar '13

05 Mar '13

My apologies to the authors of this proposal and to the members of the list. I recently posted updates about the status of the two proposals discussed at APNIC 35 and I got the results mixed up. The following is the corrected report: ---- Dear SIG Members Version 1 of prop-105: Distribution of returned IPv4 address blocks (Modification of prop-088), did not reach consensus at the APNIC 35 Policy SIG. This proposal is being returned to the author and the Policy SIG mailing list for further work and discussion. The text of the proposal follows for your reference. Kind Regards, Andy, Masato and Skeeve ---------------------------------------------------------------------- prop-105-v001: Distribution of returned IPv4 address blocks (Modification of prop-088) ---------------------------------------------------------------------- Authors: Tomohiro Fujisaki fujisaki(a)syce.net JP IPv4 address allocation discussion team 1. Introduction --------------- After the final /8 policy is implemented, IPv4 address blocks received by APNIC are handled as being part of the final /8 pool and to redistribute these resources according to the final /8 policy (prop-088). This policy proposes to define a separate distribution policy for all non-103 IPv4 address blocks in the APNIC pool, to start the distributions once "Global policy for post exhaustion IPv4 allocation mechanisms by the IANA" is activated. 2. Summary ---------- While rapid implementation of IPv6 is in progress throughout the APNIC region, demands for IPv4 address still continue. According to our survey conducted to the APNIC community, over 70% of the respondents expressed the needs to receive IPv4 address space, if a separate distribution policy is defined from the final /8 policy. In May 2012, the global policy “Global Policy for Post Exhaustion: IPv4 Allocation Mechanisms by the IANA” was ratified by ICANN board, and it will be implemented soon. Based on this policy, IPv4 address space returned to IANA will be distributed to RIRs, and its size is not expected to be so large but substantial enough to be able to consider an additional minimum allocation for APNIC members. Currently, these address blocks will be added to the reserve for distributions according to the final /8 policy, in addition to 103/8 block already reserved for the purpose. Therefore, even if additional blocks are added in APNIC's pool while reserves remain in the 103/8 block range, it is reserved for distribution under the final /8 policy. We propose to distribute this newly received address block and address blocks returned to APNIC to APNIC account holders. 3. Situation in other RIRs -------------------------- ARIN: no final /8 like policy. RIPE-NCC: similar /8 policy. 4. Details ---------- Modify prop-088 to distribute non-103 IPv4 address blocks to APNIC account holders who meet the IPv4 distribution criteria define in APNIC policies. If APNIC account holder, who was allocated an /22 from final /8 pool, needs an additional IPv4 address block, they are eligible to receive another distribution of IPv4 block. The same policy as the final /8 policy will be appied in terms of the criteria and the size of the distribution given the requestor has utilized a total of /22 block from 103/8. This policy will be effective after allocation of returned IPv4 address blocks from IANA, based on "Global policy for post exhaustion IPv4 allocation mechanisms by the IANA". The distribution policy for 103/8 block will remain unchanged, based on the final /8 policy. 5. Pros/Cons ------------ Advantages: Able to utilize non-103/8 address pool in APNIC for immediate distribution, instead of keeping as a reserve, in addition to 103/8. Disadvantages: Some may feel the concern that adopting this policy discourages IPv6 deployment in the APNIC region. However, according to our survey, majority of the respondents responded revising the policy does not impact their IPv6 deployment plan. 6. Effect on APNIC ------------------ APNIC account holders can obtain one more IPv4 block of minimum allocation size as the upper limit (currently /22). 7. Effect on NIRs ----------------- NIRs can choose whether to implement this policy or not.

1 0

IMPORTANT: Correction on status of Prop 106 - proposal abandoned
by Andy Linton 05 Mar '13

05 Mar '13

My apologies to the authors of this proposal and to the members of the list. I recently posted updates about the status of the two proposals discussed at APNIC 35 and I got the results mixed up. The following is the corrected report: ---- Dear SIG Members Version 2 of prop-106: Restricting excessive IPv4 address transfers under the final /8 block, did not reach consensus at the APNIC 35 Policy SIG. As a result the proposal was abandoned by the Chairs. The text of the proposal follows for your reference. Kind Regards, Andy, Masato and Skeeve ------------------------------------------------------------------------ prop-106-v002: Clarifying operational practices in the APNIC region for transfers under the final /8 delegation ------------------------------------------------------------------------ Authors: Shin SHIRAHATA shin(a)clara.ad.jp Tomohiro Fujisaki fujisaki(a)syce.net 1. Introduction --------------- The current APNIC IPv4 address management policy clearly states that "each new or existing APNIC account holder is only eligible to request and receive delegations totalling a maximum /22 worth of address space from the APNIC IPv4 address pool." When the final /8 policy was implemented, the possible loophole to the policy was pointed out for people who try to obtain multiple /22s from the final /8 block. It was argued it can be addressed by the APNIC secretariat taking adequate actions when it finds such cases. However, there are no clearly written descriptions in APNIC documents for the secretariat to refer to, in order to take operational measures for such cases. Based on our observations of the APNIC transfer history records, some LIRs seems to collect IPv4 address blocks under the final /8 range by using multiple accounts, and transfer these blocks to a single account. We believe having a clearly described operational guidelines for the APNIC secretariat would help them take adequate actions when they find such cases. 2. Summary ---------- This policy proposes to clearly define, as the operational guidelines that APNIC may not approve transfers under the final /8 block for cases against the spirit of the final /8 policy. The current number of "misused" transfers may not be large enough to apply restrictions as APNIC policy. However, if "misused" transfers are not desirable in principle, it would be good to allow some capabilities for APNIC secretariat to refrain from approving such transfers as an operational decision, when it clearly finds the case of misuse. This would help the APNIC secretariat to have an APNIC document to refer to, and to take adequate actions when it finds such cases. 3. Situation in other RIRs -------------------------- No similar policy at other RIRs. 4. Details ---------- We propose to add following text in the APNIC guidelines document about IPv4 address transfers under the final /8 block. - For transfers of address blocks approved the final /8 policy, APNIC/NIR will confirm if it matches with the spirit of the final /8 policy. - When APNIC/NIR confirm requested transfers do not match with the spirit of the final /8 policy, it cannot guarantee to approve such transfers This would allow APNIC/NIRs referring to the guidelines document, when they find the case of misuse. 5. Pros/Cons ------------ Advantages: - Allow the APNIC secretariat to take adequate actions when they clearly find the case of misuse against the spirit of the final /8 policy. - It would not have a strong restriction as in the policy. Disadvantages: - There may be some opinions about the need to address the problem at this stage. 6. Effect on APNIC ------------------ Needs to justify transfers of IPv4 address blocks under the final /8 block if it matches with the spirit of final /8 policy. 7. Effect on NIRs ----------------- NIRs need to adopt this policy.

1 0

Draft of merged APNIC Policy Document
by Adam Gosling 05 Mar '13

05 Mar '13

Hello SIG Members In the Documentation Update at APNIC 35, Singapore, I reported on the work done to merge all the APNIC resource policies into a single document. The move is intended to reduce maintenance while increasing accessibility and cohesion in the policy framework. You can access the Documentation Update presentation from this page: http://conference.apnic.net/35/policy As the restructuring is significant the initial drafts are being made available for two months for informal feedback and discussion before the document is posted for a one month Editorial Comment in accordance with the APNIC Document Editorial Policy. Below are two links. One in Microsoft Word format and a PDF version. https://www.apnic.net/policy/drafts/DRAFT_apnic-resource-policies_20130305.… https://www.apnic.net/policy/drafts/DRAFT_apnic-resource-policies_20130305.… Please provide comments and feedback on any aspect of the document and the work done to merge the policies. Send comments to policy(a)apnic.net before 17:00 (UTC+10) on Monday, 6 May 2013. Kind regards, Adam -- Adam Gosling Senior Policy Specialist email: adam(a)apnic.net APNIC sip: adam(a)voip.apnic.net http://www.apnic.net phone: +61 7 3858 3100 ________________________________________________________________________ * Sent by email to save paper. Print only if necessary.

1 0

prop-105 abandoned at APNIC 35
by Andy Linton 03 Mar '13

03 Mar '13

Dear SIG Members Version 1 of prop-105: Distribution of returned IPv4 address blocks (Modification of prop-088), did not reach consensus at the APNIC 35 Policy SIG. As a result the proposal was abandoned by the Chairs. The text of the proposal follows for your reference. Kind Regards, Andy, Masato and Skeeve ---------------------------------------------------------------------- prop-105-v001: Distribution of returned IPv4 address blocks (Modification of prop-088) ---------------------------------------------------------------------- Authors: Tomohiro Fujisaki fujisaki(a)syce.net JP IPv4 address allocation discussion team 1. Introduction --------------- After the final /8 policy is implemented, IPv4 address blocks received by APNIC are handled as being part of the final /8 pool and to redistribute these resources according to the final /8 policy (prop-088). This policy proposes to define a separate distribution policy for all non-103 IPv4 address blocks in the APNIC pool, to start the distributions once "Global policy for post exhaustion IPv4 allocation mechanisms by the IANA" is activated. 2. Summary ---------- While rapid implementation of IPv6 is in progress throughout the APNIC region, demands for IPv4 address still continue. According to our survey conducted to the APNIC community, over 70% of the respondents expressed the needs to receive IPv4 address space, if a separate distribution policy is defined from the final /8 policy. In May 2012, the global policy “Global Policy for Post Exhaustion: IPv4 Allocation Mechanisms by the IANA” was ratified by ICANN board, and it will be implemented soon. Based on this policy, IPv4 address space returned to IANA will be distributed to RIRs, and its size is not expected to be so large but substantial enough to be able to consider an additional minimum allocation for APNIC members. Currently, these address blocks will be added to the reserve for distributions according to the final /8 policy, in addition to 103/8 block already reserved for the purpose. Therefore, even if additional blocks are added in APNIC's pool while reserves remain in the 103/8 block range, it is reserved for distribution under the final /8 policy. We propose to distribute this newly received address block and address blocks returned to APNIC to APNIC account holders. 3. Situation in other RIRs -------------------------- ARIN: no final /8 like policy. RIPE-NCC: similar /8 policy. 4. Details ---------- Modify prop-088 to distribute non-103 IPv4 address blocks to APNIC account holders who meet the IPv4 distribution criteria define in APNIC policies. If APNIC account holder, who was allocated an /22 from final /8 pool, needs an additional IPv4 address block, they are eligible to receive another distribution of IPv4 block. The same policy as the final /8 policy will be appied in terms of the criteria and the size of the distribution given the requestor has utilized a total of /22 block from 103/8. This policy will be effective after allocation of returned IPv4 address blocks from IANA, based on "Global policy for post exhaustion IPv4 allocation mechanisms by the IANA". The distribution policy for 103/8 block will remain unchanged, based on the final /8 policy. 5. Pros/Cons ------------ Advantages: Able to utilize non-103/8 address pool in APNIC for immediate distribution, instead of keeping as a reserve, in addition to 103/8. Disadvantages: Some may feel the concern that adopting this policy discourages IPv6 deployment in the APNIC region. However, according to our survey, majority of the respondents responded revising the policy does not impact their IPv6 deployment plan. 6. Effect on APNIC ------------------ APNIC account holders can obtain one more IPv4 block of minimum allocation size as the upper limit (currently /22). 7. Effect on NIRs ----------------- NIRs can choose whether to implement this policy or not.

1 0

prop-106 returned to mailing list at APNIC 35
by Andy Linton 03 Mar '13

03 Mar '13

Dear SIG Members Version 2 of prop-106: Restricting excessive IPv4 address transfers under the final /8 block, did not reach consensus at the APNIC 35 Policy SIG. Therefore, this proposal is being returned to the author and the Policy SIG mailing list for further work and discussion. The text of the proposal follows for your reference. Kind Regards, Andy, Masato and Skeeve ------------------------------------------------------------------------ prop-106-v002: Clarifying operational practices in the APNIC region for transfers under the final /8 delegation ------------------------------------------------------------------------ Authors: Shin SHIRAHATA shin(a)clara.ad.jp Tomohiro Fujisaki fujisaki(a)syce.net 1. Introduction --------------- The current APNIC IPv4 address management policy clearly states that "each new or existing APNIC account holder is only eligible to request and receive delegations totalling a maximum /22 worth of address space from the APNIC IPv4 address pool." When the final /8 policy was implemented, the possible loophole to the policy was pointed out for people who try to obtain multiple /22s from the final /8 block. It was argued it can be addressed by the APNIC secretariat taking adequate actions when it finds such cases. However, there are no clearly written descriptions in APNIC documents for the secretariat to refer to, in order to take operational measures for such cases. Based on our observations of the APNIC transfer history records, some LIRs seems to collect IPv4 address blocks under the final /8 range by using multiple accounts, and transfer these blocks to a single account. We believe having a clearly described operational guidelines for the APNIC secretariat would help them take adequate actions when they find such cases. 2. Summary ---------- This policy proposes to clearly define, as the operational guidelines that APNIC may not approve transfers under the final /8 block for cases against the spirit of the final /8 policy. The current number of "misused" transfers may not be large enough to apply restrictions as APNIC policy. However, if "misused" transfers are not desirable in principle, it would be good to allow some capabilities for APNIC secretariat to refrain from approving such transfers as an operational decision, when it clearly finds the case of misuse. This would help the APNIC secretariat to have an APNIC document to refer to, and to take adequate actions when it finds such cases. 3. Situation in other RIRs -------------------------- No similar policy at other RIRs. 4. Details ---------- We propose to add following text in the APNIC guidelines document about IPv4 address transfers under the final /8 block. - For transfers of address blocks approved the final /8 policy, APNIC/NIR will confirm if it matches with the spirit of the final /8 policy. - When APNIC/NIR confirm requested transfers do not match with the spirit of the final /8 policy, it cannot guarantee to approve such transfers This would allow APNIC/NIRs referring to the guidelines document, when they find the case of misuse. 5. Pros/Cons ------------ Advantages: - Allow the APNIC secretariat to take adequate actions when they clearly find the case of misuse against the spirit of the final /8 policy. - It would not have a strong restriction as in the policy. Disadvantages: - There may be some opinions about the need to address the problem at this stage. 6. Effect on APNIC ------------------ Needs to justify transfers of IPv4 address blocks under the final /8 block if it matches with the spirit of final /8 policy. 7. Effect on NIRs ----------------- NIRs need to adopt this policy.

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

sig-policy March 2013