Re: [v6ops] IPREF as a transitioning tool

["Soni \"They/Them\" L." <[e-mail]>]

On 2023-11-12 09:21, Gert Doering wrote:
> Hi,
>
> On Sun, Nov 12, 2023 at 09:00:07AM -0300, Soni "They/Them" L. wrote:
> > > This encourages application programmers to stick to IPv4 sockets, because,
> > > why should they care?  CLAT will take care.
> > > 
> > > Remember we're still talking servers here, in a v6-only DC, and server
> > > applications being under much better control (normally) than clients
> > > (or worse, IOT).  Adding CLAT functionality just adds more code paths
> > > that need to be tested, and get in the way - a hard and fast fail on
> > > "try to use an IPv4 socket" is good, not "it works most of the time".
> > 
> > Moving it into the libc also means removing those pesky IPv4 syscalls.
> > 
> > It is about pushing it on application developers to deal with.
>
> Actually, not.  If libc gives appication developers working IPv4 sockets,
> they can continue to use them.  If IPv4 breaks hard, they will need to
> upgrade their applications to use IPv6 sockets.

It would probably be a good idea to deal with the sysadmin problem first.

Alternatively... There is the nuclear option. You can stop using vhosts 
and start bolting more IPv4 to your VPSes/servers. Yes it'll be 
expensive but it's one of the more direct ways to take out IPv4. 
(Ironically, deploying more IPv4 accelerates IPv4's own demise. Almost 
like anything else that has scarcity value.)

>
> Gert Doering
>          -- NetMaster