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_1.rst

@@ -0,0 +1,27 @@
+SECoP Issue 1: About SECoP Issues
+=================================
+
+The idea behind SECoP Issues is to document properly what was proposed,
+what was discussed, what was decided and why it was decided.
+
+An issue might take different states:
+
+proposed
+--------
+
+A proposal should contain the motivation. As long as nobody else
+joins into a discussion, the state remains *proposed*
+
+under discussion
+----------------
+
+This state is kept until there is a decision taken.
+
+closed
+------
+
+After a decision the state is *closed*. The issue is not deleted,
+even if the decision was to not follow further the proposal.
+This is helpful if somebody later rises a similar issue.
+However, it should be possible to reopen an issue, if new
+arguments arise.