Analysis resulted in changing into unidirectional objects would (if possible) not be backward compatible.
Unidirectional objects will not to be part of TR-532 v1.1
Issue#25 remains open
When radio is equipped with single transmitter and 2 receivers
two possible solutions presented in the proposals
decision to stick with the 'solution 2' with 2 airInterface and to work to a 'clean' solution to introduce unidirectional objects; this would cover the case of space diversity and future scenarios of P2MP
A table comparing the TX and RX classes have been discussed:
Proposals for sorting airInterface attributes into TX and RX classes
In the WT call of 18/4 it has been decided to have a modified proposal from Thorsten to address the cases of bidirectional parameters; deadline moved to 25/4
In the WT call of 2/5 it has been verified that there are still pending the actions; deadline moved to 25/5 after modelling session in Italy
What about the proposal to have additional attributes ?