move new RFCs to 1xx number, move RFC process doc to 000

Author: birkenfeld

issues/README.rst

@@ -3,7 +3,7 @@ Note
 
 SECoP Issues have been replaced by the RFC process, which is described in
 `RFC 1
-<https://github.com/SampleEnvironment/SECoP/blob/master/rfcs/RFC-001-RFC-process.rst>`_.
+<https://github.com/SampleEnvironment/SECoP/blob/master/rfcs/RFC-000-RFC-process.rst>`_.
 
 If there is renewed interest in one of the remaining open issues, please
 migrate to an RFC before restarting discussion.

protocol/specification/changes.rst

@@ -51,11 +51,11 @@ loss of functionality.
 - The :ref:`matrix <matrix>` data type has been specified for datainfo.
 
 - The `AcquisitionController`, `AcquisitionChannel` and `Acquisition` interface
-  classes have been specified (:ref:`rfc-006`).
+  classes have been specified (:ref:`rfc-106`).
 
-- The UDP discovery protocol has been specified (:ref:`rfc-005`).
+- The UDP discovery protocol has been specified (:ref:`rfc-105`).
 
-- Optional SECoP transport over WebSockets has been specified (:ref:`rfc-007`).
+- Optional SECoP transport over WebSockets has been specified (:ref:`rfc-107`).
 
 
 Version 1.1

protocol/specification/classes.rst

@@ -83,7 +83,7 @@ The following terms are relevant here:
   quantity.  An acquisition can acquire data for one or more channels at the
   same time.
 
-See also :secop-rfc:`006-acquisition`.
+See also :ref:`rfc-106`.
 
 .. baseclass:: AcquisitionController
 

protocol/specification/discovery.rst

@@ -80,4 +80,4 @@ Implementation hints
   necessary.
 
 
-See also :ref:`rfc-005`.
+See also :ref:`rfc-105`.

protocol/specification/transport.rst

@@ -104,7 +104,7 @@ exchanging raw SECoP messages is not an option.  The best alternative is
 WebSockets (:rfc:`6455`), which are a relatively overhead-free way of
 exchanging messages between two endpoints in an arbitrary pattern.
 
-See also :ref:`rfc-007`.
+See also :ref:`rfc-107`.
 
 Implementation in a SEC node
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

rfcs/RFC-001-RFC-process.rst rfcs/RFC-000-rfc-process.rstrfcs/RFC-001-RFC-process.rst renamed to rfcs/RFC-000-rfc-process.rst

@@ -62,7 +62,7 @@ How to contribute
 Here we lay out the steps to follow to change the specification.
 
 - If you do not have a concrete idea, come talk to us to flesh it out.
-- Copy the RFC-000-template.rst file and fill in the details. You can add
+- Copy the RFC-template.rst file and fill in the details. You can add
   sections freely, but try to fill out all the provided ones.
 - Take the next free number and add it to the template file.  Renumbering might
   happen when the PR is merged.