MEF Technical Standards & SDKs represent the primary set of products developed by MEF. Adopting them enables service providers, technology suppliers, and other members of the ecosystem, to take advantage of MEF’s collaborative, global industry best practices to drive innovation in the ICT and empower enterprise digital transformation.
MEF uses a formal numbering system to track the progress and state of MEF Technical Standards: Show MEF #s Explained
MEF #: When a new project is approved by the relevant MEF Committee, MEF Staff assign it a unique MEF number. Once assigned, numbers are never re-used, even if no MEF Standard or Draft Standard is ever published using that number.
MEF Standards are numbered MEF X.Y.Z
Working Drafts: Until the standard is approved, the working standard is referenced using a ‘W’ prefix. Published standards are available to the public; working standards are available to members only.
E.g. MEF W55
Draft Standards: To obtain additional community input, pre-published standards may be made available to the general public prior to letter ballot and ratification by the Board. They are numbered MEF X.Y.Z Draft (RU). MEF X.Y.Z is the MEF Standard of which the Draft Standard is an early version. U is the Release Number of the Draft Standard.
E.g. MEF 10.4 Draft (R2) is the 2nd Draft Standard of what will be MEF 10.4 when published as a MEF Standard.
Published Standards: Each standard goes through a rigorous process of defining requirements, editing, and multiple calls-for-comments before reaching the letter ballot. To move forward, each stage requires a successful vote from the Membership. Once a letter ballot is passed, it is formally approved by the Board of Directors and published here.