Desktop application, for classic client/server should allocate a transient IPv6 local address only for one session (namely a desktop policy system must give tha

Desktop application, for classic client/server should allocate a transient IPv6 local address only for one session (namely a desktop policy system must give that right to user selected applications only), and I even wonder if browsing one site should not get its own IPv6. Ofc, the local ISP IPv6 router should be scaled for a reasonable domestic usage. Ofc, server like desktop applications should randomly choose an IPv6 there, but it has to stay stable since this number will have to be given to other people to connect to such server (I am talking dodging DNS $$$ racketeering or Big Tech "name<->IPv6" mapper service, aka for the smhol internet). Only if the ISP is providing a /64 prefix ofc. In my country, nearly 100% of domestic internet lines are working like that, and it has been the case for years. The main issue, is IPv6 on mobile internet: in my country most mobile internet has IPv6 enabled... but it seems you don't get a /64 prefix but a different /128 ip address at each authentication of your sim card. If it ends up not being a trick of my current IPv6 mobile internet modem, this is very bad, REALLY bad: I cannot give a stable mobile internet IPv6 to my contacts for communication (sort of a phone number dedicated to them). Mechanically, it will force people to use classic centralized client-server services, hence force people into Big Tech.