Apr 29, 2024, 09:34 by r...@remlab.net: > > > Le 28 avril 2024 23:11:48 GMT+03:00, Lynne <d...@lynne.ee> a écrit : > >Apr 28, 2024, 20:15 by r...@remlab.net: > >>> Le torstaina 11. huhtikuuta 2024, 10.50.01 EEST Lynne a écrit : >>> >>>> Is there a reason why we can't switch to IPv4 addresses mapped >>>> in IPv6 and just use the IPv6 API everywhere? >>>> >>> >>> IPv6-mapped IPv4 addresses are pretty much deprecated, if supported >>> anymore. >>> Some people consider them insecure. But even if you don't agree with that >>> assessment, the fact of the matter is that they are not portable. >>> > >They were they deprecated? > > They caused more bugs than they solved problems (because what we need is to > add IPv6 to IPv4 apps, not IPv4 to IPv6 apps). >
What bugs did they cause? I know they're not very well used, because the documentation is very lacking, but given that it's a feature of the standard network stack of both Linux and Windows, surely it's fuzzed and unit tested more than enough. >> Why would they not be portable? >> > > Some OS just don't support them, or have a privileged setting to disable them > globally. As a user process, you can't rely on them. > Which ones have a setting? Some have a setting to disable IPv6 globally which must be fairly more used, but I haven't heard ones which have that setting in. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".