You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Variable-length fields cause all sorts of problems in practice (most immediately, I can't implement fixed-width telemetry messages).
This doesn't limit practical applications; if you need more than 2**64 data origins in the next hundred years you're doing something very wrong.
Six bytes is the convention, but there's no point wasting the last two bytes of the word.
This is a breaking change, so I suggest it be slipped into v3. For now, I propose a documentation change indicating a limit-by-convention, and that origins in telemetry messages be truncated to eight bytes.
The text was updated successfully, but these errors were encountered:
This is a breaking change, so I suggest it be slipped into v3. For now, I propose a documentation change indicating a limit-by-convention, and that origins in telemetry messages be truncated to eight bytes.
The text was updated successfully, but these errors were encountered: