Exclusively IPv6 without any transitional mechanisms would be difficult to succeed with.

However, there are network upstarts like Jio (India) which made huge v6 investments from day one which use 464xlat for subscribers to access v4-only resources.

▲

1970-01-01 8 hours ago | parent | next [-]

>Exclusively IPv6 without any transitional mechanisms would be difficult to succeed with.

That's my point; why is it still difficult? What exactly are the pain points for a fully commercialized native IPV6-only business, and why do we think it will be easier to maintain the status quo?

	▲	pixl97 6 hours ago \| parent \| next [-]
		Because a few large companies are holdouts. Github for example. Some AWS backend stuff. Many smaller ISPs that represent a very long tail. Most of it is not any particular difficulty for you, but because of someone else.
	▲	patmorgan23 6 hours ago \| parent \| prev \| next [-]
		There are still lots of customers with IPv6, if you go completely and totally v6 only then you limit your potential customer base. Now going v6 internally with a dual stack edge makes sense, Meta has done this.
	▲	tormeh 7 hours ago \| parent \| prev [-]
		Many wired networks are IPv4-only, so you've excluded a bunch of consumers. It'd be like not supporting the Edge browser.

▲

immibis 8 hours ago | parent | prev [-]

Also every mobile phone network ever (with a handful of exceptions) is IPv6-only, with a slow translation layer to reach v4 sites. Your app or website literally runs faster if you use IPv6.