Skip to content

docs: add vendor ID allocation table#81

Open
alexcekay wants to merge 1 commit into
dronecan:masterfrom
PX4:pr-reserve-vendor-ranges
Open

docs: add vendor ID allocation table#81
alexcekay wants to merge 1 commit into
dronecan:masterfrom
PX4:pr-reserve-vendor-ranges

Conversation

@alexcekay
Copy link
Copy Markdown

@alexcekay alexcekay commented May 28, 2026

Context

The vendor range [20000, 21000) has grown organically with no tracking of who uses what. The result is vendors picking IDs ad-hoc. Without documented allocations, downstream projects cannot add messages independently without risking ID collisions when syncing with upstream.

Changes

This PR documents current usage and formalizes contiguous blocks so each namespace has room to grow autonomously: 100 IDs for open-source projects, 20 IDs for companies. Blocks are anchored to each vendor's first existing allocation. IDs that fall outside their natural block are listed in another table.

This also adds the px4.* namespace (20800–20899) following the existing ardupilot/ precedent, and com.auterion.* (20900–20919) as Auterion's company namespace.

If your namespace is represented incorrectly or you'd prefer a different block size, comment and I'll happily adapt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant