revision of SECoP documentation

- created secop_v2017-09-14.rst, based on the GoogleDocs
  SECoP Preliminary V2016-11-30 (rc 2)
- this Document is supposed to contain the full SECoP standard
- created SECoP issues
- moved everything else to "outdated" (kept for reference)

Change-Id: I87d69d1846fc4ed55f1c78b22fd4650d8550152b
Reviewed-on: https://forge.frm2.tum.de/review/16573
Reviewed-by: Enrico Faulhaber <enrico.faulhaber@frm2.tum.de>
Tested-by: JenkinsCodeReview <bjoern_pedersen@frm2.tum.de>

doc/source/protocol/issue_4.rst

@@ -0,0 +1,18 @@
+SECoP Issue 4: Timeout (under discussion)
+=========================================
+
+For a SECoP client, in order to detect that a connection to a SECoP server is dead,
+'ping' messages can be sent. When no 'pong' message is received within a specified
+time, then the client can consider the connection as dead.
+
+If the server does not specify a the SEC node property 'timeout', the timeout
+is assumed to be 3s.
+
+Opinions
+--------
+
+On the meeting in Garching (2017-09-14) it was proposed to fix this a standard.
+
+
+Decision
+--------