incoming LSs for RAN2 #62 in Kansas City, USA, 05.05.-09.05.2008:
status Fri 09.05.08 pm (43 incoming LSs)

Agenda item 4.1 Incoming LSs to LTE: 39 LSs

R2-082063	Reply LS to S3-080229 = R2-081918 and R2-082036 on outstanding NAS messages (C1-081386; to: SA3, RAN2; cc: -; contact: NSN)	CT1
R2-082064	Reply LS to R3-080547 = R2-081425 on LTE-cell- and eNB-identification (C1-081422; to: RAN3; cc: RAN2, SA2; contact: NSN)	CT1
R2-082065	Reply LS to R3-080979 = R2-082072 on frequency restrictions (C1-081427; to: RAN3; cc: RAN2, SA2; contact: Ericsson)	CT1
R2-082066	Reply LS to R2-082047 on NAS–AS interaction for dependent procedures (C1-081433; to: RAN2; cc: RAN3, SA2; contact: Qualcomm)	CT1
R2-082068	Reply LS to R2-080520 on SI-1 transmission (R1-081676; to: RAN2; cc: -; contact: Ericsson)	RAN1
R2-082069	LS on information about new PDCCH Format 1C (R1-081683; to: RAN2; cc: -; contact: Ericsson)	RAN1
R2-082071	LS on the necessity of to convey ‘Receive Status of UL PDCP SDU’ in S1 Handover (R3-080976; to: RAN2; cc: -; contact: NTT)	RAN3
R2-082072	LS on frequency restrictions (R3-080979; to: SA2, RAN2, CT1; cc: -; contact: Ericsson)	RAN3
R2-082073	Partial handover (R3-080982; to: SA2, RAN2; cc: -; contact: Ericsson)	RAN3
R2-082075	Reply LS to S5-080548 on neighbour relations and ANR function (R3-080987; to: SA5; cc: RAN2; contact: Qualcomm)	RAN3
R2-082076	Reply LS to C4-080449 on RAN3 requirements for GTPv2 (R3-080990; to: CT4; cc: SA2, RAN2; contact: Fujitsu)	RAN3
R2-082077	LS on S1 Overload Control (R3-080993; to: RAN3; cc: RAN2, SA2; contact: NSN)	RAN3
R2-082078	Response LS to GP-080395 = R2-081412 on various aspects related to GERAN to E-UTRAN interworking (R4-080839; to: GERAN; cc: RAN2; contact: Nokia)	RAN4
R2-082079	Reply LS to R2-080599 on UE specific paging DRX (S2-083103; to: RAN2; cc: CT1; contact: Ericsson)	SA2
R2-082080	LS reply to R2-081355 on “subscriber type” indication via S1 (S2-083105; to: RAN2; cc: RAN3; contact: Ericsson)	SA2
R2-082081	Reply LS to R2-075462 on ”Principles on Idle Mode Signalling Reduction” (S2-083116; to: RAN2; cc: CT1, CT4, RAN3; contact: NSN)	SA2
R2-082082	LS on SRVCC from EUTRAN to 1xRTT (S2-083147; to: RAN2; cc: -; contact: Nortel)	SA2
R2-082083	Reply to S4-080124 = R2-080666 on QoS Characterization for LTE/EPS (S2-083148; to: SA4; cc: RAN2; contact: Qualcomm)	SA2
R2-082084	Reply LS to S3a071047 on security for service request message (S2-083151; to: SA3; cc: RAN2; contact: NSN)	SA2
R2-082085	LS on Earthquake and Tsunami Warning System (S2-083168; to: RAN3, RAN2, RAN1, CT1, SA1, SA3, GERAN, GERAN2; cc: -; contact: NTT)	SA2
R2-082086	Reply LS to R2-081380 on inter-MME load balancing, Attach/TAU/Service Request procedures and corresponding RRC/S1 connection establishment procedures (S2-083171; to: RAN2; cc: RAN3, CT1, SA3; contact: NSN)	SA2
R2-082087	Reply LS to R3-080564 = R2-081427 on the necessity of Location Reporting procedure in S1 (S2-083174; to: RAN2, RAN3; cc: -; contact: NTT)	SA2
R2-082088	LS Request for Evaluation Framework Link Level Data (S4-080256; to: RAN1, RAN2; cc: -; contact: Qualcomm)	SA4
R2-082089	Reply LS to R2-080614 on Uplink Messaging Mechanism for LTE Dedicated Carrier MBMS Transmissions (S4-080275; to: RAN2; cc: SA2; contact: Vodafone)	SA4

