Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spelling errors and markdown nits #8

Merged
merged 2 commits into from
May 22, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 6 additions & 9 deletions draft-ietf-scitt-scrapi.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,7 @@ normative:
RFC7231:
RFC3553:
RFC5785:
RFC8792:

IANA.params:
I-D.draft-ietf-scitt-architecture: SCITT-ARCH
Expand All @@ -64,7 +65,7 @@ informative:
--- abstract

This document describes a REST API that supports the normative requirements of the SCITT Architecture {{-SCITT-ARCH}}.
Optional key discovery and query interfaces are provided to support interoperability issues with Decentralized Identifiers, X509 Certificates and Artifact Reposistories.
Optional key discovery and query interfaces are provided to support interoperability issues with Decentralized Identifiers, X509 Certificates and Artifact Repositories.

--- middle

Expand Down Expand Up @@ -101,9 +102,9 @@ This specification uses "payload" as defined in {{RFC9052}}.
# Endpoints

Authentication is out of scope for this document.
If Authentication is not implemented, rate limiting or other denial of service mititations MUST be applied to enable anonymous access.
If Authentication is not implemented, rate limiting or other denial of service mitigations MUST be applied to enable anonymous access.

NOTE: '\' line wrapping per RFC 8792 in HTTP examples.
NOTE: '\' line wrapping per {{RFC8792}} in HTTP examples.

All messages are sent as HTTP GET or POST requests.

Expand Down Expand Up @@ -138,11 +139,10 @@ In the absence of this header field, this document does not specify a minimum.

The following HTTP endpoints are mandatory to implement to enable conformance to this specification.


### Transparency Configuration

Authentication SHOULD NOT be implemented for this endpoint.
This endpoint is used to discovery the capabilites of a transparency service implementing this specification.
This endpoint is used to discovery the capabilities of a transparency service implementing this specification.

Request:

Expand Down Expand Up @@ -345,7 +345,6 @@ TODO: other error codes

The following HTTP endpoints are optional to implement.


### Issue Statement

Authentication MUST be implemented for this endpoint.
Expand Down Expand Up @@ -557,7 +556,7 @@ Content-Type: application/json
This endpoint in inspired by {{-Nonce-Endpoint}}.

Authentication SHOULD NOT be implemented for this endpoint.
This endpoint is used to demonstrate proof of posession, which is the reason that authentication is not required.
This endpoint is used to demonstrate proof of possession, which is the reason that authentication is not required.
Client holding signed statements that require demonstrating proof of possession MUST use this endpoint to obtain a nonce.

Request:
Expand Down Expand Up @@ -714,7 +713,6 @@ Registry {{IANA.params}}, following the template in {{RFC3553}}:
Index value: No transformation needed.
~~~


## Well-Known URI for Issuers

The following value is requested to be registered in the "Well-Known URIs" registry (using the template from {{RFC5785}}):
Expand Down Expand Up @@ -763,4 +761,3 @@ To indicate that the content is a SCITT Receipt:
- Provisional registration? No

--- back

Loading