Thread Network Roles Workbench
Thread Network Roles Workbench
Thread role names are useful only when they are tied to evidence. The goal is not to memorize labels; the goal is to know what each label proves about the network.
Border Router
Routes between the Thread mesh and another IP network. Evidence should show the specific boundary, service behavior, and owner of the off-mesh path.
Leader
Maintains management state for a connected Thread partition. Evidence should show that leadership is a network role, not an application controller or single permanent device.
Router
Participates in mesh forwarding and may host child devices. Evidence should show that it is awake enough to support routing responsibilities.
REED
Is eligible to become a router when the network needs and permits that role. Evidence should avoid assuming that eligible means currently routing.
FED
Is an end device that remains ready to receive without acting as a mesh router. Evidence should separate low-latency reception from routing responsibility.
MED or SED
Communicates through a parent and may trade response timing for power. Evidence should show parent choice, queued-message behavior, and whether the application can tolerate the delay.