3GPP TSG CN WG1 Meeting #18 				 			Dresden0107.rtf 
Dresden, Germany, 10th - 12th July 2001									(revision of Tdoc N1-010920)
Documents for TSG CN WG1 meeting #18, Dresden	Cyan cells indicate an allocated but not available tdoc	Yellow cells indicate an available not not yet treated tdoc.	
Agenda item	Agenda item title	3GPP Tdoc	Title	Spec.	Source	Result	
1	Opening
Tuesday 10.7.2001						
			Disclosure of IPRs		MCC	The attention of the members of this Technical Specification Group is drawn to the fact that 3GPP Individual Members have the obligation under the IPR Policies of their respective Organizational Partners to inform their respective Organizational Partners of Essential IPRs they become aware of. 	
2	Agenda & Reports
Tuesday 10.7.2001						
		N1-010920	Agenda		Chairman	Agreed.	
	2	N1-010926	Summary of current IETF documents on SIP		Lucent Technologies / Keith Drage	Noted.	
	2	N1-010927	Summary of current IETF documents on SIPPING		Lucent Technologies / Keith Drage	Noted.	
	2	N1-010928	Summary of current IETF documents on MMUSIC		Lucent Technologies / Keith Drage	Noted	
	2	N1-010929	Summary of current IETF documents on SIMPLE		Lucent Technologies / Keith Drage	Noted	
	2	N1-011001	DRAFT STATUS REPORT v1.1.0 3GPP TSG-CN#12		MCC	Noted	
	2	N1-011002	Meeting Report
TSG CN WG1# 17
Puerto Rico, USA
14 - 18 M ay 2001		MCC	Agreed	

3	Input Liaison statements 
Tuesday 10.7.2001		Only those incoming LSs should be provided which are relevant for SIP issues.				
	3	N1-010921	LS Clarifications of aspects of Multimedia Capabilities [ID 1281]		T2	Reply in N1-011019
T2 are asking for clarification on their WT 1806, Terminal capabilities and Interactions on running multimedia from an external terminal, under WT 1281, Multimedia capabilities.
Additionally they are proposing a joint meeting, if necessary, on multimedia capabilities. Our meetings are not synchronised so next alternatives would be during CN1 #19 27-31-Aug-2001 or during T2 #14 3-7-Sep-2001.
T2 work is not covered in CN1 originated WID, so one alternative is to delete WT 1806 unless CN1 sees a proposal to revise the existing WID.	
	3	N1-010922	LS on the termination of authentication in the IMS		S2	Noted.
SA2 reply to SA3 with CC to CN1 on the requirement that the authentication takes place in the home network. SA2 have studied this further and taken the approach that S-CSCF performs the authentication. 23.228 signalling flow based on this assumption is attached.
Linked CR is in N1-010937	
	3	N1-010923	WI on the End-to-End QoS Architecture for Release 5		S2	Noted.
SA2 inform the other groups that the restructuring of the WI ' Ensure reliable QoS for PS domain' was endorsed in their meeting. This led to creation of new feature level WI ' End-to-End QoS for PS Domain'. The WI description is attached.
There are several building blocks under this WI and one of them, 'End-to-End QoS IE for PS Domain' is for CN1 with expected impact on 24.008, 24.228 and 24.229.
The main WI has already been added to the 010612 version of the work plan and the old one has been marked for deletion.	
	3	N1-010924	Reply LS on  "IM CN Subsystem Roaming"		S2	Noted (because even though the issue is interesting for CN1 the service requirement is SA1 territory)
SA2 reply to CN1 (N1-010482, S2-011387), and SA1 (S1-010569, S2-011435) on IM CN subsystem roaming.
SA2 see that separating the IMS subscription from the PS subscription would be justified and ask SA1 what would be the service requirement for the UE with PS but no IMS roaming allowed.	
	3	N1-010925	Reply to the following LSs:
