Normative references added.

Signed-off-by: Ulf Bjorkengren <ulfbjorkengren@geotab.com>

spec/VISSv2_Transport.html

@@ -103,7 +103,7 @@
       on control units within a vehicle's network. It exposes this
       information using a hierarchical tree like taxonomy defined in
       COVESA Vehicle Signal Specification (VSS). The service provides
-      this information in JSON format. The service may reside in the vehicle, 
+      this information in JSON format ([[RFC8259]]). The service may reside in the vehicle, 
       or on servers in the internet with information already brought off the vehicle.
       </p>
 
@@ -132,7 +132,8 @@ <h2>Introduction</h2>
       <p>This document describes the transport bindings of the Vehicle Information Service Specification, version 2. 
       The split between transport bindings and messaging layer specifications improves readability and simplifies 
       extending the specification to further transports in the future. 
-      This specification supports multiple transport bindings, the secure versions of HTTP, WebSocket, and MQTT.
+      This specification supports multiple transport bindings, the secure versions of HTTP ([[RFC9112]]),
+      WebSocket ([[RFC6455]]), and MQTT ([[https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html]]).
       </p>
     </section>
 
@@ -1552,7 +1553,7 @@ <h2>JSON Schema Definitions</h2>
           <p>
           The payload that is sent over the supported transport protocols SHALL use the JSON definitions in this appendix, 
           unless otherwise specified in the VISSv2 TRANSPORT specification.<br>
-          The definitions within this section describe the datatypes referenced within the JSON Schema for the VISSv2 WebSocket interfaces, 
+          The definitions within this section describe the datatypes referenced within the JSON Schema ([[https://json-schema.org/specification]]) for the VISSv2 WebSocket interfaces, 
           and for the VISSv2 HTTP payloads.
           </p>
               <pre><code>