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] 2017-03, New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
- Previous message (by thread): [address-policy-wg] 2017-03, New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
- Next message (by thread): [address-policy-wg] 2017-03, New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jetten Raymond
raymond.jetten at elisa.fi
Tue Sep 26 12:23:18 CEST 2017
Hi Everyone, So to conclude* the whole thing, although we have not technically run out, we practically already have, and as you probably know by now, I still see no point in making another policy on this and still oppose this proposal. A /22 is not even enough, let alone a /24 to yet connect to the "dark ages of the IPv4 internet", not now and unfortunately not in the future either... * means I will not again explain my opinion after this on the same subject, it will remain unchanged. Rgds, Ray -----Original Message----- From: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] On Behalf Of Jan Zorz - Go6 Sent: 26. syyskuuta 2017 13:03 To: address-policy-wg at ripe.net Subject: Re: [address-policy-wg] 2017-03, New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space) On 26/09/2017 10:26, Jan Zorz - Go6 wrote: > If you connect to your upstream with *their* IP addresses and not break > your /24 into smaller bits and connect your NAT64 or A+P PRR box > directly to that BGP router, use first usable address as a gateway, > second address as an interface address for your translation/transition > box, then you are left with 252 usable addresses for your purpose. That > means 65.535 ports per address, giving you 16.514.820 usable ports. > Usually sane people predicts between 700 and 1000 ports per user, and > that gives you between 16.514 and 23.592 possible users that you can > serve at the same time and connect them to legacy IPv4 world. > > Now everyone will have to figure out if that's enough or not. :) Forgot to add (thnx Raymond for reminding me of this issue)... While the above numbers may seem technically feasible, the hidden (or not so hidden) forces may want us to go different direction. Apparently there is a Belgium case: https://www.intgovforum.org/multilingual/content/igf-2017-ws-214-how-can-we-limit-the-negative-impact-of-carrier-grade-nat-technologies-and "The emphasis will be put on the Belgium case where the telecom regulator entered in a voluntary agreement with the 4 biggest ISPs in 2012 for them to limit the number of end-users behind each IPv4 addresses for security purposes (to help to identify end-users when served with a legal order in the framework of a criminal investigation). This led to the unintended positive consequence that major Belgium-based ISPs have made strategic business decision to transition quickly to IPv6. As a result, today Belgium has the highest IPv6 adoption rate in the world." I heard (and please correct me if I'm wrong) that in order to have a success in this legal investigations, there should not be more than 4 to 6 users behind each IP address. If this is really the case, then both /22 and /24 are more or less useless for any transition/translation technique if regulation will ever require this ratio as a requirement. :( It's a deep swamp and we created it as an industry with not keeping up properly and deploying IPv6... My question here is: Now what? Cheers, Jan
- Previous message (by thread): [address-policy-wg] 2017-03, New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
- Next message (by thread): [address-policy-wg] 2017-03, New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]