From 45ca4d6b1cdd15671f7a8615d1c37470542660bd Mon Sep 17 00:00:00 2001 From: steve lasker Date: Fri, 3 Jan 2025 09:45:54 -0800 Subject: [PATCH] Merge cleanup from github UX Signed-off-by: steve lasker --- draft-ietf-scitt-scrapi.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/draft-ietf-scitt-scrapi.md b/draft-ietf-scitt-scrapi.md index bdb6258..f5318b1 100644 --- a/draft-ietf-scitt-scrapi.md +++ b/draft-ietf-scitt-scrapi.md @@ -289,7 +289,8 @@ In cases where the registration request is accepted but the Transparency Service If the `OperationID` is a valid URL, it MAY be included as a `Location` header in the HTTP response. -Transparency Services do not guarantee retention of operation IDs for a period of time or the entirety of its lifecycle. A Transparency MAY delete operation records and some operation IDs lookups MAY return error XYZ at one time even though they were valid in the past. +Transparency Services do not guarantee retention of operation IDs for a period of time or the entirety of its lifecycle. +A Transparency MAY delete operation records and some operation IDs lookups MAY return error XYZ at one time even though they were valid in the past. The length of validity of the `OperationID` is Transparency Service specific, but at a minimum, the Transparency Service MUST maintain a record of every running or successful operation until at least one client has fetched the completed Receipt. The Transparency Service MAY include a `Retry-After` header in the HTTP response to help with polling.