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

How to encode extension / attribute if the extension / attribute value cannot be CBOR encoded? #189

Open
xipki opened this issue Apr 28, 2024 · 2 comments

Comments

@xipki
Copy link
Contributor

xipki commented Apr 28, 2024

To encode the extension / attribute value in CBOR, pre-conditions have to be satisifed. It is not clear how to encode them in negative cases.

Considering the extension CertificatePolicies as example, shall it be encoded as option 1 or option 2?

  • Option 1: (extenionID : uint, extensionValue : bstr)
  • Option 2: (extensionID: ~oid/pen, ?critical, extensionValue: bstr)
@highlunder
Copy link
Collaborator

Recap of discussion: yes option 1 can cause problems for the future, if we are later adding cbor encoding/decoding of the values. To be further looked into!

@gselander
Copy link
Collaborator

The design team are currently in favor of specifying option 2. @xipki is welcome to make a PR before the cutoff if time permits.

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

3 participants