From e0796825982a80f0df05dedc11852a1cb765274e Mon Sep 17 00:00:00 2001 From: Martin Vrachev Date: Wed, 21 Apr 2021 19:14:25 +0300 Subject: [PATCH] Clarify that delegations are optional Nowhere in the spec, we clarify that "delegations" is an optional field in the targets metadata file. This is a possible reason why (at the time of writing this commit) in the TUF python reference implementation "delegations" is still a required field. Signed-off-by: Martin Vrachev --- tuf-spec.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/tuf-spec.md b/tuf-spec.md index 8a6dde1..83d3e6e 100644 --- a/tuf-spec.md +++ b/tuf-spec.md @@ -3,7 +3,7 @@ Title: The Update Framework Specification Shortname: TUF Status: LS Abstract: A framework for securing software update systems. -Date: 2020-12-11 +Date: 2021-04-21 Editor: Justin Cappos, NYU Editor: Trishank Karthik Kuppusamy, Datadog Editor: Joshua Lock, VMware @@ -16,7 +16,7 @@ Boilerplate: copyright no, conformance no Local Boilerplate: header yes Markup Shorthands: css no, markdown yes Metadata Include: This version off, Abstract off -Text Macro: VERSION 1.0.17 +Text Macro: VERSION 1.0.18 Note: We strive to make the specification easy to implement, so if you come @@ -976,7 +976,8 @@ as is described for the root.json file. TARGETPATH. The application may use this information to guide download decisions. -DELEGATIONS is an object whose format is the following: +DELEGATIONS is an optional object and if defined it has the following +format: 
 {