There will be (is? under standards development?) a DTLS replacement built on QUIC but today these are orthogonal technologies. QUIC makes you a TCP-but-encrypted while DTLS is more TLS-but-for-UDP
In a world with no legacy technology rusted in place, QUIC would be a new IP protocol, like TCP and UDP, but there's stuff rusted in place which can barely manage UDP and would not understand how there can possibly be a new protocol even though the entire network was designed to allow that, so that's why QUIC is spelled as UDP data.
And if ISPs properly let enough bits to client in order to randomize IPv6 addresses (a reasonable amount per domestic line) for their internet client-server sessions in the IPv6 prefixes they provide, it will make those toxic 'global internet scanners' near useless.
I can do that with my domestic internet line, and that has been the case for more than a decade. Now, my sight is on mobile IPv6 internet: my current ISP is actually generating that randomized IPv6 address (unless it is what is actually done by my modem and I don't see it). In theory, the upper 64bits IPv6 should be enough, but mobile ISP could give a bit less to client: a 96bits prefix, with 32bits to choose addresses from. The real hard part is to make that prefix uniq to each mobile line, that globally namely what they actually do with phone number roaming.
As I said, it will make those toxic "global IP scanners" near useless, and even recording the IPv6 won't matter much with good randomization, that in the case of classic client-server (the web for instance).
For p2p contact-based communication, like audio/video IP phones, the client OS will have to choose a stable IPv6 addresses in order for the contacts to be able to use those very addresses for communication. The nice part, could have a few of them (for filters), and it is ez to move to new addresses, the tough part is to tell selected contacts of the new addresses upon phasing out some addresses.
ISPs are basically forced to provide /64 because some end devices insist on SLAAC - if they don't, their customers will call them up and complain their internet doesn't work.
It's server hosts that are sometimes stingy. Hetzner gives a full /64 per server, and a /64 per subnet on cloud, but AFAIK Digital Ocean only gives a /124 per server, and some hosts give a /128 meaning you have to use an exact address.
This is what I was implying: I don't know what my mobile IPv6 ISP is providing to my modem (/64? /96? /128?). All I know, my modem is providing a randomized /128 to my laptop (then this is bad omens).
It is impossible to know. There is no way to get in touch with the guys who know.
I would have to get into my 4G LTE USB modem, and I have other things to do, not to mention I am not up to competence on that matter.
BTW, you should quit digital ocean, as self hosted, their ASes are entirely blocked due to the fact they are infestations of scanners, hacking bots (script kiddy grades), etc.
Random IPs are always 64 bits. There is no standard for random IPs less than 64 bits. There are no normal operating systems that randomize less than 64 IP bits.
In a world with no legacy technology rusted in place, QUIC would be a new IP protocol, like TCP and UDP, but there's stuff rusted in place which can barely manage UDP and would not understand how there can possibly be a new protocol even though the entire network was designed to allow that, so that's why QUIC is spelled as UDP data.