DIN and SID in DaaS-IoT¶

DaaS-IoT uses two core identifiers to define addressing, routing and domain boundaries: DIN (Device Identification Number) and SID (System Identifier).

These identifiers determine how nodes communicate, synchronize, discover each other and maintain separation between independent overlays.

1. DIN — Device Identification Number¶

A DIN is a unique 32-bit identifier assigned to each node.

It functions as the equivalent of an address in the overlay:

every DDO includes a source DIN and destination DIN
routing and link tracking depend on DINs
discovery and synchronization events use DIN references

DINs allow the runtime to:

maintain active link states
track communication sessions
identify nodes during time synchronization (dATS)
manage overlay membership

DIN uniqueness is guaranteed within the scope of a SID.

2. SID — System Identifier¶

The SID defines the logical domain in which a set of DINs is visible and able to communicate.

You can think of it as:

a network namespace
a cluster identifier
an isolation boundary

Nodes can exchange DDOs only if they share the same SID.

SID is used for:¶

overlay initialization
discovery domain definition
time synchronization grouping
routing and topology management
multi-network isolation

3. Relationship Between DIN and SID¶

Concept	DIN	SID
Identifies	A unique node	A logical network domain
Scope	Single node	Group of nodes
Used for	Addressing, routing, timestamps	Isolation, visibility, cluster boundaries
Assigned	Per‑node	Per‑deployment or dynamically
Required for	Sending/receiving DDOs	Joining a DaaS-IoT overlay

4. Dynamic Assignment¶

DaaS-IoT supports dynamic runtime assignment:

Nodes can join a network without knowing their DIN beforehand.
The SID can be negotiated or inherited during discovery.

This makes deployments plug‑and‑play and avoids manual provisioning.

Summary¶

DIN identifies a node.
SID identifies a network.
Together, they define how addressing, routing, visibility and synchronization behave in the overlay.