Documents for CN1 – SA2 joint meeting on SIP	Cyan cells indicate an allocated but not available tdoc	Yellow cells indicate an available but not yet treated tdoc	
Agenda item	Agenda item title	Tdoc 3GPP N1-00	Title	Spec.	Source	Result	
1	Opening
tuesday 28.11.2000					Planning to open at 9:00	
			Make calls for IPRs		MCC	Disclosure of IPRs is done by reference to the tdoc	
			Agenda		Chairman		
							
2	Reports
tuesday 28.11.2000						
			SA2 meeting report		MCC	
Only SIP related decisions to be presented for information for the meeting.	
			CN1 #14 meeting report		MCC	
Only SIP related decisions to be presented for information for the meeting.	
							
3	Input Liaison statements
tuesday 28.11.2000		Only SIP & IM subsystem related LSs are provided for this meeting				

4 	SIP Work Plan for TSGN WG1
tuesday 28.11.2000					2000:
CN1 SIP ad-hoc 17.-19.10.2000 (Sophia Antipolis)
TSGN1 #14 20.11 – 24.11.2000 (Cardiff, UK/Lucent) 
CN1-SA2 SIP joint meeting on SIP 28.11.2000 with possibility to extend to 29.11.2000 in a smaller CN1 drafting meeting (New Jersey / USA)
TSGN#10  6.-8.12.2000

2001:
CN1 #15 15.-19.1.2001 (Host needed) 
    (N4 is at the same time)
CN1 – SA2 SIP ad hoc 
22.1.2001 with possibility to extend to 23.1.2001 in smaller drafting group 
CN1 – SA2 SIP ad hoc 26.2.2001 (CN1 and SA2 should be co-located)
CN1 #16 27.2.-1.3.2001 (Host needed)
    (N4 is at the same time)
CN #11 14.-16.3.2001 (US)
CN1 – SA2 SIP ad hoc 3.-4.4.2001 (Nokia candidate host)
CN1 #17 14.-18.5.2001 (Host needed)
    (N4 is at the same time)
CN #12 13.-15.6.2001 (Europe)
CN1 #18 27.-31.8.2001 (Host needed)
CN #13 19.-21.9.2001 (China)
CN1 #19 22.-26.10.2001 (Host needed)
CN1 #20 20.-23.11.2001 (Host needed)
CN #14 12.-14.12.2001 (Japan)	
							
5	Technical issues
tuesday 28.11.2000					CN1 SIP ad hoc #1 decided that 3 new CN1 specifiations will be needed:
•	Detailed IP multimedia signalling flows, proposed specification number 24.228
•	Stage 3 for the multimedia call control based on SIP with proposed specification number 24.229.
•	Call model specification the scope of which has not been defined yet but understood to be the IM variant of 23.018.	
5.1	Storing confidential information in UE / P-CSCF / S-CSCF					CN1 SIP ad hoc #1 made a working assumption that sending encrypted information on call path, caller identity, etc to UE is not very practical and instead we should study whether P-CSCF or S-CSCF would be more appropriate entity to store the information.	

5.2	SIP REGISTER related call flows						

5.3	SIP INVITE related call flows						

5.4	Other call flows						

							
5.5	Other technical issues						

6	A.O.B.
Evening session on tuesday 28.11.2000 and short wrapup wednesday morning (29.11.2000) is possible if needed.