I had a long reply, but when I went back and read your original comment, I realized I was just restating a portion of your original comment but with far more words. So I think I'm being unnecessarily contentious.
Standards serve the purpose of when user agents want to interoperate, so Mozilla was definitely ok with not implementing ActiveX, just as they would be ok with not implementing EME.
But if Chrome and Safari and Edge all want to interoperate with EME, they're going to do that. Whether it's a W3C standard or a WHATWG standard, or an RFC, or a IHateFreeSoftworeSociety standard doesn't really matter. It's just whether W3C wants to be part of the conversation or not. I see little benefit and little downside to having it be a W3C standard vs. anything else. Or even for that matter, whether the term "standard" is used; even if it's somehow disallowed it's still the same situation.
Standards serve the purpose of when user agents want to interoperate, so Mozilla was definitely ok with not implementing ActiveX, just as they would be ok with not implementing EME.
But if Chrome and Safari and Edge all want to interoperate with EME, they're going to do that. Whether it's a W3C standard or a WHATWG standard, or an RFC, or a IHateFreeSoftworeSociety standard doesn't really matter. It's just whether W3C wants to be part of the conversation or not. I see little benefit and little downside to having it be a W3C standard vs. anything else. Or even for that matter, whether the term "standard" is used; even if it's somehow disallowed it's still the same situation.