Child pages
  • #37: Different types of loop backs not sufficiently covered

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Page properties
label
Status
Status
colourBlue
titleExecuted
Stakeholders
Outcome
Due date 
OwnerThorsten Heinze 

Decision

Adding additional values "RF_TO_REMOTE", " RF_TO_LOCAL", "IF_TO_REMOTE", and "IF_TO_LOCAL" to TypeDefinitions::LoopBackType Enumeration.

NOT deleting the existing values "IF" and "RF" to keep backward compatibility, but setting the stereotype "deprecated".

Keeping Issue#37 open until updating TR-532 without backward compatibility requirement and deleting the values "IF" and "RF" then

Background

Content of the Mantis Bug Tracker:

DescriptionSome device types apply the loopback in a different way than the one described in the loop-back-kind-on attribute of the microwave model.

While the microwave model is limiting on returning header information back to the remote side, some equipment apply the loopback by returning to themselves the air interface frames transmitted towards the remote side.

A potential solution might be detailing the values of the loopBackType enumeration:
- RF_TO_REMOTE
- RF_TO_LOCAL
- IF_TO_REMOTE
- IF_TO_LOCAL

Some attributes' comments have to be checked for limitations.