The 5G Standard

3GPP TDocs (written contributions) at meeting

Meeting: S3-33 - 2004-05-10 to 2004-05-14, Beijing

meeting id: S3-33 (click id for more info on this meeting)

Click on the Tdoc to open its file.

TDoc Title Source Remarks
S3‑040202 - - -
S3‑040203 - - -
S3‑040204 - - -
S3‑040205 - - -
S3‑040206 - - -
S3‑040207 - - -
S3‑040208 - - -
S3‑040209 - - -
S3‑040210 - - -
S3‑040211 - - -
S3‑040212 - - -
S3‑040213 - - -
S3‑040214 - - -
S3‑040215 - - -
S3‑040216 - - -
S3‑040217 - - -
S3‑040218 - - -
S3‑040219 - - -
S3‑040220 - - -
S3‑040221 - - -
S3‑040222 - - -
S3‑040223 - - -
S3‑040224 - - -
S3‑040225 - - -
S3‑040226 - - -
S3‑040227 - - -
S3‑040228 - - -
S3‑040229 - - -
S3‑040230 - - -
S3‑040231 - - -
S3‑040232 - - -
S3‑040233 - - -
S3‑040234 - - -
S3‑040235 - - -
S3‑040236 - - -
S3‑040237 - - -
S3‑040238 - - -
S3‑040239 - - -
S3‑040240 - - -
S3‑040241 - - -
S3‑040242 - - -
S3‑040243 - - -
S3‑040244 - - -
S3‑040245 - - -
S3‑040246 - - -
S3‑040247 - - -
S3‑040248 - - -
S3‑040249 - - -
S3‑040250 - - -
S3‑040251 - - -
S3‑040252 - - -
S3‑040253 - - -
S3‑040254 - - -
S3‑040255 - - -
S3‑040256 - - -
S3‑040257 - - -
S3‑040258 - - -
S3‑040259 - - -
S3‑040260 - - -
S3‑040261 - - -
S3‑040262 - - -
S3‑040263 - - -
S3‑040264 - - -
S3‑040265 - - -
S3‑040266 Removal of inconsistencies regarding SEG actions during IKE phase 1 - -
S3‑040267 Removal of unnecessary restriction on CA path length - -
S3‑040268 - - -
S3‑040269 - - -
S3‑040270 - - -
S3‑040271 - - -
S3‑040272 - - -
S3‑040273 Handling of key sets at inter-system change - -
S3‑040274 Handling of key sets at inter-system change - -
S3‑040275 - - -
S3‑040276 - - -
S3‑040277 - - -
S3‑040278 - - -
S3‑040279 - - -
S3‑040280 - - -
S3‑040281 - - -
S3‑040282 - - -
S3‑040283 - - -
S3‑040284 - - -
S3‑040285 - - -
S3‑040286 - - -
S3‑040287 - - -
S3‑040288 - - -
S3‑040289 - - -
S3‑040290 - - -
S3‑040291 Diffie-Hellman groups in NDS/IP - -
S3‑040292 - - -
S3‑040293 - - -
S3‑040294 - - -
S3‑040295 - - -
S3‑040296 Correction of ‘Extended key usage’ extension in SEG Certificate profile - -
S3‑040297 - - -
S3‑040298 - - -
S3‑040299 - - -
S3‑040300 - - -
S3‑040301 Clarification on delivery of IRI and CC - -
S3‑040302 - - -
S3‑040303 - - -
S3‑040304 - - -
S3‑040305 Correction on interception identities in multi-media domain - -
S3‑040306 WGS 84 coordinates length correction - -
S3‑040307 WGS 84 coordinates length correction - -
S3‑040308 - - -
S3‑040309 - - -
S3‑040310 - - -
S3‑040311 CR offering alignment to ETSI TS 101 671 - -
S3‑040312 - - -
S3‑040313 Additional text for Definition and Acronym section - -
S3‑040314 - - -
S3‑040315 - - -
S3‑040316 - - -
S3‑040317 - - -
S3‑040318 - - -
S3‑040319 - - -
S3‑040320 - - -
S3‑040321 - - -
S3‑040322 - - -
S3‑040323 - - -
S3‑040324 - - -
S3‑040325 - - -
S3‑040326 - - -
S3‑040327 - - -
S3‑040328 - - -
S3‑040329 - - -
S3‑040330 - - -
S3‑040331 - - -
S3‑040332 - - -
S3‑040333 Removal of Annex A - -
S3‑040334 - - -
S3‑040335 - - -
S3‑040336 - - -
S3‑040337 - - -
S3‑040338 - - -
S3‑040339 - - -
S3‑040340 - - -
S3‑040341 - - -
S3‑040342 - - -
S3‑040343 - - -
S3‑040344 - - -
S3‑040345 - - -
S3‑040346 - - -
S3‑040347 - - -
S3‑040348 - - -
S3‑040349 - - -
S3‑040350 - - -
S3‑040351 - - -
S3‑040352 - - -
S3‑040353 - - -
S3‑040354 - - -
S3‑040355 - - -
S3‑040356 - - -
S3‑040357 - - -
S3‑040358 - - -
S3‑040359 - - -
S3‑040360 - - -
S3‑040361 - - -
S3‑040362 - - -
S3‑040363 - - -
S3‑040364 - - -
S3‑040365 - - -
S3‑040366 - - -
S3‑040367 - - -
S3‑040368 - - -
S3‑040369 - - -
S3‑040370 - - -
S3‑040371 - - -
S3‑040372 - - -
S3‑040373 - - -
S3‑040374 - - -
S3‑040375 - - -
S3‑040376 - - -
S3‑040377 - - -
S3‑040378 - - -
S3‑040379 - - -
S3‑040380 - - -
S3‑040381 - - -
S3‑040382 Reply LS on Security of the Management Plane S3 -
S3‑040383 Reply LS on Potential Security issues relating to use of AT Commands to access UICC S3 -
S3‑040384 LS on new ITU-T Recommendations for secure mobile end-to-end data communication, X.1121 and X.1122 S3 -
S3‑040385 LS on GUP security status in SA3 and on collaboration of 3GPP and Liberty Alliance Project S3 -
S3‑040386 - - -
S3‑040387 - - -
S3‑040388 - - -
S3‑040389 - - -
S3‑040390 - - -
S3‑040391 - - -
S3‑040392 - - -
S3‑040393 - - -
S3‑040394 - - -
S3‑040395 Profiling of IKEv2 and ESP for NAT traversal - -
S3‑040396 LS on non-compliance to IMS security S3 -
S3‑040397 Correction on IMS confidentiality protection - -
S3‑040398 - - -
S3‑040399 - - -
S3‑040400 Clarification on Authentication re-attempt parameter - -
S3‑040401 - - -
S3‑040402 Correction of inconsistencies in AK computation for re-synchronisation - -
S3‑040403 - - -
S3‑040404 Reply LS on the use of Kc in the Uplink TDOA location method S3 -
S3‑040405 - - -
S3‑040406 - - -
S3‑040407 NAF remove the security associations - -
S3‑040408 - - -
S3‑040409 - - -
S3‑040410 Removal of editors notes on Transaction Identifiers - -
S3‑040411 - - -
S3‑040412 - - -
S3‑040413 Introduction of a UICC-based Generic Bootstrapping Architecture - -
S3‑040414 Editorial corrections to TS 33.220 - -
S3‑040415 - - -
S3‑040416 Sending of temporary identities from WLAN UE - -
S3‑040417 - - -
S3‑040418 Extension of IKEv2 and IPsec profiles - -
S3‑040419 - - -
S3‑040420 Support of EAP SIM and AKA in AAA server and WLAN UE - -
S3‑040421 - - -
S3‑040422 - - -
S3‑040423 - - -
S3‑040424 - - -
S3‑040425 Reply LS (from SA3) to T3-040329 (S3-040370) on VGCS and VBS security S3 -
S3‑040426 - - -
S3‑040427 - - -
S3‑040428 - - -
S3‑040429 SIP Privacy mechanism when IMS interworking with non-IMS (foreign) network - -
S3‑040430 Reply LS to N4-040247 (S3-040208) on use of authentication re-attempt IE S3 -
S3‑040431 LS on removal of A5/2 from handsets. S3 -
S3‑040432 Support for NAF in visited network - -
S3‑040433 Editorial changes and clarifications to TS 33.220 - -
S3‑040434 Multiple key derivation mandatory - -
S3‑040435 NAF’s public hostname verification - -
S3‑040436 Reply LS on "e-authentication and key set change during inter-system handover" S3 -
S3‑040437 Introduction of UE split alternative 2 in TS 33.234 - -
S3‑040438 Re-authentication failure notification to HSS - -
S3‑040439 Identity request procedure clarification - -
S3‑040440 WLAN mechanism to allow restrictions on simultaneous sessions - -
S3‑040441 Requirement on keeping WLAN access keys independent from 2G/3G access keys stored in USIM - -
S3‑040442 Response to LS (S2-041630 = S3-040364) on moving security requirements to SA3 MBMS TS S3 -
S3‑040443 LS on Protection of streaming and download MBMS data S3 -
S3‑040444 LS on MBMS MSK key update S3 -
S3‑040445 LS on MBMS key Management S3 -
S3‑040446 Liaison Statement on VGCS and VBS security S3 -
S3‑040447 Liaison Statement on VGCS and VBS security S3 -
S3‑040448 Response to LS (S3-040268) on key derivation for the Generic Bootstrapping Architecture S3 -
S3‑040449 - - -

page generated from database: 2024-04-22 07:58:53

Get news. Get knowledge. Get involved
Get news.
Get knowledge.
Get involved.
Image
The 5G Standard
3GPP General Enquiries:
info@3gpp.org 


Connect:

Quick Links