Can a product still be DLNA Certified in 2026?

No. The Digital Living Network Alliance dissolved in January 2017 and the DLNA Certified programme is no longer operated by the original organisation. The Guidelines (last public edition HNv2, 2014) and the certified products database remain available for consultation, but no new certifications are issued under the DLNA name. Existing products may continue to bear the DLNA Certified mark obtained before dissolution, without active renewal.

Which organisation took over the DLNA scope after 2017?

No organisation formally inherited the full DLNA mandate. The UPnP protocols that underpinned DLNA were transferred to the Open Connectivity Foundation (OCF) in 2016 through the UPnP Forum + AllSeen Alliance merger. For consumer media streaming, the market has shifted towards Matter (smart home), AirPlay, Chromecast and HTTPS Adaptive Streaming (DASH, HLS), which cover analogous use cases without a DLNA logo.

What distinguishes OCF from Matter?

OCF targets a broad Internet of Things scope, including smart building, industrial IoT and some smart home segments, with a generic Resource Type model and an ACL2 security scheme. Matter, operated by the Connectivity Standards Alliance, specifically targets consumer smart home over IPv6 on Thread or Wi-Fi, with a DAC/PAI/PAA attestation scheme. Matter reused several OCF concepts (Access Control List in particular) but is not a subset of OCF.

Is IoTivity mandatory to certify an OCF product?

No. IoTivity is the open-source reference implementation of the OCF specifications, hosted by the Open Connectivity Foundation. A manufacturer may implement its own OCF stack from the published specifications (Core, Security, Resource Type, Wi-Fi Easy Setup) and submit it to OCF Certified. IoTivity simply lowers the entry cost for teams that prefer not to develop a stack from scratch.

What does ICAID mean in the OCF context?

ICAID, Identifier Certificate Authority Identifier, is the identifier assigned by OCF to each certificate authority approved to issue device identity certificates in the OCF ecosystem. The Manufacturer Certificate provisioned in the factory is issued under a given ICAID, and the commissioner (OBT) verifies the chain at onboarding time. The conceptual role is analogous to the PAA in Matter, the operational scope is however not equivalent.

What is the OBT in OCF?

OBT, Onboarding Tool, is the OCF commissioning tool responsible for the secure introduction of a new device into an OCF network. The OBT executes the Device Onboarding sequence described in the OCF Security Specification, including discovery, mutual authentication, ownership transfer and provisioning of initial ACL2. The OBT is the conceptual analogue of the Matter commissioner, with OCF-specific mechanics.

Can an older DLNA Certified product still be sold in 2026?

The DLNA Certified mark is no longer actively licensed, but the right to use the mark acquired on a product certified before dissolution generally remains valid under the original licence terms. In practice, the commercial value of the mark has dropped sharply since 2017. New products looking for a media interoperability signal lean instead towards ecosystem programmes (Works with Apple AirPlay, Google Cast) or towards Matter for smart home.

What are the recurring pitfalls with OCF today?

Three errors come up often. First, assuming that the DLNA mark is still actively managed and confusing the two programmes. Second, omitting the OCF Security Profile choice (Baseline, Black, Blue, Purple) that drives the cryptographic perimeter and the onboarding sequence. Third, believing that Matter certification removes the need for OCF certification on products that are not pure smart home. Matter does not cover industrial IoT, OCF remains relevant in that segment.

DLNA and OCF: media + IoT interoperability

Author Hugues Orgitello Last updated 27 May 2026 ~12 min read

Guide · DLNA / OCF

Two interoperability marks occupy the same historical niche, media streaming and device discovery on the local IP network, with opposite trajectories. DLNA, Digital Living Network Alliance, structured the shared media market for fifteen years across TVs, NAS appliances, smartphones and set-top boxes before dissolving its organisation in January 2017. OCF, Open Connectivity Foundation, formed in 2016 through the merger of UPnP Forum and AllSeen Alliance, took over part of the UPnP substrate and extended it to the Internet of Things with its own security scheme. The most common confusion treats the two programmes as equivalent or interchangeable. They are not, and the arrival of Matter has redistributed part of the scope. This page covers DLNA separately as a legacy reference and OCF as an active programme, then positions both against Matter and the proprietary ecosystem solutions.

