Skip to content

Commit

Permalink
Clarify intent statements for mandatory endpoints (#28)
Browse files Browse the repository at this point in the history 
Issue #19

Signed-off-by: Jon Geater <jon.geater@rkvst.com>
Co-authored-by: Jon Geater <jon.geater@rkvst.com>
  • Loading branch information
@JAG-UK
JAG-UK and Jon Geater authored Aug 20, 2024
1 parent 0b9c753 commit 888fcfb
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion draft-ietf-scitt-scrapi.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down Expand Up @@ -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:
Expand Down

0 comments on commit 888fcfb

Please sign in to comment.