ITS - Intelligent Transport Systems issueshttps://forge.etsi.org/rep/groups/ITS/-/issues2022-06-22T08:50:26Zhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/11Load certificate on the flow2022-06-22T08:50:26ZYann Garciayann.garcia@fscom.frLoad certificate on the flowDo not load all certificates when starting the TestSystem but only when a certificate in requiredDo not load all certificates when starting the TestSystem but only when a certificate in requiredYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/10Report EC comments into ETSI standard documents2022-06-22T08:50:41ZYann Garciayann.garcia@fscom.frReport EC comments into ETSI standard documentsCreate NWI to add EC comments (https://etsihq.sharepoint.com/:f:/r/teams/STF594/Shared%20Documents/General/2020-03_STF_594_Deliverables_JRC-Review?csf=1&web=1&e=fKGm6d)Create NWI to add EC comments (https://etsihq.sharepoint.com/:f:/r/teams/STF594/Shared%20Documents/General/2020-03_STF_594_Deliverables_JRC-Review?csf=1&web=1&e=fKGm6d)Yann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/9Add a PIXITs to omit geographicalRegion in innerEcRequest2022-03-31T13:21:25ZYann Garciayann.garcia@fscom.frAdd a PIXITs to omit geographicalRegion in innerEcRequestIn bot functions f_generate_inner_ec_request() and f_generate_inner_ec_request_with_wrong_parameters()In bot functions f_generate_inner_ec_request() and f_generate_inner_ec_request_with_wrong_parameters()Yann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/8Need to validate TC_SECPKI_ITSS_CTL_xxx2022-03-25T08:28:40ZYann Garciayann.garcia@fscom.frNeed to validate TC_SECPKI_ITSS_CTL_xxxYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/7Need to validate IS against real devices2022-03-25T08:28:05ZYann Garciayann.garcia@fscom.frNeed to validate IS against real devicesYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/6Minimize size of virtualized image for ISG MEC MEC-030 simulation of Uu & PC52022-06-22T08:49:30ZYann Garciayann.garcia@fscom.frMinimize size of virtualized image for ISG MEC MEC-030 simulation of Uu & PC5Yann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/5Create a TITAN framework library sub-module2022-09-29T12:12:04ZYann Garciayann.garcia@fscom.frCreate a TITAN framework library sub-moduleYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/4Create branch for ITS Release 22022-03-22T09:46:28ZYann Garciayann.garcia@fscom.frCreate branch for ITS Release 2Align Test System Release 2 with ASN.1 files
Add new ASN.1 Release 2 filesAlign Test System Release 2 with ASN.1 files
Add new ASN.1 Release 2 filesYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/3Update ETSI TR 103 0992022-03-22T07:13:12ZYann Garciayann.garcia@fscom.frUpdate ETSI TR 103 099Add UtPkiEventInd message
Provide more details on configuration for each ATS
Clean upAdd UtPkiEventInd message
Provide more details on configuration for each ATS
Clean upYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/2Add support of Nist-P384 signature2022-06-23T13:35:21ZYann Garciayann.garcia@fscom.frAdd support of Nist-P384 signatureYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/TS.ITS/-/issues/1Add support of non-privacy2022-03-22T07:10:35ZYann Garciayann.garcia@fscom.frAdd support of non-privacyYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/asn1/cdd_ts102894_2/-/issues/4CDD DENM cause code name spelt incorrectly2022-08-25T02:01:40ZMatthew BanksCDD DENM cause code name spelt incorrectlyOne of the most recent DENM cause code names is spelt incorrectly...
In https://forge.etsi.org/rep/ITS/asn1/cdd_ts102894_2/-/blob/master/ITS-Container.asn there is a cause code:
```
aquaplannning (7),
```
This should "aquapla...One of the most recent DENM cause code names is spelt incorrectly...
In https://forge.etsi.org/rep/ITS/asn1/cdd_ts102894_2/-/blob/master/ITS-Container.asn there is a cause code:
```
aquaplannning (7),
```
This should "aquaplaning"
-- Thanks, Matthttps://forge.etsi.org/rep/ITS/asn1/cdd_ts102894_2/-/issues/3testing issue2021-07-14T11:20:02ZDenis Filatovtesting issueShall be tested!
[ticket place](https://forge.etsi.org/rep/ITS/asn1/cdd_ts102894_2/blob/release2/ITS-Container.asn#L24)Shall be tested!
[ticket place](https://forge.etsi.org/rep/ITS/asn1/cdd_ts102894_2/blob/release2/ITS-Container.asn#L24)https://forge.etsi.org/rep/ITS/asn1/cdd_ts102894_2/-/issues/2Release 2 message IDs2022-08-25T02:03:33ZMatthew BanksRelease 2 message IDsITS-Container.asn contains the PDU header message ID for each message type. Currently this lists up to the "rtcmem" ID of 13.
```
ItsPduHeader ::= SEQUENCE {
protocolVersion INTEGER (0..255),
messageID INTEGER{ denm(1), cam(2),...ITS-Container.asn contains the PDU header message ID for each message type. Currently this lists up to the "rtcmem" ID of 13.
```
ItsPduHeader ::= SEQUENCE {
protocolVersion INTEGER (0..255),
messageID INTEGER{ denm(1), cam(2), poi(3), spatem(4), mapem(5), ivim(6), ev-rsr(7), tistpgtransaction(8), srem(9), ssem(10), evcsn(11), saem(12), rtcmem(13) } (0..255), -- Mantis #7209, #7005
stationID StationID
}
```
However there are a number of newer message types that don't have a definition even though the specs refer to ETSI TS 102 894-2, this includes CPM, MCDM, VAM, PZM. Whilst these are Release 2 features I don't see where their message IDs are defined, especially since the BTP ports and ITS-AIDs are already defined for these services.https://forge.etsi.org/rep/ITS/ITS/-/issues/19Brainpool P384r1 support2020-12-01T11:05:45ZSzilveszter TÓTHBrainpool P384r1 supportHello!
We are using ITS on branch STF525 for testing our V2X PKI services. This is a great tool, and we find it very helpful. It can be used for keys on elliptic curves NIST P256 and Brainpool P256r1. However, we do not find a way to us...Hello!
We are using ITS on branch STF525 for testing our V2X PKI services. This is a great tool, and we find it very helpful. It can be used for keys on elliptic curves NIST P256 and Brainpool P256r1. However, we do not find a way to use it with Brainpool P384r1.
If we set LibItsPki_Pixits.PX_EC_ALG_FOR_EC := e_brainpool_p384_r1 in the config file, it fails with the following error message:
Wrong encryption variant
I suspect that this happens because it tries to use the same algorithm for encryption, too, which is not possible.
Is there a way to use key on curve Brainpool P384r1 extensively for testing, is it supported?
Thank you!https://forge.etsi.org/rep/ITS/asn1/cdd_ts102894_2/-/issues/1Integration of Errata Document2020-05-11T07:50:36ZHendrik-Joern GuentherIntegration of Errata DocumentThe errata document has been published at https://docbox.etsi.org/ITS/Open. The erratas need to be integrated into the CDD. The tagging and referencing scheme has to be harmonized and agreed.The errata document has been published at https://docbox.etsi.org/ITS/Open. The erratas need to be integrated into the CDD. The tagging and referencing scheme has to be harmonized and agreed.https://forge.etsi.org/rep/ITS/ITS/-/issues/18HTTP 1.1 status reason-phrase (status text) is optional2019-08-27T09:49:58ZSzilveszter TÓTHHTTP 1.1 status reason-phrase (status text) is optionalDear ETSI Team,
We had an issue with the ITS testing tool on branch STF525.
Namely, it expects the reason-phrase to be present, which is optional according to RFC 7230 (https://tools.ietf.org/html/rfc7230#section-3.1.2):
> The rea...Dear ETSI Team,
We had an issue with the ITS testing tool on branch STF525.
Namely, it expects the reason-phrase to be present, which is optional according to RFC 7230 (https://tools.ietf.org/html/rfc7230#section-3.1.2):
> The reason-phrase element exists for the sole purpose of providing a
> textual description associated with the numeric status code, mostly
> out of deference to earlier Internet application protocols that were
> more frequently used with interactive text clients. A client SHOULD
> ignore the reason-phrase content.
>
> reason-phrase = *( HTAB / SP / VCHAR / obs-text )
(The asterisk there means that it may not appear at all.)
Some HTTP server implementations now omit this part of the status line, barely emitting
```
HTTP/1.1 200
```
(with no "OK" at the end).
The testing tool would fail with an error log like this:
```
MTC@13cb672994ff: Matching on port httpPort .response.statustext := "" with "OK" unmatched: First message in the queue does not match the template:
```
We had to change the web server implementation to include the reason-phrase to pass the test.
Thank you for your help!https://forge.etsi.org/rep/ITS/ITS/-/issues/17Errors because of removing trailing 0A and 0D bytes from HTTP responses2019-08-22T09:36:14ZSzilveszter TÓTHErrors because of removing trailing 0A and 0D bytes from HTTP responsesDear ETSI ITS Team,
We are using the STF525 branch of the project to test our (Microsec's) V2X PKI infrastructure software. This is a great help and many thanks for building such a useful testing tool!
During our tests sometimes we get...Dear ETSI ITS Team,
We are using the STF525 branch of the project to test our (Microsec's) V2X PKI infrastructure software. This is a great help and many thanks for building such a useful testing tool!
During our tests sometimes we get a message from the test suite as follows:
```
fx__decrypt__aes__128__ccm__test: Failed to decrypt message
```
As we investigated further, we saw that the error was that the last byte of the authTag was changed to 00. When the HTTP response was read, it contained either 0A (LF) or 0D (CR) as the last byte:
```
MTC@aa2a65190077: http_codec::decode_body: Aligned body='...0EB347CDCF7EEDE541E20E517455770D'O
MTC@aa2a65190077: http_codec::decode_body: counter=1
MTC@aa2a65190077: http_codec::decode_body: body length=331
MTC@aa2a65190077: http_codec::decode_body: Finalised body='...0EB347CDCF7EEDE541E20E51745577'O
```
As you can see, here we have already lost the last byte (0D). The authTag is incorrect too:
```
MTC@aa2a65190077: fx__decrypt__aes__128__ccm__test: tag: '0EB347CDCF7EEDE541E20E5174557700'O
```
The following code snippet removes trailing CR/LF bytes from HTTP responses, which may be incorrect and causes the above phenomenon:
```
// Remove CRLF if any
int counter = 0;
if ((body[body.lengthof() - 1].get_octet() == 0x0d) || (body[body.lengthof() - 1].get_octet() == 0x0a)) {
counter += 1;
if ((body[body.lengthof() - 2].get_octet() == 0x0d) || (body[body.lengthof() - 2].get_octet() == 0x0a)) {
counter += 1;
}
}
loggers::get_instance().log("http_codec::decode_body: counter=%d", counter);
```
How can we correctly transfer an HTTP response which contains trailing 0A or 0D bytes to the test system? Now the only solution is re-running the test to see the error message (probably) disappear.
Thanks in advance for your response,
BR,
Szilveszter Tóth
MicrosecYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/ITS/-/issues/16Information on BTP Test Suite2019-08-08T06:45:12ZkronnebergInformation on BTP Test SuiteHello,
I would just like to know if the BTP test suite is available for execution. I ask you this question because there is no btp_generate_makefile.bash script nor a cfg file. I built them but the test failed.
If it is possible to laun...Hello,
I would just like to know if the BTP test suite is available for execution. I ask you this question because there is no btp_generate_makefile.bash script nor a cfg file. I built them but the test failed.
If it is possible to launch this suite, can you give me a model of cfg.
Thank you for your help.
Regards,
Valerie kronnebergYann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.frhttps://forge.etsi.org/rep/ITS/ITS/-/issues/15GBC routerHopLimit invalid value2019-08-08T08:30:00ZkronnebergGBC routerHopLimit invalid valueHi,
When running the test TC_GEONW_PON_GBC_BV_07 , TITAN tester sends to the IUT a GBC which routerHopLimit=1 when a value > 1 is expected.
For debug purpose, I changed the c_defaultHopLimit value from 10 to 9
and also PICS_GN_DEFAULT_H...Hi,
When running the test TC_GEONW_PON_GBC_BV_07 , TITAN tester sends to the IUT a GBC which routerHopLimit=1 when a value > 1 is expected.
For debug purpose, I changed the c_defaultHopLimit value from 10 to 9
and also PICS_GN_DEFAULT_HOP_LIMIT := 9
However the titan traces shows at "build_geonetworking_pdu: gbc:"[TC_GEONW_PON_GBC_BV_07.zip](/uploads/8cf015611f2a8bd2b248b75c3caa1109/TC_GEONW_PON_GBC_BV_07.zip) that routerHopLimit = 1 (line 5105)
The point that is surprising is that at line 4649 the traces show routerHopLimi := 9
I join the titan , sut and wireshark traces and cfg file.
Please, could you tell me how setting up the Hop Limit .
Regards,
Valerie Kronneberg[TC_GEONW_PON_GBC_BV_07.zip](/uploads/5cb1635b6914b588a6ac46e7f924a980/TC_GEONW_PON_GBC_BV_07.zip)Yann Garciayann.garcia@fscom.frYann Garciayann.garcia@fscom.fr