DLNA (legacy)

Origin and historical scope

The Digital Living Network Alliance was founded in 2003 under the name Digital Home Working Group, by an industrial consortium led by Sony, Intel, Microsoft, Samsung, HP and Nokia. Its objective: define a common framework so that consumer electronics devices could discover, list and play media content (audio, video, image) present on other devices on the same home network, without manual configuration.

The technical scope crystallised around two deliverables:

the DLNA Guidelines, a set of usage profiles that constrain and complement the underlying specifications (UPnP AV, HTTP, codecs, container formats);
the DLNA Certified programme, which validated a product's conformance to one or more DLNA profiles and authorised use of the logo.

The last public edition of the Guidelines, Home Networked Device Interoperability Guidelines version 2 (HNv2), was published in 2014. The Guidelines covered networking (IPv4 unicast/multicast, SSDP discovery), content (MP3, AAC, H.264, JPEG codecs and MPEG video profiles), security (DTCP-IP for protected content), and functional roles.

DLNA roles, the nomenclature

DLNA broke the media ecosystem into several roles, which a single physical device could combine. The nomenclature remains useful to recognise because many older product datasheets still reference it:

Acronym	Role	Typical example
DMS	Digital Media Server, host of content	NAS, computer, smartphone sharing photos
DMR	Digital Media Renderer, player driven remotely	Connected TV, network speaker, hi-fi system
DMP	Digital Media Player, standalone player with UI	Connected TV browsing a NAS itself
DMC	Digital Media Controller, virtual remote	Smartphone driving a DMR from a DMS
DMPr	Digital Media Printer, network printing	Network printer accepting DLNA content
M-DMS, M-DMP, M-DMR, M-DMC, M-DMPr	Mobile variants, constrained profiles for smartphone	DLNA photo app on a smartphone
MPP	Mobile Network Connectivity Function	Adaptation layer for mobile networks

DLNA's commercial success concentrated on the DMS/DMR/DMC triplet, typically a NAS serving content, a TV rendering it, and a smartphone driving the whole. Standalone DMP and DMC roles saw more diluted usage.

UPnP foundation

DLNA never reinvented the discovery layer nor the control layer. The whole framework rests on UPnP (Universal Plug and Play), originally specified by the UPnP Forum, and more specifically on the UPnP AV profile that models MediaServer, MediaRenderer and their ContentDirectory, AVTransport, RenderingControl services. DLNA adds on top of UPnP a set of profile constraints (allowed codecs, container formats, network behaviour, pause mechanisms, sequencing) that ensure that a DMS from vendor A is consumable by a DMR from vendor B without surprises.

This dependency on UPnP is precisely what made it possible to transfer the UPnP specifications to OCF in 2016, during the UPnP Forum / AllSeen Alliance merger. The DLNA Guidelines, on the other hand, were not taken over by OCF, they remain a historical deliverable accessible through archives.

Dissolution in 2017

In January 2017, the DLNA announced the dissolution of the organisation. Publicly stated reasons combined the decline of the local shared-media market (consumption shifted to OTT streaming such as Netflix, YouTube, and to closed ecosystems such as AirPlay and Chromecast), the maturity of the Guidelines (HNv2 being judged stable), and the arrival of OCF taking over the UPnP substrate towards IoT.

Concretely, since 2017:

no new DLNA Guidelines are published;
no new product is certified DLNA by the historical organisation;
the certified products database is frozen, accessible via archives;
DLNA Certified logos already affixed to existing products remain legally usable under the original licence terms, without active renewal.

