|
|
| 24.008 | 3252 | 1 | F | 17.1.0 | Rel-17 | Adding the RFC reference of PAP/CHAP protocol identifier contents and related abbreviations |
C1-210332
| agreed | CT1#127-bis-e | China Telecommu... |
CP-210131
| approved | CT#91-e | CT1 | 17.2.0 | PAP_CHAP |
|
|
|
| 24.008 | 3252 | - | F | 17.1.0 | Rel-17 | Adding the RFC reference of PAP/CHAP protocol identifier contents and related abbreviations |
C1-210218
| revised | CT1#127-bis-e | China Telecommu... |
| | | | | PAP_CHAP |
|
|
|
| 24.501 | 2941 | 1 | F | 17.0.0 | Rel-17 | Avoid including both PAP/CHAP and EAP identifiers in PDU session establishment request |
C1-207560
| agreed | CT1#127-e | ZTE / Joy |
CP-203205
| approved | CT#90-e | CT1 | 17.1.0 | 5GProtoc17, PAP_CHAP |
|
|
|
| 24.501 | 2941 | - | F | 17.0.0 | Rel-17 | Avoid including both PAP/CHAP and EAP identifiers in PDU session establishment request |
C1-207461
| revised | CT1#127-e | ZTE / Joy |
| | | | | PAP_CHAP, 5GProtoc17 |
|
|
|
| 24.501 | 2882 | 1 | F | 17.0.0 | Rel-17 | Adding the abbreviations of PAP/CHAP in TS 24.501 and fixing a minor grammatical error in the NOTE on PAP/CHAP |
C1-207704
| agreed | CT1#127-e | China Telecom C... |
CP-203205
| approved | CT#90-e | CT1 | 17.1.0 | PAP_CHAP |
|
|
|
| 24.501 | 2882 | - | B | 17.0.0 | Rel-17 | Adding the abbreviations of PAP/CHAP in TS 24.501 and fixing a minor grammatical error in the NOTE on PAP/CHAP |
C1-207262
| revised | CT1#127-e | China Telecom C... |
| | | | | PAP_CHAP |
|
|
|
| 24.501 | 2860 | 2 | B | 17.0.0 | Rel-17 | DNN setting in the 5GSM sublayer |
C1-207676
| agreed | CT1#127-e | Nokia, Nokia Sh... |
CP-203205
| approved | CT#90-e | CT1 | 17.1.0 | 5GProtoc17, PAP_CHAP |
|
|
|
| 24.501 | 2860 | 1 | F | 17.0.0 | Rel-17 | DNN setting in the 5GSM sublayer |
C1-207611
| revised | CT1#127-e | Nokia, Nokia Sh... |
| | | | | 5GProtoc17, PAP_CHAP |
|
|
|
| 24.501 | 2860 | - | F | 17.0.0 | Rel-17 | DNN setting in the 5GSM sublayer |
C1-207178
| revised | CT1#127-e | Nokia, Nokia Sh... |
| | | | | 5GProtoc17, PAP_CHAP |
|
|
|
| 24.501 | 2823 | - | B | 17.0.0 | Rel-17 | Adding the abbreviations of PAP/CHAP in TS 24.501 |
C1-207034
| withdrawn | CT1#127-e | China Telecom C... |
| | | | | PAP_CHAP |
|
|
|
| 24.501 | 2821 | - | B | 17.0.0 | Rel-17 | Inclusion of the DNN during the PDU session establishment when PAP/CHAP protocol is used |
C1-206640
| withdrawn | CT1#126-e | China Telecom C... |
| | | | | PAP_CHAP |
|
|
|
| 24.501 | 2660 | 2 | B | 17.0.0 | Rel-17 | Inclusion of the DNN during the PDU session establishment when PAP/CHAP protocol is used |
C1-207508
| merged | CT1#127-e | China Telecom C... |
| | | | | PAP_CHAP |
|
|
|
| 24.501 | 2660 | 1 | B | 17.0.0 | Rel-17 | Inclusion of the DNN during the PDU session establishment when PAP/CHAP protocol is used |
C1-206712
| revised | CT1#126-e | China Telecom C... |
| | | | | PAP_CHAP |
|
|
|
| 24.526 | 0103 | 1 | F | 17.0.0 | Rel-17 | DNN setting in the upper layers for PAP/CHAP |
C1-207678
| agreed | CT1#127-e | Nokia, Nokia Sh... |
CP-203205
| approved | CT#90-e | CT1 | 17.1.0 | PAP_CHAP |
|
|
|
| 24.526 | 0103 | - | F | 17.0.0 | Rel-17 | DNN setting in the upper layers for PAP/CHAP |
C1-207181
| revised | CT1#127-e | Nokia, Nokia Sh... |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0121 | - | F | 17.2.0 | Rel-17 | Correct PAP/CHAP description |
C3-214155
| agreed | CT3#117-e | Ericsson |
CP-212216
| approved | CT#93-e | CT3 | 17.3.0 | PAP_CHAP |
|
|
|
| 29.561 | 0091 | 1 | F | 17.0.0 | Rel-17 | Update clarification for PAP/CHAP in Diameter message flow |
C3-211617
| agreed | CT3#114-e | China Telecommu... |
CP-210214
| approved | CT#91-e | CT3 | 17.1.0 | PAP_CHAP |
|
|
|
| 29.561 | 0091 | - | F | 17.0.0 | Rel-17 | Update clarification for PAP/CHAP in Diameter message flow |
C3-211140
| revised | CT3#114-e | China Telecommu... |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0090 | 1 | F | 17.0.0 | Rel-17 | Update clarification for PAP/CHAP in RADIUS message flow |
C3-211616
| agreed | CT3#114-e | China Telecommu... |
CP-210214
| approved | CT#91-e | CT3 | 17.1.0 | PAP_CHAP |
|
|
|
| 29.561 | 0090 | - | F | 17.0.0 | Rel-17 | Update clarification for PAP/CHAP in RADIUS message flow |
C3-211139
| revised | CT3#114-e | China Telecommu... |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0087 | 1 | B | 17.0.0 | Rel-17 | 5GS interworking with EPS for PAP/CHAP in Diameter message flow |
C3-211502
| not pursued | CT3#114-e | Ericsson |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0087 | - | B | 17.0.0 | Rel-17 | 5GS interworking with EPS for PAP/CHAP in Diameter message flow |
C3-211088
| revised | CT3#114-e | Ericsson |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0086 | 1 | B | 17.0.0 | Rel-17 | 5GS interworking with EPS for PAP/CHAP in RADIUS message flow |
C3-211501
| not pursued | CT3#114-e | Ericsson |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0086 | - | B | 17.0.0 | Rel-17 | 5GS interworking with EPS for PAP/CHAP in RADIUS message flow |
C3-211086
| revised | CT3#114-e | Ericsson |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0085 | 1 | B | 17.0.0 | Rel-17 | 5GS interworking with EPS for IPv4IPv6 Non-transparent access using PAPCHAP |
C3-211500
| agreed | CT3#114-e | Ericsson |
CP-210214
| approved | CT#91-e | CT3 | 17.1.0 | PAP_CHAP |
|
|
|
| 29.561 | 0085 | - | B | 17.0.0 | Rel-17 | 5GS interworking with EPS for IPv4IPv6 Non-transparent access using PAPCHAP |
C3-211085
| revised | CT3#114-e | Ericsson |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0084 | 2 | F | 17.0.0 | Rel-17 | Update Descriptions for PAPCHAP in Diameter message flow |
C3-211601
| agreed | CT3#114-e | Ericsson, China... |
CP-210214
| approved | CT#91-e | CT3 | 17.1.0 | PAP_CHAP |
|
|
|
| 29.561 | 0084 | 1 | F | 17.0.0 | Rel-17 | Update Descriptions for PAPCHAP in Diameter message flow |
C3-210299
| agreed | CT3#113-e | Ericsson, China... |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0084 | - | F | 17.0.0 | Rel-17 | Update Descriptions for PAPCHAP in Diameter message flow |
C3-210248
| revised | CT3#113-e | Ericsson |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0083 | 2 | F | 17.0.0 | Rel-17 | Update Descriptions for PAPCHAP in RADIUS message flow |
C3-211600
| agreed | CT3#114-e | Ericsson, China... |
CP-210214
| approved | CT#91-e | CT3 | 17.1.0 | PAP_CHAP |
|
|
|
| 29.561 | 0083 | 1 | F | 17.0.0 | Rel-17 | Update Descriptions for PAPCHAP in RADIUS message flow |
C3-210298
| agreed | CT3#113-e | Ericsson, China... |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0083 | - | F | 17.0.0 | Rel-17 | Update Descriptions for PAPCHAP in RADIUS message flow |
C3-210247
| revised | CT3#113-e | Ericsson |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0074 | - | B | 16.5.0 | Rel-17 | Adding PAP/CHAP in RADIUS message flow(successful case) |
C3-205573
| withdrawn | CT3#112-e | China Telecom C... |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0062 | 1 | B | 16.5.0 | Rel-17 | Adding PAP/CHAP in Diameter message flow(successful case) |
C3-205577
| agreed | CT3#112-e | China Telecom C... |
CP-203134
| approved | CT#90-e | CT3 | 17.0.0 | PAP_CHAP |
|
|
|
| 29.561 | 0062 | - | B | 16.5.0 | Rel-17 | Adding PAP/CHAP in Diameter message flow(successful case) |
C3-205191
| revised | CT3#112-e | China Telecom C... |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0061 | 1 | B | 16.5.0 | Rel-17 | Adding PAP/CHAP in RADIUS message flow(successful case) |
C3-205575
| agreed | CT3#112-e | China Telecom C... |
CP-203134
| approved | CT#90-e | CT3 | 17.0.0 | PAP_CHAP |
|
|
|
| 29.561 | 0061 | - | B | 16.5.0 | Rel-17 | Adding PAP/CHAP in RADIUS message flow(successful case) |
C3-205184
| revised | CT3#112-e | China Telecom C... |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0058 | 1 | B | 16.5.0 | Rel-17 | Adding a note for IPv4/IPv6 Non-transparent access to DN using PAP/CHAP |
C3-205572
| agreed | CT3#112-e | China Telecom C... |
CP-203134
| approved | CT#90-e | CT3 | 17.0.0 | PAP_CHAP |
|
|
|
| 29.561 | 0058 | - | B | 16.5.0 | Rel-17 | Adding a note for IPv4/IPv6 Non-transparent access to DN using PAP/CHAP |
C3-205135
| revised | CT3#112-e | China Telecom C... |
| | | | | PAP_CHAP |
|
|
|
| 29.561 | 0057 | - | B | 16.5.0 | Rel-17 | Adding the abbreviations of PAP/CHAP in TS 29.561 |
C3-205132
| merged | CT3#112-e | China Telecom C... |
| | | | | PAP_CHAP |
|