Content for TS 29.573 Word version: 17.2.0
A OpenAPI Specification
B Examples of N32-f Encoding
C End to end call flows when SEPP is on path
D Withdrawn API versions
$ Change history
A (Normative) OpenAPI Specification
A.1 General
A.2 N32 Handshake API Word‑p. 59
A.3 JOSE Protected Message Forwarding API on N32-f Word‑p. 65
A.4 SEPP Telescopic FQDN Mapping API |R16| Word‑p. 69
B Examples of N32-f Encoding Word‑p. 70
B.1 General
B.2 Input Message Containing No Binary Part
B.3 Input Message Containing Multipart Binary Part Word‑p. 71
C End to end call flows when SEPP is on path Word‑p. 72
C.1 General
C.2 TLS security between SEPPs Word‑p. 73
C.2.1 When http URI scheme is used
C.2.1.1 General |R16|
C.2.1.2 Without TLS protection between NF and SEPP and with TLS security without the 3gpp-Sbi-Target-apiRoot header used over N32f |R16|
C.2.1.3 Without TLS protection between NF and SEPP and with TLS security with the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| Word‑p. 76
C.2.2 When https URI scheme is used Word‑p. 77
C.2.2.1 General |R16|
C.2.2.2 With TLS protection between NF and SEPP relying on telescopic FQDN, and TLS security without the 3gpp-Sbi-Target-apiRoot header used over N32f |R16|
C.2.2.3 With TLS protection between NF and SEPP relying on 3gpp-Sbi-Target-apiRoot header, and TLS security without the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| Word‑p. 81
C.2.2.4 With TLS protection between NF and SEPP relying on telescopic FQDN, and TLS security with the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| Word‑p. 84
C.2.2.5 With TLS protection between NF and SEPP relying on 3gpp-Sbi-Target-apiRoot header, and TLS security with the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| Word‑p. 87
C.3 Application Layer Security between SEPPs Word‑p. 89
D Withdrawn API versions Word‑p. 99
$ Change history Word‑p. 101