R2-082090	LS on UE capability for DRS (R1-081692; to: RAN2; cc: RAN4; contact: China Mobile)	RAN1
R2-082091	LS about RAN1 decision regarding to the transmission of UL/DL allocation signal (R1-081696; to: RAN2; cc: -; contact: Nokia)	RAN1
R2-082092	LS on information about RAN1 assumptions regarding TPC-PDCCH (R1-081698; to: RAN2; cc: -; contact: Ericsson )	RAN1
R2-082094	LS on additional RSRP trigger for ICIC (R1-081704; to: RAN2; cc: RAN3; contact: Ericsson)	RAN1
R2-082095	LS on Transport Block Size (R1-081705; to: RAN2; cc: RAN4; contact: Motorola)	RAN1
R2-082096	LS on AS and NAS message protection (S3-080502; to: RAN2; cc: CT1; contact: NSN)	SA3
R2-082097	LS on key change on-the-fly (S3-080503; to: RAN2; cc: -; contact: Ericsson)	SA3
R2-082098	Follow up LS on Earthquake and Tsunami Warning System (S3-080522; to: RAN3, RAN2; cc: SA2; contact: NTT)	SA3
R2-082099	Reply LS on "outstanding NAS messages from RAN2 (R2-082036) and CT1 (C1-081386=R2-082063) (S3-080525; to: RAN2, CT1; cc: -; contact: NSN)	SA3
R2-082635	Reply LS to R2-082046 on security aspects on inter-system handover (S3-080526; to: RAN2; cc: -; contact: Ericsson)	SA3

5 LSs received during the meeting:
R2-082761	Reply LS to R2-081361 on retransmission of UL and DL NAS message during inter-eNB handovers (C1-081987; to: RAN2; cc: RAN3; contact: Qualcomm)	CT1
R2-082766	LS on power headroom reporting (R1-082096; to: RAN2; cc: RAN4; contact: Ericsson)	RAN1
R2-082833	RESPONSE LS to R2-080589 on value ranges of mobility IEs (R4-081188; to: RAN2, GERAN; cc: -; contact: NTT)	RAN4
R2-082834	LS reply to C1-081422 = R2-082064 and R2-082041 on E-UTRAN Identifiers (R3-081534; to: RAN2, CT1, CT4, SA2; cc: -; contact: NSN)	RAN3
R2-082855	Response LS to C4-081303 on RAN3 requirements for GTPv2 (R3-081532; to: CT4; cc: RAN2; contact: Ericsson)	RAN3


Agenda item 6.1 Incoming LSs on UTRA (all releases): 4 LSs

R2-082067	LS on Messaging Support for Network Based Location Technologies on User Plane (C4-081019; to: SA2, OMA LOC; cc: RAN2, RAN3; contact: Polaris Wireless)	CT4
R2-082070	Reply LS to R2-081969 on HS-DPCCH usage with Enhanced Uplink in Cell_FACH (R3-080963; to: RAN2; cc: RAN1; contact: NSN)	RAN3
R2-082074	LS on the Introduction of UE History Information in HSPA evolution (R3-080984; to: RAN2; cc: -; contact: Telecom Italia)	RAN3

R2-082093	LS on E-AICH Power Offset and Error Targets for AICH/E-AICH (R1-081702; to: RAN2, RAN3, RAN4; cc: -; contact: Qualcomm)	RAN1


40 of the 43 incoming LSs were treated during RAN2 #62.
 3 LSs were not treated, i.e. they are automatically postponed to the next meeting (RAN2 #62bis): R2-082833=R4-081188, R2-082834=R3-081534, R2-082855=R3-081532.