Raphael Riebl

Hi @Irisbus, can you please cross-check my *srem_ssem_ivim* branch? I have rebased your commits on the current master branch and would like to merge them. However, I would feel more...

Thanks @Irisbus for your update! These ASN.1 names tend to clash increasingly as we add more and more ASN.1 sources. Regarding the *ITS_Container_Temperature_t*: Nothing I have changed explicitly, probably caused...

I have finally merged the SREM, SSEM and IVIM messages into the master branch. Next will be your `IssuerIdentifier_t` PR.

I cannot recall the details anymore. One of the limitations has been the lack of support for SUMO's GUI back then. This might have changed meanwhile.

Sorry, I did not notice that *socktap* cannot be compiled. I should add *socktap* to the CI! Are you also suffering from the assertion failure mentioned by @lo-hei?

Thanks for your hard work and patience @khevessy!

Hi @serserHR, this PR is no longer compatible with our upstream *master* branch. Secured v3 messages can be received meanwhile. Support for outgoing v3 secured messages is a top priority...

You call the `subscribe` method provided by the `ItsG5BaseService` which subscribes to signals emitted by the middleware module or any of its submodules: https://github.com/riebl/artery/blob/4bc468e372091fa392d43c5fc3358821a21534c9/src/artery/application/ItsG5BaseService.cc#L101 Thus, signals emitted by the router...

Hi @Krupass, Such a feature has never existed officially, and I am also unaware of it "unofficially". If you only want to forward a particular message type, such as CAMs,...

Sure, just use GeoBroadcast (GBC) instead of Single-Hop-Broadcast (SHB) as transport type in the BTP data request: https://github.com/riebl/vanetza/blob/f0a136acc26c53c70d4d43a0215ff4ebc7eaf9b3/vanetza/btp/data_request.hpp#L19 Of course, you will also need to specify the destination area for...