3 ms·
I doubt the accuracy of what you are saying. Treating certain IP ranges differently would not be net neutral, which is exactly why we have net neutrality: other
by lucb1e 8y ago
I doubt the accuracy of what you are saying. Treating certain IP ranges differently would not be net neutral, which is exactly why we have net neutrality: otherwise it's impossible for new entrants in the market to compete. Also, most ISPs don't run CGNAT (except historically notoriously many in Italy, and by now also a few in the USA). And "oodles" sounds like a lot but running a push server doesn't sound like it would require that much disk space. At Google's level, sure, but for your average app... it can easily be run without Google.
The real problem (afaik) is that people change address whenever they change network (so it doesn't all boil down to v4, either), so you need regular keepalives. If every app starts doing keepalives individually, your phone will be using its radio every 30 seconds 24/7 (assuming you have four apps that need push, and those devs want a maximum delay of 2 minutes, and their timers are roughly evenly distributed). By having a single server to keepalive, the issue is avoided.
- jmgao 8y ago> Also, most ISPs don't run CGNAT (except historically notoriously many in Italy, and by now also a few in the USA). My understanding is that essentially every mobile network in the world uses CGNAT. I happen to have AT&T, T-Mobile, and Verizon SIMs handy at the moment, and all 3 of them are behind NAT.