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] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Friaças
cfriacas at fccn.pt
Tue Feb 19 09:36:25 CET 2019
Hi, On Tue, 19 Feb 2019, Dominik Nowacki wrote: > Dear Colleagues, We do not support this proposal. > > RIPE NCC's available IPv4 pool will not be empty everytime (addresses are de-registered by lack of payment, > closures, ...), so a complete and *permanent* "run out of IPv4" is highly unlikely. > > > ARIN style never-ending queue that basically means you will never get the addressees you request at this stage is synonymous > with a complete and permanent run out of IPv4 to me. That's what 2019-02 is about: We're in scarcity-mode since 2012. "What you request" and "What you need" are completely irrelevant. When the pool reaches 0 for the 1st time, people will still get /22s *when* some addresses are made available. Changing that into /24s will allow more people to get a minimum of IPv4 eventually at some point (smaller lifeboats, but 4x more lifeboats...) When the *need* for a /24 arises, and a company is still in a bad queue position, the answer is obvious: get it from the market! It would be really easy if IPv6 deployment would solve it, but one is only able to control one's infrastructure, there is absolutely no ability in dictacting what (and if when) 3rd party networks are going to deploy. That depends on their judgement and of course, budget :-) > You can also observed that, for example, US where they observe a > ?complete and permanent run out of IPv4? has more IPv6 traffic, > according to Google, already than say UK where the national ISP, BT, and > majority of alternative ISP supports IPv6 for ages already, out of the > box. It's not only traffic volume that matters. The number of networks and how much IPv6 is within each network is also very important. > No access to V4 - better incentive to have eyeballs on V6 (and granted, > some CGNAT probably too). We might not like CGNAT, but noone can stop anybody to use it... :/ > More eyeballs on V6 makes an incentive for > content providers to make more services available on V6. As i see it, content is the easy bit... Regards, Carlos > That?s my take on it. > > With Kind Regards, > Dominik Nowacki > > Clouvider Limited is a limited company registered in England and Wales. Registered number: 08750969. Registered office: 88 > Wood Street, London, United Kingdom, EC2V 7RS. > > On 19 Feb 2019, at 08:08, Carlos Friaças via address-policy-wg <address-policy-wg at ripe.net> wrote: > > RIPE NCC's available IPv4 pool will not be empty everytime (addresses are de-registered by lack of payment, > closures, ...), so a complete and *permanent* "run out of IPv4" is highly unlikely. > > >
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]