|
| 33.122 | 0075 | - | F | 18.3.0 | Rel-18 | Alignment on resource definition |
S3-242206
| not pursued | SA3#116 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0074 | 1 | F | 18.3.0 | Rel-18 | Corrections and removing token claim related EN |
S3-242385
| agreed | SA3#116 | Huawei, HiSilic... |
SP-240655
| approved | SA#104 | SA WG3 | 18.4.0 | SNAAPPY |
|
|
| 33.122 | 0074 | - | F | 18.3.0 | Rel-18 | Corrections and removing token claim related EN |
S3-241965
| revised | SA3#116 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0073 | - | F | 18.3.0 | Rel-18 | Addressing EN on claim versus scope |
S3-241859
| merged | SA3#116 | Nokia |
| | | | | SNAAPPY |
|
|
| 33.122 | 0072 | - | F | 18.3.0 | Rel-18 | Resource owner function |
S3-241858
| agreed | SA3#116 | Nokia |
SP-240655
| approved | SA#104 | SA WG3 | 18.4.0 | SNAAPPY |
|
|
| 33.122 | 0071 | - | F | 18.2.0 | Rel-18 | Resolve ENs related to API invoker ID mapping |
S3-240795
| not pursued | SA3#115 | Xiaomi |
| | | | | SNAAPPY |
|
|
| 33.122 | 0070 | - | F | 18.2.0 | Rel-18 | Resolve EN related to authorization request or token request |
S3-240794
| agreed | SA3#115 | Xiaomi |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
| 33.122 | 0069 | - | F | 18.2.0 | Rel-18 | Resolve ENs related to token claims |
S3-240793
| merged | SA3#115 | Xiaomi |
| | | | | SNAAPPY |
|
|
| 33.122 | 0068 | 1 | F | 18.2.0 | Rel-18 | Add revocation procedure for RNAA-related tokens |
S3-240850
| agreed | SA3#115 | Xiaomi |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
| 33.122 | 0068 | - | F | 18.2.0 | Rel-18 | Add revocation procedure for RNAA-related tokens |
S3-240792
| revised | SA3#115 | Xiaomi |
| | | | | SNAAPPY |
|
|
| 33.122 | 0067 | 1 | F | 18.2.0 | Rel-18 | Update for CAPIF 8 |
S3-240851
| agreed | SA3#115 | Xiaomi |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
| 33.122 | 0067 | - | F | 18.2.0 | Rel-18 | Update for CAPIF 8 |
S3-240791
| revised | SA3#115 | Xiaomi |
| | | | | SNAAPPY |
|
|
| 33.122 | 0065 | - | F | 18.2.0 | Rel-18 | Details for RNAA token |
S3-240636
| merged | SA3#115 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0064 | - | F | 18.2.0 | Rel-18 | Security Negotiation for RNAA |
S3-240635
| merged | SA3#115 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0063 | - | F | 18.2.0 | Rel-18 | SNAAPPY - Update to RNAA functional security model description |
S3-240625
| agreed | SA3#115 | Nokia, Nokia Sh... |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
| 33.122 | 0062 | 1 | F | 18.2.0 | Rel-18 | Alignment of 33.122 for RNAA |
S3-241039
| agreed | SA3#115 | NTT DOCOMO |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
| 33.122 | 0062 | - | F | 18.2.0 | Rel-18 | Alignment of 33.122 for RNAA |
S3-240475
| revised | SA3#115 | NTT DOCOMO |
| | | | | SNAAPPY |
|
|
| 33.122 | 0061 | 1 | F | 18.2.0 | Rel-18 | Clarification to flow selection for RNAA |
S3-240849
| agreed | SA3#115 | Huawei, HiSilicon |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
| 33.122 | 0061 | - | F | 18.2.0 | Rel-18 | Clarification to flow selection for RNAA |
S3-240427
| revised | SA3#115 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0060 | 1 | F | 18.2.0 | Rel-18 | Access token profile for Annex C |
S3-240852
| agreed | SA3#115 | Huawei, HiSilicon |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
| 33.122 | 0060 | - | F | 18.2.0 | Rel-18 | Access token profile for Annex C |
S3-240426
| revised | SA3#115 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0059 | - | F | 18.2.0 | Rel-18 | Correction on authentication and authorization for RNAA |
S3-240425
| agreed | SA3#115 | Huawei, HiSilicon |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
| 33.122 | 0058 | - | F | 18.2.0 | Rel-18 | Revocation procedures invoked by API invoker |
S3-240424
| merged | SA3#115 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0057 | - | F | 18.2.0 | Rel-18 | Revocation procedure invoked by resource owner client |
S3-240423
| merged | SA3#115 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0056 | 1 | F | 18.1.0 | Rel-18 | Resolving stage 2 editor's notes |
S3-234961
| not pursued | SA3#113 | NTT DOCOMO |
| | | | | SNAAPPY |
|
|
| 33.122 | 0056 | - | F | 18.1.0 | Rel-18 | resolving RNA stage 2 editor's notes |
S3-234945
| revised | SA3#113 | NTT DOCOMO INC. |
| | | | | SNAAPPY |
|
|
| 33.122 | 0055 | - | C | 18.1.0 | Rel-18 | Resolve EN related to API invoker ID and GPSI |
S3-234911
| not pursued | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
| 33.122 | 0054 | - | F | 18.1.0 | Rel-18 | Update for authorization revocation procedure for RNAA |
S3-234910
| not pursued | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
| 33.122 | 0053 | - | D | 18.1.0 | Rel-18 | Streamline the Editor's Notes for RNAA |
S3-234909
| not pursued | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
| 33.122 | 0052 | 1 | F | 18.1.0 | Rel-18 | Resolve EN related to authorization flow |
S3-235114
| agreed | SA3#113 | Xiaomi,Nokia, N... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
| 33.122 | 0052 | - | F | 18.1.0 | Rel-18 | Resolve EN related to authorization flow |
S3-234908
| revised | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
| 33.122 | 0051 | 1 | F | 18.1.0 | Rel-18 | Clarification for CAPIF-8 |
S3-235111
| agreed | SA3#113 | Xiaomi,Nokia, N... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
| 33.122 | 0051 | - | F | 18.1.0 | Rel-18 | Clarification for CAPIF-8 |
S3-234907
| revised | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
| 33.122 | 0050 | 1 | F | 18.1.0 | Rel-18 | Detailed functional security model description for support of RNAA |
S3-235104
| agreed | SA3#113 | Nokia, Nokia Sh... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
| 33.122 | 0050 | - | F | 18.1.0 | Rel-18 | Detailed functional security model description for support of RNAA |
S3-234868
| revised | SA3#113 | Nokia, Nokia Sh... |
| | | | | SNAAPPY |
|
|
| 33.122 | 0048 | - | F | 18.1.0 | Rel-18 | Optimization in the authorization code flow usage |
S3-234790
| not pursued | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0047 | 1 | F | 18.1.0 | Rel-18 | Clarification on the scope of the Rel-18 RNAA specification |
S3-235060
| withdrawn | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0047 | - | F | 18.1.0 | Rel-18 | Clarification on the scope of the Rel-18 RNAA specification |
S3-234787
| not pursued | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0046 | 1 | F | 18.1.0 | Rel-18 | Clarification on resource owner ID |
S3-235059
| agreed | SA3#113 | Ericsson |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
| 33.122 | 0046 | - | F | 18.1.0 | Rel-18 | Clarification on resource owner ID |
S3-234786
| revised | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0045 | 1 | F | 18.1.0 | Rel-18 | Optimizations for accessing own resources |
S3-235065
| withdrawn | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0045 | - | F | 18.1.0 | Rel-18 | Optimizations for accessing own resources |
S3-234785
| not pursued | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0044 | 1 | F | 18.1.0 | Rel-18 | Identification of RNAA token |
S3-235064
| withdrawn | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0044 | - | F | 18.1.0 | Rel-18 | Identification of RNAA token |
S3-234784
| merged | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
| 33.122 | 0043 | - | F | 18.1.0 | Rel-18 | Refreshing Token for RNAA |
S3-234622
| merged | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0042 | - | F | 18.1.0 | Rel-18 | Obtaining Tokens Procedure for RNAA |
S3-234621
| merged | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0041 | 1 | F | 18.1.0 | Rel-18 | Access token profile for RNAA |
S3-235115
| agreed | SA3#113 | Huawei, HiSilic... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
| 33.122 | 0041 | - | F | 18.1.0 | Rel-18 | Access token profile for RNAA |
S3-234620
| revised | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0040 | - | F | 18.1.0 | Rel-18 | Security negotiation for RNAA |
S3-234619
| merged | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0039 | 1 | F | 18.1.0 | Rel-18 | Correction on authentication and authorization for RNAA |
S3-235113
| agreed | SA3#113 | Huawei, HiSilic... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
| 33.122 | 0039 | - | F | 18.1.0 | Rel-18 | Correction on authentication and authorization for RNAA |
S3-234618
| revised | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0038 | - | F | 18.1.0 | Rel-18 | Revocation procedure invoked by resource owner client |
S3-234617
| not pursued | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0037 | - | F | 18.1.0 | Rel-18 | Revocation procedures invoked by API invoker |
S3-234616
| not pursued | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
| 33.122 | 0036 | - | B | 18.0.0 | Rel-18 | CR on security for resource owner aware northbound access to APIs |
S3-234360
| agreed | SA3#112 | NTT DOCOMO INC. |
SP-230907
| approved | SA#101 | SA WG3 | 18.1.0 | SNAAPPY |
|