A company named SpireSpark International, which already operated DLNA testing, announced that it had taken over part of the testing activity privately. This service does not however reproduce the DLNA Certified programme in the original sense, and does not constitute authority for affixing the logo. For any new product, treating DLNA as a legacy programme is the prudent industrial reading.

Modern fate, who took over

The functional scope formerly covered by DLNA has fragmented across several technologies:

HTTPS Adaptive Streaming (DASH, HLS) for video streaming, which now dominates consumption and does not require a specific interoperability logo;
UPnP AV persists de facto, as a technical substrate, in many NAS appliances and media players, but without active DLNA codec constraints;
OCF for IoT device discovery and control in the broad sense, see the following section;
Matter for consumer smart home, with a deliberately restricted scope to domestic devices (lighting, plugs, thermostats, etc.) and not to media;
Apple AirPlay and Google Cast (Chromecast) for media casting, on proprietary models that depend on neither DLNA nor Matter;
Amazon Fire TV / Roku / Apple TV for media hub functions, with their own partner SDKs.

On datasheets of 2020+ products that still mention DLNA, the mention typically reflects UPnP AV support rather than possession of an active DLNA certification. The marketing reading of the logo has lost its original value.

OCF (current)

Formation and scope

The Open Connectivity Foundation was formed in 2016 through the merger of the UPnP Forum, the AllSeen Alliance (which carried AllJoyn) and the Open Interconnect Consortium (OIC, founded by Intel, Samsung and others in 2014). The mandate: define a common interoperability framework for the Internet of Things, covering device discovery, control and security, independently of the transport layer.

Unlike DLNA which remained centred on home media, OCF targets a broad IoT perimeter, including:

smart home (in competition with Matter, see below);
smart building (HVAC, commercial lighting, access control, supervision);
industrial IoT (industrial sensors, M2M, production line supervision);
automotive lateral applications (connected car interacting with home, charging infrastructure);
non-medical connected health (wellness telemonitoring, fitness).

OCF specifications, the stack

OCF publishes a coherent versioned set of specifications. The main ones for a certification project are:

Specification	Scope
Core Specification	Resource model, REST framework, CoAP/HTTP transport, multicast discovery
Security Specification	Authentication, authorisation, ACL2, Device Onboarding, security profiles
Resource Type Specification	Catalogue of Resource Types (oic.r.switch.binary, oic.r.temperature, etc.)
Device Specification	Typical device profiles and their resource composition
Wi-Fi Easy Setup Specification	Initial onboarding procedure over Wi-Fi for headless devices
Cloud API Specification	Interface between OCF Server and an OCF cloud
Bridging Specification	Bridge between OCF and other protocols (Zigbee, BLE, Z-Wave, etc.)

The stack is designed to be stateless on the model side, with each device's resource representation following RESTful philosophy (GET, PUT, POST, DELETE, OBSERVE), carried on CoAP as the primary transport and HTTP as a secondary transport.

OCF Certified and ICAID

The OCF Certified programme validates the conformance of a product to a set of specifications. Certification covers:

Core conformance, verifying that the device correctly implements discovery, resource representation and REST routing;
Resource Type conformance, verifying that each declared Resource Type respects the schema exactly (attributes, types, value ranges);
Security conformance, verifying the chosen security profile implementation (Baseline, Black, Blue, Purple), certificate chain, factory provisioning;
interoperability, verifying that the device interacts correctly with other OCF-certified devices.

At the heart of the OCF security scheme sits the ICAID, Identifier Certificate Authority Identifier, assigned by OCF to each recognised certificate authority. The Manufacturer Certificate provisioned in the device at the factory is issued under an ICAID, and the commissioner verifies at onboarding that the chain traces back to a recognised CA. The conceptual analogy with Matter's PAA is strong, the functional scope is however broader in OCF.

An additional identifier, the Vendor ID (di + Vendor ID + Model + serial number), uniquely identifies a device in the OCF ecosystem. OCF Certified registration pushes this identifier into the public certified products database, accessible via the OCF portal.

IoTivity, the reference implementation

