In general, things that become IETF standards have different standard names from the names they originally had, when a company has a trademark on the original name. For that matter, a standard has to permit competing implementations, which are obviously going to be not from the ZeroMQ community but confusingly similar to ZeroMQ, and therefore violate any sensible trademark policy on that name. Of course, "Crossroads I/O", while a fine project name, isn't any better for this purpose. If they want to have a standard, they'll need a generic name, like "facial tissue" or "copy machine" or "XMPP", and that's what other companies would claim support for without having conflicts with trademark policies on it.
ZeroMQ and Crossroads I/O: Forking over trademarks
Posted Mar 31, 2012 16:36 UTC (Sat) by giraffedata (subscriber, #1954)
[Link]
You seem to be talking about the name for the protocol, while the trademark in question is the name of a piece of software that implements the protocol. I don't believe it would satisfy Sustrik if the protocol were given a new non-proprietary name while iMatix retained the trademark on the piece of software Sustrik works to distribute.
The freedom to use the mark that Sustrik advocates wouldn't be the freedom for a developer to call his code "Foobar Enterprise 0MQ" to indicate that it uses the same protocol as the original 0MQ; it would be the freedom to call it that to indicate that it contains all the features of the original software.