635 Overlap of bufTim and Integrity report

Created: 06 Mar 2009

Status: Not Applicable

Part: Part 7-2 (2003)

Links:

Page:

Clause: 14

Paragraph:

Category: Issue for edition 2 of this part

Issue

In case that data change with bufTim and integrity report are configured at the same report control block, it is not clear what happens if the integrity report is generated before bufTim times out. The alternatives are: sending the buffered events before the integrity report, thus repeating the buffered events immediately, or cancelling the sending of the buffered events.

Proposal

Events are generated for event based updating, integrity reports to recover lost events - i.e. it must not be considered to be an event. From this point of view sending buffered events before the integrity report is superfluous, as they are also contained as status update in the integrity report. To reduce the amount of data sent it is suggested to cancel the sending of the buffered events in this case, or leave this a local implementation decision.

Discussion	Created	Status
According to 7-2, clause 16.2.3.2.3.3 Integrity: All buffered entries shall be sent before integrity reportss can be sent. That means alternative 1) : sending the buffered events before the integrity report. I disagree with the reducing data, sending only integrity and not the dChg report. For client, it should means when data.integrity != lastData.dChg that 1) a report has been lost 2) the seqNum has not mismatched -> I'd say it is not a correct implemtation.	07 Mar 09	Discussion (red)

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1