When we talk about building a resilient, off-grid communication system, most people immediately think about radios, mesh networks, or long-distance links.
But there’s a deeper question:
How does the system actually know who a message is for—and how to reach them?
That’s where the EHN Directory comes in.
The Problem: Messages Without Meaningful Destinations
In traditional radio systems, communication is often tied directly to:
- a callsign
- a frequency
- a specific network
That works well—until you try to bridge multiple systems together.
Imagine this:
- A Meshtastic node sends a message
- The message crosses an HF link
- It reaches another region
- The intended recipient is… on SMS
Now what?
Without a shared understanding of identity, the system can only:
- broadcast blindly
- or fail to deliver
Neither is acceptable in an emergency system.
The EHN Approach: Logical Identity First
The EHN Directory introduces a simple but powerful idea:
Separate identity from transport
Instead of saying:
- “send this to a phone number”
- or “send this to a node ID”
We say:
DST=USER:mary
Now the system can decide:
- Is Mary on mesh?
- Should this go via SMS?
- Is there a better path?
The message becomes about the person, not the network.
Personal vs Operational Identities
One of the key design decisions in EHN is supporting two types of identity.
Personal Identity
Represents an individual:
USER:jsmith
USER:n2dh
Used for:
- direct communication
- personal coordination
- one-to-one messaging
Operational Identity
Represents a function or group:
TEAM:ops-1
ROLE:net-control
TEAM:shelter-2
Used for:
- emergency coordination
- team communication
- persistent roles
Why This Matters
In real-world operations:
- People change roles
- Devices fail
- Teams rotate
But:
The role must remain reachable
If “net control” changes operators, the system still needs to reach:
ROLE:net-control
That’s something traditional systems struggle with—and something EHN handles cleanly.
The Missing Piece: A Stable User Identity
Under the hood, the Directory introduces another important concept:
Every person gets a unique internal user ID
This ID:
- never changes
- is not reused
- ties everything together
So even if:
- someone changes their phone
- switches devices
- takes on a new role
…the system still knows it’s the same person.
Multiple Endpoints, One Identity
A single user might be reachable through:
- Meshtastic node
- SMS
- Winlink
- APRS
- local network
The Directory links all of these together.
So when you send:
DST=USER:jsmith
The system can choose:
- best path
- fallback path
- multiple simultaneous paths
Verification Matters
Of course, not all endpoints are equal.
Before bridging into public systems like SMS, the Directory ensures:
- the endpoint is verified
- the user is authorized
- the message meets policy and compliance rules
This prevents:
- spoofing
- abuse
- accidental misuse of external networks
From Messaging to Decision-Making
The EHN Directory doesn’t just enable delivery—it enables intelligent routing.
The system can decide:
- which network is currently available
- which path is most reliable
- how to escalate delivery if needed
This turns a simple message system into a decision-aware communication platform.
Real-World Example
Emergency Scenario
A flood sensor triggers an alert:
DST=TEAM:ops-1
The Directory resolves that to:
- Meshtastic nodes in the field
- SMS numbers for on-call staff
- Winlink addresses for EOC
The result:
- immediate local alert
- broader notification
- durable reporting
All from a single logical destination.
Personal Scenario
A field operator sends:
DST=USER:mary
The system determines:
- Mary is currently reachable via SMS
- mesh is unavailable
The message is delivered via SMS—without the sender needing to know anything about the network.
Why This Matters for EmergencyHam
The EHN Directory is a key part of the bigger vision:
- bridging amateur radio and modern networks
- supporting both education and real-world deployment
- enabling resilient communication in degraded environments
It allows us to move from:
“send a message over a network”
to:
“deliver a message to the right person or role, no matter what network is available”
Looking Ahead
The Directory opens the door to:
- smarter routing decisions
- automated responses
- AI-assisted coordination
- distributed applications
It’s not just a feature—it’s a foundation.
Final Thought
In a resilient communication system, networks will fail—but identity must persist.
The EHN Directory ensures that no matter what happens to the infrastructure:
- people remain reachable
- roles remain functional
- communication continues
Leave a Reply