The Ripe NCC Has Run Out of IPv4 Addresses

Re:The Ripe NCC Has Run Out of IPv4 Addresses by q3k on Monday November 25, 2019 @02:29PM (#21631812)

There's one big issue with CGNAT for ISPs: compliance.

At least in Poland, you must provide law enforcement with information about your subscriber for any given 5-tuple at a given time (timestamp, {src,dest}{ip,port} and protocol). If you're CGNATing everyone, you have to either:

- log all outgoing connections (which is a GDPR hazard)

- design your CGNAT to use static outgoing ports for a given customer (but then you're running out of ports pretty fast, if you're doing anything close to >=500 subscribers)

With IPv6, you can just immediately tell who the subscriber is based on the IP address, and as such don't have to log anything.

[ Parent | on HN ]

Re:The Ripe NCC Has Run Out of IPv4 Addresses by ec109685 on Monday November 25, 2019 @10:17PM (#21635390)

If you need consistent ports, you could assign many internal IP’s to the NAT to support more ports for your NAT.

[ Parent | on HN ]

Re:The Ripe NCC Has Run Out of IPv4 Addresses by Mathnerd314 on Tuesday November 26, 2019 @01:22AM (#21636025)

Does the GPDR override the data retention law? I was reading some stuff about VPNs which suggested it might.

[ Parent | on HN ]

Re:The Ripe NCC Has Run Out of IPv4 Addresses by q3k on Tuesday November 26, 2019 @05:32AM (#21637068)

No. The GDPR explicitly doesn't concern matters of lawful interception, intelligence, police and justice.

[ Parent | on HN ]

Re:The Ripe NCC Has Run Out of IPv4 Addresses by trollied on Monday November 25, 2019 @02:44PM (#21631979)

Crikey, the amount of storage required to keep that will be insane. What's the retention period?

[ Parent | on HN ]

Re:The Ripe NCC Has Run Out of IPv4 Addresses by q3k on Monday November 25, 2019 @03:50PM (#21632673)

One year but not a day more (data protection laws).

[ Parent | on HN ]