incoming LSs for RAN2 #64bis in Ljubljana, Slovenia, 12.01.-16.01.2009:
status Wed 28.01.09 (40 incoming LSs)

Agenda item 5.1: Incoming LS to LTE:  34 LSs
R2-090003$	LS on P_A value and L1 parameter range (R1-084514; to: RAN2; cc: -; contact: Panasonic)	RAN1
R2-090004$	LS on removing delta_offset^PUCCH for PUCCH formats 1/1a/1b (R1-084517; to: RAN2; cc: -; contact: Qualcomm)	RAN1
R2-090005$	LS on radio link monitoring (R1-084566; to: RAN2, RAN4; cc: -; contact: Ericsson)	RAN1
R2-090006$	LS on UE emission control (R4-083197; to: RAN1; cc: RAN2; contact: Motorola)	RAN4
R2-090007$	LS on Common Test Environment (TS 36.508) (R5-085515; to: RAN1, RAN2, RAN4; cc: -; contact: NTT DOCOMO)	RAN5
R2-090008$	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)	SA3
R2-090009$	LS on support of ACK/NACK repetition in Rel-8 (R1-084649; to: RAN2, RAN4; cc: -; contact: Texas Instruments)	RAN1
R2-090010	LS on Interaction between PLMN selection and manual CSG selection (C1-085377; to: SA1; cc: RAN2; contact: Qualcomm)	CT1
R2-090011	LS on discovered issues due to linking of Cell ID and CSG ID (C1-085500; to: RAN3, CT4; cc: RAN2, SA2; contact: Qualcomm)	CT1
R2-090013	Reply-LS to S2-086392 = R2-084981 on Applicability of “subscriber type” indication for UTRAN & GERAN (GP-081804; to: RAN2, SA2, RAN3; cc: -; contact: NSN)	GERAN
R2-090014	LS on encoding of groups of PCI values (R1-081933; to: RAN2; cc: -; contact: NSN)	GERAN2
R2-090015	Reply LS to S2-087344 = R2-086057 on Duplicate Detection for ETWS (R1-081935; to: SA2, RAN2; cc: CT1, CT4, RAN3; contact: Ericsson)	GERAN2
R2-090016	Response to LS R2-087404 on Harmonisation of the absolute priority cell reselection parameters (GP-081958; to: RAN2, RAN4; cc: -; contact: NSN)	GERAN
R2-090017	Response to LS R2-084901 on scope and reference for parameter “sameRefSignalsInNeighbour” (R1-084672; to: RAN2; cc: RAN4; contact: Philips)	RAN1
R2-090018	LS on dependency analyses on feature lists (R1-084687; to: RAN2; cc: -; contact: NTT DOCOMO)	RAN1
R2-090021	Reply LS to S2-087342 = R2-086055 and S2-087343 = R2-086056 on Transparent container and QCI usage for SRVCC (R3-083567; to: SA2; cc: RAN2; contact: NSN)	RAN3
R2-090022	Reply LS to S3-081505 = R2-086955 on E-UTRAN security related issues (R3-083569; to: SA3, RAN2; cc: -; contact: NSN)	RAN3
R2-090023	LS on architecture for HeNB (R3-083572; to: CT1, CT4, RAN2, SA2, SA3, SA5; cc: -; contact: Qualcomm)	RAN3
R2-090024	Response LS to R2-085958 on Maximum allowed transmission power on the uplink (R4-083041; to: RAN2, GERAN; cc: RAN1; contact: NTT DOCOMO)	RAN4
R2-090025	Response LS to R1-080616 = R2-080653 on E-UTRA UL Power Control (R4-083264; to: RAN1, RAN2; cc: -; contact: NTT DOCOMO)	RAN4
R2-090026	Response LS to R1-084566 = R2-087117 on radio link monitoring (R4-083298; to: RAN1, RAN2; cc: -; contact: NTT DOCOMO)	RAN4
R2-090027	LS on new definitions of maximum UE output powers (R4-083317; to: RAN1, RAN2; cc: -; contact: Ericsson)	RAN4
R2-090028	LS on idle interval of LCR TDD for E-UTRAN cell monitoring (R4-083323; to: RAN2, RAN3; cc: RAN1; contact: CATT)	RAN4
R2-090029	Response to LS R2-084901 on scope and reference for parameter “sameRefSignalsInNeighbour” (R4-083331; to: RAN1, RAN2; cc: ; contact: Vodafone)	RAN4
R2-090033	Reply LS to C1-085377 = R2-090010 on Interaction between PLMN selection and manual CSG selection (S1-084231; to: CT1, RAN2; cc: -; contact: Qualcomm)	SA1
R2-090034	LS on Preferential CSG Cell Selection (S1-084239; to: RAN2; cc: -; contact: Vodafone)	SA1
R2-090035	Reply LS to R3-083567 = R2-090021 on question related to “policy to not perform “PS-PS” handovers in SRVCC” (S2-088306; to: RAN3; cc: RAN2; contact: NSN)	SA2
R2-090036	Reply LS on ETWS (S3-081495; to: GERAN; cc: RAN2, RAN3, CT1; contact: NTT DOCOMO)	SA3
R2-090037	Reply LS to R2-085973? on maximum PDCP SDU size (S3-081516; to: RAN2, CT1; cc: SA2, CT4; contact: Nokia)	SA3
R2-090038	Request for guidance on use of START in HO from E-UTRAN to UTRAN (S3-081521; to: RAN2; cc: -; contact: NSN)	SA3
R2-090039	LS on triggered HO events (S5-082452; to: RAN2; cc: -; contact: Huawei)	SA5
R2-090040	Response LS to R2-087431 on QoS measurements (S5-082474; to: RAN2; cc: -; contact: Huawei)	SA5

