Keyboard Shortcuts
Thread View
j: Next unread messagek: Previous unread messagej a: Jump to all threadsj l: Jump to MailingList overview
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear SIG members,
Version 2 of the proposal, 'Inter-RIR IPv4 address transfer proposal', has been sent to the Policy SIG for review. It will be presented at the Policy SIG at APNIC 31 in Hong Kong SAR, China, 21-25 February 2011.
Change in version 2:
- Correction of co-author's name, Fuminori Tanizaki.
We invite you to review and comment on the proposal on the mailing list before the meeting.
The comment period on the mailing list before an APNIC meeting is an important part of the policy development process. We encourage you to express your views on the proposal:
- Do you support or oppose this proposal? - Does this proposal solve a problem you are experiencing? If so, tell the community about your situation. - Do you see any disadvantages in this proposal? - Is there anything in the proposal that is not clear? - What changes could be made to this proposal to make it more effective?
Information about this and other policy proposals is available from:
http://www.apnic.net/policy/proposals
Gaurab, Ching-Heng, and Terence
_______________________________________________________________________
prop-095-v001: Inter-RIR IPv4 address transfer proposal _______________________________________________________________________
Author: Tomohiro Fujisaki
Co-authors: Fuminori Tanizaki Masaru Akai Toshio Tachibana Akira Nakagawa
Version: 2
Date: 22 February 2011
1. Introduction - ----------------
This is a proposal to allow and define a mechanism for the transfer of IPv4 address space between APNIC account holders and organizations in other RIR region(s), providing that the counterpart RIR has a policy that allows transfers of address space with APNIC account holders.
2. Definitions - --------------
2.1 Source
When the source is from the APNIC region, the definition of "source" from the active APNIC transfer policy [1] is to be used. That is, the source must be a current APNIC account holder.
When the source of the transfer is from another RIR region, then the source must be that RIR's equivalent to the "source" defined in the active APNIC transfer policy.
2.2 Recipient
When the recipient is from the APNIC region, the definition of "recipient" from the active APNIC transfer policy is to be used. That is, the recipient must be a current APNIC account holder.
When the recipient of the transfer is from another RIR region, then the recipient must be that RIR's equivalent to the "recipient" defined in the active APNIC transfer policy.
3. Summary of the current problem - ----------------------------------
The goal of the APNIC transfer policy was to help distribute IPv4 addresses from those who no longer need the addresses to organizations that need the addresses, but can no longer obtain them from their RIR.
However, the current APNIC transfer policy is restricted to IPv4 transfers within the APNIC region. It does not allow transfers between APNIC account holders and organizations with IPv4 addresses registered with other RIRs. This restriction limits the ability of APNIC's transfer policy's goal of allowing IPv4 addresses to be transferred to networks that need them by preventing surplus and need to be balanced across regional boundaries as well as within the APNIC region.
4. Situation in other RIRs - ---------------------------
ARIN:
The ARIN policy proposal 119, "Globally Coordinated Transfer Policy," is currently on the ARIN Address Council's docket for development and evaluation:
http://lists.arin.net/pipermail/arin-ppml/2010-October/018588.html
There are no similar proposals in the AfriNIC, LACNIC or RIPE regions.
5. Details - -----------
It is proposed that:
5.1 Inter-RIR transfers be permitted when the other RIR involved in the transfer has a policy in place that permits transfers of IPv4 address space between APNIC and their own region.
5.2 APNIC acknowledge and process the transfer of IPv4 space to a current APNIC account holder according to the following processes and conditions:
5.2.1 Conditions on the space to be transferred
- The IPv4 address space should be under the management of the counterpart RIR.
- The authentic holder of the space should match with the source without any disputes.
5.2.2 Conditions on the transfer
- The conditions defined by the active policy of the counterpart RIR at the time of transfer will apply. This includes conditions such as the size of the transfer, requirements for justification on utilization, or any other conditions included in the counterpart RIR's policy.
- APNIC should provide the necessary documentation to the counterpart RIR.
5.2.3 Approval of the transfer
The transfer must have the approval of both the counterpart RIR and APNIC to proceed with the transfer, with confirmation that both the source and recipient have agreed to the transfer.
5.3 APNIC acknowledge and process the transfer of IPv4 space from a current APNIC account holder to another RIR region according to the following processes and conditions:
5.3.1 Conditions on the space to be transferred
- The IPv4 address space should be under the management of APNIC.
- The authentic holder of the space should match with the source without any disputes.
5.3.2 Conditions on the transfer
- The conditions defined by APNIC's transfer policy active at the time of transfer will apply. This includes conditions such as the size of the transfer, requirements for justification on utilization, or any other conditions included in APNIC's transfer policy.
- The counterpart RIR should provide the necessary documentation to APNIC
5.3.3 Approval of the transfer
The transfer must have the approval of both the counterpart RIR and APNIC to proceed with the transfer, with confirmation that both the source and recipient have agreed to the transfer.
6. Pros/Cons - -------------
Advantages:
- This proposal will expand the scope of transferable IPv4 address space outside of the APNIC region, and therefore better meet the goals of the APNIC transfer policy.
Disadvantages:
- The other RIR's transfer policy will apply when the source of the transfer is from the other RIR's region. This could potentially create confusion for APNIC account holders expecting APNIC's transfer policy to apply.
7. Effect on APNIC - -------------------
When APNIC account holders are the recipient of a transfer, and the source is located in another RIR, the account holder must be aware of the transfer policy in place at that other RIR.
8. Effect on NIRs - ------------------
NIRs are given a choice on whether to adopt this policy. If NIRs choose to adopt this policy, the transfer procedure will be processed via APNIC.
9. References - --------------
[1] Section 3, "Transfers of IPv4 addresses," in "APNIC transfer, merger, acquisition, and takeover policy" http://www.apnic.net/policy/transfer-policy
I support the context of the proposal, inter-RIR transfers. I would suggest that the author consider supplanting this text with similar text to the ARIN proposal that he references. Having a globally coordinated policy for inter-rir transfer will be key to being successful.
The URL for that proposal is :
https://www.arin.net/policy/proposals/2011_1.html
Best,
-M<
On 2/22/11 12:00 AM, "Gaurab Raj Upadhaya" gaurab@lahai.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear SIG members,
Version 2 of the proposal, 'Inter-RIR IPv4 address transfer proposal', has been sent to the Policy SIG for review. It will be presented at the Policy SIG at APNIC 31 in Hong Kong SAR, China, 21-25 February 2011.
Change in version 2:
- Correction of co-author's name, Fuminori Tanizaki.We invite you to review and comment on the proposal on the mailing list before the meeting.
The comment period on the mailing list before an APNIC meeting is an important part of the policy development process. We encourage you to express your views on the proposal:
- Do you support or oppose this proposal? - Does this proposal solve a problem you are experiencing? If so, tell the community about your situation. - Do you see any disadvantages in this proposal? - Is there anything in the proposal that is not clear? - What changes could be made to this proposal to make it more effective?Information about this and other policy proposals is available from:
http://www.apnic.net/policy/proposalsGaurab, Ching-Heng, and Terence
prop-095-v001: Inter-RIR IPv4 address transfer proposal _______________________________________________________________________
Author: Tomohiro Fujisaki
Co-authors: Fuminori Tanizaki Masaru Akai Toshio Tachibana Akira Nakagawa
Version: 2
Date: 22 February 2011
- Introduction
This is a proposal to allow and define a mechanism for the transfer of IPv4 address space between APNIC account holders and organizations in other RIR region(s), providing that the counterpart RIR has a policy that allows transfers of address space with APNIC account holders.
- Definitions
2.1 Source
When the source is from the APNIC region, the definition of "source" from the active APNIC transfer policy [1] is to be used. That is, the source must be a current APNIC account holder. When the source of the transfer is from another RIR region, then the source must be that RIR's equivalent to the "source" defined in the active APNIC transfer policy.2.2 Recipient
When the recipient is from the APNIC region, the definition of "recipient" from the active APNIC transfer policy is to be used. That is, the recipient must be a current APNIC account holder. When the recipient of the transfer is from another RIR region, then the recipient must be that RIR's equivalent to the "recipient" defined in the active APNIC transfer policy.
- Summary of the current problem
The goal of the APNIC transfer policy was to help distribute IPv4 addresses from those who no longer need the addresses to organizations that need the addresses, but can no longer obtain them from their RIR.
However, the current APNIC transfer policy is restricted to IPv4 transfers within the APNIC region. It does not allow transfers between APNIC account holders and organizations with IPv4 addresses registered with other RIRs. This restriction limits the ability of APNIC's transfer policy's goal of allowing IPv4 addresses to be transferred to networks that need them by preventing surplus and need to be balanced across regional boundaries as well as within the APNIC region.
- Situation in other RIRs
ARIN:
The ARIN policy proposal 119, "Globally Coordinated Transfer Policy," is currently on the ARIN Address Council's docket for development and evaluation: http://lists.arin.net/pipermail/arin-ppml/2010-October/018588.htmlThere are no similar proposals in the AfriNIC, LACNIC or RIPE regions.
- Details
It is proposed that:
5.1 Inter-RIR transfers be permitted when the other RIR involved in the transfer has a policy in place that permits transfers of IPv4 address space between APNIC and their own region.
5.2 APNIC acknowledge and process the transfer of IPv4 space to a current APNIC account holder according to the following processes and conditions:
5.2.1 Conditions on the space to be transferred - The IPv4 address space should be under the management of the counterpart RIR. - The authentic holder of the space should match with the source without any disputes. 5.2.2 Conditions on the transfer - The conditions defined by the active policy of the counterpart RIR at the time of transfer will apply. This includes conditions such as the size of the transfer, requirements for justification on utilization, or any other conditions included in the counterpart RIR's policy. - APNIC should provide the necessary documentation to the counterpart RIR. 5.2.3 Approval of the transfer The transfer must have the approval of both the counterpart RIR and APNIC to proceed with the transfer, with confirmation that both the source and recipient have agreed to the transfer.5.3 APNIC acknowledge and process the transfer of IPv4 space from a current APNIC account holder to another RIR region according to the following processes and conditions:
5.3.1 Conditions on the space to be transferred - The IPv4 address space should be under the management of APNIC. - The authentic holder of the space should match with the source without any disputes. 5.3.2 Conditions on the transfer - The conditions defined by APNIC's transfer policy active at the time of transfer will apply. This includes conditions such as the size of the transfer, requirements for justification on utilization, or any other conditions included in APNIC's transfer policy. - The counterpart RIR should provide the necessary documentation to APNIC 5.3.3 Approval of the transfer The transfer must have the approval of both the counterpart RIR and APNIC to proceed with the transfer, with confirmation that both the source and recipient have agreed to the transfer.
- Pros/Cons
Advantages:
- This proposal will expand the scope of transferable IPv4 address space outside of the APNIC region, and therefore better meet the goals of the APNIC transfer policy.Disadvantages:
- The other RIR's transfer policy will apply when the source of the transfer is from the other RIR's region. This could potentially create confusion for APNIC account holders expecting APNIC's transfer policy to apply.
- Effect on APNIC
When APNIC account holders are the recipient of a transfer, and the source is located in another RIR, the account holder must be aware of the transfer policy in place at that other RIR.
- Effect on NIRs
NIRs are given a choice on whether to adopt this policy. If NIRs choose to adopt this policy, the transfer procedure will be processed via APNIC.
- References
[1] Section 3, "Transfers of IPv4 addresses," in "APNIC transfer, merger, acquisition, and takeover policy" http://www.apnic.net/policy/transfer-policy -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1jQtIACgkQSo7fU26F3X3V6QCgg99rWSrdOth5f6D5qeSxOWn2 ESAAoIewVR5JC/pPNLj4+m98v8+kXRZR =JBP1 -----END PGP SIGNATURE-----
sig-policy: APNIC SIG on resource management policy
sig-policy mailing list sig-policy@lists.apnic.net http://mailman.apnic.net/mailman/listinfo/sig-policy
Having a globally coordinated policy for inter-rir transfer will be key to being successful.
having a globally coordinated policy for X, for almost all values of X, varies from extremely hard to impossible.
in this case, all that is needed was suggested a few years back, the source of the transfer should comply with the source *IR's policies, and the destination of the transfer should comply with the destination *IR's policies.
there is no need for the source IR to tell the destination IR what its policies should be or vice versa.
randy
On Feb 22, 2011, at 11:21 AM, Randy Bush wrote:
Having a globally coordinated policy for inter-rir transfer will be key to being successful.
having a globally coordinated policy for X, for almost all values of X, varies from extremely hard to impossible.
in this case, all that is needed was suggested a few years back, the source of the transfer should comply with the source *IR's policies, and the destination of the transfer should comply with the destination *IR's policies.
there is no need for the source IR to tell the destination IR what its policies should be or vice versa.
randy
sig-policy: APNIC SIG on resource management policy *
sig-policy mailing list sig-policy@lists.apnic.net http://mailman.apnic.net/mailman/listinfo/sig-policy
That is pretty much what the ARIN proposal says, Randy.
So you are objecting to what you are asking for.
Owen
On Feb 23, 2011, at 3:28 AM, Owen DeLong wrote:
On Feb 22, 2011, at 11:21 AM, Randy Bush wrote:
there is no need for the source IR to tell the destination IR what its policies should be or vice versa.
That is pretty much what the ARIN proposal says, Randy. So you are objecting to what you are asking for.
For clarity, the ARIN policy proposal also includes the requirement for the RIRs to:
"maintain compatible, needs-based transfer policies that exercise Internet stewardship consistent with the values expressed in RFC2050."
While this does not direct specific policies, it does imply inter-RIR commitment to the common policy framework.
/John
John Curran President and CEO ARIN
For clarity, the ARIN policy proposal also includes the requirement for the RIRs to:
"maintain compatible, needs-based transfer policies that exercise Internet stewardship consistent with the values expressed in RFC2050."
While this does not direct specific policies, it does imply inter-RIR commitment to the common policy framework.
now why am i not surprised at an arin policy proposal which tells the rest of the world how they should run their things?
randy
Activity Summary
- 4594 days inactive
- 4594 days old
- sig-policy@lists.apnic.net
- 5 participants
- 5 comments