Report of sa wg2 meeting #114

Discussion and conclusion:

Telecom Italia commented that it is not clear how the new container is passed to the upper layer. Huawei replied that this could be added. Qualcomm asked for clarification of the Reason for Change and Consequences if not approved. This was left for further off-line discussion and revised in TD S2 160556 which was reviewed. Some corrections were needed and this was revised in TD S2 160884 which was approved.

TD S2 160020 LS from SA WG3: LS on Security requirements for Public Safety Discovery messages. (SA WG3) (Revision of TD S2 154135).
Abstract: SA WG3 have progressed their work on Public Safety Discovery security and wish to bring a couple of issues to the attention of SA WG2 and CT WG1.
Firstly, SA WG3 has decided that the security information used to protect Relay Discovery messages will be associated with the Relay Service Code. In effect the Relay Service Code is used to help identity the security parameters needed by the receiving UE to process the discovery message. SA WG3 have noted that the Relay Service code is not included in the Relay Discovery Additional Information message. Hence SA WG3 would like to ask SA WG2 and CT WG1 to ensure that it is included.
Secondly, SA WG3 are specifying the security functions to protect the various Public Safety Discovery messages. SA WG3 have observed that it would simplify the specification of these function if there was one overall format for the Public Safety Discovery Message, e.g. 8 bits of Message type | 184 bits of Message | 32 bit MIC | 8 bit of UTC-based Counter LSB SA WG3 believe that keeping to such a format would be possible by including 'spare' or 'undefined' IEs.
Keeping to such an overall format would means that SA WG3 would not need to specify different truncations of the security functions based on the exact contents of the discovery message.
Therefore SA WG3 would like to ask CT WG1 to consider keeping the overall format of Public Safety Discovery message fixed.
Action: Please include the Relay Service Code in the Relay Discovery Additional Information message.

Convenors comment: Related CR drafted in late TD S2 160087.