LS on  "Security for IM SIP session Signaling" 
(Tdoc N1-010588, received as S3-010152) 
LS on “ IM User Identities” 
(Tdoc S2-010757, received as S3-010160)		S3	Noted
SA3 reply to CN1 LS (N1-010588 / S3-010152)  and SA2 LS (S2-010757 / S3-010160) on user identities. 
CN1 asked in our original LS SA3 opinion of several security issues. SA3 reply by confirming some of the assumptions we have made but add that that they still have got more work to do in this area in SA3. But at this stage they do not overrule any of the assumptions that have been made in CN1. Did the CN1 delegation's presentation in the latest SA3 meeting yield any more information to be shared?	
	3	N1-010976	Response to Liaison Statement on the IM Call Transfer Service
 N1-010890 (S3-010249)		S3	Forwarded to joint session in 8.2
SA3 reply to CN1 LS IM Call Transfer Service
(N1-010890 / S3-010249). 
SA3 have briefly looked at the IMS CT call flows and agree that there is a security issue but would like to have more detailed walkthrough of the flows.
Is there anything more to report from the latest SA3 meeting?
Linked LS in N1-010979.	
	3	N1-010977	Using a generic authentication scheme for SIP		S3	Reply in N1-011020
The SA3 recommends that the “407 Proxy Authentication Required” error response and the “WWW-Authenticate” and “Authorization” headers used in IMS authentication should carry EAP (Extensible Authentication Protocol)
There is also a DIAMETER question to CN4.
Is an attachment (S3-010263) missing?	
	3	N1-010978	Reply to LS on "Handling of ICMP messages by 3GPP SIP Implementations"		S3	Noted
SA3 reply to our LS in N1-010892. Our question was should the 3GPP SIP implementation handle the ICMP messages as recommended in RFC 2543, or should they be ignored by the 3GPP SIP implementation?
SA3 say that the NDS/IP architecture for the core network does not provide any support for protecting ICMP messages and that there is no intention to do so in the future.
So CN1 should assume that ICMP messages are not security protected.	
	3	N1-011008	LS on ISC		S2	Forwarded to 23.218 joint session
SA2 have endorsed the term ISC for IMS Service Control interface. 
Furthermore they have decided that the protocol to be run at this interface will be SIP. At the moment no extensions to SIP are known but if some are needed that will be stage 3 work as usual.	
	3	N1-011009	LS on SIP Compression between UE and P-CSCF		S2	Noted.
SA2 have agreed that the compression of SIP messages between UE and P-CSCF is needed.
•	UMTS shall support mechanisms to optimize transport of SIP signaling packets over the radio interface, typically by compressing the SIP signaling messages and by compressing the IP and transport layer protocol headers that carry these SIP messages.
•	The chosen solution(s) shall be extensible to facilitate the incorporation of new and improved compression algorithms in a backward compatible way as they become available. 
•	The chosen solution(s) should work in roaming scenarios.
•	Application specific compression shall minimize impacts on existing UMTS release e.g. it could be defined between the UE and associated application server, e.g. at the SIP Client and at the first SIP Proxy.
•	There must be a negotiation mechanism to agree the compression algorithm so that new algorithms can be added later on
Linked CR in N1-010984	
	3	N1-011010	LS on Future proof specification of the Go interface		S2	Forwarded to 24.228 joint session.
SA2 to CN3 with CC to CN1.
It has been decided in SA2 that in Release 5 there will be no standardised open interface between the PCF (Policy Control Function) and the P-CSCF. However, introducing such an interface in later releases should not be prevented.
Does this mean that PCP needs to be shown as a separate entity in 24.228?	
	3	N1-011011	LS on Cell ID in SIP messages		S2	Noted.
CN1 action is required but there are no contributions available at this meeting.
SA2 asks CN1 to study the means of providing cell identity across the Gm interface during SIP registration and session initiation procedures.	

