incoming LSs for RAN2 #64 in Prague, Czech Republic, 10.11.-14.11.2008:
status Fri 21.11.08 (72 incoming LSs)

Agenda item 5.1: Incoming LS to LTE:  63 LSs
R2-086002$	LS on PCI Clarification (S3-081118; to: RAN2; cc: RAN3; contact: Qualcomm)	SA3
R2-086003$	Reply LS to R2-084907 on KeNB handling at handover (S3-081121; to: RAN2, RAN3; cc: -; contact: NTT DOCOMO)	SA3
R2-086004$	Reply LS to R2-083787 on "LS NULL integrity protection algorithm" (S3-081129; to: RAN2, RAN5, CT1; cc: -; contact: NSN)	SA3
R2-086005$	Reply LS to R2-084876 on "AS Message Exception list" (S3-081130; to: RAN2; cc: -; contact: Nokia)	SA3
R2-086006$	Reply LS to R2-084898 on "counter check procedure" (S3-081135; to: RAN2; cc: -; contact: Nokia)	SA3
R2-086007$	Reply LS to R2-084909 on “Intersystem RAT handover security” (S3-081138; to: RAN2; cc: -; contact: NSN)	SA3
R2-086008$	LS on preventing inter-RAT HO for UE with SIM access (S3-081150; to: RAN3; cc: RAN2, CT1, CT4; contact: Huawei)	SA3
R2-086009$	Reply LS to R3-082373 = R2-084972 on E-UTRAN security related issues (S3-081175; to: RAN3; cc: RAN2; contact: Ericsson)	SA3
R2-086010$	LS on the start of security on IRAT handover from GERAN/UTRAN (S3-081139; to: CT1, RAN2; cc: -; contact: Nokia)	SA3
R2-086011$	LS on UE emission control (R4-082585; to: RAN1, RAN2; cc: RAN3; contact: Motorola)	RAN4
R2-086013	Reply LS to R2-084919 on UE behaviour of NAS message transmission during UTRAN to E-UTRAN handover (C1-084185; to: RAN2; cc: SA2; contact: Samsung)	CT1
R2-086014	Reply LS to R3-082867 = R2-086038 and R2-085954 on UE-EPC signalling and paging cause (C1-084465; to: RAN3, SA2, RAN2; cc: SA3; contact: NEC)	CT1
R2-086015	Reply LS to R2-085973 on maximum PDCP SDU size (C1-084468; to: RAN2; cc: CT4, SA3, SA2; contact: NEC)	CT1
R2-086016	LS on Allowed CSG list and Home Node B Name (C1-084474; to: SA1, SA2, SA3, RAN2, RAN3, RAN5, CT4, CT6; cc: -; contact: Samsung)	CT1
R2-086017	LS on RRC and SABP update (C1-084494; to: RAN2, RAN3; cc: -; contact: NTT DOCOMO)	CT1
R2-086018	Reply LS to S2-086378 = R2-084978 on Connection recovery by NAS (C1-084495; to: SA2, RAN2, RAN3; cc: RAN1; contact: Panasonic)	CT1
R2-086019	Reply LS to S3-081139 = R2-085857 = R2-086010 on the start of security on IRAT handover from GERAN/UTRAN (C1-084496; to: SA3; cc: RAN2; contact: NSN)	CT1
R2-086021	LS on definition of out of service area (R4-082621; to: RAN2; cc: -; contact: NTT DOCOMO)	RAN4
R2-086022	Reply LS to R2-085961 on AS/NAS Split for CSG Selection (C1-084568; to: RAN2; cc: SA2; contact: Qualcomm)	CT1
R2-086023	Reply LS to R2-082869 on RAN3 requirements for GTPv2 (C4-083129; to: RAN2, RAN3; cc: SA2; contact: Fujitsu)	CT4
R2-086024	Reply LS to R2-085973 on maximum PDCP SDU size (C4-083164; to: RAN2; cc: SA3, CT1, SA2; contact: NSN)	CT4
R2-086025	LS on measurement gap for TDD (R1-084055; to: RAN2; cc: RAN4; contact: CATT)	RAN1
R2-086026	LS Response to R2-084903 on Semi-Persistent Scheduling Activation with single PDCCH (R1-084056; to: RAN2; cc: -; contact: Qualcomm)	RAN1
R2-086027	Response LS to R2-084910 on RAN2 decision to use Pathloss parameter in the RACH preamble group selection (R1-084057; to: RAN2; cc: RAN4; contact: LG)	RAN1
R2-086028	Reply LS to R2-084911 on PDCCH DL data arrival (R1-084058; to: RAN2; cc: -; contact: Ericsson)	RAN1
R2-086029	LS on transport block size on BCH (R1-084063; to: RAN2; cc: -; contact: NTT DOCOMO)	RAN1
R2-086031	LS on RV Determination for BCCH (R1-084067; to: RAN2; cc: -; contact: NSN)	RAN1
R2-086032	LS on default value of ul-Bandwidth (R1-084068; to: RAN2; cc: -; contact: NEC)	RAN1
R2-086034	Response LS to S2-086378 = R2-084978 on Connection recovery by NAS (R3-082850; to: SA2, RAN2; cc: RAN1, CT1; contact: Vodafone)	RAN3
R2-086036	Reply LS to S3-081121 = R2-085772 = R2-086003 and S3-081175 = R2-085786 = R2-086009 on E-UTRAN security related issues (R3-082858; to: SA3, RAN2; cc: -; contact: Ericsson)	RAN3
R2-086037	LS response to C1-083626 =R2-084952 on NAS message concatenation and multiple EPS bearer setup (R3-082860; to: CT1, SA2; cc: RAN2; contact: Ericsson)	RAN3
R2-086038	LS on UE-EPC signalling (R3-082867; to: CT1, SA2; cc: SA3, RAN2; contact: NEC)	RAN3
R2-086039	LS on UE emission control (R4-082178; to: RAN1, RAN2; cc: -; contact: Verizon Wireless)	RAN4
R2-086040	Response LS to R2-083034 on value ranges and high quality criterion (R4-082620; to: RAN2, GERAN; cc: RAN1; contact: NTT DOCOMO)	RAN4
R2-086041	LS on EARFCN number range (R4-082638; to: RAN2; cc: RAN1; contact: CATT)	RAN4
R2-086042	Response LS to GP-081347 = R2-084957 on reporting E-UTRAN measurements (R4-082645; to: GERAN; cc: RAN2; contact: Nokia)	RAN4
R2-086043	LS measurement reporting in DRX (R4-082654; to: RAN2; cc: -; contact: Nokia)	RAN4
R2-086044	Response LS to R1-082252 = R2-083062 on indicating radio problem detection (R4-082655; to: RAN1, RAN2; cc: -; contact: Nokia)	RAN4
R2-086045	Reply LS to R2-084891 on reselection handling towards non-allowed CSG cell (R4-082656; to: RAN2; cc: -; contact: Qualcomm)	RAN4
R2-086046	Reply LS to R1-083364 = R2-084888 and R2-084897 on Consequence analysis of Low/ Medium features in LTE Rel-8 (R5-084203; to: RAN WG1, RAN WG2; cc: RAN WG4, RAN; contact: NTT DOCOMO)	RAN5
R2-086047	LS answer to S2-086405 = R2-084983 on Guidance for ARP Values (S1-083378; to: SA2; cc: RAN2, RAN3; contact: NSN)	SA1
R2-086048	Reply LS to C1-084474 = R2-086016 on allowed CSG list and Home Node B Name (S1-083395; to: CT1; cc: SA2, SA3, RAN2, RAN3, RAN5, CT4, CT6; contact: Samsung)	SA1
R2-086049	Reply LS to GP-081310 = R2-084956 on ETWS (S1-083435; to: GERAN; cc: SA2, SA3, CT1, RAN2, RAN3; contact: Ericsson)	SA1
R2-086050	Reply LS to R2-084916, R2-084894, C1-083625 = R2-084951 on HNB/HeNB Open Access Mode (S1-083461; to: RAN2, CT1; cc: RAN3, SA3; contact: Vodafone)	SA1
R2-086052	LS on handling of GERAN, UTRAN and E-UTRAN DRX parameters in SAE (S2-087301; to: RAN2, GERAN2, GERAN1, CT4, CT1; cc: -; contact: Vodafone)	SA2
R2-086053	Reply LS to R2-085973, C1-084468 = R2-086015, C4-083164 = R2-086024 on maximum PDCP SDU size (S2-087304; to: RAN2, SA3, CT1; cc: CT4; contact: Panasonic)	SA2
R2-086054	Response LS to R2-085972, R3-082850 = R2-086034, C1-084495 = R2-086018 on Connection recovery by NAS (S2-087325; to: CT1, RAN2; cc: RAN3; contact: NTT DOCOMO)	SA2
R2-086055	LS on QCI usage for SR VCC (S2-087342; to: RAN 2, RAN3; cc: -; contact: Ericsson)	SA2
R2-086056	LS on Transparent container for SRVCC (S2-087343; to: RAN3; cc: RAN2, GERAN2; contact: NSN)	SA2
R2-086057	Reply LS to R2-085963 on Duplicate Detection for ETWS (S2-087344; to: RAN2, GERAN2; cc: CT1, CT4, GERAN, RAN3; contact: NTT DOCOMO)	SA2
R2-086059	Reply LS to R3-082846 = R2-086033 on 3G HNB Management (S5-081927; to: RAN3; cc: SA2, RAN4, RAN2, Broadband Forum; contact: Vodafone)	SA5

