Node Names [DRAFT]
Meshcore Node Naming Guide
This guide outlines the standardised naming convention for MeshCore infrastructure nodes (Room Servers and Repeaters only). It ensures consistency, readability, and compatibility within a 32-character limit.
Naming Format
Repeaters
Naming Layout
[SSS3]-[LOC10] [TYPE3]-[SUBTYPE3]-[ID2] [DESC6]
Segment Definitions
| Field | Length | Description |
|---|---|---|
SSS3 |
3 | State/Province/Territory, uppercase (e.g. VIC, NSW) |
LOC10 |
10 | Up to 10 letters of locality (e.g. MELTON, GEELONG, CHELTENHAM) |
TYPE3 |
3 |
Node type
|
SUBTYPE3 |
3 |
Repeaters
Room Servers
|
ID2 |
2 | 2 digit number (01-99) identifying the node. |
DESC6 |
≤6 | Less than 6 characters optional free-text (for all node types), human-readable description. e.g. to identify node maintainer or special purpose. Can be more than 6 characters if location is less than 10 characters. |
Room Servers
Naming Layout
[SSS3] [TYPE3]-[SUBTYPE3] [DESC21]
Segment Definitions
| Field | Length | Description |
|---|---|---|
SSS3 |
3 | State/Province/Territory, uppercase (e.g. VIC, NSW) |
TYPE3 |
3 |
Node type
|
SUBTYPE3 |
3 |
Room Servers
|
DESC21 |
≤21 | Less than 21 characters optional free-text, human-readable description. e.g. to identify node location, purpose, owner. |
Rules
-
All segments are separated by single spaces or hyphen (review the Naming Format heading at the top of this page).
-
Total name must not exceed 32 characters.
-
Description field is optional, but encouraged to help identify node purpose or owner.
Examples
Room Servers
| Purpose | Node Name |
|---|---|
| Room Server (non-repeating) node for public use | VIC RMS-PUB MeshCore Fan Club |
| Room Server (Repeating) node for private use | VIC RMP-PRV Lewd ASCII Art |
Repeaters
| Purpose | Node Name |
|---|---|
| Core Repeater in Hobart | TAS-HOBART RPT-COR-01 |
| Distribution Repeater in Dandenong | VIC-DANDENONG RPT-DIS-01 |
| Edge Repeater in Geelong on Phil's house | VIC-GEELONG RPT-EDG-01 Phil |