doc: Document a shortcoming of the current OML code
The BTS has 10s to respond to a command but we do not run any
timer. So it is possible that the BTS gets stuck in the process
of the bring up.
diff --git a/openbsc/doc/oml-interface.txt b/openbsc/doc/oml-interface.txt
index 8ddcfea..02bead7 100644
--- a/openbsc/doc/oml-interface.txt
+++ b/openbsc/doc/oml-interface.txt
@@ -7,6 +7,7 @@
* therefore, we can have e.g. both the BSC and the OML interface send a
SET ATTRIBUTE message, where the responses would end up at the wrong
query.
+* The BTS has 10s to ACK/NACK a command. We do not run any timers.
the only possible solutions i can imagine:
* have some kind of exclusive locking, where the OML interface gets blocked