1. Review of Q.8/13 work TTC 20-22 February 2008

2. 2 Q.8/13 work completed in January 2008 1.Y.2232 (formerly Y.wsconv) was approved by incorporating all last call comments. 2.Draft Y.ctmp (Service scenarios for convergence services in a multiple network and application service provider environment) was asked another review at September meeting, changed as a Supplement and approved at January meeting. 3.TD601r2(wp3) is the meeting report.

3. 3 Q.8/13 work ongoing 1.Y.cwbs (Converged web-browsing service scenario over NGN) 2.Y.cmr (Deployment models for customized multimedia ring service) 3.cmoip (Convergence service scenario and use cases for high quality mobile VOIP)

4. 4 Some opinions regarding Q.8 1.Service scenario is an input to identify service requirements and capabilities. They should be studied jointly. 2.Service itself should not be standardized. It seems to restrict operators’ business or impose as extra burden. 3.Capabilities should be identified by examining services. 4.Deployment model is a guide for network operators to build the network. This is the final stage of the study. 5.In other words, service scenario and deployment model come before to stages 1/2/3 or after them. 6.If new stages 1/2/3 are required, the proposal should be directed to requirements (including capability), architecture (including information flow), or signalling. 7.Regarding cmoip, concerns were raised during the WP plenary whether it might cover the signalling and protocol aspect, which should be discussed in SG11. It was also pointed out that a new study concerning a mobility control functions (MCF) architecture under Q.3/13 should be taken into account. 8.Please consider these points carefully.