M17_spec
M17_spec copied to clipboard
M17-Project
M17 standard specification
ARNCE?
Howdy, I saw that you were encoding callsigns in a similar way to the mechanism I came up with a few years ago: https://github.com/arngll/arnce-spec/blob/main/README.md#amateur-radio-numeric-callsign-encoding-readme I put a lot of thought...
Provide a CRC value for some example LSF, like SRC: A1BCD, DEST: E2FGH, TYPE: 0x0005, CAN: 0, META: 0, reserved bits zeroed. Just so the reader/implementer can test his/her code...
I propose the IP Networking Control Packets specification be extended with two additional types to provide optional password authentication. This will allow operators of servers to choose whether they wish...
NACK is defined as a packet type, but it's not explained what this packet does. Also, provide a flowchart of a client connecting to a reflector.
The IP Networking section (`docs/ip_encapsulation.rst`) of the specification refers specifically to reflectors throughout. While this is currently the only method of doing M17 Internet linking, a healthy discussion happened on...
Had a few suggestions, take it for what it is, just a couple things I've thought to myself while writing both an M17 decoder, and more recently, an encoder as...
At the moment, section 1.4.1 describes, that the preamble can be sequence of `(+3, -3)` or `(-3, +3)`. When each of them is used is later described in section 2.4...
>Packet superframes are composed of a 1..n byte data type specifier, 0..797 bytes of payload data. I believe the value should be updated to `33*25-3=822`.
Link Setup Data* must remain the same over the course of a superframe, and receivers should only reassemble the LSD chunks from within a single superframe. *naming convention - LSF...