29 Calling number verification using signature verification and attestation information

29.1653GPPInter-IMS Network to Network Interface (NNI)Release 18TS

Based on inter-operator agreement, "Calling number verification using signature verification and attestation information " functionality, as described in IETF RFC 8224 [206] and 3GPP TS 24.229 [5], may be supported over the II-NNI.

If the "Calling number verification using signature verification and attestation information" is supported, the related procedures in 3GPP TS 24.229 [5] shall be applied with the requirements in this clause.

A 200 (OK) response to a REGISTER request including a "g.3gpp.verstat" feature-capability indicator (defined in 3GPP TS 24.229 [5] clause 7.9A.11) and a "sip.607" feature-capability indicator (defined in IETF RFC 8197 [207]) in a Feature-Caps header field shall be supported at the roaming II-NNI.

An initial INVITE request and a MESSAGE request containing a P-Asserted-Identity header field and a From header field with a "verstat" tel URI parameter (defined in 3GPP TS 24.229 [5] clause 7.2A.20) in a tel URI or in a SIP URI with a "user=phone" parameter shall be supported at the roaming II-NNI.

An initial INVITE request and a MESSAGE request containing:

– an Identity header field (defined in IETF RFC 8224 [206]);

– an Attestation-Info header field (defined in 3GPP TS 24.229 [5] clause 7.2.18); and

– an Origination-id header field (defined in 3GPP TS 24.229 [5] clause 7.2.19),

shall be supported at the non-roaming II-NNI.

A 607 (Unwanted) response (defined in IETF RFC 8197 [207]) to an initial INVITE request and a MESSAGE request shall be supported at the II-NNI.

A Reason header field with a protocol value set to "SIP" and a "cause" header field parameter set to "607" in a BYE request shall be supported at the II-NNI.

A Reason header field with a protocol value set to "STIR", "cause" and "ppi" header field parameters (specified in IETF draft-ietf-stir-identity-header-errors-handling [220]) in a provisional response or a final response to an initial INVITE or a MESSAGE request shall be supported at the non-roaming II-NNI.

NOTE: Multiple Reason header fields with the protocol value set to "STIR" can be present in a provisional response or a final response to an initial INVITE or a MESSAGE request.