1433 URCB Resv during an association lost/abor/release

Created: 18 Aug 2015

Status: In Force (green)

Part: Part 7-2 (2010; Edition 2)

Links: #1432 Resv required to be set before configuring URCB

Page: 117

Clause: 17.2.4.5

Paragraph:

Category: Issue for edition 2 of this part

Issue

There is nothing specified if a Server device shall reset an reserved URCB after the association got lost/were aborted/released.

Proposal

The server shall set Resv to FALSE after association lost/release/abort to avoid a blocked URCB. If a non-persistent dataset were used the UCRB needs anyhow a reconfiguration.

Discussion	Created	Status
Valid with Ed2.1	16 Dec 15	In Force (green)
For URCB not reserved by SCL, The server shall set Resv to FALSE after association lost/release/abort. See TISSUE 1432 also. SCL issues are addressed there.	28 Oct 15	Ballot Period
A lost client does not automatically mean that the client releases the URCB. Having a link to a non persistent data set is a special case. The reset may only be appropriate if Resv has been set with communication services directly or indirectly via RptEna, but even then not always, if the data set is preconfigured or persistently defined. If it has been reserved via SCD file, it must stay reserved.	26 Aug 15	Discussion (red)
accepted. as a non-persistent data-set will be deleted at association lost, the datSet attribute will automatically be emptied too.	19 Aug 15	Discussion (red)

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1