Final consensus on 2015-01: Alignment of Transfer Requirements for IPv4 Allocations
Hello working group, We have reached the end of the last-call period for 2015-01 (Alignment of Transfer Requirements for IPv4 Allocations). After analysing the messages on the mailing list that were posted about 2015-01 after the last-call was announced I have come to the conclusion that the consensus declared at the end of the review phase still stands. I therefore declare final consensus on this policy proposal and ask the RIPE NCC to turn it into active policy and implement it. My decision is based on the following: Shahin Gharghi, Petr Umelov and Yuri@Ip4market argued that this proposal doesn't solve all problems. This has already been discussed and acknowledged during the review phase. No policy proposal will ever solve everything all at once. People wanting additional changes are encouraged to submit new policy proposals to address any remaining issues. Petr Umelov was under the impression that RIPE NCC receives a fixed size IPv4 block from IANA every 6 months, which is not correct as pointed out by Leo Vegoda. Petr Umelov and Vladimir Andreev also discussed the statistics on transfers and whether the trend justifies changing policy. Arguments that RIPE NCC has enough address space and a policy change would therefore not be necessary have already been discussed in the review phase and are considered addressed. Vladimir Andreev suggested writing a summary of the discussions so I hope he reads this email. Arash Naderpour argued that with 2015-01 existing LIRs cannot request their last /22 and then immediately transfer it. This has been discussed before: it is one of the actual goals of this policy: to stop LIRs from requesting a /22 just to transfer it. Sincerely, Sander Steffann APWG co-chair
22.07.2015, 15:14, "Sander Steffann" <sander@steffann.nl>:
Hello working group,
Shahin Gharghi, Petr Umelov and Yuri@Ip4market argued that this proposal doesn't solve all problems. This has already been discussed and acknowledged during the review phase. No policy proposal will ever solve everything all at once. People wanting additional changes are encouraged to submit new policy proposals to address any remaining issues.
If it wouldn't solve the problems - this would be okay and we could start new proposal, described this unresolved problems. But this proposal will increase multiple LIR accounts creation and the number of IPv4 will be decrease. Why don't you understand it?
Petr Umelov was under the impression that RIPE NCC receives a fixed size IPv4 block from IANA every 6 months, which is not correct as pointed out by Leo Vegoda.
But the RIPE NCC receives a fixed size. But you don't consider it.
Sincerely, Sander Steffann APWG co-chair
-- Kind regards, Petr Umelov
Hi Petr, Petr Umelov wrote: [...]
Petr Umelov was under the impression that RIPE NCC receives a fixed size IPv4 block from IANA every 6 months, which is not correct as pointed out by Leo Vegoda.
But the RIPE NCC receives a fixed size. But you don't consider it.
I do not understand what you mean. Can you please explain? In May 2014 the RIRs each received the equivalent of a /11. That dropped to a /12 in September 2014 and a /13 or equivalent in March 2015. Regards, Leo Vegoda
I mean the next Frome: "Ingrid Wijte" <ingrid@ripe.net> Date: 3 March 2015 г. 12:52 Subject: [ncc-announce] [news] RIPE NCC Receives a /13 from IANA's Recovered IPv4 Pool To: <ncc-announce@ripe.net> Dear colleagues, Yesterday, on 2 March 2015, the RIPE NCC and other Regional Internet Registries (RIRs) were each allocated a /13 of IPv4 address space from the Internet Assigned Numbers Authority (IANA). The RIPE NCC received the IPv4 address range 45.8.0.0/13 and we are currently adding this to our available pool. Following the exhaustion of IANA's free pool of IPv4 addresses in 2011, when the RIRs received their final /8s, a global policy caused IANA to create a recovered pool of leftover and returned IPv4 address blocks. This policy was ratified by all five RIR communities in 2012 and stated that IANA would begin making equal, periodic allocations from the recovered pool when the first RIR reached a /9 of remaining addresses. This point was reached by LACNIC, the RIR for Latin America and the Caribbean on 20 May 2014, triggering the global policy and the first post-exhaustion allocation from IANA. You can read the global policy here: http://www.icann.org/en/resources/policy/global-addressing/allocation-ipv4-p... With the current policy in place, the RIPE NCC will receive one-fifth of any recovered addresses in the pool every six months (every March and September). The RIPE NCC will continue to distribute these according to the current last /8 policy, under which Local Internet Registries (LIRs) may receive a one-time /22 allocation (1,024 addresses). It is important that network operators continue to deploy IPv6 on their networks to ensure the future growth of the Internet. More information on IPv6 deployment can be found here: www.ipv6actnow.com With the current policy in place, the RIPE NCC will receive one-fifth of any recovered addresses in the pool every six months (every March and September). 22.07.2015, 19:04, "Leo Vegoda" <leo.vegoda@icann.org>:
Hi Petr,
Petr Umelov wrote:
[...]
> Petr Umelov was under the impression that RIPE NCC receives > a fixed size IPv4 block from IANA every 6 months, which is not > correct as pointed out by Leo Vegoda.
But the RIPE NCC receives a fixed size. But you don't consider it.
I do not understand what you mean. Can you please explain? In May 2014 the RIRs each received the equivalent of a /11. That dropped to a /12 in September 2014 and a /13 or equivalent in March 2015.
Regards,
Leo Vegoda
-- Kind regards, Petr Umelov
Hi Petr,
I mean the next
Frome: "Ingrid Wijte" <ingrid@ripe.net> Date: 3 March 2015 г. 12:52
Subject: [ncc-announce] [news] RIPE NCC Receives a /13 from IANA's Recovered IPv4 Pool To: <ncc-announce@ripe.net>
[...]
With the current policy in place, the RIPE NCC will receive one-fifth of any recovered addresses in the pool every six months (every March and September).
This is not a fixed size. As Leo has already shown you the size RIPE NCC gets has been smaller each time. But to avoid any lengthy discussions on 2015-01: it has been *concluded*. As working group chair I have made my decision and I decided that there is consensus on 2015-01. If you do not agree with this decision then please use the appeals procedure [1]. There is no point in discussing this any further on this mailing list as I have thoroughly reviewed everything and I stand by my decisions. Cheers, Sander [1] https://www.ripe.net/publications/docs/ripe-642 section 4
I mean the next From: "Ingrid Wijte" <ingrid@ripe.net> Date: 3 March 2015 г. 12:52 Subject: [ncc-announce] [news] RIPE NCC Receives a /13 from IANA's Recovered IPv4 Pool To: <ncc-announce@ripe.net> Dear colleagues, Yesterday, on 2 March 2015, the RIPE NCC and other Regional Internet Registries (RIRs) were each allocated a /13 of IPv4 address space from the Internet Assigned Numbers Authority (IANA). The RIPE NCC received the IPv4 address range 45.8.0.0/13 and we are currently adding this to our available pool. Following the exhaustion of IANA's free pool of IPv4 addresses in 2011, when the RIRs received their final /8s, a global policy caused IANA to create a recovered pool of leftover and returned IPv4 address blocks. This policy was ratified by all five RIR communities in 2012 and stated that IANA would begin making equal, periodic allocations from the recovered pool when the first RIR reached a /9 of remaining addresses. This point was reached by LACNIC, the RIR for Latin America and the Caribbean on 20 May 2014, triggering the global policy and the first post-exhaustion allocation from IANA. You can read the global policy here: http://www.icann.org/en/resources/policy/global-addressing/allocation-ipv4-p... With the current policy in place, the RIPE NCC will receive one-fifth of any recovered addresses in the pool every six months (every March and September). The RIPE NCC will continue to distribute these according to the current last /8 policy, under which Local Internet Registries (LIRs) may receive a one-time /22 allocation (1,024 addresses). It is important that network operators continue to deploy IPv6 on their networks to ensure the future growth of the Internet. More information on IPv6 deployment can be found here: www.ipv6actnow.com With the current policy in place, the RIPE NCC will receive one-fifth of any recovered addresses in the pool every six months (every March and September). 22.07.2015, 19:04, "Leo Vegoda" <leo.vegoda@icann.org>:
Hi Petr,
Petr Umelov wrote:
[...]
> Petr Umelov was under the impression that RIPE NCC receives > a fixed size IPv4 block from IANA every 6 months, which is not > correct as pointed out by Leo Vegoda.
But the RIPE NCC receives a fixed size. But you don't consider it.
I do not understand what you mean. Can you please explain? In May 2014 the RIRs each received the equivalent of a /11. That dropped to a /12 in September 2014 and a /13 or equivalent in March 2015.
Regards,
Leo Vegoda
-- Kind regards, Petr Umelov
participants (3)
-
Leo Vegoda -
Petr Umelov -
Sander Steffann