Measure, explain, propose

The working principles

• Measure before asserting.

  Every recommendation rests on published and reproducible data. Before a frequency or a channel width is proposed, its effect on neighbouring networks is measured. The methods are documented so that the results can be challenged or confirmed.

• Propose, never impose.

  No convention carries any binding force. A rule holds because it is justified and followed by default, not because it is decreed. No community is called upon to abandon its settings: the division of the sub-band is discussed with each of them. Every operator remains in control of their own equipment.

• Explain the consequences.

  A recommendation is published with the effect it produces and the cost it avoids, for example what a larger channel width takes away from neighbouring protocols. The recipient must be able to judge for themselves.

• Produce tools.

  A tool that configures a device correctly, or that shows the actual occupancy of the sub-band, does more for coexistence than a corpus of recommendations. Effort goes first to what reduces friction.

• Give credit.

  Work that is reused is cited. Settings published by a community, such as those of Gaulix for Meshtastic, are reused with their source. Outside contributions are attributed to their authors.