mitshell

And thank you for the introductory message. It's OK ask questions in issues: as I am currently the only active maintainer / developer for the project, I prefer to keep...

Thanks a lot for the feedback. Do not hesitate to update this issue with any new findings.

These ITS ASN.1 specs seem really to have spreaded, being reused and adapted in several countries and by multiple SDOs. I can't answer your question btw, choose the naming which...

The definition of `AChBillingChargingCharacteristics` is in _CAP-datatypes.asn_: ``` AChBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE (bound.&minAChBillingChargingLength .. bound.&maxAChBillingChargingLength)) (CONSTRAINED BY {-- shall be the result of the BER-encoded value...

The current Camel ASN.1 definition is extracted (semi-automatically) from the corresponding 3GPP specification. It may be possible to change a type from the existing spec, plus the constraint (moving to...

Can you please indicate where the object `TCI_Dispatcher.TCIMsg` comes from? I don't think the module `tci` comes from pycrate. This is needed for me to reproduce the issue. Thx

OK, thanks for spotting this issue. Would you have a suggestion for a fix?

I implemented a fix: https://github.com/pycrate-org/pycrate/commit/91b7713c7a53a9b3c1ee2cf58dc5fc79a066a205. Can you pull it and have a look to ensure your issue is adressed @ttt710516 ?

Thanks for the report. Pycrate's exception says `RetrieveNotificationsListResponse.notificationList._item_.otherSignedNotification: missing mandatory component, tbsOtherNotification`, which means the value you submitted to the decoder is missing the mandatory field `tbsOtherNotification` within the SEQUENCE...

So, the `RSPDefinitions` module is defined with the directive `AUTOMATIC TAGS`, but then in the object `OtherSignedNotification`, they tag the optional component `otherCertsInChain` manually with tag 1. I don't know...