OpenOMCI not enforcing stop-and-wait protocol

According to G.988 Section B.2.2, when using the Baseline message set, the OLT must ensure that a transaction to a given ONU is completed prior to starting a new transaction within the same priority level. Two priority levels are defined  0 and 1. priority levels are encoded in MSB of transaction ID. Hence transaction IDs must be in the range 0x0001-0x0fff.

Currently, multiple Tasks that are not exclusive can all launch separate, concurrent messages to ONU.

Within one task, more analysis is need to see if stop-and-wait is being implemented.

It does not appear that the core omci_cc is enforcing different tasks to have unique transaction ids. It is probably better for TIDs to be allocated in omci_cc to prevent overlap. And to enforce the range 1-fff.