This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
- Previous message (by thread): [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
- Next message (by thread): [address-policy-wg] 2014-12 Proposal Accepted (Allow IPv6 Transfers)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
sandrabrown at ipv4marketgroup.com
sandrabrown at ipv4marketgroup.com
Wed Mar 11 16:01:39 CET 2015
Hi Andrea, At APNIC39 in Fukuoka, I spoke with Adam Gosling of APNIC. He suggested that the APNIC EC would wait for an interpretation and implementation of the new RIPE inter-RIR policy before making a decision. But, as reflected in the discussion already made, he did feel that an APNIC to RIPE transfer would not be subjected to needs justification because he (and APNIC in general) do not interpret APNIC policy as requiring needs justification if the receiving RIR does not. Two comments on this: Why would APNIC to RIPE not require needs justification when APNIC to APNIC does? Secondly, there are so few IPs within APNIC, how often will there ever be IPs transferred from APNIC to RIPE region under the inter-RIR policy? I would not think this is a big transfer path. The reality is that the huge supply of IPs for transfer to RIPE is in ARIN region and this supply is the target of the new RIPE inter-RIR policy. If APNIC never allows transfer to RIPE region, this would be ok from the perspective of supply to RIPE region. In fact this would be preferable to APNIC allowing transfers with no needs justification, such that ARIN then flipped its position to block transfers to APNIC because they could subsequently to transferred to RIPE. A more tangible flaw is that APNIC has no time delay on re-transfers. While ARIN would not allow a transferred block to be re-transferred for 12 months and RIPE would not allow a transferred block to be re-transferred for 24 months, APNIC has no limitation. But this problem exists today for IPs transferred to APNIC; they can immediately be re-transferred within APNIC. No change just because they could now be transferred to RIPE region, so I can't see ARIN complaining about this now. ARIN being concerned with APNIC allowing transfers to APNIC being subsequently transferred to RIPE should not influence the implementation of direct transfers from ARIN to RIPE using the new needs justification criteria of 50% use over 5 years that ARIN had agreed was compatible with its policy. Based on this analysis, I don't see the initial buy-in or non-buy-in by APNIC as a concern. It is ARIN as a supply that is needed. Sandra Brown Message: 3 Date: Tue, 10 Mar 2015 17:03:03 +0000 From: Nick Hilliard <nick at inex.ie> To: Andrea Cima <andrea at ripe.net>, Address Policy Working Group <address-policy-wg at ripe.net> Subject: Re: [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC? Message-ID: <54FF23C7.4020403 at inex.ie> Content-Type: text/plain; charset=utf-8 Hi Andrea, On 10/03/2015 16:05, Andrea Cima wrote: > While I cannot answer on behalf of the other RIRs, we have given an > update about the inter-RIR transfer policy proposal last week, during > APNIC 39. I hope the video and transcripts will provide you with the > clarification requested (please see session Policy SIG-3) thanks for the reference. The context is located at pages 35-49 of: https://conference.apnic.net/data/39/5-March-Policy-SIG-3.txt and at: https://www.youtube.com/watch?v=2iKK_8iJU6E#t=1h09m11s Nick
- Previous message (by thread): [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
- Next message (by thread): [address-policy-wg] 2014-12 Proposal Accepted (Allow IPv6 Transfers)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]