spec: 1.0.0: mention supported TAPs

Author: SantiagoTorres

tuf-spec.md

@@ -210,6 +210,24 @@ repo](https://github.com/theupdateframework/specification/issues).
       * The root of trust must not rely on external PKI.  That is, no authority will
       be derived from keys outside of the framework.
 
+    - **1.5.4. TUF Augmentation Proposal support**
+
+      * This version (1.0.0) of the specification adheres to the following TAPS:
+
+        - [TAP 3](https://github.com/theupdateframework/taps/blob/master/tap3.md): 
+            Multi Role Delegations
+        - [TAP 4](https://github.com/theupdateframework/taps/blob/master/tap4.md):
+            Multiple Repository Consensus on entrusted targets
+        - [TAP 6](https://github.com/theupdateframework/taps/blob/master/tap6.md):
+            Include specification version in metadata
+        - [TAP 9](https://github.com/theupdateframework/taps/blob/master/tap9.md):
+            Mandatory Metadata signing schemes
+        - [Tap 10](https://github.com/theupdateframework/taps/blob/master/tap10.md):
+           Remove native support for compressed metadata
+
+	   Implementations compliant with this version (1.0.0) of the specification
+       must also comply with the TAPs mentioned above.
+
 ## **2. System overview**
 
    The framework ultimately provides a secure method of obtaining trusted