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.

Sign up for GitHub

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

corrected two typographical errors #13

Merged
merged 1 commit into from
Mar 5, 2025
Merged

corrected two typographical errors #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions specifications.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Each Group can have multiple TAs.

Every Peer in a Group **MUST** accept the same TA(s).

The TA **SHOULD** validate a Peers identity, i.e. the TA **MUST** preform Organization Validation.
The TA **SHOULD** validate a Peers identity, i.e. the TA **MUST** perform Organization Validation.

### TLS configuration {#tls_configuration}

Expand Down Expand Up @@ -391,7 +391,7 @@ The payload of the JWT:
Not before [section 4.1.5](https://www.rfc-editor.org/rfc/rfc7519#section-4.1.5) of [[RFC7519]]
* *cnf(object):*
* *x5t#S256(string):*
The thumbprint of the certificate that is allowed ot use the access token. [section 3.1] of [[RFC8705]]
The thumbprint of the certificate that is allowed to use the access token. [section 3.1] of [[RFC8705]]
* *act(object):*
* *sub(string):*
The ID of the Peer connecting to the Service on behalf of another Peer. The field `grant.data.delegator.peer_ID` of the DelegatedServiceConnectionGrant.
Expand Down