-
Notifications
You must be signed in to change notification settings - Fork 41
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
Support for CLASS ... WITH SYNTAX ... #46
Comments
I looked up |
Hi Kim,
I was also confused, but then I find this as a coherent explanation:
http://www.oss.com/asn1/resources/asn1-made-simple/advanced-topics.html
Especially "Information Objects" and "Open Types".
What they say is that there's a table describing instance values.
I've seen it used in RFCs with &Id / &Type pairs to replace earlier versions using ANY DEFINED BY (oidfield), which would assume that a table is defined to work out what OID belongs to what type in the ANY field.
…-Rick
|
Aaaw, my head hurts! Thanks, that was a good example. I'll save it for a day when I'm feeling perkier to think about whether it's implementable. |
Hi! |
I found asn1ate fairly straightforward to get into, as it is programmed really cleanly. I can only suggest that you consider adding this to the code and offering it as a PR. It's what we did for Quick DER, for imports. (I am not kimgr, so I have no say of what comes in of course, but I'd like this in Quick DER as well.)
http://github.com/vanrein/quick-der
|
Sorry, time has been scarce for asn1ate. I'll try to get to this, but I can't promise when. |
(feature request)
This construct is popping up in RFCs and other specifications to an increasing degree. It would be splendid to have it added to asn1ate, and then also to asn2quickder.
The text was updated successfully, but these errors were encountered: