XAMPPRocky

Well Real types should have `{encode, decode}_real` methods on `Encoder` and `Decoder`. I just haven't added it yet, because real types are the most difficult to understand and implement IMO....

Thank you for your issue! Yes in fact, as noted in the last release. This project has received a grant to add PER support to the framework. There's a branch...

@laf0rge Yes, APER will be also be released at the same time, the implementation is the same as BER/CER/DER, where we have a single encoder/decoder, that changes only when the...

Thank you for your issue! I’m still working on supporting constraints as part of the framework, but I don’t have any plans for when though as I work on this...

> (sorry if I'm being nit-picky, I just want to be sure that's how I should declare it) No worries, feel free to ask me any questions. > then any...

I'm going to keep this open, since there's a need to support constrained types in general for encodings like PER.

> When will PER, UPER, OER and COER be supported？ Indeterminate, this a project I work on in my spare-time on-top of my other projects and a full-time job. It...

Thank you for your issue! It might be that it’s registered under both, because looking at RFC 5280 (the RFC where these OIDs came from), it’s under `2, 2`. I...

Yeah it should be fine, we don't actually ensure the tree is unique IIRC

Thank you for your issue! This seems maybe valid, it's definitely a difference at least, though I'm not sure why yet, and not entirely sure how to fix it. The...