3GPP TSG SA WG2 (System Architecture)	3GPP S2-99241
_________________		__________________________________________________________
Source: 	Nokia   	(Version 1.1) 

Title: 	Release 99 Security Features

Document for:	Discussion

Agenda Item: 	
		___________________________________________________________________________
Introduction
This document discusses the prioritization between different features in 3GPP specifications. Due to tight time scales a clear distinction between those features that are mandatory in Release 99 and other features is necessary. 
Discussion
On some markets, 3G service is scheduled for launch within two years.  Short timescales imply that two modes of specification work are needed in 3GPP. Rapid progress is necessary for those features that are mandatory in Release 99 specs. On the other hand, study of features which are included in future releases must proceed in parallel.

In the 3G Security Architecture specification draft TR S3.03 no distinction is made between the two classes of features. Some features are simply marked "for further study" which seems to indicate that they are aimed for later releases and not as mandatory features in Release 99. The group S2 should define clearly these two classes of features and state explicitly that separation between Release 99 work and long term work exists. Furthermore, the security group S3 should be asked to clarify how the distinction can be seen in the security architecture.  

One specific feature that must be included in Release 99 spec is ciphering of user and signallind data in radio access network. As ciphering algorithm requirements are not yet fully stabilised, the schedule for the algorithm design process seems to be very tight. In order to guarantee that user data and speech confidentiality is offered from the very beginning, it is essential that specifications for at least one ciphering algorithm are ready well in advance of the launching time. Hardware implementation and testing requirements imply that detailed description of the algorithm is available at least 18 months before the system is introduced to public use. Some backup plan is needed in order to minimise the risk that due to tight time schedule constraints 3G service begins with no user data or speech confidentiality at all. 

Proposal 

It is proposed that 

1)	S3 is asked to make it clear which security features that are to be developed for  inclusion in Release 99  

2) 	S2, with the guidance of S3,  as soon as possible clarifies in what functional entities (CN, RNC, Node B etc) and on what protocol level these features are to be implemented. 

3) 	S3 is asked to clarify the plans for exact schedule for the new ciphering algorithm. Furthermore, S3 should be asked to make a backup plan to minimise the risk that due to tight time constraints new ciphering algorithm cannot be delivered early enough.