Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 33.828  Word version:  11.1.0

Top   Top   None   None   Next
1…   4…

 

1  Scopep. 7

The present document studies use cases, requirements and candidate solutions for protecting the IMS media plane against eavesdropping and undetected modification. Currently IMS media protection relies on security provided at the lower layers. With Common IMS, it has become possible to use IMS over a wide variety of access networks which provide varying levels of security and in some cases no security at all. It is therefore desirable to study solutions for securing the IMS media plane in a uniform manner across all access networks. Furthermore, media transport in the core network, although generally less vulnerable than in the access network, may also be realised in varying ways with different levels of security. Therefore, the present document also studies solutions for end-to-end protection of IMS media.
Up

2  Referencesp. 7

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: Vocabulary for 3GPP Specifications
[2]
RFC 5479:  Requirements and Analysis of Media Security Management Protocols
[3]
TS 23.228: IP Multimedia Subsystem (IMS); Stage 2
[4]
TS 26.234: Transparent end-to-end Packet-switched Streaming Service (PSS)
[5]
RFC 4975:  The Message Session Relay Protocol (MSRP)
[6]
RFC 4976:  Relay Extensions for the Message Sessions Relay Protocol (MSRP)
[7]
RFC 4346:  The Transport Layer Security (TLS) Protocol Version 1.1
[8]
RFC 4279:  Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)
[9]
RFC 3851:  Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1
[10]
RFC 4347:  Datagram Transport Layer Security
[11]
draft-ietf-avt-dtls-srtp-06:  Datagram Transport Layer Security (DTLS) Extension to Establish Keys for Secure Real-time Transport Protocol (SRTP) (work in progress)
[12]
draft-ietf-sip-dtls-srtp-framework-05:  Framework for Establishing an SRTP Security Context using DTLS (work in progress)
[13]
RFC 4474:  Enhancements for Authenticated Identity Management in the Session Initiation Protocol
[14]
RFC 4916:  Connected Identity in the Session Initiation Protocol (SIP)
[15]
E.-J. Goh, D. Boneh, P. Golle, B. Pinkas, "The Design and Implementation of Protocol-Based Hidden Key Recovery", 2003; http://crypto.stanford.edu/~pgolle/papers/escrow.pdf
[16]
draft-wing-sipping-srtp-key-04:  Secure Media Recording and Transcoding with the Session Initiation Protocol (work in progress, expired)
[17]
draft-wing-avt-dtls-srtp-key-transport-02:  DTLS-SRTP Key Transport (work in progress)
[18]
TR 23.894: System enhancements for the use of IMS services in local breakout and optimal routing of media
[19]
TS 33.210: 3G security: Network Domain Security (NDS): IP network layer security
[20]
draft-cakulev-mikey-ibake-00:  Identity-Based Mode of Key Distribution in Multimedia Internet KEYing (work in progress)
Up

3  Definitions, symbols and abbreviationsp. 8

3.1  Definitionsp. 8

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Application layer security:
In the context of the present document, application layer security is security applied on payload data and it is independent of the transport mechanism used.
Channel security:
In the context of the present document, channel security is security applied on data and it is dependent of used transport mechanism or transport identities.
IMS User Equipment:
User equipment used for IMS media communications over access networks. The presence of the UICC in this equipment is optional when the equipment does not support any 3GPP access technology. In the case where the user equipment is used for IMS media communications over any 3GPP access network, the IMS User Equipment shall contain a UICC.
Up

3.2  Symbolsp. 8

For the purposes of the present document, the following symbols apply:

3.3  Abbreviationsp. 8

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
NSPS
National Security and Public Safety
QoE
Quality of Experience

Up   Top   ToC