Signing and Verification Request/Response Body Formats

[kpolitz]

We are currently reviewing and confirming the intent of original 3GPP Annex V contributors on body formats. The reference APIs support the second body format (without the redundant "signingRequest" for the /signing endpoint). As we investigate, please feel free to share your feedback on this item. Thanks!

{
“signingRequest”: {
"attest": "A",
"orig": {
"tn": "sip:+17035550001@example.com"
},
"dest": {
"tn": [
"sip:+15715550000@example.com"
]
},
"iat": 1671467335,
"origid": "2088448c-718e-4930-be5d-0ec9b25d2f00"
}
}

and not simply:

{
"attest": "A",
"orig": {
"tn": "sip:+17035550001@example.com"
},
"dest": {
"tn": [
"sip:+15715550000@example.com"
]
},
"iat": 1671467335,
"origid": "2088448c-718e-4930-be5d-0ec9b25d2f00"
}

[di-shi]

I would prefer the atis10k82 format, but both of them work for me.

[jchilds-rbbn]

I would also prefer the ATIS format

[kpolitz]

Folks, we are going to start making the updates to better follow the original ATIS 10K82. Will let folks know when available for testing. Thanks for the feedback.

[kpolitz]

We have added and deployed "signingRequest", "signingResponse", "verificationRequest" and "verificationResponse" body formats on 3/10/23. PLease test and confirm.