KB8PMY
/
FreeDMR
mirror of http://gitlab.hacknix.net/hacknix/FreeDMR.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c2c7e654cb'
${ noResults }
FreeDMR/docs/freedmr-2/05-data-packet-policy.md

1.1 KiB
Raw Blame History

Data Packet Policy

No regression of DMR data support is permitted.

FreeDMR should forward supported DMR data packets according to conference/subscription and mesh rules. The FreeDMR core should not become a general GPS/SMS application processor.

GPS, SMS, and similar application processing should be implemented by systems connected via FBP or another mesh/access-adjacent interface. DATA-GATEWAY is understood as an earlier expression of this model.

Existing SUB_MAP / last-known-location behaviour is intentional: data addressed to a DMR ID can be routed toward the last known HBP/client location.

Narrow exceptions may exist for SMS-based dial-a-TG control or DMR SMS alerts to the sysop.

Data/control classification must be separate from group-vs-unit addressing. A group-addressed data packet is not automatically a voice stream.

The packet layer may inspect data packets for admission, routing, loop/source-quench safety, reporting, and metadata preservation. Application-level GPS/SMS semantics should live outside the core unless a specific control-plane feature requires it.

Powered by TurnKey Linux.