So I'm pretty convinced it's not at all "just a small matter of code". At
best, it's "a small matter of code now to make it perhaps workable in 2025
or so".
And even after you fix the MTAs and the MUAs you also have to stop
"ssh/telnet/<choose your app> <label>" working or suddenly "mail
user@label" and "ssh label" end up at different machines. This
is about providing constistent naming across everything.
And this assumes that there's sufficient incentive to actually bother
"fixing" anything. Seems to me this is another case of something that's
quite common in the email world: An asymmetry between who bears the costs
and who accrues the benefits.
The cost of abandoning shortform names in a large deployment is likely to be
considerable, especially if they are what users are used to. And while the
benefits to the people operating the TLDs may be real, the benefits to the
large deployment are ... what exactly? The ability to send to a handful of
addresses nobody is likely to care about?
Heck, even in the unlikely event there's sufficient cause to send mail to one
of these TLDs, it's almost certainly going to be easier to add special routing
for it and ignore the general problem.
Ned
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp