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

Pre-populated packing tables #3

Open
miri64 opened this issue Aug 10, 2023 · 0 comments
Open

Pre-populated packing tables #3

miri64 opened this issue Aug 10, 2023 · 0 comments

Comments

@miri64
Copy link
Contributor

miri64 commented Aug 10, 2023

@chrysn wrote on the CBOR mailing list:

Are the packing tables pre-populated with any values? ("_coap._udp."
and ".com" would come to mind). If so, is the 1 in ;packed=1
intended to serve as an extension point that dispatches the values of
the table?

I really like this idea! However, some details need to be ironed out as this could go several (somewhat disjunct) routes:

  1. Are these extension points pre-defined tables?

  2. Do we use CRIs/URIs to identify and find tables (see e.g. https://datatracker.ietf.org/doc/draft-amsuess-cbor-packed-by-reference/)?

  3. Should the extension point be used in a similar manner as SCHC rule IDs, i.e., identify some pre-shared tables?

  4. and 3. don't necessarily contradict each other, as we could reserve number ranges for either pre-defined tables or pre-shared tables? 2. could also be integrated, e.g. with a dedicated number.

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

1 participant