R2-086954#	LS on discovered issues due to linking of Cell ID and CSG ID (R3-083384; to: CT1, RAN2 ; cc: SA2, CT4; contact: T-Mobile)
R2-086955#	Reply LS to R3-082858 = R2-086036 on "LS on E-UTRAN security related issues" (S3-081505; to: RAN3, RAN2; cc: -; contact: Nokia)
R2-086988#	LS on forward compatibility support in Rel-8 (R1-084538; to: RAN2; cc: RAN4; contact: Qualcomm)
R2-087111#@	LS on P_A value and L1 parameter range (R1-084514; to: RAN2; cc: -; contact: Panasonic)
R2-087112#	LS on CR for 36.300 (R1-084516; to: RAN2; cc: -; contact: CATT)
R2-087113#@	LS on removing delta_offset^PUCCH for PUCCH formats 1/1a/1b (R1-084517; to: RAN2; cc: -; contact: Qualcomm)
R2-087117#@	LS on radio link monitoring (R1-084566; to: RAN2, RAN4; cc: -; contact: Ericsson)
R2-087118#@	LS on UE emission control (R4-083197; to: RAN1; cc: RAN2; contact: Motorola)
R2-087284#@	LS on Common Test Environment (TS 36.508) (R5-085515; to: RAN1, RAN2, RAN4; cc: -; contact: NTT DOCOMO)
R2-087373#@	Reply LS to R2-086968 on preventing inter-RAT HO for UE with SIM access (S3-081589; to RAN2, RAN3, GERAN2, CT1, CT4; cc: -; contact: Huawei)
R2-087397#@	LS on support of ACK/NACK repetition in Rel-8 (R1-084649; to: RAN2, RAN4; cc: -; contact: Texas Instruments)
R2-087401#*	LS on Special Conformance Testing Functions for UE (TS 36.509) (R5-085540; to: RAN2; cc: -; contact: Rohde & Schwarz)


