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

Jump to bottom

Update Network layer protection guidance in CAEP Interoperability Profile #213

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update Network layer protection guidance in CAEP Interoperability Profile #213

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cfc1908
Update Network layer protection guidance in CAEP Interoperability Pro…
Oct 8, 2024
536eef4
Use TLS version independent guidance for SSF transmitter
Oct 8, 2024
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 openid-caep-interoperability-profile-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ normative:
ins: A. Tulshibagwale
name: Atul Tulshibagwale
org: SGNL
RFC7525: # Recommendations for Secure Use of Transport Layer Security
RFC9325: # Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
RFC6125: # Representation and Verification of Domain-Based Application Service Identity within Internet Public Key
# Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
RFC6750: # The OAuth 2.0 Authorization Framework: Bearer Token Usage
Expand Down Expand Up @@ -125,7 +125,7 @@ The following requirements are common across all use-cases defined in this docum

## Network layer protection
* The SSF transmitter MUST offer TLS protected endpoints and MUST establish connections to other servers using TLS. TLS connections MUST be set up to use TLS version 1.2 or later.
* When using TLS 1.2, follow the recommendations for Secure Use of Transport Layer Security in [RFC7525]{{RFC7525}}.
* The SSF transmitter MUST follow the recommendations for Secure Use of Transport Layer Security in [RFC9325]{{RFC9325}}.
* The SSF receiver MUST perform a TLS server certificate signature checks, chain of trust validations, expiry and revocation status checks before calling the SSF transmitter APIs, as per [RFC6125]{{RFC6125}}.

## CAEP specification version
Expand Down