It's just not that they're implementation specific, but they're also side-channel timing attacks. Not that they shouldn't be discovered and fixed, but this sort

It's just not that they're implementation specific, but they're also side-channel timing attacks. Not that they shouldn't be discovered and fixed, but this sort of thing is kind of inevitable in the first days of a brand-new protocol, and I don't really think it deserves a named vulnerability. I can't imagine it won't be fixed in short order.