Fixup RFC references

Author: birkenfeld

protocol/specification/datainfo.rst

@@ -310,7 +310,7 @@ Binary large object: ``blob``
 
 .. rubric:: Transport
 
-As a single-line base-64 (see :RFC:`4648`) encoded JSON string.
+As a single-line base-64 (see :rfc:`4648`) encoded JSON string.
 
 Example: ``"AA=="`` (a single, zero valued byte)
 
@@ -460,7 +460,7 @@ As a JSON object containing the following items:
     List of the actual length of each dimension in the data.
 
 ``"blob"``
-    The data, encoded as a single-line base64 (see :RFC:`4648`) encoded
+    The data, encoded as a single-line base64 (see :rfc:`4648`) encoded
     JSON-string.
 
 Example: ``{"len": [2, 3], "blob": "AACAPwAAAEAAAEBAAACAQAAAoEAAAMBA"}``

protocol/specification/discovery.rst

@@ -76,7 +76,4 @@ Implementation hints
   necessary.
 
 
-See also `SECoP RFC 5`_.
-
-
-.. _SECoP RFC 5: https://github.com/SampleEnvironment/SECoP/blob/master/rfcs/RFC-005-udp-discovery.rst
+See also :secop-rfc:`005-udp-discovery`.

protocol/specification/future.rst

@@ -75,5 +75,5 @@ representation may be developed.  This will essentially keep the structure of
 the messages, but replace the components of a message with shorter, binary
 representations.
 
-Good candidates for this are CBOR (see :RFC:`7049`) and MessagePack (see
+Good candidates for this are CBOR (see :rfc:`7049`) and MessagePack (see
 https://msgpack.org/).

protocol/specification/messages.rst

@@ -7,7 +7,8 @@ carriage return character (ASCII 13, ``"\r"``), which must be ignored.
 
 A message starts with an action keyword, followed optionally by one space and a
 specifier (not containing spaces), followed optionally by one space and a JSON
-value called data, which contains all remaining characters in the line.
+value (see :rfc:`8259`) called data, which contains all remaining characters in
+the line.
 
 The specifier consists of a module identifier, and for most actions, followed by
 a colon as separator and an accessible identifier.  In special cases

protocol/specification/reports.rst

@@ -70,7 +70,7 @@ Values are transferred as a JSON value.
     If an implementation uses a library which can not (de-)serialize all JSON
     values, the implementation can add square brackets around a JSON value,
     decode it and take the first element of the result.  When encoding, the
-    reverse action might be used as a workaround.  See also :RFC:`7493`.
+    reverse action might be used as a workaround.  See also :rfc:`7493`.
 
 
 .. _qualifiers:

protocol/specification/transport.rst

@@ -101,10 +101,10 @@ SECoP over WebSockets
 Since browser (i.e. HTML+JavaScript) based human interface solutions are more
 and more important, and JavaScript lacks traditional socket based APIs,
 exchanging raw SECoP messages is not an option.  The best alternative is
-WebSockets (RFC :rfc:`6455`), which are a relatively overhead-free way of
+WebSockets (:rfc:`6455`), which are a relatively overhead-free way of
 exchanging messages between two endpoints in an arbitrary pattern.
 
-See also `SECoP RFC 7`_.
+See also :secop-rfc:`007-websockets`.
 
 Implementation in a SEC node
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -160,6 +160,3 @@ they come in.  A very minimal example in JavaScript::
 
     // Whenever needed, send messages, for example:
     ws.send('change mod:param 42');
-
-
-.. _SECoP RFC 7: https://github.com/SampleEnvironment/SECoP/blob/master/rfcs/RFC-007-websockets.rst