Etsi stylesheet (V 0)

7.2.6 Security context

7.2.6.1 Multiple registrations

S3-180259 pCR: Multiple Registrations in different PLMNs using K_AUSF (Updated)

Type: pCR For: Approval
33.501 v0.6.0 Source: Qualcomm Incorporated

Discussion:

Discussed together with 284.

Ericsson: the whole solution is really complex and totally new, for being optional.

Ericsson: this is an optimization that can be used later in phase two. Huawei and Intel supported this view.

Decision: The document was noted.

7.2.6.2 KDF agility

7.2.6.3 Intra-serving network handling

7.2.6.4 UE handling

S3-180313 New UE requirement to store two 5G security contexts in TS 33.501

Type: pCR For: Approval
33.501 v0.6.0 Source: Ericsson, Qualcomm Incorporated

Discussion:

Gemalto: why is the storage at the power-off? It’s different from the EPS.

Qualcomm: it includes the de-registration, we can clarify it.

Gemalto: CT6 defines the different types of services: support of 5G security context and others. Qualcomm disagreed.

Dragan (IDEMIA): we need to stay general, not to focus on 5G security context. We need to mention 5G security services.

It was agreed to reword this sentence in the revision and text from 33.401.

Decision: The document was revised to S3-180445.



S3-180445 New UE requirement to store two 5G security contexts in TS 33.501

Type: pCR For: Approval
33.501 v0.6.0 Source: Ericsson, Qualcomm Incorporated

(Replaces S3-180313)

Decision: The document was approved.

7.2.6.5 Emergency call

7.2.6.6 Miscellaneous

S3-180055 Clarification on 5G security context

Type: pCR For: Approval
33.501 v0.6.0 Source: CATT

Decision: The document was revised to S3-180446.



S3-180446 Clarification on 5G security context

Type: pCR For: Approval
33.501 v0.6.0 Source: CATT

(Replaces S3-180055)

Decision: The document was approved.

7.2.6.7 Editorials

7.2.7 Visibility and Configurability

7.2.7.1 Miscellaneous

S3-180333 Discussion of security visibility

Type: discussion For: Endorsement
Source: NTT DOCOMO INC.

Discussion:

BT: API design is not out of scope.

Docomo: better an API written in the language of the applications than a 3GPP API.

BT: find security features that need to be indicated; e.g. type of authentication, privacy and so on. We cannot do this at this meeting.

Docomo clarified that this is visibility of security features from the UE side. Configurability is done elsewhere.

Huawei: details of what should be there, will come next meeting.

ORANGE supported the contribution, also commented that if there is no support of this there will be no visibility at all.

Ericsson: this doesn’t have implications on the network architecture, should we do this in phase two?

Qualcomm wasn't sure about the practical value of proposal 2.

DT supported this contribution.

The group had a general understanding of this issue but was not in the situation to endorse the whole paper.

Decision: The document was noted.



S3-180200 Clarification of security visibility

Type: pCR For: Approval
33.501 v0.6.0 Source: LG Electronics

Decision: The document was revised to S3-180453.



S3-180453 Clarification of security visibility

Type: pCR For: Approval
33.501 v0.6.0 Source: LG Electronics

(Replaces S3-180200)

Decision: The document was approved.



S3-180085 Authorization of SN by UE - was S3-173125

Type: pCR For: Decision
33.501 v0.5.0 Source: Nokia, LG Electronics

(Replaces S3-173125)

Discussion:

ORANGE: in the case of roaming, if the UE has selected ciphering as compulsory and the visited network has no ciphering, the UE will not connect to any network. This is hard to sell.

AT&T: tell the user that they are going to connect in a non-secure way. He can have the choice.

Decision: The document was revised to S3-180454.



S3-180454 Authorization of SN by UE - was S3-173125

Type: pCR For: Approval
33.501 v0.5.0 Source: Nokia, LG Electronics

(Replaces S3-180085)

Decision: The document was approved.



S3-180086 Visibility and configurability supporting serving network authorization - was S3-173126

Type: pCR For: Approval
33.501 v0.5.0 Source: Nokia, LG Electronics

(Replaces S3-173126)

Discussion:

Ericsson: why having a list of countries in the USIM? Countries split and change all the time.

Docomo: countries seem to be reasonably stable, it's not so often that they change.

Vodafone: this has been in the SIM card since Rel-5. Country codes and network names are already recorded there. This has been used regularly. I don’t agree with having the user turning it off.

Decision: The document was merged.

7.2.7.2 Editorials