Etsi stylesheet (V 0)



Yüklə 1,91 Mb.
səhifə4/18
tarix27.12.2018
ölçüsü1,91 Mb.
#87108
1   2   3   4   5   6   7   8   9   ...   18

7.2.1 Key hierarchy

7.2.1.1 Miscellaneous

S3-180124 Discussion on deleting KSEAF from key hierarchy

Type: discussion For: Endorsement
33.501 v.. Source: Huawei, Hisilicon


Discussion:

Qualcomm and DT disagreed. China Mobile supported this contribution.

Nokia commented that they assume that SA2 doesn’t want a standalone SEAF.

ORANGE: send an LS to SA2, as we are speculating what they are doing with SEAF and AMF in phase two.

The Chair asked for a show of hands for this document:

In favour of 124:

China Mobile, Ericsson, Huawei,ZTE,Nokia

Opposed to 124:

DT, Qualcomm, Docomo, BT, KPN,NCSC, NEC

This had to be taken offline for conversations with SA2.

It was finally noted, may be considered later in phase two.

Decision: The document was noted.



S3-180076 Resolving editors notes in clause on key hierarchy

Type: pCR For: Approval
33.501 v0.5.0 Source: Nokia


Decision: The document was revised to S3-180447.



S3-180447 Resolving editors notes in clause on key hierarchy

Type: pCR For: Approval
33.501 v0.5.0 Source: Nokia

(Replaces S3-180076)



Decision: The document was approved.



S3-180138 Clean up the EN in 6.2.1

Type: pCR For: Approval
33.501 v0.6.0 Source: Huawei, Hisilicon


Decision: The document was revised to S3-180448.



S3-180448 Clean up the EN in 6.2.1

Type: pCR For: Approval
33.501 v0.6.0 Source: Huawei, Hisilicon

(Replaces S3-180138)



Decision: The document was approved.



S3-180221 Adding details of K’AMF to clause 6.2.1

Type: pCR For: Approval
33.501 v0.6.0 Source: NEC Telecom MODUS Ltd.


Abstract:

This pCR proposes to add details of the key, K’AMF, to clause 6.2.1 Key Hierarchy of TS 33.501.



Decision: The document was revised to S3-180449.



S3-180449 Adding details of K’AMF to clause 6.2.1

Type: pCR For: Approval
33.501 v0.6.0 Source: NEC Telecom MODUS Ltd.

(Replaces S3-180221)



Decision: The document was approved.



S3-180174 pCR for overview of 5G security architecture

Type: pCR For: Approval
33.501 v0.7.0 Source: Huawei, Hisilicon, China Mobile, CATR, ZTE


Discussion:

Vodafone: it's not readable in black and white.

Nokia: not a clear representation and it's misleading. Dragan(IDEMIA) agreed.

Huawei: we are just showing the main points.

The figure was not clear enough for the companies.

Nokia clarified that there was a similar picture in 33.401.

The consensus was that such figure could be welcome but some discussions were needed to agree on a figure.

Decision: The document was noted.



S3-180176 Modification of Kausf

Type: pCR For: Approval
33.501 v0.7.0 Source: Huawei, Hisilicon,


Decision: The document was merged.



S3-180178 Key distribution and key derivation scheme

Type: pCR For: Approval
33.501 v0.7.0 Source: Huawei, Hisilicon,


Discussion:

Docomo: the note is a definition and it needs to be checked if the definition applies to the whole spec.

There were some issues as well with the figure 6.2.2-1.

Decision: The document was revised to S3-180450.



S3-180450 Key distribution and key derivation scheme

Type: pCR For: Approval
33.501 v0.7.0 Source: Huawei, Hisilicon,

(Replaces S3-180178)



Decision: The document was approved.



S3-180308 Assignment of KSIamf

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


Decision: The document was merged.



S3-180292 On feature set relevance for independent SEAF deployment

Type: discussion For: Approval
33.501 v.. Source: Ericsson


Decision: The document was withdrawn.




7.2.1.2 Editorials

7.2.2 Key derivation

7.2.2.1 Key derivation mobility related
7.2.2.2 Key derivation NAS related

S3-180021 Handling of user-related keys – key setting

Type: pCR For: Approval
33.501 v0.6.0 Source: ZTE Corporation


Abstract:

This paper proposes text for section about key setting



Decision: The document was merged.



S3-180053 Adding context on key setting

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


Decision: The document was merged.




7.2.2.3 Key derivation AS related
7.2.2.4 Miscellaneous

S3-180098 Clause 6.2.3 Handling of user related keys

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


Abstract:

Propose new text for empty clause



Decision: The document was merged.



S3-180323 Storage of key material in the UE

Type: pCR For: Approval
33.501 v0.6.0 Source: Gemalto, IDEMIA


Abstract:

Storage of key material in the UE



Decision: The document was revised to S3-180452.



S3-180452 Storage of key material in the UE

Type: pCR For: Approval
33.501 v0.6.0 Source: Gemalto, IDEMIA,Qualcomm

(Replaces S3-180323)



Decision: The document was approved.



S3-180257 Keys in the UE

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


Decision: The document was merged.



S3-180322 Handling of 5G security contexts in the UE

Type: pCR For: Approval
33.501 v0.6.0 Source: Gemalto, IDEMIA


Abstract:

Handling of 5G security contexts in the UE



Discussion:

Vodafone replace UICC with USIM.

ORANGE: The same with the related contributions that will merge.

Decision: The document was merged.




7.2.2.5 Editorials


Yüklə 1,91 Mb.

Dostları ilə paylaş:
1   2   3   4   5   6   7   8   9   ...   18




Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©muhaz.org 2024
rəhbərliyinə müraciət

gir | qeydiyyatdan keç
    Ana səhifə


yükləyin