IoTivity is the open-source reference implementation of the OCF specifications. The project is hosted by the Open Connectivity Foundation and distributed under Apache 2.0 licence. Several branches have existed over time:

IoTivity-Classic, a feature-rich C base historically carried by Intel/Samsung;
IoTivity-Lite, a C base oriented towards constrained devices (microcontroller with a few tens of kilobytes of RAM);
community ports in Java, Python for prototyping.

A manufacturer is not required to use IoTivity, they may implement their own stack from the OCF specifications and submit it for certification. IoTivity however lowers the entry cost, particularly for small teams and for prototyping.

OCF security, ACL2 and profiles

OCF security revolves around four profiles, which a product selects at certification time:

Profile	Cryptography	Target
Baseline	TLS/DTLS, X.509 certificates, PSK	Standard residential smart home
Black	Hardened cipher suites, extended audit logs	Professional smart building
Blue	Hardened, additional isolation requirements	Industrial IoT
Purple	Reserved for governmental profiles	Defence, critical infrastructure

Profile choice is not trivial, it drives the cryptographic perimeter, the onboarding complexity and the certification cost. A consumer smart home product typically settles for Baseline. An industrial product must select Blue. The declared profile must be consistent with the commercial target.

The core of the access control model is ACL2, Access Control List version 2, which specifies for each device resource which subjects (device or group identities) have which rights (CRUD plus Notify). ACL2 is provisioned initially by the OBT at onboarding, then mutable by authorised subjects according to OCF policy. The ACL2 schema explicitly influenced the design of the Matter fabric and ACL system, which carries the philosophy without being a strict subset.

Onboarding, the OBT role

The OBT (Onboarding Tool) is the component that commissions a new OCF device into an existing network. The typical sequence:

The device enters onboarding mode (Random PIN, Just Works, or Manufacturer Certificate depending on the profile).
The OBT discovers the device via CoAP multicast.
Mutual authentication between device and OBT, using the chosen onboarding mode.
Ownership transfer, the device adopts the OBT as its initial owner.
Credential provisioning, the OBT writes the definitive identity certificates into the device.
Initial ACL2 provisioning, defining who can do what on the device.
Switch to operational mode, the OBT releases its exclusive role.

This sequence is the OCF analogue of Matter commissioning, with its own security-profile specifics and ownership role. A frequently underestimated point, the OBT is not necessarily a dedicated piece of equipment: in a smart home OCF deployment, the OBT is typically integrated into the manufacturer's mobile application or into an OCF hub; in an industrial deployment it may be a dedicated commissioning station.

OCF vs Matter vs DLNA, scope comparison

The most expressive positioning summary lays out the three programmes on three axes, scope, status, layers covered:

Axis	DLNA	OCF	Matter
Target domain	Home media (audio, video, image)	Broad IoT (smart home, smart building, industrial)	Consumer smart home (domestic devices)
Status	Legacy programme, organisation dissolved in 2017	Active programme, versioned specifications	Active programme, versioned CSA specs
Network layer	UPnP over IPv4	CoAP/HTTP over IPv4/IPv6	IPv6 over Thread / Wi-Fi
Native security	DTCP-IP for protected content, otherwise limited	ACL2, Baseline/Black/Blue/Purple profiles, OBT	DAC/PAI/PAA, fabric, OCF-inspired ACL
Active logo	No	Yes (OCF Certified)	Yes (Matter logo)
Membership fees	Not applicable	OCF membership, see public schedule	CSA membership, see public schedule
Certification tool	Not applicable (frozen)	OCF Certification Testing Tool (CTT) test plans	CSA ATL + chip-tool + TestHarness

Practical reading:

