I guess the point with this to facilitate usage of IPv6.

More like, the point is to facilitate turning off IPv4. It's much nicer to manage a single-stacked backbone, but you still need IPv4 out in the edges somehow (for many cases, anyway). I guess this is another way to do that.

Heck, I would be happy if I could remove some IPv4 linknets from my IS-IS, myself, and just route using IPv6 link-local nexthops…

▲

Polizeiposaune 27 minutes ago | parent | prev | next [-]

It's to facilitate use of IPv4 in an IPv6-mostly network.

▲

simoncion 2 hours ago | parent | prev | next [-]

The Abstract and Introduction sections of the RFC [0] explain what the point of this is. The "Changes Compared to RFC 5549" section is especially good reading, as it both alerts you to the fact that this is an update to a seventeen year old RFC and explains what changed in the update.

[0] <https://datatracker.ietf.org/doc/html/rfc8950>

▲

miyuru an hour ago | parent | prev | next [-]

Multiple ISPs in my country have already deployed IPv6 with NAT64 support, and with CLAT support now available, I think IPv6-only networks will be the next step for most ISPs.

	▲	ianburrell 14 minutes ago \| parent \| next [-]
		There is also MAP-T which basically does CGNAT with IPv6-only provider network. The local network gets IPv4, the router translates to IPv6 which goes to stateless IPv4 NAT proxy. The advantage is that the proxy is stateless unlike CGNAT. The downside is requires custom code on the router.
	▲	yayachiken 38 minutes ago \| parent \| prev [-]
		IPv6 mostly (RFC 8925) is a rather nice migration option. Modern operating systems will gladly do CLAT, and old operating systems (or fussy users) can still get their IPv4 by just ignoring the new DHCPv4 option. But admins can finally stop keeping an IPv4 around for every potential client as most applications and users really don't care.

▲

q3k 39 minutes ago | parent | prev [-]

It's also just nice to not need numbered point-to-point links (ie. just use IPv6 LL).

(this is one of those things that's really magical with OSPv3 - it just runs on IPv6 LL addresses, no need to set anything up other than set the link to be within some area and it just works! well, as much as they do with OSPF anyway.)