Agenda item 7.1: Incoming LSs on UTRA (all releases): 9 LSs
R2-086012$	Reply LS to S1-082418 = R2-084550 on UE-Aggregate Maximum Bit Rate for GERAN/UTRAN (G2-080614; to: SA1, SA2; cc: RAN3, RAN2, CT1, CT4; contact: Vodafone)	GERAN2
R2-086020	LS on Alignment of description in stage1, 2 and 3 regarding PPAC (C1-084497; to: SA1; cc: RAN2; contact: NTT DOCOMO)	CT1
R2-086030	LS on the HS-DPCCH structure for Dual-Cell HSDPA operation (R1-084066; to: RAN2, RAN3, RAN4; cc: -; contact: Ericsson)	RAN1
R2-086033	LS on 3G HNB Management (R3-082846; to: SA5; cc: SA2, RAN4, RAN2, Broadband Forum; contact: Vodafone)	RAN3
R2-086035	Reply LS to C1-083429 = R2-084948 on access control for CSG cells (R3-082853; to: CT1; cc: RAN2, CT4, SA2; contact: Qualcomm)	RAN3
R2-086051	Reply LS to S1-082418 = R2-084550 on UE-Aggregate Maximum Bit Rate for GERAN/UTRAN (S2-087288; to: SA1; cc: RAN3, RAN2, GERAN2, CT1, CT4; contact: Vodafone)	SA2
R2-086058	Reply LS to GP-080883 = R2-083051 regarding GAN Iu mode security (S3-080905; to: GERAN2; cc: RAN2, RAN3, CT1; contact: Alcatel-Lucent)	SA3

R2-087264#	LS on E-UTRAN cell detection in idle mode (R4-083221; to: RAN2; cc: -; contact: Telecom Italia)
R2-087365#*	LS on MBMS Improvement for HSPA Evolution (R3-083468; to: RAN2, SA2, CT4; cc: -; contact: Nokia Siemens Networks)


$: 11 LSs resubmitted from RAN2 #63bis:
R2-086002= R2-085771 = S3-081118
R2-086003= R2-085772 = S3-081121
R2-086004= R2-085773 = S3-081129
R2-086005= R2-085774 = S3-081130
R2-086006= R2-085775 = S3-081135
R2-086007= R2-085776 = S3-081138
R2-086008= R2-085777 = S3-081150
R2-086009= R2-085786 = S3-081175
R2-086010= R2-085857 = S3-081139
R2-086011= R2-085814 = R4-082585
R2-086012= R2-085910 = G2-080614

#: 14 LSs received during RAN2 #64:
R2-086954 = R3-083384
R2-086955 = S3-081505
R2-086988 = R1-084538
R2-087111 = R1-084514
R2-087112 = R1-084516
R2-087113 = R1-084517
R2-087117 = R1-084566
R2-087118 = R4-083197
R2-087264 = R4-083221
R2-087284 = R5-085515
R2-087365 = R3-083468
R2-087373 = S3-081589
R2-087397 = R1-084649
R2-087401 = R5-085540

65 of the 72 incoming LSs were treated during RAN2 #64,
*: 2 LS are for email discussion (actually their attachments are for email discussion)

@: 7 LSs were not treated and they will be resubmitted to the next meeting (RAN2 #64bis):
R2-087111 = R1-084514
R2-087113 = R1-084517
R2-087117 = R1-084566
R2-087118 = R4-083197
R2-087284 = R5-085515
R2-087373 = S3-081589
R2-087397 = R1-084649