One big issue with IRC is the missing support of Unicode. An IRC log is a potential mixture of latin1, utf8, and whatever encoding user write.
I fear that cannot be fixed in a backwards-compatible way.
That's a big one indeed. I'm currently running a small private IRC server (~50 users) for local community speaking Thai; the best solution I found for encoding issue is to force everyone to use Unicode. However, this is a really hard thing to do, as most do not see benefit over whatever they're using (tis620 in my case) or benefit over upgrading their dated client.
Does it require encrypted connections?
You may be able to help influence it at https://github.com/ircv3/ircv3-specifications/issues
It does not require encrypted connections, although it does have extensions to indicate that future connections should occur over TLS (through the optional `tls` extension in IRCv3.1) and there is discussion for standardizing IRC over SCTP in IRCv3.3
You mean the IRCv3? I believe encrypted connection is still optional.
[1]: http://ircv3.atheme.org/