Re:IPv6 Adoption
by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @10:40AM
(#14856541)
> For email, this was true only about the mid-to-late 90s--surprisingly recent.
Actually, email still is not nominally 8-bit transparent (ESMTP 8BITMIME is optional and not supported by all MTAs), but it doesn't need to be, that's what quoted-printable and base64 are for.
The timeframe I'm using is the timeframe where you stop seeing servers mangle 8-bit email. 8BITMIME technically requires converting 8-bit bodies to QP and base64, which is generally not necessary nowadays, and some would argue that software that chooses not to implement that shouldn't advertise 8BITMIME.
Re:IPv6 Adoption
by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @11:25AM
(#14856985)
> and some would argue that software that chooses not to implement that shouldn't advertise 8BITMIME.
Which is why I wrote that email still nominally isn't 8-bit clean :-)
Yes, in practice, you won't find an MTA that doesn't leave your 8 bit data unharmed, but you do find MTAs that don't advertise 8BITMIME, and so nominally noone should send them 8 bit data ... except everyone does anyway, of course ...
One of major blockers of UTF-8 transition is Windows world - the operating system itself, who stubbornly stuck with not even complete UTF-16 support, and also a big amount of software for this OS family without the proper UTF-8 compatibility.
Switching to UTF-8 requires two major steps. The first was making software and interchange systems preserve the 8th bit (it used to be commonly used as a parity bit). For email, this was true only about the mid-to-late 90s--surprisingly recent. The second step, which is still incomplete today, is letting control mechanisms that used to speak only ASCII understand UTF-8 (or something else non-ASCII) reliably. You could only put UTF-8 in C++ or C code as of C++11/C11, for example. Non-ASCII domain names are still problematic, to say nothing of non-ASCII email addresses. In other words, trying to speak UTF-8 to someone who only speaks ASCII is still as problematic as trying to speak IPv6 to someone who only speaks IPv4. We just don't notice it as much because we keep advising people to only speak ASCII in key places.