From fa044945cc40911972a43e539a1e0541a0ee0f5e Mon Sep 17 00:00:00 2001 From: Marina Moore Date: Tue, 19 Mar 2024 12:26:30 +0100 Subject: [PATCH] Move to deferred Signed-off-by: Marina Moore --- README.md | 5 ++++- tap14.md | 4 ++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9b20ad79..bcb4ef49 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,6 @@ * [TAP 10: Remove native support for compressed metadata](tap10.md) * [TAP 11: Using POUFs for Interoperability](tap11.md) * [TAP 12: Improving keyid flexibility](tap12.md) -* [TAP 14: Managing TUF Versions](tap14.md) * [TAP 15: Succinct hashed bin delegations](tap15.md) ## Draft @@ -21,6 +20,10 @@ * [TAP 16: Snapshot Merkle Trees](tap16.md) * [TAP 17: Remove Signature Wrapper from the TUF Specification](tap17.md) +## Deferred + +* [TAP 14: Managing TUF Versions](tap14.md) + ## Rejected * [TAP 5: Setting URLs for roles in the root metadata file](tap5.md) diff --git a/tap14.md b/tap14.md index c6a415ef..fe9c1035 100644 --- a/tap14.md +++ b/tap14.md @@ -3,7 +3,7 @@ * Version: 1 * Last-Modified: 13-October-2022 * Author: Marina Moore, Justin Cappos -* Status: Accepted +* Status: Deferred * Content-Type: text/markdown * Created: 19-December-2018 @@ -292,7 +292,7 @@ where `MAJOR_VERSION` is the integer representing a supported major version For backwards compatability, version 1 should be assumed to be in the top-level repository with no directory named 1. `ROOT_FILENAME` is the name of the root metadata file in the new specification version. `ROOT_DIGEST` is the digest of the new root metadata file. `VERSION_PATH` is the path to the directory for this version. In many cases, this will match the specification version, ie "2/". -`FEATURES_STRING` is a string for the features supported in this version. This string may be used to include an API version for a particular implementation, or to indicate which features in a new specification version are supported. This field MAY be empty, but if it is used, the client MUST ensure that they support the features used. A combination of the specification version and features string will be used to determine which version the client should use. +`FEATURES_STRING` is a string for the features supported in this version. This string may be used to include an API version for a particular implementation, or to indicate which features in a new specification version are supported. This field MAY be empty, but if it is used, the client MUST ensure that they support the features used. A combination of the specification version and features string will be used to determine which version the client should use. All entries in `supported-versions` will be in priority order so that a client will use the last specification version and feature combination that they support.