mosh:protocol:layers:transport:framing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| mosh:protocol:layers:transport:framing [2026/05/10 19:47] – [Domains, Operations Codes, and Context ID] mosh | mosh:protocol:layers:transport:framing [2026/05/15 04:27] (current) – [Domains, Operations Codes, and Context ID] mosh | ||
|---|---|---|---|
| Line 25: | Line 25: | ||
| All MOSH packets follow this structure: | All MOSH packets follow this structure: | ||
| - | | Header (12 Bytes) | | + | | Header (13 Bytes) | |
| | Payload (1,456 Bytes max) | | | Payload (1,456 Bytes max) | | ||
| | Footer (CRC16) (2 Bytes) | | | Footer (CRC16) (2 Bytes) | | ||
| Line 40: | Line 40: | ||
| | Destination Address | | Destination Address | ||
| | Context | | Context | ||
| - | | Payload Length | + | | Payload Length |
| ===== Footer (2 Bytes) ===== | ===== Footer (2 Bytes) ===== | ||
| Line 87: | Line 87: | ||
| ===Domain (3-bits)=== | ===Domain (3-bits)=== | ||
| ^ Domain ^ Context | ^ Domain ^ Context | ||
| - | | 0 | Core/system messages (discovery, sync, error) | | + | | 0x00 |
| - | | 1 | Node-level (hardware) operations | + | | 0x01 |
| - | | 2 | Element-level operations | + | | 0x02 |
| - | | 3 | Virtual wire messaging | + | | 0x03 |
| - | | 4–7 | RESERVED | + | | 0x04 |
| + | | 0x05 | Routing messages | ||
| + | | 0x06 | RESERVED1 | ||
| + | | 0x07 | ||
| ===Operations Code (5-bits)=== | ===Operations Code (5-bits)=== | ||
| - | Each domain has it's own operations code definitions | + | Each domain has it's own operations code definitions. |
| * [[mosh: | * [[mosh: | ||
| * [[mosh: | * [[mosh: | ||
| * [[mosh: | * [[mosh: | ||
| * [[mosh: | * [[mosh: | ||
| + | * [[mosh: | ||
| + | * [[mosh: | ||
/var/www/wiki.moshnetworks.com/data/attic/mosh/protocol/layers/transport/framing.1778442478.txt.gz · Last modified: by mosh
