1038 Loss of Info Detection After Resynch
Created: 11 Mar 2013
Status: In Force (green)
Part: Part 7-2 (2010; Edition 2)
Category: Issue for edition 2 of this part
Clause 220.127.116.11.2.8 says that: "The detection of possible loss of information occurs when a client requests a resynchronization to a non-existent entry...". On the other hand, clause 18.104.22.168 (when explaining BRCB state machine, resync state) says: "If the value of the set EntryID does not exist within the queue of entries, a ServiceError of parameter-value-inappropriate shall be returned and the BRCB state shall transition to disabled". According to the last statement there is no way that we can differentiate between wrong EntryID input and possible loss of information from client's point of view. More than that, having addressed to the wrong EntryID, we get no reports at all (no BufOvfl value indicated).
The detection of possible loss of information occurs when a client requests a resynchronization to the first entry in the queue.
Privacy | Contact | Disclaimer
Tissue DB v. 22.214.171.124