Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reserving ranges #158

Open
raulk opened this issue Jan 31, 2020 · 4 comments
Open

Reserving ranges #158

raulk opened this issue Jan 31, 2020 · 4 comments

Comments

@raulk
Copy link
Member

raulk commented Jan 31, 2020

Add the ability to reserve ranges in the multicodec table, à la Protobuf.

@Stebalien
Copy link
Member

We can "soft" reserve small ranges in the 2 byte range (16,256) codes, we can probably hard reserve small ranges in the 3 and 4 byte ranges (2e6 and 2.5e8 codes respectively). Assuming there's a good argument for it.

By "soft" reserve, I mean "try to leave this range open unless we need to use it for something else".

@ntninja
Copy link
Contributor

ntninja commented Aug 24, 2020

Could we designate a private-use area in the 4-byte range? Specifically, I hereby nominate this range to be 0x300000 - 0x3fffff (just above the designated media type area of #159) and will use this until/unless some other area is decided upon.

@rvagg
Copy link
Member

rvagg commented Aug 25, 2020

^ @ntninja open a PR to note that in the README and check for their absence in the validation script and we can probably lock that in.

ntninja added a commit to ntninja/multicodec that referenced this issue Aug 25, 2020
@ntninja
Copy link
Contributor

ntninja commented Aug 25, 2020

@rvagg: Done!

rvagg pushed a commit that referenced this issue Aug 28, 2020
See GH/#158. Changes are analogous to those proposed in GH/#159.
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

No branches or pull requests

5 participants
@ntninja @Stebalien @rvagg @raulk and others