I'm designing a data transmission pattern template for some Arduino development, and I want to designate a field in the data to describe the purpose and status of that packet of data. Before transmission it'd be used to describe if the packet is empty or malformed, and during transmission that same space would be used to convey the purpose of the packet. I'd like it to be an extensible but sensible field, so I want to name it appropriately so users don't stash information in it that ought to be stored somewhere else.
This value will always be included in the packet header, whereas the payload (contents of the packet) is optional.
Some earlier considerations:
- META - describes itself, possibly too broadly
- FLAGS - used to indicate a set of true-false values, not a single complex value
- STATUS - doesn't imply that this field also describes the intent of a packet