4 	CN1 work plan
Thursday 12.7.2001					Meeting calendar for 2001:	
						15.-19.Jan.2001	CN1 #15, Beijing	
						7.-8.Feb.2001	Joint SA1-CN1-RAN2-RAN4-GERAN1 idle mode workshop (Nokia, Helsinki/Finland)	
						13.-15.Feb.2001	CN1-SA2 SIP joint meeting (AT&T, New Jersey/USA	
						26.Feb-1.Mar. 2001	CN1 #16, CN1-2-3-4 (ETSI, Sophia Antipolis / France) 	
						14.-16.Mar.2001	CN #11, (Palm Springs / USA)	
						3.-5. Apr.2001	CN1–SA2 SIP joint meeting (ETSI, Sophia Antipolis / France)
3.-4.4 joint, 5.4 CN1.
23.218 could be excluded?	
						8.-9. May 2001	CN1 R99 and older ad hoc meeting, Nokia candidate host.	
						14.-18.May 2001	CN1 #17, CN1-2-3-4 (North American friends of 3GPP / Puerto Rico)	
						13.-15.Jun.2001	CN #12 (Ericsson / Stockholm)	
						10.-12.Jul.2001	CN1 #18 with 11.7. joint sessions on 23.218 and 24.228 (Dresden, Germany / D2 Vodafone)	
						27.-31.Aug.2001	CN1 #19 (Nokia, Helsinki / Finland)	
						19.-21.Sep.2001	CN #13 (China)	
						15.-19.Oct.2001	CN1 #20 (BT, Vodafone, Lucent / UK)	
						26.-30.Nov.2001	CN1 #21 (North American friends of 3GPP / USA)	
						12.-14.Dec.2001	CN #14 (Japan)	
						14.-18. Jan. 2002	CN1 #22	
						6.-8. Mar. 2002	CN #15 (Korea)	
						8.-12. Apr. 2002	CN1 #23	
						13.-17. May 2002	CN1 #24	
						5.-7. Jun. 2002	CN #16 (?)	
						29. Jul. – 2. Aug. 2002	CN1 #25 (Sonera, Finland)	
						4.-6- Sep. 2002	CN #17 (France)	
						23.-27. Sep. 2002	CN1 #26	
						11.-15. Nov. 2002	CN1 #27	
						4.-6. Dec. 2002	CN #18 (New Orleans)	
	4	N1-010980	Workplan of 12th June for N1 review	MCC			

5	Void
					Maintenance of R98 and older releases is outside the scope of this meeting.	

6	Void					R99 is outside the scope of this meeting.	

7	Void					Rel-4 is outside the scope of this meeting.	

8	Release 5

		Please indicate agenda item 8.1 or 8.2 for those tdocs which are intended for CN WG joint session.
			24.228 related issues will be discussed together with the interested delegates from the other CN WGs 	
8.1	23.218 issues for joint CN WG session
Wednesday 10.07.2001 at 11:00		All building blocks under feature ID 1273
			Also other CN WGs are welcomed but it is up to the WGs to decide if they schedule other issues for a separate session for this same time.

	8.1	N1-010930	CR to 23.218: Filter Criteria mode in IMS	23.218	Lucent Technologies/Xin Chen	Revised to N1-011013	
	8.1	N1-010931	CR to 23.218: Initial filter criteria in IMS	23.218	Lucent Technologies/Xin Chen	Revised to N1-011014	
	8.1	N1-010936	Filter Criteria for ISC Interface	23.218	Ericsson	Revised to N1-011025	
	8.1	N1-010979	Reply to N1-010890 “Liaison Statement on the IM Call Transfer service”	23.218	S5	Forwarded to 24.228 joint session in 8.2
SA5 reply to the joint CN1-2-3-4 session IMS CT LS N1-010890. They acknowledge the LS and promise to look at the details from charging viewpoint in their next reqular meeting 16-20 July 2001.
Linked LS from SA3 in N1-010976	
	8.1	N1-010981	23.218 v051 IP Multimedia (IM) Session Handling;IP Multimedia (IM) call model	23.218	Motorola, Andrew Allen		
	8.1	N1-010982	Removal of I-CSCF and P-CSCF from Section 5 of 23.218	23.218	Motorola, Andrew Allen		
1.	8.1	N1-010983	Modifications to layout of 23.218 based on revised SA2 architecture for  Service Control and selection of SIP for the ISC interface protocol	23.218	Motorola  Andrew Allen		
	8.1	N1-010986	CR to 23.218: Information Flows for IMS Service Examples: Call Forwarding Scenarios	23.218	Lucent Technologies / Moh Torabi	Revised to N1-011015	
	8.1	N1-010987	CR to 23.218: Pre-paid Service Control Examples	23.218	Lucent Technologies / Moh Torabi	Revised to N1-011016	
	8.1	N1-010988	Updates to CAMEL sections in 23.218	23.218	Lucent Technologies / Michel Grech	Revised to N1-011026
The discussion on this document depends on the decision made on N1-010988. If 988 is agreed then is this needed at all?	
	8.1	N1-010989	CR to 23.218: Additional changes to initial filter criteria based on N1-010930	23.218	Lucent Technologies / Xin Chen	Revised to N1-011017	
	8.1	N1-010990	CR to 23.218: Revision of the originating and terminating call state models	23.218	Lucent Technologies / Michel Grech	Revised to N1-011027	
	8.1	N1-010997	S-CSCF Rolemapping		Siemens		
	8.1	N1-011003	Addressing B2BUA in a SIP network		Ericsson		
	8.1	N1-011004	Network Controlled Session Disconnection 		Ericsson		
	8.1	N1-011005	Network Controlled Session Setup, Modification 		Ericsson		
	8.1	N1-011006	Network Controlled Addition/Removal of legs		Ericsson		
	8.1	N1-011008	LS on ISC		S2	Forwarded to 23.218 joint session
SA2 have endorsed the term ISC for IMS Service Control interface. 
Furthermore they have decided that the protocol to be run at this interface will be SIP. At the moment no extensions to SIP are known but if some are needed that will be stage 3 work as usual.	
2.	8.1	N1-011013	CR to 23.218: Filter Criteria mode in IMS	23.218	Lucent Technologies/Xin Chen	

Revision of N1-010930	
	8.1	N1-011014	CR to 23.218: Initial filter criteria in IMS	23.218	Lucent Technologies/Xin Chen	

Revision of N1-010931	
	8.1	N1-011015	CR to 23.218: Information Flows for IMS Service Examples: Call Forwarding Scenarios	23.218	Lucent Technologies / Moh Torabi	

Revision of N1-010986	
	8.1	N1-011016	CR to 23.218: Pre-paid Service Control Examples	23.218	Lucent Technologies / Moh Torabi	

Revision of N1-010987	
	8.1	N1-011017	CR to 23.218: Additional changes to initial filter criteria based on N1-010930	23.218	Lucent Technologies / Xin Chen	

Revision of N1-010989	
	8.1	N1-011018	Filter Criteria and Service Points of Interests		Siemens		
	8.1	N1-011025	Filter Criteria for ISC Interface		Ericsson	
Revised from 936	
	8.1	N1-011026	Updates to CAMEL sections in 23.218		Lucent Technologies / Michel Grech	

Revised from 988	
	8.1	N1-011027	CR to 23.218: Revision of the originating and terminating call state models		Lucent Technologies / Michel Grech	

Revised from 990	

							
8.2	24.228 issues for joint CN WG session
Wednesday 11.7.2001
at 16:00		All building blocks under feature ID 1273
			Also other CN WGs are welcomed but it is up to the WGs to decide if they schedule other issues for a separate session for this same time.	
	8.2	N1-010941	Missing QoS Interaction in 24.228 Procedures	24.228	AT&T Wireless		
1.	8.2	N1-010944	24.228v110 "Signalling flows for the IP multimedia call controlbased on SIP and SDP"	24.228	Motorola  / Ericsson J. O'Hare		
2.	8.2	N1-010985	Document Structure for the Cx Interface Protocol Standards		Lucent Technologies / Nigel Berry	
Is there any problem for the joint session to ask CN4 to follow the proposed principle in documenting Cx interface.	
	8.2	N1-010993	CR to 24.228: Proposal for Media Gating Timing at MGW for Early Media 	24.228	Lucent Technologies / Daisuke Yokota		
	8.2	N1-010994	CR to 24.228: Removal of the T-SGW 	24.228	Lucent Technologies / Keith Drage		
	8.2	N1-010976	Response to Liaison Statement on the IM Call Transfer Service
 N1-010890 (S3-010249)		S3	
SA3 reply to CN1 LS IM Call Transfer Service
(N1-010890 / S3-010249). 
SA3 have briefly looked at the IMS CT call flows and agree that there is a security issue but would like to have more detailed walkthrough of the flows.
Is there anything more to report from the latest SA3 meeting?
Linked LS in N1-010979.	
	8.2	N1-010979	Reply to N1-010890 “Liaison Statement on the IM Call Transfer service”	24.228	S5	
SA5 reply to the joint CN1-2-3-4 session IMS CT LS N1-010890. They acknowledge the LS and promise to look at the details from charging viewpoint in their next reqular meeting 16-20 July 2001.
Linked LS from SA3 in N1-010976	
	8.2	N1-010999	Proposal on the work split of "End-to-end QoS Stage 3" among CN and RAN working groups		Lucent Technologies / Daisuke Yokota		
	8.2	N1-011007	Handling of Unsupported media types in SDP		InterDigital Communication		
	8.2	N1-011010	LS on Future proof specification of the Go interface		S2	Forwarded to 24.228 joint session.
SA2 to CN3 with CC to CN1.
It has been decided in SA2 that in Release 5 there will be no standardised open interface between the PCF (Policy Control Function) and the P-CSCF. However, introducing such an interface in later releases should not be prevented.
Does this mean that PCP needs to be shown as a separate entity in 24.228?	
	8.2	N1-011012	CR to 24.228: Quality of Service Authorization in IM CN subsystem	24.228	Lucent Technologies / Xin Chen		

8.3	Rel 5 corrections					CN1 session	
	8.3
Tuesday 10.7.2001	N1-010935	Current draft 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP"	24.229	Lucent Technologies / Keith Drage	Noted	
	8.3	N1-010961	Notation conventions	24.228	Nokia/ Bajkó Gábor	Revised to N1-01024
Not a CR but the linked CRs are in tdocs N1-010967 and N1-010968.	
	8.3	N1-011024	Notation conventions	24.228	Nokia/ Bajkó Gábor	
Not a CR but the linked CRs are in tdocs N1-010967 and N1-010968.
Revision of N1-010961	
							
8.4	SIP call control protocol for the IM CN subsystem: 
Registration
Tuesday 11.7.2001		All building blocks under feature ID 1273
				
	8.4	N1-010933	CR to 24.228: Contact header in registration request	24.228	Lucent Technologies / Milo Orsic	Postponed	
	8.4	N1-010934	CR to 24.228: Handling of contact header by the P-CSCF	24.228	Lucent Technologies / Milo Orsic	Revised to N1-011025	
	8.4	N1-010940	Comments on Signaling Flows for REGISTER	24.228	AT&T Wireless	Rejected	
	8.4	N1-010945	CR to 24.228: A review of the editor's notes in clause 7 (prior to clause 7.1)	24.228	Lucent Technologies / Keith Drage	Agreed	
	8.4	N1-010946	CR to 24.228: A review of the editor's notes in clause 7.1 and 7.3	24.228	Lucent Technologies / Keith Drage	Agreed the proposal except for that editor's notes 2 and 4 remain as they are.	
	8.4	N1-010947	CR to 24.228: A review of the editor's notes in clause 7.2	24.228	Lucent Technologies / Keith Drage	Agreed	
	8.4	N1-010952	CR to 24.228: Adding Date header in registration flows	24.228	Lucent Technologies /Xin Chen	Agreed	
	8.4	N1-010956	CR to 24.229: Path mechanism	24.229	Lucent Technologies / Milo Orsic	Revised to N1-011028	
	8.4	N1-010957	CR to 24.229: Route establishment procedure	24.229	Lucent Technologies / Milo Orsic	Revised to N1-011029
•	The discussion on whether P-CSCF is allowed to touch Contact header is still open.
•	The editor's note in 9.2.1 should be made to cover the precised handling of the Path header instead of deleting it.
•	Clarify that it is the RR header where the route list is constructed in 9.2.1	
	8.4	N1-010963	Explicit Subscription	24.228	Nortel Networks	
CR to propose deletion of implicit subscription of deregistration events and to introduce explicit signalling for the same purpose. The procedure is made generic and could be used for subscribing other event also, even though none have been identified yet.
Implicit subscription is not compliant with IETF SIP and would need major rework to make it work.
tdocs N1-010963, 971 and 998 are related.	
	8.4	N1-010974	Registration Flow updates	24.228	Nokia/ Bajkó Gábor		
	8.4	N1-010992	CR to 24.228: Private user identity within REGISTER requests	24.228	Lucent Technologies / Xin Chen		
	8.4	N1-010998	DISCUSSION to 24.228: Use of Event Notification within Registration	24.228	Lucent Technologies / Keith Drage	Agreed with comment that the need for P-CSCF to run registration related timer needs to be checked with SA2.
Discussion
This discussion document outlines the problem addressed in Nortel contribution N1-010963 and Nokia contribution N1-010971. The documents do not disagree with each other(?)
tdocs N1-010963, 971 and 998 are related.	
	8.4	N1-011028	CR to 24.229: Path mechanism	24.229	Lucent Technologies / Milo Orsic	

Revision of N1-010956	

8.5	SIP call control protocol for the IM CN subsystem: 
De-registration
Wednesday 11.7.2001 		All building blocks under feature ID 1273
				
	8.5	N1-010948	CR to 24.228: A review of the editor's notes in clause 7.4	24.228	Lucent Technologies / Keith Drage		
	8.5	N1-010951	CR to 24.228: Network initiated deregistration upon UE roaming without de-registration	24.228	Lucent Technologies /Xin Chen	Withdrawn	
	8.5	N1-010962	Network Initiated De-registration changes	24.228	Nortel Networks		
	8.5	N1-010971	Subscribing for the Network Initiated Deregistration event	24.228	Nokia/ Krisztian Kiss	
Explicit procedure for network initiated de-registration.
tdocs N1-010963, 971 and 998 are related.	
	8.5	N1-010975	Network Initiated Deregistration	24.228	Nokia/ Krisztian Kiss		

							
8.6	SIP call control protocol for the IM CN subsystem: 
Configuration hiding
Thursday 12.7.2001		All building blocks under feature ID 1273
				
	8.6	N1-010939	Network Configuration Hiding with a BGCF	24.228	Ericsson		

8.7	SIP call control protocol for the IM CN subsystem: 
Authentication
Thursday 12.7.2001		All building blocks under feature ID 1273
				
	8.7	N1-010937	Network Controlled Authentication Without the Use of A B2BUA	24.228	Ericsson	
What are the SA3 requirements in authenticating registrations / other SIP procedures?	

8.8 	SIP call control protocol for the IM CN subsystem: 
Call Initiation
Thursday 12.7.2001		All building blocks under feature ID 1273
				
	8.8	N1-010949	CR to 24.228: A review of the editor's notes in clause 8.1	24.228	Lucent Technologies / Keith Drage		
	8.8	N1-010950	CR to 24.228: A review of the editor's notes in clause 8.2	24.228	Lucent Technologies / Keith Drage		
	8.8	N1-010953	CR to 24.228: The deletion of Proxy-Require header 	24.228	Lucent Technologies /Xin Chen		
	8.8	N1-010958	CR to 24.229: P-CSCF processing of the initial INVITE request	24.229	Lucent Technologies / Milo Orsic		
	8.8	N1-010959	CR to 24.229: I-CSCF processing of the initial INVITE request	24.229	Lucent Technologies / Milo Orsic		
	8.8	N1-010960	CR to 24.229: S-CSCF processing of the initial INVITE request	24.229	Lucent Technologies / Milo Orsic		
	8.8	N1-010965	Anonymity	24.228	Nokia/ Bajkó Gábor		
	8.8	N1-010966	SDP in Prack	24.228	Nokia/ Bajkó Gábor	Revised to N1-011022	
	8.8	N1-010967	#2 Flow updates	24.228	Nokia/ Bajkó Gábor		
	8.8	N1-010968	#1 Flow updates	24.228	Nokia/ Bajkó Gábor		
1.	8.8	N1-010972	The content of To: and From: fields	24.228	Nokia/ Bajkó Gábor		
1.	8.8	N1-010984	SIP/SDP Compression	24.228	Motorola, Andrew Allen		
	8.8	N1-010991	CR to 24.228: Correction on Content-Length header in INVITE	24.228	Lucent Technologies /Xin Chen		
	8.8	N1-010995	CR to 24.228: Correct placement of state info tables 	24.228	Lucent Technologies / Keith Drage		
	8.8	N1-011022	SDP in Prack	24.228	Nokia/ Bajkó Gábor	
Revision of N1-010966	

							
							
8.9 	SIP call control protocol for the IM CN subsystem: 
Call clearing		All building blocks under feature ID 1273

							
8.10	SIP call control protocol for the IM CN subsystem: 
Abnormal cases and error handling
Thursday 12.7.2001		All building blocks under feature ID 1273
				
	8.10	N1-010969	Warning header in 403 Forbidden	24.228	Nokia/ Bajkó Gábor		
	8.10	N1-010970	Roaming not allowed	24.228	Nokia/ Bajkó Gábor		

8.11 	SIP call control protocol for the IM CN subsystem: 
Editorial changes
Thursday 12.7.2001 if there is any time left		All building blocks under feature ID 1273
			If the meeting runs out of time with these let's at least identify the ones that can be email approved (i.e. the real editorial ones)	
	8.11	N1-010932	CR to 24.228: Editorial corrections	24.228	Lucent Technologies / Keith Drage		
	8.11	N1-010942	Revision of the key in 24.228 for empty headers	24.228	Motorola,Ericsson / J O'Hare		
	8.11	N1-010943	Proposal to delay implementation of N1-010893 "Proposed revision of the presentation of SIP headers in 24.228" "	24.228	Motorola, Ericsson / J O'Hare		
	8.11	N1-010955	CR to 24.229: Editorial corrections	24.229	Lucent Technologies / Keith Drage		
	8.11	N1-010964	Corrections to 24.228	24.228	Nortel Networks		
	8.11	N1-010973	Document restructuring	24.228	Nokia/ Bajkó Gábor		
	8.11	N1-010996	CR to 24.228: Minor corrections 	24.228	Lucent Technologies / Keith Drage		
	8.11	N1-011000	CR to 24.228: General editorial issues	24.228	Lucent Technologies / Keith Drage		

							
8.12	IP & PS based emergency call enhancements
		All building blocks under feature ID 1653			WI status: not started.	

8.13	Other SIP issues
Thursday 12.7.2001						
	8.13	N1-010938	Terminal Capabilities	24.228	Ericsson		
	8.13	N1-010954	CR to 24.229: An analysis of the requirements for the Date header	24.229	Lucent Technologies / Keith Drage		

9	Output Liaison Statements
Thursday 12.7.2001						
		N1-011019			Keith	
Reply to N1-010921	

							

10	A.O.B.
Thursday 12.7.2001						

11	Closing
Thursday 12.7.2001 at 17:00					Any document which is not mentioned in this report shall be interpreted as "reserved", i.e. not defined and shall be ignored if received.