R2-090767#	Reply LS to GP-081935 = R2-090015 on Duplicate Detection for ETWS (S2-090723; to: GERAN2, RAN2, CT1; cc: CT4, RAN3; contact: NTT DOCOMO)	SA2
R2-090796#	Response LS to R2-087402 on preamble group selection based on radio link condition (R1-090494; to: RAN2; cc: -; contact: Texas Instruments)	RAN1

Agenda item 7.1: Incoming LSs on UTRA (all releases): 6 LSs
R2-090012	LS on Indication of mobile access network type/capabilities to IMS (C1-085549; to: RAN2, SA2; cc: -; contact: Orange)	CT1
R2-090019	Reply LS to S5-081927 = R2-086059 on 3G HNB Management (R3-083504; to: SA5; cc: SA2, RAN4, RAN2, Broadband Forum; contact: Vodafone)	RAN3
R2-090020	LS on paging optimisation via allowed CSG list in paging message (R3-083510; to: CT1; cc: SA2, RAN2; contact: NSN)	RAN3
R2-090030@	LS on enhancing radio bearer parameters in 34.108 for Improved Layer 2 UL (FDD) (R5-085542; to: RAN1, RAN2; cc: -; contact: Ericsson)	RAN5
R2-090031	LS on Expected UE behaviour in PMM-CONNECTED Mode (R5-085577; to: RAN2, CT1; cc: ; contact: Qualcomm)	RAN5
R2-090032@	LS on clarification on the UE behaviour in uplink when MAC i/is is configured (R5-085579; to: RAN2; cc: -; contact: Qualcomm)	RAN5


$: 7 LSs resubmitted from RAN2 #64:
R2-090003 = R2-087111 = R1-084514
R2-090004 = R2-087113 = R1-084517
R2-090005 = R2-087117 = R1-084566
R2-090006 = R2-087118 = R4-083197
R2-090007 = R2-087284 = R5-085515
R2-090008 = R2-087373 = S3-081589
R2-090009 = R2-087397 = R1-084649

#: 2 LSs received during RAN2 #64bis:
R2-090767 = S2-090723
R2-090796 = R1-090494

38 of the 40 incoming LSs were treated during RAN2 #64bis,
@: 2 LSs were not treated and they will be resubmitted to the next meeting (RAN2 #65):
R2-090030 = R5-085542
R2-090032 = R5-085579

*: 0 LS are for email discussion