ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0002000 | Part 06: TTCN-3 Control Interface | Technical | public | 14-09-2007 14:27 | 06-12-2007 10:10

Reporter | Alexander Lorenz |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | major | Reproducibility | always
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v3.2.1 (published 2007-02) |
Target Version | v3.3.1 (published 2008-04) | Fixed in Version | v3.3.1 (published 2008-04) |
Clause Reference(s) | ETSI ES 201 873-6 V3.2.1 (2007-02),
Source (company - Author) | Testing Technologies

Summary | 0002000: TCI Value instead of TriAddress is needed for matching addresses

Description

In order to be able to match the recieved adress with the expected one it is necessary to use a TCI Value instead of TRiAddress, since the TriAddress is an encoded byte array and therefore cannot be compared to a TciValuTemplate.
This concerns the following TLI methods:
tliMReceive_m
tliPrGetCall_m
tliPrGetReply_m
tliPrCatch_m
tliMReceiveMismatch_m
tliPrGetCallMismatch_m
tliPrGetReplyMismatch_m
tliPrCatchMismatch_m

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | es_20187306v030301_CR2000_v3.zip (991,002) 04-12-2007 11:56 http://oldforge.etsi.org/mantis/file_download.php?file_id=1188&type=bug

Issue History
Date Modified | Username | Field | Change
14-09-2007 14:27 | Alexander Lorenz | New Issue |
14-09-2007 14:27 | Alexander Lorenz | Clause Reference(s) | => ETSI ES 201 873-6 V3.2.1 (2007-02),
14-09-2007 14:27 | Alexander Lorenz | Source (company - Author) | => Testing Technologies
14-09-2007 15:50 | Alexander Lorenz | Note Added: 0003279 |
13-10-2007 18:43 | Ina Schieferdecker | Assigned To | => Ina Schieferdecker
13-10-2007 18:43 | Ina Schieferdecker | Status | new => assigned
15-10-2007 12:31 | tepelmann | Note Added: 0003606 |
15-10-2007 12:33 | tepelmann | Note Edited: 0003606 |
18-10-2007 12:26 | Ina Schieferdecker | Target Version | => Edition 3.3.1 (not yet published)
18-10-2007 16:57 | Ina Schieferdecker | Note Added: 0003696 |
18-10-2007 16:57 | Ina Schieferdecker | Resolution | open => fixed
18-10-2007 16:58 | Ina Schieferdecker | File Added: es_20187306v030301_CR2000.zip |
18-10-2007 17:00 | Ina Schieferdecker | File Deleted: es_20187306v030301_CR2000.zip |
04-12-2007 11:56 | Ina Schieferdecker | File Added: es_20187306v030301_CR2000_v3.zip |
04-12-2007 16:38 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Thomas DeiÃŸ
05-12-2007 16:55 | Thomas DeiÃŸ | Note Added: 0004346 |
05-12-2007 16:55 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Ina Schieferdecker
05-12-2007 16:55 | Thomas DeiÃŸ | Status | assigned => resolved
06-12-2007 10:10 | Ina Schieferdecker | Status | resolved => closed
06-12-2007 10:10 | Ina Schieferdecker | Note Added: 0004363 |
06-12-2007 10:10 | Ina Schieferdecker | Fixed in Version | => Edition 3.3.1 (not yet published)

Notes

(0003279)
Alexander Lorenz
14-09-2007 15:50

The references in above mentioned standard document are:
7.3.4.1.19 tliMReceive_m
7.3.4.1.17 tliMMismatch_m
7.3.4.1.31 tliPrGetCall_m
7.3.4.1.43 tliPrGetReply_m
7.3.4.1.55 tliPrCatch_m
7.3.4.1.29 tliPrGetCallMismatch_m
7.3.4.1.41 tliPrGetReplyMismatch_m
7.3.4.1.53 tliPrCatchMismatch_m
The respective XML Schema representation of these logging events in annex B.5 would also have to be changed accordingly.

(0003606)
tepelmann
15-10-2007 12:31 (edited on: 15-10-2007 12:33)

Furthermore there is also a need for the following send events: 7.3.4.1.9 tliMSend_m 7.3.4.1.11 tliMSend_m_MC 7.3.4.1.21 tliPrCall_m 7.3.4.1.23 tliPrCall_m_MC 7.3.4.1.33 tliPrReply_m 7.3.4.1.35 tliPrReply_m_MC 7.3.4.1.45 tliPrRaise_m 7.3.4.1.47 tliPrRaise_m_MC NOTE: In the multicast cases address value lists are needed.

(0003696)
Ina Schieferdecker
18-10-2007 16:57

The logging interface is not about matching! However, the proposal makes the named operations consistent to the other operation definitions Not only the XML mapping needs to be fixed, but also the C and the Java mapping - and annex A and B in addition. Furthermore, the duplicated TriAddressType definition in 10.3.2.13 has been removed. See attached fix

(0004346)
Thomas DeiÃŸ
05-12-2007 16:55

checked by Thomas. Take care of clauses 10.4.2 ff. In the solution they are just empty clauses as they are not relevant for this CR. In the revised text the clauses must have content. Clauses 11.3.8.2, 11.5.3.2, 11.5.4.2 contain a change, which is probably a find and replace error. system was changed to System. This must not be implemented.

(0004363)
Ina Schieferdecker
06-12-2007 10:10

Indeed 10.4.2 ff. has been a left over - only "TCI TL provided" is relevant as the XML mapping does only cope with this interface. It had been decided to get rid of the table structure in the mapping sections of TCI as all changes had to be made at several places which is errorprone - now, the operation mappings contain the C, Java or XML definitions only.