ConfirmationDataResponse may be defined incompletely

[alexandru-dinu]

Currently, ConfirmationDataResponse is defined as:

ConfirmationDataResponse:
  type: object
    properties:
      authResult:
        $ref: '#/components/schemas/AuthResult'
      supi:
        $ref: 'CommonData.yaml#/components/schemas/Supi'
      required:
        - authResult

However, in TS 33.501 [1], for 5G AKA procedure (step 12), it is mentioned that

If the authentication was successful, the KSEAF shall be sent to the SEAF in the Nausf_UEAuthentication_Authenticate Response

This response body contains a ConfirmationDataResponse object, but there's no kSeaf field.
I think kSeaf should also be added as an optional property in the definition:

ConfirmationDataResponse:
  type: object
    properties:
      authResult:
        $ref: '#/components/schemas/AuthResult'
      supi:
        $ref: 'CommonData.yaml#/components/schemas/Supi'
      kSeaf:
        $ref: '#/components/schemas/Kseaf'
      required:
        - authResult

[jdegre]

Thanks for reporting, @alexandru-dinu. Yes, you are right. This has been corrected in the official 3GPP specs in the last CT4 meeting in October (see C4-187479), and the correction will show up in the public specs after the next CT plenary meeting in December.

[alexandru-dinu]

I understand, thank you for the reply.