Clarify semantics of comm states STOP and IDLE and BusOn event: Adapt API manual

The API manual states:

In contradiction to this, the nX90 firmware, when in state STOP:

1. Does not reply to ListIdentity/Encap Services
2. Does not allow UCCM/CL3/CL1

See testcase https://subversion01.hilscher.local/svn/Testframework/Tests/EthernetIP/branch/EIP_V3/SlaveV3/EIP_Slave_SoftMaster_CommState.py 

Please clarify regarding consistency of EISV3/EISV5 and API manuals. What do other protocol stacks do? The current implementation seems to be a clear, logical solution. I propose just to redefine/rephrase in the API manual