How bad is IPv4 address exhaustion?

Re:How bad is IPv4 address exhaustion? by gwbas1c on Thursday February 15, 2018 @10:10AM (#16384576)

> As all the pieces fall in to place - hardware, ISP, OS, web/mail/services - it'll still be a gradual move, unless some major players announce IPv6 only service. If Office365 was "IPv6 only in 2020", that might motivate a lot of orgs to push their IT/ISP to upgrade and migrate.

It doesn't even need to be that drastic. Apple, Google, and Microsoft could just check for IPv6 when connecting to a network. If it's missing, display some kind of alert saying, "This internet connection is malfunctioning, please contact (lookup service number based on the IP address.)"

Constantly showing that nag will put a lot of pressure on major ISPs like Comcast.

[ Parent | on HN ]

Re:How bad is IPv4 address exhaustion? by tzs on Thursday February 15, 2018 @11:05AM (#16385063)

> Constantly showing that nag will put a lot of pressure on major ISPs like Comcast

Comcast is making good progress: http://www.worldipv6launch.org/apps/ipv6week/measurement/ima...

For others, see: http://www.worldipv6launch.org/measurements/

[ Parent | on HN ]

Re:How bad is IPv4 address exhaustion? by philg_jr on Friday February 16, 2018 @10:17AM (#16392884)

Yes, Comcast has made, relatively speaking, amazing progress on deploying IPv6 across their network. It works very well (well, except if you have one of their business "routers" required if you need a static IPv4 address). This is a stark contrast of, say, Verizon Fios, who has yet to deploy ANY IPv6 across their network.

[ Parent | on HN ]