outgoing LSs of RAN2 #62 in Kansas City, USA 05.05.-09.05.2008:
status Wed 21.05.2008 pm (27 outgoing LSs)

related to UTRA: 	5 LSs
R2-082797	LS on NodeB measurement to report common E-DCH Resource Usage (to: RAN3; cc: -; contact: Qualcomm)
R2-082804	Reply LS to R1-081702 = R2-082093 on E-AICH Power Offset and Error Targets for AICH/E-AICH (to: RAN1; cc: RAN3, RAN4; contact: Qualcomm)
R2-082805	Reply LS to R1-080619 = R2-080670 on 1.28 Mcps TDD HS-DSCH physical layer categories and related transport block sizes for 64-QAM modulation (to: RAN1; cc: -; contact: TD Tech)
R2-082900	LS on UTRA R8 hNB requirements (to: SA1, CT1; cc: -; contact: Huawei)
R2-082907	LS on HSPA VoIP to WCDMA/GSM CS continuity (to: SA2, CT1; cc: -; contact:NSN)


related to E-UTRA/LTE:	22 LSs (including 4 email approvals)
R2-082868	Reply LS to R3-080993 = R2-082077 and S2-083151 = R2-082084 on S1 Overload Control and on security for service request message (to: RAN3, SA2, SA3, CT1; cc: -; contact: NSN) 
R2-082869	Reply LS to R3-080990 = R2-082076 on RAN3 requirements for GTPv2 (to: RAN3, CT4; cc: SA2; contact: LG)
R2-082871	LS TTI Bundling (to: RAN1; cc: -; contact: NSN)
R2-082872	Reply LS to GP-080298 = R2-081411 on equal priority RATs (to: GERAN; cc: -; contact: T-Mobile)
R2-082873	LS on Development of test cases for LTE RRC procedure performance (to: RAN5; cc: -; contact: T-Mobile)
R2-082883	Reply LS to S2-083168 = R2-082085 and S3-080522 = R2-082098 on Earthquake and Tsunami Warning System (to: CT1, SA1, SA2, SA3; cc: RAN1, RAN3; contact: NTT)
R2-082884	Reply LS to R3-080543 = R2-081424 and G2-080228 = R2-082024 on Applicability of 'subscriber type' indication for UTRAN & GERAN (to: RAN3, SA2, GERAN2; cc: -; contact: Orange)
R2-082886	Reply LS to R3-080976 = R2-082071 on the necessity of to convey ‘Receive Status of UL PDCP SDU’ in S1 Handover (to: RAN3; cc: -; contact: NTT)
R2-082887	Reply LS to S2-083103 = R2-082079 on UE specific paging DRX (to: SA2; cc: CT1; contact: Ericsson)
R2-082888	Reply LS to S2-083147 = R2-082082 on SRVCC from EUTRAN to 1xRTT (to: SA2; cc: RAN3; contact: Nortel)
R2-082889	Reply LS to R1-081705 = R2-082095 on Transport Block Sizes (to: RAN1; cc: RAN4; contact: Samsung)
R2-082890	Reply LS to SA3 to S3-080503 = R2-082097 – key change on-the-fly (to: SA3, RAN3; cc: -; contact: Samsung)
R2-082892	LS on Semi-Persistent Scheduling Activation with single PDCCH (to: RAN1; cc: -; contact: Qualcomm)
R2-082893	Reply LS to R1-081676 = R2-082068 on System information scheduling (to: RAN1; cc: -; contact: NTT)
R2-082894	LS on reservation of an MMEC value (to: CT4; cc: CT1, RAN3, SA2,  SA5; contact: Motorola)
R2-082895	LS on Connection recovery by NAS (to: CT1, SA2; cc: -; contact: NTT)
R2-082896	Reply LS to C1-0801433 = R2-082066 on NAS–AS interaction for dependent procedures (to: CT1; cc: RAN3, SA2; contact: Ericsson)
R2-082897	Reply LS to S2-083105 = R2-082080 and R3-080979 = R2-082072 on per UE frequency restriction (to: SA2, RAN3; cc: CT1; contact: T-Mobile)

R2-082891	LS on priority reselection for LTE interworking (to: GERAN; cc: -; contact: Nokia), agreed by email on 14.05.2008
R2-082898	LS on synchronisation of L1 parameters from system information (to: RAN1; cc: -; contact: Panasonic), agreed by email on 17.05.2008
R2-082885	Reply LS to R1-081683 = R2-082069 on information about new PDCCH Format 1C (to: RAN1; cc: -; contact: Qualcomm), agreed by email on 22.05.2008
R2-082899	LS on CSG cell identification (to: RAN1; cc: -; contact: Qualcomm), agreed by email on 12.06.2008