-
P-CSCF and the terminal
agree on the set of parameters to establish two IPSec security associations
between them as specified in RFC 3329 and 3GPP 33.203.
-
Access security includes
authentication of users and the network, and protection of traffic
between IMS terminals and the network.
-
P-CSCF allows activation
and de-activation of access security.
-
Both P-CSCF and S-CSCF
support coexistence of IMS and non-IMS/Early IMS endpoints.
They support various authentication methods on the same network
element.
-
Both UDP and TCP are
supported on the same SA pair.
-
P-CSCF supports recovery
of the security association.
-
P-CSCF supports ESP
transport mode for
clients that are not behind NAT and supports ESP
tunnel mode for
clients behind NAT.
-
UDP encapsulation
of ESP in tunnel mode is supported.
-
P-CSCF supports authentication
algorithm HMAC-MD5-96 and HMAC-SHA-1-96, and encryption algorithm
DES EDE3 CBC, as specified in RFC 2451, and AES CBC, as specified in
RFC 3602 with 128-bit key.
As per 3GPP 33.203,
P-CSCF supports negotiation of the following SA parameters between UE
and P-CSCF using SIP:
-
-
-
SPI (Security Parameter
Index)
The following security
parameters shall not be negotiated:
-
-
-
Key length of integrity
key (The length of the integrity key IKESP depends on the integrity
algorithm. It is 128 bits for HMAC MD5 96 and 160 bits for HMAC
SHA 1 96.)
-
Key length of encryption
key
-
Two pairs of (unilateral)
security associations (SAs) are established between the UE and the P-CSCF.
The subscriber may have several IMPUs associated with one IMPI.
These may belong to the same or different service profiles. Only
two pairs of SAs shall be active between the UE and the P-CSCF.
These two pairs of SAs shall be updated when a new successful authentication
of the subscriber has occurred.
P-CSCF monitors the
expiry time of registrations without an authentication and if necessary increases
the lifetime of SAs created by the last successful authentication
such that it will expire shortly after the registration timer in
the message. P-CSCF deletes any SA whose lifetime is exceeded. The
P-CSCF deletes all SAs it holds that are associated with a particular
IMPI once all the associated IMPUs are de-registered.
The SIP application
at the P CSCF checks upon receipt of a protected REGISTER message that
the source IP address in the packet headers coincide with the UE's
IP address inserted in the Via header of the protected REGISTER
message. If the Via header does not explicitly contain the UE's
IP address, but rather a symbolic name, then the P-CSCF first resolves
the symbolic name using DNS to obtain an IP address.
For each unidirectional
SA which has been established and has not expired, the SIP application
at the P-CSCF stores the following data: (UE_IP_address,
UE_protected_port, P-CSCF_protected_port,
SPI, IMPI, IMPU1, ... , IMPUn, lifetime, mode) in an “SA_table”.
The pair (UE_protected_port, P-CSCF_protected_port)
equals either (port_uc, port_ps) or (port_us, port_pc).
P-CSCF does not accept
registration attempts from UEs with the same address and protected server
port in order to ensure unambiguous addressing of SIP messages sent
towards the UE, using the protected server port.
P-CSCF checks that,
for any one IMPI, no more than six SAs per direction are stored
at any one time. If these checks are unsuccessful, the registration
is aborted and an error message is sent to the UE.
The SIP application
at the P CSCF checks upon receipt of an initial REGISTER message
or a re-REGISTER message that the pair (UE_IP_address,
UE_protected_client_port), where the UE_IP_address
is the source IP address in the packet header and the protected
client port is sent as part of the security mode set-up procedure,
has not yet been associated with entries in the “SA_table”.
The P-CSCF associates
two ports, called port_ps and port_pc, with each
pair of security associations established in an authenticated registration.
The ports port_ps and port_pc are different from
the standard SIP ports 5060 and 5061. No unprotected messages shall
be sent from or received on the ports port_ps and port_pc.
From a security point of view, unprotected messages may be received
on any port which is different from the ports port_ps and
port_pc. The number of the ports port_ps and port_pc
are communicated to the UE during the security mode set-up procedure/SIP
registration procedure.