For a domestic media product in 2026, neither DLNA nor OCF is the right primary answer. The market has shifted to AirPlay, Cast and native apps. UPnP AV support without certification remains technically possible as a secondary feature.
For a consumer smart home product (lighting, plug, thermostat, sensor), Matter is now the most relevant regulatory target. OCF is still possible but the market pushes towards Matter, particularly because the major consumer ecosystems (Apple Home, Google Home, Amazon Alexa, SmartThings) mandate Matter for user commissioning. See Matter certification.
For a professional smart building product, OCF retains real relevance, particularly on Black profiles and on Resource Types oriented towards building management.
For an industrial IoT product, OCF Blue profile remains an option, competing with OPC UA (which is not OCF) and with vertical industrial protocols (Modbus TCP, BACnet, etc.). Matter does not cover this segment.

Articulation with radio regulatory regimes

OCF and Matter are application-layer interoperability programmes, they do not cover radio conformance. An OCF Wi-Fi product placed on the European market must comply with the RED directive (articles 3.1, 3.2, 3.3); a product placed on the US market must comply with FCC Part 15. None of these obligations is lifted by OCF certification. Symmetrically, an OCF product that has not completed its radio conformance cannot be placed on the market, even if it is technically OCF Certified.

For Bluetooth products that use OCF Bridging to expose a BLE device as an OCF resource, Bluetooth SIG qualification remains necessary for use of the Bluetooth logo, in addition to OCF certification. See the certifications glossary for the definitions of ICAID, OBT, ACL2, Resource Type, PAA and DAC.

Recurring pitfalls

On early OCF submissions and on projects that assume an active DLNA status, the following non-conformances come up regularly:

Assuming that DLNA is still actively certified. No new DLNA certification has been issued since 2017. Designing a product on the premise of targeting the DLNA logo makes no commercial sense today.
Confusing DLNA and UPnP AV. UPnP AV still exists as a technical substrate, without active DLNA codec constraints. Claiming "DLNA compatible" on a 2026 product is misleading, the correct claim would be "UPnP AV compatible".
Skipping the OCF Security Profile decision. The profile (Baseline, Black, Blue, Purple) is an early decision that shapes the cryptographic architecture. A product that starts in Baseline and has to switch to Blue late in the cycle goes through expensive redesign.
Underestimating OCF factory provisioning. The Manufacturer Certificate must be provisioned in the factory securely, with a private key that never leaves the secure storage. This is a production-line topic, not a firmware topic.
Believing that Matter removes the need for OCF. For a consumer smart home product, yes, Matter in practice supersedes OCF. For a smart building or industrial IoT product, no, Matter does not cover the scope, OCF remains relevant.
Confusing OCF ICAID and Matter PAA. Both play an analogous root-of-identity role, but these are two distinct PKIs, operated by two distinct organisations (OCF and CSA). A certificate under an OCF ICAID is not recognised by a Matter commissioner, and vice versa.
Ignoring coexistence with underlying radios. OCF certification does not lift any radio regulatory certification (RED, FCC, RCM, etc.) nor any radio ecosystem certification (Wi-Fi Alliance, Bluetooth SIG, Thread Group). See the dedicated guides for each of these regimes.
Misreading the logo on an older product. A new piece of equipment sold in 2026 that visibly carries a DLNA Certified logo is typically a product whose design dates back to a window when certification was still active. This says nothing about the relevance of the logo in 2026 from a marketing or interoperability standpoint.

Operational summary

For a manufacturer starting an IoT or media project in 2026, the decision split is:

Consumer smart home, standard domestic product: target Matter, treat OCF as complementary at most, ignore DLNA.
Professional smart building or industrial IoT: OCF remains relevant, choose the Security Profile early, treat Matter as out of scope.
Domestic media streaming: neither DLNA nor OCF first, look at proprietary ecosystems (AirPlay, Cast) and standardised streaming (DASH, HLS).
Maintenance of an existing DLNA Certified product: the mark remains legally usable under the original licence terms, but without active renewal and with sharply reduced marketing value. Migration to Matter or OCF should be evaluated against the product roadmap.

In every case, radio regulatory conformance (CE/RED in Europe, FCC in the United States, plus equivalent national regimes) remains mandatory and independent of any application-layer interoperability programme.