From 888fcfba5e5d1f785043645b47f71d64a90a5b31 Mon Sep 17 00:00:00 2001 From: Jon Geater Date: Tue, 20 Aug 2024 15:34:24 +0100 Subject: [PATCH] Clarify intent statements for mandatory endpoints (#28) Issue #19 Signed-off-by: Jon Geater Co-authored-by: Jon Geater --- draft-ietf-scitt-scrapi.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/draft-ietf-scitt-scrapi.md b/draft-ietf-scitt-scrapi.md index b76ceff..a0b78bf 100644 --- a/draft-ietf-scitt-scrapi.md +++ b/draft-ietf-scitt-scrapi.md @@ -138,7 +138,8 @@ The following HTTP endpoints are mandatory to implement to enable conformance to ### Transparency Configuration Authentication SHOULD NOT be implemented for this endpoint. -This endpoint is used to discovery the capabilities of a transparency service implementing this specification. + +This endpoint is used to discover the capabilities and current configuration of a transparency service implementing this specification. Request: @@ -201,6 +202,8 @@ Fields that are not understood MUST be ignored. Authentication MAY be implemented for this endpoint. See notes on detached payloads below. +This endpoint is used to register a Signed Statement with a Transparency Service. + The following is a non-normative example of a HTTP request to register a Signed Statement: Request: