The 5G Standard

3GPP TDocs (written contributions) at meeting

Meeting: S3-40 - 2005-09-12 to 2005-09-15, Portoroz

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

Click on the Tdoc to open its file.

TDoc Title Source Remarks
S3‑050484 - - imported from 3GU
S3‑050485 - - imported from 3GU
S3‑050486 - - imported from 3GU
S3‑050487 - - imported from 3GU
S3‑050488 - - imported from 3GU
S3‑050489 - - imported from 3GU
S3‑050490 - - imported from 3GU
S3‑050491 - - imported from 3GU
S3‑050492 - - imported from 3GU
S3‑050493 - - imported from 3GU
S3‑050494 - - imported from 3GU
S3‑050495 - - imported from 3GU
S3‑050496 - - imported from 3GU
S3‑050497 - - imported from 3GU
S3‑050498 - - imported from 3GU
S3‑050499 - - imported from 3GU
S3‑050500 - - imported from 3GU
S3‑050501 - - imported from 3GU
S3‑050502 - - imported from 3GU
S3‑050503 - - imported from 3GU
S3‑050504 - - imported from 3GU
S3‑050505 - - imported from 3GU
S3‑050506 - - imported from 3GU
S3‑050507 - - imported from 3GU
S3‑050508 - - imported from 3GU
S3‑050509 - - imported from 3GU
S3‑050510 - - imported from 3GU
S3‑050511 - - imported from 3GU
S3‑050512 - - imported from 3GU
S3‑050513 - - imported from 3GU
S3‑050514 - - imported from 3GU
S3‑050515 - - imported from 3GU
S3‑050516 - - imported from 3GU
S3‑050517 - - imported from 3GU
S3‑050518 - - imported from 3GU
S3‑050519 - - imported from 3GU
S3‑050520 - - imported from 3GU
S3‑050521 - - imported from 3GU
S3‑050522 - - imported from 3GU
S3‑050523 - - imported from 3GU
S3‑050524 - - imported from 3GU
S3‑050525 - - imported from 3GU
S3‑050526 - - imported from 3GU
S3‑050527 - - imported from 3GU
S3‑050528 - - imported from 3GU
S3‑050529 - - imported from 3GU
S3‑050530 - - imported from 3GU
S3‑050531 - - imported from 3GU
S3‑050532 - - imported from 3GU
S3‑050533 - - imported from 3GU
S3‑050534 - - imported from 3GU
S3‑050535 - - imported from 3GU
S3‑050536 - - imported from 3GU
S3‑050537 - - imported from 3GU
S3‑050538 - - imported from 3GU
S3‑050539 - - imported from 3GU
S3‑050540 - - imported from 3GU
S3‑050541 - - imported from 3GU
S3‑050542 - - imported from 3GU
S3‑050543 - - imported from 3GU
S3‑050544 - - imported from 3GU
S3‑050545 - - imported from 3GU
S3‑050546 - - imported from 3GU
S3‑050547 - - imported from 3GU
S3‑050548 - - imported from 3GU
S3‑050549 - - imported from 3GU
S3‑050550 - - imported from 3GU
S3‑050551 - - imported from 3GU
S3‑050552 - - imported from 3GU
S3‑050553 - - imported from 3GU
S3‑050554 - - imported from 3GU
S3‑050555 - - imported from 3GU
S3‑050556 - - imported from 3GU
S3‑050557 - - imported from 3GU
S3‑050558 - - imported from 3GU
S3‑050559 - - imported from 3GU
S3‑050560 - - imported from 3GU
S3‑050561 - - imported from 3GU
S3‑050562 - - imported from 3GU
S3‑050563 - - imported from 3GU
S3‑050564 - - imported from 3GU
S3‑050565 - - imported from 3GU
S3‑050566 - - imported from 3GU
S3‑050567 - - imported from 3GU
S3‑050568 - - imported from 3GU
S3‑050569 - - imported from 3GU
S3‑050570 - - imported from 3GU
S3‑050571 - - imported from 3GU
S3‑050572 - - imported from 3GU
S3‑050573 - - imported from 3GU
S3‑050574 - - imported from 3GU
S3‑050575 - - imported from 3GU
S3‑050576 - - imported from 3GU
S3‑050577 - - imported from 3GU
S3‑050578 - - imported from 3GU
S3‑050579 - - imported from 3GU
S3‑050580 - - imported from 3GU
S3‑050581 - - imported from 3GU
S3‑050582 - - imported from 3GU
S3‑050583 - - imported from 3GU
S3‑050584 - - imported from 3GU
S3‑050585 - - imported from 3GU
S3‑050586 - - imported from 3GU
S3‑050587 - - imported from 3GU
S3‑050588 - - imported from 3GU
S3‑050589 - - imported from 3GU
S3‑050590 - - imported from 3GU
S3‑050591 - - imported from 3GU
S3‑050592 - - imported from 3GU
S3‑050593 - - -
S3‑050594 - - -
S3‑050595 - - -
S3‑050596 - - -
S3‑050597 - - -
S3‑050598 - - -
S3‑050599 - - -
S3‑050600 - - -
S3‑050601 - - -
S3‑050602 Reply LS on Security Requirements for Long Term Evolved RAN/3GPP System Architecture Evolution S3 -
S3‑050603 Reply LS on TLS security requirements when incorporating draft-ietf-sip-history-info S3 -
S3‑050604 Correction of handling of IMPUs by the P-CSCF - -
S3‑050605 Correction of handling of IMPUs by the P-CSCF - -
S3‑050606 - - -
S3‑050607 Correction of an Inconsistency Between Annex H and RFC3329 - -
S3‑050608 - - -
S3‑050609 Correction of figure 1 - -
S3‑050610 Correction of handling of IP addresses by the S-CSCF at de-registration - -
S3‑050611 - - -
S3‑050612 Ut interface protection - -
S3‑050613 Clarify the use of IMSI-derved IMPU in registration procedures - -
S3‑050614 - - -
S3‑050615 - - -
S3‑050616 - - -
S3‑050617 - - -
S3‑050618 - - -
S3‑050619 Keystatus sent by CN node in Security Mode Command - -
S3‑050620 Correction of sample code - -
S3‑050621 Kasumi roundfunction, correction of formula - -
S3‑050622 Incorrect usage of COUNT-I in security mode set-up procedure - -
S3‑050623 Clarify ciphering for A5 algorithms that do not produce bit after bit output. - -
S3‑050625 - - -
S3‑050626 LS on Key establishment between a UICC and a terminal S3 -
S3‑050627 LS on Key establishment between a UICC and a terminal S3 -
S3‑050629 - - -
S3‑050630 Addition of the Dz interface for multiple HSS deployments - -
S3‑050631 Addition of the Dz interface for multiple HSS deployments - -
S3‑050632 Providing Ua-security protocol based key separation - -
S3‑050633 Providing Ua-security protocol based key separation - -
S3‑050634 - - -
S3‑050635 - - -
S3‑050636 Removing requirement to send authentication vectors in batches - -
S3‑050637 Removing requirement to send authentication vectors in batches - -
S3‑050638 Clarification concerning input parameter encoding for GBA_U NAF derivation procedure - -
S3‑050639 Clarification concerning input parameter encoding for GBA_U NAF derivation procedure - -
S3‑050640 - - -
S3‑050641 - - -
S3‑050642 - - -
S3‑050643 - - -
S3‑050644 - - -
S3‑050645 - - -
S3‑050647 Support for simultaneous WLAN direct IP access sessions - -
S3‑050648 LS support for simultaneous WLAN direct IP access sessions S3 -
S3‑050649 Clarification on obtaining Remote IP address during Tunnel Establishment Procedure - -
S3‑050650 Reply LS on Talker Priority Uplink for Shared Channel Option S3 -
S3‑050651 - - -
S3‑050652 Normative annex on 2G GBA - -
S3‑050653 - - -
S3‑050654 - - -
S3‑050655 S-CSCF reselection - -
S3‑050656 Profiling of IKEv2 to support Re-keying of IPsec SAs and IKE SAs - -
S3‑050657 Separation of authentication and authorization in WLAN 3GPP IP access - -
S3‑050658 IDs and encoding of MIKEY messages - -
S3‑050659 Moving the EXT payload - -
S3‑050660 Handling of re-sent MSK messages - -
S3‑050661 Clarification of MSK ID in service announcement - -
S3‑050662 More than one FQDN for key management - -
S3‑050663 NAF Id alignment with TS 33.220 - -
S3‑050664 Key Domain ID in MSK request - -
S3‑050665 Identifying correct MIME types, correcting various editorials and wrong references - -
S3‑050666 - - -
S3‑050667 Interworking between UE and S-CSCF - -
S3‑050668 LS on S-CSCF re-selection in early IMS S3 -
S3‑050669 Normative annex on 2G GBA - -
S3‑050670 LS on Ua Security Protocol Identifier and Organisation Identifier in Generic Bootstrapping Architecture S3 -
S3‑050671 Correction of handling of IMPUs by the P-CSCF - -
S3‑050672 Correction of handling of IMPUs by the P-CSCF - -
S3‑050673 Addition of reference to early IMS security TR - -

page generated from database: 2024-03-25 09:25:51

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