{"text_format":"1","workbook":"xlsx","n_sheets":3,"sheets":["TDoc_List","CR_Packs_List","Parameters"],"not_rendered":{"charts":0,"images":0,"macros":1,"external_links":0,"defined_names":6,"comments":1,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"TDoc_List","index":0,"n_rows":107,"n_cols":32,"rows_kept":107,"cut":false,"hidden":false,"merged":[]}
["TDoc #","Title","Source","Contact","Contact ID","Type","Type supplement","For","Abstract","Secretary Remarks","Agenda item sort order","Agenda item #","Agenda item description","TDoc sort order within agenda item","TDoc Status","Reservation date","Uploaded","Is revision of","Revised to","Release","Spec #","Version","Related WIs","CR #","CR revision #","CR category","TSG CR Pack","Reply to","To","Cc","Original LS","Reply in"]
["S3i160000","Report from last meeting","BT Group Plc","Alex Leadbeater",23753,"report","","Approval","","","2","4","Last meeting report",0,"approved","2015-12-29T20:04:14.850","2016-01-18T17:26:50.357","","","","","","","","","","","","","","",""]
["S3i160001","Agenda","BT Group Plc","Alex Leadbeater",23753,"agenda","","Approval","","","1","3","Approval of the agenda",0,"revised","2015-12-29T20:06:14.267","2016-01-26T08:16:12.093","","S3i160065","","","","","","","","","","","","",""]
["S3i160002","Addition of definition","PIDS","Koen Jaspers",9291,"CR","","Decision","Addition of LI definition","","6","7.2","Release 13\t33.106 v13.2.0",0,"not pursued","2016-01-11T16:13:02.073","2016-01-11T16:22:57.570","","","Rel-13","33.106","13.2.0","","0149","","F",null,"","","","",""]
["S3i160003","LIV8: pCR - Overview of Lawful Interception Scenarios for LBO and S8HR","Nokia Networks","Nagaraja Rao",41611,"pCR","","Approval","Provides an overview of lawful interception scenarios when LBO and S8HR approaches are used as roaming architecture for VoLTE. The text, providing the background information, can be used as an Annex within the TR 33.827. \n\nAt the last meeting (SA3LI#59), a discussion paper was presented on the same topic and at that meeting, the SA3 LI proposal was to resubmit the contents as a pCR with additional LBO scenarios included. This pCR accommodates that proposal.","","11","10","Continued Discussion and New Business",0,"revised","2016-01-11T19:40:12.583","2016-01-11T19:48:10.643","","S3i160060","Rel-14","33.827","","FS_LIV8","","",null,"","","","","",""]
["S3i160004","Editorial clean up","PIDS","Koen Jaspers",9291,"CR","","Decision","","","8","8.2","Release 13\t33.107 v13.1.0",0,"revised","2016-01-14T09:24:39.037","2016-01-14T09:39:02.990","","S3i160067","Rel-13","33.107","13.1.0","","0193","","D",null,"","","","",""]
["S3i160005","Withdrawal of Old GSM LI Specifications","BT Group Plc","Alex Leadbeater",23753,"discussion","","Decision","Withdrawal of Old GSM LI Specifications","","11","10","Continued Discussion and New Business",0,"noted","2016-01-15T11:30:52.427","2016-01-18T17:22:50.697","","","Rel-13","","","","","","","","","","","",""]
["S3i160006","Scope Purpose Improvements","BT Group Plc","Alex Leadbeater",23753,"CR","","Approval","Scope Improvements to resolve second scope editor's note.","","6","7.2","Release 13\t33.106 v13.2.0",0,"revised","2016-01-15T11:36:00.417","2016-01-19T16:00:01.023","","S3i160073","Rel-13","33.106","13.2.0","","0150","","F",null,"","","","",""]
["S3i160007","SA3-LI Group Structure","BT Group Plc","Alex Leadbeater",23753,"discussion","","Decision","Discussion on possible changes to SA3-LI structure and organisation.","","11","10","Continued Discussion and New Business",0,"noted","2016-01-15T11:40:15.927","2016-01-19T20:34:37.700","","","","","","","","","","","","","","",""]
["S3i160008","Removing requirements from NOTEs","PIDS","Koen Jaspers",9291,"CR","","Decision","","","8","8.2","Release 13\t33.107 v13.1.0",0,"revised","2016-01-15T11:51:28.160","2016-01-15T11:55:08.290","","S3i160066","Rel-13","33.107","13.1.0","","0194","","F",null,"","","","",""]
["S3i160009","P-CR proposing additional Key Issue #10 to LIV Study","ORANGE","Lionel Thual",46478,"pCR","","Approval","during SA3LI #58 meeting, SA3LI agreed that there was a key issue related to the requirement for VPLMN to be able to prevent the use by a S8HR Roamer-In of confidentiality mechanisms (encryption of VoLTE signalling and media). This contribution is adding this key issue.","","11","10","Continued Discussion and New Business",0,"approved","2016-01-18T08:58:45.307","2016-01-18T10:19:25.487","","","Rel-14","","","","","",null,"","","","","",""]
["S3i160010","P-CR proposing additional Key Issue #11 to LIV Study","ORANGE","Lionel Thual",46478,"pCR","","Approval","LI solution for S8HR for VoLTE must have the capacity to implement Non Local Number Interception.This contribution is adding this key issue.","","11","10","Continued Discussion and New Business",0,"approved","2016-01-18T09:05:15.910","2016-01-18T10:19:25.533","","","","","","","","",null,"","","","","",""]
["S3i160011","FS-LIV8: pCR – Key Issue #9 Retained Data","Nokia Networks","Nagaraja Rao",41611,"pCR","","Approval","","","11","10","Continued Discussion and New Business",0,"noted","2016-01-18T17:09:22.090","2016-01-18T17:17:01.133","","","Rel-14","33.827","0.0.1","FS_LIV8","","",null,"","","","","",""]
["S3i160012","FS-LIV8: pCR – Key Issue #9 Retained Data Solution","Nokia Networks","Nagaraja Rao",41611,"pCR","","Approval","Provides a proposed solution to address the Data Retention capabilities in the VPLMN when S8HR based approach is used for VoLTE roaming.","","11","10","Continued Discussion and New Business",0,"noted","2016-01-18T17:13:27.133","2016-01-18T17:17:15.437","","","Rel-14","33.827","0.0.1","FS_LIV8","","",null,"","","","","",""]
["S3i160013","Liaison Report: PTSC LAES","Nokia Networks","Nagaraja Rao",41611,"report","","Information","","","3","5","Reports of other bodies which are relevant to SA3-LI",0,"noted","2016-01-18T17:14:54.990","2016-01-18T17:17:28.930","","","","","","","","","","","","","","",""]
["S3i160014","Text changes required from SA70 to 33.106 CR147 r8","Rogers Communications","Edward O'Leary",24518,"CR","","Approval","Proposed changes to address Note 5, 6 in SA70 SP request to SP150835","","6","7.2","Release 13\t33.106 v13.2.0",0,"revised","2016-01-18T17:20:19.470","2016-01-19T16:54:33.460","","S3i160090","Rel-13","33.106","13.2.0","LI13","0151","","F",null,"","","","",""]
["S3i160015","Text changes required from SA70 to 33.106 CR147 r8","Rogers Communications","Edward O'Leary",24518,"CR","","Approval","Proposed changes to address Note 7, 8 in Annex B in SA70 SP request to SP150835","","6","7.2","Release 13\t33.106 v13.2.0",0,"revised","2016-01-18T17:27:33.583","2016-01-19T16:54:33.413","","S3i160089","Rel-13","33.106","13.2.0","","0152","","F",null,"","","","",""]
["S3i160016","Text changes required from SA70 to 33.106 CR147 r8","Rogers Communications","Edward O'Leary",24518,"CR","","Approval","Proposed changes to address Note 3, 4 in SA70 SP request to SP150835, and minor edits","","6","7.2","Release 13\t33.106 v13.2.0",0,"revised","2016-01-18T17:32:13.180","2016-01-19T16:54:33.383","","S3i160088","Rel-13","33.106","13.2.0","","0153","","F",null,"","","","",""]
["S3i160017","ASN.1 Correction to have PacketDataSummaryReport in clause B.9","Nokia Networks","Nagaraja Rao",41611,"CR","","Approval","Two errors are corrected: one in clause B.3a (adding a “,” after the “…”) and another one in clause B.9 to have the correct name PacketDataSummaryReport.    \nThe error was discovered and correction was provided by Jean-Pascal  Chavanne (OFCOM).","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-18T19:18:44.523","2016-01-18T19:21:31.753","","S3i160034","Rel-13","33.108","13.0.0","LI13","0294","","F",null,"","","","",""]
["S3i160018","Correction in comment-part of ASN.1 for VoIP HI3 to refer to IMS-VoIP-Correlation","Nokia Networks","Nagaraja Rao",41611,"CR","","Approval","VoIP HI3 ASN.1 module has a reference pointing to a field “CorrelationValues” in HI2 that is not used for VoIP based on the recent changes. Even though the reference is in the comment-part of the ASN.1, it can still become the cause of a confusion.     \n\nThe reference in the comment-part is changed from “CorrelationValues” to “IMS-VoIP-Correlation”.","","10","9.2","Release  13  33.108 v13.0.0",0,"not pursued","2016-01-18T21:02:06.430","2016-01-18T21:04:17.517","","","Rel-13","33.108","13.0.0","LI13","0295","","F",null,"","","","",""]
["S3i160019","Legal Interception of Non Local Number","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","Decision","New clause describing stage 1 requirements on of Non Local Number, that are required by national regulations","","6","7.2","Release 13\t33.106 v13.2.0",0,"revised","2016-01-18T23:13:45.707","2016-01-19T21:57:34.957","","S3i160074","Rel-14","33.106","13.2.0","LI13","0154","","B",null,"","","","",""]
["S3i160020","Stage 2 Description of LI Functions in the VPLMN for IMS Roaming","Nokia Networks","Nagaraja Rao",41611,"CR","","Approval","A new clause is added to describe the LI functions in VPLMN for IMS roaming. Four new scenarios are added in Annex E. The details shown in Annex E are in the same style as the details shown for the other scenarios.     \n\nThe action item AP15-05 asks for raising CRs for 33.107/33.108 to address LBO. LBO is one of the roaming architecture for VoLTE and happens to be one of the examples of IMS roaming.  The functions required in the VPLMN to provide the lawful interception when S8HR approach is used as the roaming architecture for VoLTE is currently in study and this CR does not address that.","","8","8.2","Release 13\t33.107 v13.1.0",0,"revised","2016-01-19T01:35:01.927","2016-01-19T01:40:49.993","","S3i160056","Rel-13","33.107","13.1.0","LI13","0195","","B",null,"","","","",""]
["S3i160021","Discussion of Lawful Intercept definition","SPRINT Corporation","Greg Schumacher",35113,"discussion","","Decision","Continued discussion of what LEA services should be included as LI.","","11","10","Continued Discussion and New Business",0,"withdrawn","2016-01-19T06:09:49.743","2016-01-19T06:15:17.637","","","Rel-14","","","","","","","","","","","",""]
["S3i160022","P-CR proposing an additional reference point and cleanup","SPRINT Corporation","Greg Schumacher",35113,"pCR","","Decision","Addition of a reference point between the LPCG and the DF3 to inform the DF3 of mobility events where S-GW or BBIFF relocation occurs.","","11","10","Continued Discussion and New Business",0,"noted","2016-01-19T06:32:11.070","2016-01-19T06:35:48.113","","","Rel-14","","0.0.1","","","",null,"","","","","",""]
["S3i160023","P-CR proposing support of S-GW relocation and clarification for the network element clauses","SPRINT Corporation","Greg Schumacher",35113,"pCR","","Agreement","P-CR proposing support of S-GW relocation and clarification for the network element clauses in S8HR study","","11","10","Continued Discussion and New Business",0,"noted","2016-01-19T06:59:25.690","2016-01-19T07:01:13.143","","","Rel-14","","","","","",null,"","","","","",""]
["S3i160024","P-CR proposing an additional reference point in the architecture diagram","SPRINT Corporation","Greg Schumacher",35113,"pCR","","Agreement","Addition of a reference point between the LPCG and the DF3 to inform the DF3 of mobility events where S-GW or BBIFF relocation occurs in the S8HR study","","11","10","Continued Discussion and New Business",0,"noted","2016-01-19T07:03:22.107","2016-01-25T12:22:06.263","","","Rel-14","","","","","",null,"","","","","",""]
["S3i160025","Dynamic Codecs and VoLTE HI3 RTP interpretation","THALES","Eric Meilleray",24419,"discussion","","Decision","","","10","9.2","Release  13  33.108 v13.0.0",0,"noted","2016-01-19T09:10:38.273","2016-01-19T13:29:11.390","","","","","","","","","","","","","","",""]
["S3i160026","LS on Remote UE identities available to the UE-to-Network Relay UE","C1-160763","Mirko Cano Soveri",41957,"LS in","","","","","4","6","Generic incoming Liaisons",0,"noted","2016-01-19T09:39:12.140","2016-01-20T10:48:54.907","","","","","","","","","",""]
["S3i160027","LS on Mobile Equipment Identity Signalling over WLAN","C4-151756","Mirko Cano Soveri",41957,"LS in","","","","","4","6","Generic incoming Liaisons",0,"noted","2016-01-19T09:39:12.140","2016-01-20T10:48:54.797","","","","","","","","","",""]
["S3i160028","LS on ePDG Selection versus LI requirements","S2-154414","Mirko Cano Soveri",41957,"LS in","","","","","4","6","Generic incoming Liaisons",0,"noted","2016-01-19T09:39:12.140","2016-01-20T10:48:54.827","","","","","","","","","",""]
["S3i160029","LS on ePDG Selection versus LI requirements","SP-150831","Mirko Cano Soveri",41957,"LS in","","","","","4","6","Generic incoming Liaisons",0,"noted","2016-01-19T09:39:12.157","2016-01-20T10:48:54.873","","","","","","","","","",""]
["S3i160030","User Location Information reporting extensions over s2b","Ericsson LM","Maurizio Iovieno",23687,"CR","","","","","8","8.2","Release 13\t33.107 v13.1.0",0,"revised","2016-01-19T12:32:20.537","2016-01-19T15:48:08.060","","S3i160071","Rel-13","33.107","13.1.0","","0196","","B",null,"","","","",""]
["S3i160031","User Location Information reporting extensions over s2b","Ericsson LM","Maurizio Iovieno",23687,"CR","","","","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-19T12:35:52.413","2016-01-19T15:48:55.687","","S3i160072","Rel-13","33.108","13.0.0","","0296","","B",null,"","","","",""]
["S3i160032","TPKT – Connection Establishment Simplification","OTD","Selvam Rengasami",31626,"CR","","Approval","This contribution proposes simplification to the TPKT Connection Establishment Procedures to minimize LEMF and CSP impacts.","","9","9.1","Release 12 33.108 v12.11.0 and earlier",0,"revised","2016-01-19T14:37:18.773","2016-01-19T16:53:49.033","","S3i160051","Rel-12","33.108","12.11.0","","0297","","C",null,"","","","",""]
["S3i160033","Definition of Lawful Interception","NTT DOCOMO INC.","Alf Zugenmaier",52494,"CR","","","This CR provides a clear definition of lawful interception.","","6","7.2","Release 13\t33.106 v13.2.0",0,"not pursued","2016-01-19T15:24:10.077","2016-01-19T15:35:31.433","","","Rel-13","33.106","13.2.0","","0155","","F",null,"","","","",""]
["S3i160034","ASN.1 Correction to have PacketDataSummaryReport in clause B.9","Nokia Networks","Nagaraja Rao",41611,"CR","","Approval","Two errors are corrected: one in clause B.3a (adding a “,” after the “…”) and another one in clause B.9 to have the correct name PacketDataSummaryReport.    \nThe error was discovered and correction was provided by Jean-Pascal  Chavanne (OFCOM).       \n\nA few additional errors were discovered in the submitted CR and this revision takes care of them.","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-19T15:50:22.953","2016-01-19T15:52:39.030","S3i160017","S3i160055","Rel-13","33.108","13.0.0","LI13","0294","1","F",null,"","","","",""]
["S3i160035","Correction of GLIC to ULIC","OTD","Selvam Rengasami",31626,"CR","","Approval","The term “GLIC” is used in several places where the term ULIC should be used.  This is a historic leftover and needs to be corrected. All instances of “GLIC” are changed to “ULIC”. There will be incorrect references to GLIC which is not defined in the standard and certain features will not be implementable which can lead a CSP to not be able to meet its regulatory obligations.","","9","9.1","Release 12 33.108 v12.11.0 and earlier",0,"revised","2016-01-19T15:54:14.767","2016-01-19T16:54:25.193","","S3i160097","Rel-12","33.108","12.11.0","","0298","","F",null,"","","","",""]
["S3i160036","TPKT – Connection Establishment Simplification","OTD","Selvam Rengasami",31626,"CR","","Approval","Annex G on use of TPKT indicates that the TCP Connection may be established by the LEMF, however, normally this should be established by the MF.  There are no procedures for the LEMF to initiate such procedures.  In addition, there TPKT establishment procedures include many capability negotiation mechanisms, many of which are not needed for a simple implementation. Thus, simplification is proposed to not require the TPKT connection establishment negotiation mechanism.  Currently this mechanism is restricted to the U.S. which does not allow other regions to make use of it if so desired.","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-19T16:00:44.360","2016-01-19T16:54:25.240","","S3i160052","Rel-13","33.108","13.0.0","","0299","","A",null,"","","","",""]
["S3i160037","Correction of GLIC to ULIC","OTD","Selvam Rengasami",31626,"CR","","Approval","The term “GLIC” is used in several places where the term ULIC should be used.  This is a historic leftover and needs to be corrected. All instances of “GLIC” are changed to “ULIC”. There will be incorrect references to GLIC which is not defined in the standard and certain features will not be implementable which can lead a CSP to not be able to meet its regulatory obligations.","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-19T16:04:32.320","2016-01-19T16:54:25.270","","S3i160076","Rel-13","33.108","13.0.0","","0300","","A",null,"","","","",""]
["S3i160038","Inclusion Conditions for the Stage 2 in Clause 6","OTD","Selvam Rengasami",31626,"CR","","Approval","The inclusion conditions for parameters defined in the Stage 2, Clause 6 are not clear.  For example, mandatory parameters are listed incorrectly as conditional with no inclusion condition specified. Many conditional parameters have unstated inclusion conditions. All tables in Clause 6 are updated to clear indicate that parameters are mandatory with a straight shall requirement or for actual conditional parameters and inclusion condition is included. The standard can be implemented to leave out mandatory parameters that are incorrectly labeled as conditional which will then not allow an operator to meet their regulatory obligations of reporting all IRI and CC that they should be reporting.","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-19T16:09:24.023","2016-01-19T16:54:25.303","","S3i160079","Rel-13","33.108","13.0.0","","0301","","F",null,"","","","",""]
["S3i160039","Interception of ProSe Remote UE","OTD","Selvam Rengasami",31626,"CR","","Approval","Interception of the communications of a Prose Remote UE is not currently covered because, until recently, it was not feasible to identify the Remote UE in the core network.  However, SA2 at its Oct 2015 meeting developed a mechanism which enables the MME, S-GW, and P-GW to be able to identify the remote UE.","","8","8.2","Release 13\t33.107 v13.1.0",0,"revised","2016-01-19T16:40:11.380","2016-01-19T16:54:25.350","","S3i160094","Rel-13","33.107","13.1.0","","0197","","B",null,"","","","",""]
["S3i160040","LI Impacts of CUPS Work in SA2","OTD","Selvam Rengasami",31626,"discussion","","Discussion","SA2 is working on Control Plane User Plane Separation (CUPS) study and SA3-LI should consider the LI implications of CUPS in order to provide timely input to SA2 on their work.  This contribution intends to start this consideration process in SA3-LI.","","11","10","Continued Discussion and New Business",0,"noted","2016-01-19T18:47:00.807","2016-01-19T20:03:55.913","","","Rel-14","","","","","","","","","","","",""]
["S3i160041","Next Step On  Lawful Intercept of Non-Local Number for Stage 2 and 3","Ministère Economie Indu. Numer","Pierre Courbon",52806,"discussion","","Decision","As a draft CR is proposed on stage 1 (TS 33.106) to this SA3LI meeting, in order to prepare stage 2 and 3 of such LEAs need, or extension of the concept on Packet Data Multimedia Service / GSN Packet Data services domains, based on public external IP address, some points are proposed:","","11","10","Continued Discussion and New Business",0,"noted","2016-01-20T10:27:55.290","2016-01-20T10:32:18.540","","","Rel-14","","","","","","","","","","","",""]
["S3i160042","Alignment of HI2 and HI3 ASN.1 Correlation parameters for for VoIP","OTD","Selvam Rengasami",31626,"CR","","Approval","VoIP HI3 ASN.1 module has a reference pointing to a field “CorrelationValues” in HI2 that is not used for VoIP based on the recent changes. In fact, the this parameter is not aligned with that used for IRI for VoIP.  This is a compatibility issue which can cause confusion at the LEMF and needs to be corrected.  The ASN.1 type “CorrelationValues” is changed to to “IMS-VoIP-Correlation” and the “IMS-VoIP-Correlation” type is imported from the HI2 for EPS.            Can lead to incompatibility, mis-interpretation and possible wrong implementation and consequently hinder a CSP from meeting its regluatory obligations of providing correlated IRI and CC to the LE.","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-20T12:16:41.353","2016-01-20T13:22:43.760","","S3i160083","Rel-13","33.108","13.0.0","","0302","","F",null,"","","","",""]
["S3i160043","P-CR proposing text for key issue #1 IMEI targeting","SPRINT Corporation","Greg Schumacher",35113,"pCR","","Agreement","P-CR proposing text for key issue #1 IMEI targeting","","11","10","Continued Discussion and New Business",0,"noted","2016-01-20T12:41:25.823","2016-01-20T12:44:45.893","","","Rel-14","","","","","",null,"","","","","",""]
["S3i160044","P-CR proposing additional text for Introduction in LIV Study","Rogers Communications","Edward O'Leary",24518,"pCR","","Approval","Introduction of GATS","","11","10","Continued Discussion and New Business",0,"revised","2016-01-20T13:32:13.327","2016-01-20T13:47:47.777","","S3i160069","Rel-14","","","FS_LIV8","","",null,"","","","","",""]
["S3i160045","P-CR proposing text for Scope of LIV Study","Rogers Communications","Edward O'Leary",24518,"pCR","","Approval","Inclusion of GATS, localized HPLM services in VPLMN","","11","10","Continued Discussion and New Business",0,"revised","2016-01-20T13:34:39.140","2016-01-20T13:47:47.807","","S3i160068","Rel-14","","","FS_LIV8","","",null,"","","","","",""]
["S3i160046","P-CR proposing additional references for LIV Study","Rogers Communications","Edward O'Leary",24518,"pCR","","Approval","GATS References","","11","10","Continued Discussion and New Business",0,"approved","2016-01-20T13:37:46.137","2016-01-20T13:47:47.857","","","Rel-14","","","FS_LIV8","","",null,"","","","","",""]
["S3i160047","Location of the target 2G/3G CS clarifications","AQSACOM S.A.S.","Jerome GOUY",37768,"CR","","Approval","","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-20T13:42:19.790","2016-01-20T15:44:09.777","","","Rel-13","33.108","13.0.0","LI13","0303","","F","SP-160050","","","","",""]
["S3i160048","P-CR proposing additional Abbreviations in the LIV Study","Rogers Communications","Edward O'Leary",24518,"pCR","","Approval","GATS Abbrevations","","11","10","Continued Discussion and New Business",0,"approved","2016-01-20T13:43:11.020","2016-01-20T13:47:47.887","","","Rel-14","","","FS_LIV8","","",null,"","","","","",""]
["S3i160049","User Location Information clarification","AQSACOM S.A.S.","Jerome GOUY",37768,"CR","","Approval","Clarification of the information to be provided in the userLocationInfo parameter.","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-20T13:53:03.737","2016-01-20T15:44:30.917","","S3i160059","Rel-13","33.108","13.0.0","","0304","","F",null,"","","","",""]
["S3i160050","Editorial correction and clarifications for serviceCenterAddress and XmlCivicAddress","AQSACOM S.A.S.","Jerome GOUY",37768,"CR","","Approval","Clarification of the information to be provided for serviceCenterAddress parameter, the Calling or/and Called are not defined in partyinformation.\nEditorial correction for XmlCivicAddress information, reference to RFC 5139 is corrected from [yy] to [72].","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-20T15:55:57.093","2016-01-20T16:00:02.463","","","Rel-13","33.108","13.0.0","LI13","0305","","F","SP-160050","","","","",""]
["S3i160051","TPKT – Connection Establishment Simplification","OTD","Selvam Rengasami",31626,"CR","","Approval","Annex G on use of TPKT indicates that the TCP Connection may be established by the LEMF, however, normally this should be established by the MF.  There are no procedures for the LEMF to initiate such procedures.  In addition, there TPKT establishment procedures include many capability negotiation mechanisms, many of which are not needed for a simple implementation. Thus, simplification is proposed to not require the TPKT connection establishment negotiation mechanism.","","9","9.1","Release 12 33.108 v12.11.0 and earlier",0,"revised","2016-01-20T16:54:53.777","2016-01-20T17:09:50.567","S3i160032","S3i160084","Rel-12","33.108","12.11.0","","0297","1","F",null,"","","","",""]
["S3i160052","TPKT – Connection Establishment Simplification","OTD","Selvam Rengasami",31626,"CR","","Approval","Annex G on use of TPKT indicates that the TCP Connection may be established by the LEMF, however, normally this should be established by the MF.  There are no procedures for the LEMF to initiate such procedures.  In addition, there TPKT establishment procedures include many capability negotiation mechanisms, many of which are not needed for a simple implementation. Thus, simplification is proposed to not require the TPKT connection establishment negotiation mechanism.","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-20T16:59:03.687","2016-01-20T17:09:50.600","S3i160036","S3i160085","Rel-13","33.108","13.0.0","","0299","1","A",null,"","","","",""]
["S3i160053","TPKT – Application Beyond the U.S.","OTD","Selvam Rengasami",31626,"CR","","Approval","Annex G describes the use of TPKT for delivery of IRI and CC to the LEMF. Currently this mechanism is restricted to the U.S. which does not allow other regions to make use of it if so desired. Annex G is changed from a U.S. Annex to a more global Annex and is no longer informative.","","10","9.2","Release  13  33.108 v13.0.0",0,"not pursued","2016-01-20T17:06:06.897","2016-01-20T17:09:50.647","","","Rel-13","33.108","13.0.0","","0306","","C",null,"","","","",""]
["S3i160054","Clarification of Lawful Interception","VODAFONE Group Plc","Gerald McQuaid",25351,"CR","","Decision","Clarification of terms as per ETSI understanding and the reality of compliance","","6","7.2","Release 13\t33.106 v13.2.0",0,"not pursued","2016-01-20T22:27:29.177","2016-01-20T22:40:08.440","","","Rel-13","33.106","13.2.0","","0156","","D",null,"","","","",""]
["S3i160055","ASN.1 Correction to have PacketDataSummaryReport in clause B.9","Nokia Networks","Nagaraja Rao",41611,"CR","","Approval","Two errors are corrected: one in clause B.3a (adding a “,” after the “…”) and another one in clause B.9 to have the correct name PacketDataSummaryReport.    \nThe error was discovered and correction was provided by Jean-Pascal  Chavanne (OFCOM).       \n\nA few additional errors were discovered in the submitted CR and this revision takes care of them. The zip file S3i160034 accidentally had a blank file. So, whatever was supposed to be S3i160034.zip is in this TDoc.","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-22T15:58:27.050","2016-01-22T16:01:04.093","S3i160034","","Rel-13","33.108","13.0.0","LI13","0294","2","F","SP-160050","","","","",""]
["S3i160056","Stage 2 Description of LI Functions in the VPLMN for IMS Roaming","Nokia Networks","Nagaraja Rao",41611,"CR","","Approval","A new clause is added to describe the LI functions in VPLMN for IMS roaming. Four new scenarios are added in Annex E. The details shown in Annex E are in the same style as the details shown for the other scenarios.     \n\nThe action item AP15-05 asks for raising CRs for 33.107/33.108 to address LBO. LBO is one of the roaming architecture for VoLTE and happens to be one of the examples of IMS roaming.  The functions required in the VPLMN to provide the lawful interception when S8HR approach is used as the roaming architecture for VoLTE is currently in study and this CR does not address that. This revision incorporates the changes due to off-line comments received from OTD and Orange Labs.","","8","8.2","Release 13\t33.107 v13.1.0",0,"revised","2016-01-22T16:03:11.577","2016-01-22T20:07:41.893","S3i160020","S3i160075","Rel-13","33.107","13.1.0","LI13","0195","1","B",null,"","","","",""]
["S3i160057","P-CR proposing text for key issue #2 Public User identity targeting","SPRINT Corporation","Greg Schumacher",35113,"pCR","","Agreement","P-CR proposing text for key issue #2 Public User identity targeting","","11","10","Continued Discussion and New Business",0,"noted","2016-01-22T16:06:54.593","2016-01-22T16:08:37.490","","","Rel-14","","","","","",null,"","","","","",""]
["S3i160058","Response LS on ePDG Selection versus LI requirements","BlackBerry UK Limited","Nicholas Alfano",16849,"LS out","","Approval","Clarification of SA3-LI requirements for ePDG selection.","","16","13","Outgoing Liaisons",0,"noted","2016-01-22T16:28:35.560","2016-01-22T16:37:55.597","","","Rel-13","","","","","","",""]
["S3i160059","User Location Information clarification","AQSACOM S.A.S.","Jerome GOUY",37768,"CR","","Approval","Clarification of the information to be provided in the userLocationInfo parameter.\n\nAfter few exchange with several participants, the change affects also APN-AMBR parameter.","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-22T16:37:52.383","2016-01-22T16:44:48.823","S3i160049","","Rel-13","33.108","13.0.0","LI13","0304","1","F","SP-160050","","","","",""]
["S3i160060","LIV8: pCR - Overview of Lawful Interception Scenarios for LBO and S8HR","Nokia Networks","Nagaraja Rao",41611,"pCR","","Approval","Provides an overview of lawful interception scenarios when LBO and S8HR approaches are used as roaming architecture for VoLTE. The text, providing the background information, can be used as an Annex within the TR 33.827. \n\nAt the last meeting (SA3LI#59), a discussion paper was presented on the same topic and at that meeting, the SA3 LI proposal was to resubmit the contents as a pCR with additional LBO scenarios included. This pCR accommodates that proposal. This revision incorporates a few offline comments received from OTD and Orange Labs.","","11","10","Continued Discussion and New Business",0,"noted","2016-01-22T17:15:42.450","2016-01-22T20:06:03.053","S3i160003","","Rel-14","33.827","","FS_LIV8","","",null,"","","","","",""]
["S3i160061","LS on GSM LI Specification Withdrawal","BT Group Plc","Alex Leadbeater",23753,"LS out","","Approval","LS to SA on GSM LI Specification Withdrawal","","12","11.1","3GPP TR 41.033 V13.0.0 (2015-12) old 01.33",0,"approved","2016-01-25T11:23:20.390","2016-01-26T12:00:59.023","","","Rel-13","","","","","","",""]
["S3i160062","LS on SA3 LI Structure","BT Group Plc","Alex Leadbeater",23753,"LS out","","Approval","LS on SA3 LI Structure","","11","10","Continued Discussion and New Business",0,"withdrawn","2016-01-25T11:24:43.537",null,"","","Rel-13","","","","","","",""]
["S3i160063","P-CR on LIV-8 study for handover","NTT DOCOMO INC.","Alf Zugenmaier",52494,"pCR","","","Proposes a description and a solution for the key issue number #5.","","11","10","Continued Discussion and New Business",0,"revised","2016-01-25T11:45:07.740","2016-01-25T11:47:15.037","","S3i160070","","","","","","",null,"","","","","",""]
["S3i160064","Summary report ETSI TC-LI","PIDS","Koen Jaspers",9291,"other","","Information","Summary report ETSI TC-LI","","3","5","Reports of other bodies which are relevant to SA3-LI",0,"noted","2016-01-25T16:13:13.150","2016-01-25T16:15:42.203","","","","","","","","","","","","","","",""]
["S3i160065","Agenda","BT Group Plc","Alex Leadbeater",23753,"agenda","","Information","Agenda","","1","3","Approval of the agenda",0,"approved","2016-01-26T08:23:26.287","2016-01-26T08:24:15.050","S3i160001","","","","","","","","","","","","","",""]
["S3i160066","Removing requirements from NOTEs","PIDS","Koen Jaspers",9291,"CR","","Decision","","","8","8.2","Release 13\t33.107 v13.1.0",0,"agreed","2016-01-26T11:32:28.027","2016-01-28T08:12:18.920","S3i160008","","Rel-13","33.107","13.1.0","LI13","0194","1","F","SP-160050","","","","",""]
["S3i160067","Editorial clean up","PIDS","Koen Jaspers",9291,"CR","","Decision","","","8","8.2","Release 13\t33.107 v13.1.0",0,"agreed","2016-01-26T11:39:38.710","2016-01-27T13:31:13.913","S3i160004","","Rel-13","33.107","13.1.0","LI13","0193","1","D","SP-160050","","","","",""]
["S3i160068","P-CR proposing text for Scope of LIV Study","Rogers Communications","Edward O'Leary",24518,"pCR","","Approval","Inclusion of GATS, localized HPLM services in VPLMN, revised as an editor's note","","11","10","Continued Discussion and New Business",0,"noted","2016-01-26T17:27:54.027","2016-01-26T17:31:58.647","S3i160045","","Rel-14","","","FS_LIV8","","",null,"","","","","",""]
["S3i160069","P-CR proposing additional text for Introduction in LIV Study","Rogers Communications","Edward O'Leary",24518,"pCR","","Approval","Introduction of GATS, changes to text to make it clearer","","11","10","Continued Discussion and New Business",0,"revised","2016-01-26T17:41:13.927","2016-01-26T17:43:27.570","S3i160044","S3i160080","Rel-14","","","FS_LIV8","","",null,"","","","","",""]
["S3i160070","P-CR on LIV-8 study for handover","NTT DOCOMO INC.","Alf Zugenmaier",52494,"pCR","","","Proposes a description and a solution for the key issue number #5.","","11","10","Continued Discussion and New Business",0,"available","2016-01-26T17:59:07.277","2016-01-26T18:01:02.827","S3i160063","","","","","FS_LIV8","","",null,"","","","","",""]
["S3i160071","User Location Information reporting extensions over s2b","Ericsson LM","Maurizio Iovieno",23687,"CR","","","","","8","8.2","Release 13\t33.107 v13.1.0",0,"revised","2016-01-27T07:50:08.457","2016-01-27T17:13:45.307","S3i160030","S3i160081","Rel-13","33.107","13.1.0","","0196","1","B",null,"","","","",""]
["S3i160072","User Location Information reporting extensions over s2b","Ericsson LM","Maurizio Iovieno",23687,"CR","","","","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-27T07:51:09.407","2016-01-27T17:15:13.557","S3i160031","S3i160082","Rel-13","33.108","13.0.0","","0296","1","B",null,"","","","",""]
["S3i160073","Scope Purpose Improvements","BT Group Plc","Alex Leadbeater",23753,"CR","","Approval","Scope Improvements to resolve second scope editor's note.","","6","7.2","Release 13\t33.106 v13.2.0",0,"agreed","2016-01-27T10:55:57.037","2016-01-27T11:05:29.240","S3i160006","","Rel-13","33.106","13.2.0","LI13","0150","1","F","SP-160050","","","","",""]
["S3i160074","Legal Interception of non local identity","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","Decision","New clause describing stage 1 requirements on targeting of Non Local Identity, that are required by national regulations\nAnd new clause, to limit the maximum of simultaneous intercepted communications of target, requested by some local regulation","","6","7.2","Release 13\t33.106 v13.2.0",0,"agreed","2016-01-27T12:23:12.097","2016-01-28T14:10:03.820","S3i160019","","Rel-13","33.106","13.2.0","LI13","0154","1","B","SP-160050","","","","",""]
["S3i160075","Stage 2 Description of LI Functions in the VPLMN for IMS Roaming","Nokia Networks","Nagaraja Rao",41611,"CR","","Approval","A new clause is added to describe the LI functions in VPLMN for IMS roaming. Four new scenarios are added in Annex E. The details shown in Annex E are in the same style as the details shown for the other scenarios.     \n\nThe action item AP15-05 asks for raising CRs for 33.107/33.108 to address LBO. LBO is one of the roaming architecture for VoLTE and happens to be one of the examples of IMS roaming.  The functions required in the VPLMN to provide the lawful interception when S8HR approach is used as the roaming architecture for VoLTE is currently in study and this CR does not address that. This revision incorporates the changes due to off-line comments received from OTD and Orange Labs.","","8","8.2","Release 13\t33.107 v13.1.0",0,"revised","2016-01-27T13:37:17.357","2016-01-27T13:39:42.183","S3i160056","S3i160096","Rel-13","33.107","13.1.0","LI13","0195","2","B",null,"","","","",""]
["S3i160076","Correction of GLIC to ULIC","OTD","Selvam Rengasami",31626,"CR","","Approval","The term “GLIC” is used in several places where the term ULIC should be used.  This is a historic leftover and needs to be corrected.","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-27T16:04:31.007","2016-01-27T16:09:10.107","S3i160037","","Rel-13","33.108","13.0.0","LI12","0300","1","A","SP-160049","","","","",""]
["S3i160077","Authenticity of identifiers","NTT DOCOMO INC.","Alf Zugenmaier",52494,"CR","","Agreement","","","6","7.2","Release 13\t33.106 v13.2.0",0,"revised","2016-01-27T16:24:05.087","2016-01-27T16:25:56.707","","S3i160093","Rel-13","33.106","13.2.0","LI13","0157","","F",null,"","","","",""]
["S3i160078","Editorial clean up of SGN","OTD","Selvam Rengasami",31626,"CR","","Approval","Unclear abbriviation used, SGN instead of SGSN. Change SGN to SGSN","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-27T16:31:22.930","2016-01-27T16:33:38.510","","","Rel-13","33.108","13.0.0","LI13","0307","","F","SP-160050","","","","",""]
["S3i160079","Inclusion Conditions for the Stage 2 in Clause 6","OTD","Selvam Rengasami",31626,"CR","","Approval","The inclusion conditions for parameters defined in the Stage 2, Clause 6 are not clear.  For example, mandatory parameters are listed incorrectly as conditional with no inclusion condition specified. Many conditional parameters have unstated inclusion conditions. All tables in Clause 6 are updated to clearly indicate that parameters are mandatory with a straight shall requirement or for actual conditional parameters an inclusion condition is included.","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-27T16:41:15.850","2016-01-27T16:44:57.917","S3i160038","","Rel-13","33.108","13.0.0","LI13","0301","1","F","SP-160050","","","","",""]
["S3i160080","P-CR proposing additional text for Introduction in LIV Study","Rogers Communications","Edward O'Leary",24518,"pCR","","Approval","Introduction of GATS, changes to text to make it clearer, moving to annex","","11","10","Continued Discussion and New Business",0,"revised","2016-01-27T17:18:19.553","2016-01-27T17:26:19.533","S3i160069","S3i160099","Rel-14","","","FS_LIV8","","",null,"","","","","",""]
["S3i160081","User Location Information reporting extensions over s2b","Ericsson LM","Maurizio Iovieno",23687,"CR","","","","","8","8.2","Release 13\t33.107 v13.1.0",0,"agreed","2016-01-27T21:36:33.500","2016-01-28T07:37:18.957","S3i160071","","Rel-13","33.107","13.1.0","LI13","0196","2","B","SP-160050","","","","",""]
["S3i160082","User Location Information reporting extensions over s2b","Ericsson LM","Maurizio Iovieno",23687,"CR","","","","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-27T21:37:22.297","2016-01-28T07:37:58.807","S3i160072","","Rel-13","33.108","13.0.0","LI13","0296","2","B","SP-160050","","","","",""]
["S3i160083","Alignment of HI2 and HI3 ASN.1 Correlation parameters for VoIP","OTD","Selvam Rengasami",31626,"CR","","Approval","VoIP HI3 ASN.1 module has a reference pointing to a field “CorrelationValues” in HI2 that is not used for VoIP based on the recent changes. In fact, this parameter is not aligned with that used for IRI for VoIP.  This is a compatibility issue which can cause confusion at the LEMF and needs to be corrected.","","10","9.2","Release  13  33.108 v13.0.0",0,"revised","2016-01-28T08:17:47.750","2016-01-28T08:20:12.220","S3i160042","S3i160086","Rel-13","33.108","13.0.0","","0302","1","F",null,"","","","",""]
["S3i160084","TPKT – Connection Establishment Simplification","OTD","Selvam Rengasami",31626,"CR","","Approval","Annex G on use of TPKT indicates that the TCP Connection may be established by the LEMF, however, normally this should be established by the MF/DF.  There are no procedures for the LEMF to initiate such procedures.  In addition, the TPKT establishment procedures include many capability negotiation mechanisms, many of which are not needed for a simple implementation. In fact, the current specification allows the CSP and LEMF to implement different incompatible options.  Thus this CR proposes changes to simplify the delivery interface in such a way that assures compatibility.","","7","8.1","Release 12\t33.107 v12.13.0",0,"agreed","2016-01-28T08:33:23.633","2016-01-28T08:43:00.503","S3i160051","","Rel-12","33.107","12.13.0","LI12","0297","2","F","SP-160049","","","","",""]
["S3i160085","TPKT – Connection Establishment Simplification","OTD","Selvam Rengasami",31626,"CR","","Approval","Annex G on use of TPKT indicates that the TCP Connection may be established by the LEMF, however, normally this should be established by the MF/DF.  There are no procedures for the LEMF to initiate such procedures.  In addition, the TPKT establishment procedures include many capability negotiation mechanisms, many of which are not needed for a simple implementation. In fact, the current specification allows the CSP and LEMF to implement different incompatible options.  Thus this CR proposes changes to simplify the delivery interface in such a way that assures compatibility.","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-28T08:41:08.417","2016-01-28T08:43:00.597","S3i160052","","Rel-13","33.108","13.0.0","LI12","0299","2","A","SP-160049","","","","",""]
["S3i160086","Alignment of HI2 and HI3 ASN.1 Correlation parameters for VoIP","OTD","Selvam Rengasami",31626,"CR","","Approval","VoIP HI3 ASN.1 module has a reference pointing to a field “CorrelationValues” in HI2 that is not used for VoIP based on the recent changes. In fact, this parameter is not aligned with that used for IRI for VoIP.  This is a compatibility issue which can cause confusion at the LEMF and needs to be corrected.","","10","9.2","Release  13  33.108 v13.0.0",0,"agreed","2016-01-28T08:58:22.193","2016-01-28T09:00:34.683","S3i160083","","Rel-13","33.108","13.0.0","LI13","0302","2","F","SP-160050","","","","",""]
["S3i160087","Solving Lawful Intercept for LIPA/SIPTO: Providing Automated Capability to Notify Law Enforcement of Small Cell Broadband Provider","AT&T GNS Belgium SPRL","Peter Musgrove",28558,"discussion","","Discussion","Discussion contribution on providing automated notification to law enforcement of small cell broadband provider to assist operators to enable LIPA/SIPTO traffic offload capabilities from small cells","","11","10","Continued Discussion and New Business",0,"available","2016-01-28T09:05:56.633","2016-01-28T09:08:13.087","","","Rel-13","","","LI13","","","","","","","","",""]
["S3i160088","Text changes to address Note 4 provided in SP-150835","Rogers Communications","Edward O'Leary",24518,"CR","","Approval","Proposed changes to address Note 4 in SA70 SP request to SP150835, and minor edits","","6","7.2","Release 13\t33.106 v13.2.0",0,"agreed","2016-01-28T11:32:51.480","2016-01-28T11:36:13.843","S3i160016","","Rel-13","33.106","13.2.0","LI13","0153","1","F","SP-160050","","","","",""]
["S3i160089","Text changes to address Note 7, 8 in Annex B","Rogers Communications","Edward O'Leary",24518,"CR","","Approval","Proposed changes to address Note 7, 8 in Annex B in SA70 SP request to SP150835","","6","7.2","Release 13\t33.106 v13.2.0",0,"revised","2016-01-28T12:10:13.407","2016-01-28T13:16:18.697","S3i160015","S3i160100","Rel-13","33.106","13.2.0","","0152","1","F",null,"","","","",""]
["S3i160090","Proposed changes to address Note 5, 6","Rogers Communications","Edward O'Leary",24518,"CR","","Approval","Proposed changes to address Note 5, 6 in SA70 SP request to SP150835","","6","7.2","Release 13\t33.106 v13.2.0",0,"revised","2016-01-28T12:13:58.450","2016-01-28T12:33:04.683","S3i160014","S3i160101","Rel-13","33.106","13.2.0","LI13","0151","1","F",null,"","","","",""]
["S3i160091","Revised LI13 WID to include LI LCS","SPRINT Corporation","Greg Schumacher",35113,"WID revised","","Agreement","","","11","10","Continued Discussion and New Business",0,"agreed","2016-01-28T12:48:45.123","2016-01-28T13:20:53.567","","","Rel-13","","","","","","","","","","","",""]
["S3i160092","Clarification of \"Lawful Interception\"","BT Group Plc","Alex Leadbeater",23753,"CR","","Approval","Clarification of \"Lawful Interception\"","","6","7.2","Release 13\t33.106 v13.2.0",0,"agreed","2016-01-28T12:53:36.980","2016-01-28T12:57:57.250","","","Rel-13","33.106","13.2.0","LI13","0158","","F","SP-160050","","","","",""]
["S3i160093","Authenticity of identifiers","NTT DOCOMO INC.","Alf Zugenmaier",52494,"CR","","Agreement","","","6","7.2","Release 13\t33.106 v13.2.0",0,"agreed","2016-01-28T13:23:00.130","2016-01-28T13:26:04.737","S3i160077","","Rel-13","33.106","13.2.0","LI13","0157","1","F","SP-160050","","","","",""]
["S3i160094","Interception of ProSe Remote UE","OTD","Selvam Rengasami",31626,"CR","","Approval","Interception of the communications of a Prose Remote UE is not currently covered because, until recently, it was not feasible to identify the Remote UE in the core network.  However, SA2 at its Oct 2015 meeting developed a mechanism which enables the MME, S-GW, and P-GW to be able to identify the remote UE.","","8","8.2","Release 13\t33.107 v13.1.0",0,"agreed","2016-01-28T14:13:27.290","2016-01-28T14:15:53.243","S3i160039","","Rel-13","33.107","13.1.0","LI13","0197","1","B","SP-160050","","","","",""]
["S3i160095","DRAFT LS on impact on S8HR of regulations implementing WTO GATS Annex on Telecommunications","SPRINT Corporation","Greg Schumacher",35113,"LS out","","Agreement","[DRAFT] LS on impact on S8HR of regulations implementing WTO GATS Annex on Telecommunications","","11","10","Continued Discussion and New Business",0,"revised","2016-01-28T14:16:02.667","2016-01-28T14:19:34.217","","S3i160098","Rel-14","","","","","","",""]
["S3i160096","Stage 2 Description of LI Functions in the VPLMN for IMS Roaming","Nokia Networks","Nagaraja Rao",41611,"CR","","Approval","A new clause is added to describe the LI functions in VPLMN for IMS roaming. Four new scenarios are added in Annex E. The details shown in Annex E are in the same style as the details shown for the other scenarios.     \n\nThe action item AP15-05 asks for raising CRs for 33.107/33.108 to address LBO. LBO is one of the roaming architecture for VoLTE and happens to be one of the examples of IMS roaming.  The functions required in the VPLMN to provide the lawful interception when S8HR approach is used as the roaming architecture for VoLTE is currently in study and this CR does not address that. This revision incorporates the changes due to off-line comments received from OTD and Orange Labs.","","8","8.2","Release 13\t33.107 v13.1.0",0,"agreed","2016-01-28T14:16:47.780","2016-01-28T14:20:50.513","S3i160075","","Rel-13","33.107","13.1.0","LI13","0195","3","B","SP-160050","","","","",""]
["S3i160097","Correction of GLIC to ULIC","OTD","Selvam Rengasami",31626,"CR","","Approval","The term “GLIC” is used in several places where the term ULIC should be used.  This is a historic leftover and needs to be corrected.","","9","9.1","Release 12 33.108 v12.11.0 and earlier",0,"agreed","2016-01-28T14:22:55.517","2016-01-28T14:25:51.030","S3i160035","","Rel-12","33.108","12.11.0","LI12","0298","1","F","SP-160049","","","","",""]
["S3i160098","DRAFT LS on impact on S8HR of regulations implementing WTO GATS Annex on Telecommunications","SPRINT Corporation","Greg Schumacher",35113,"LS out","","Agreement","LS on impact on S8HR of regulations implementing WTO GATS Annex on Telecommunications","","11","10","Continued Discussion and New Business",0,"revised","2016-01-28T14:31:58.563","2016-01-28T14:53:51.063","S3i160095","S3i160102","Rel-14","","","","","","",""]
["S3i160099","P-CR proposing additional text for Introduction in LIV Study","Rogers Communications","Edward O'Leary",24518,"pCR","","Approval","Introduction of GATS, changes to text to make it clearer, moving to annex","","11","10","Continued Discussion and New Business",0,"approved","2016-01-28T14:44:20.667","2016-02-01T13:05:14.457","S3i160080","","Rel-14","","","FS_LIV8","","",null,"","","","","",""]
["S3i160100","Text changes to address Note 7, 8 in Annex B","Rogers Communications","Edward O'Leary",24518,"CR","","Approval","Proposed changes to address Note 7, 8 in Annex B in SA70 SP request to SP150835","","6","7.2","Release 13\t33.106 v13.2.0",0,"revised","2016-01-28T15:44:26.583","2016-01-28T15:55:16.757","S3i160089","S3i160103","Rel-13","33.106","13.2.0","","0152","2","F",null,"","","","",""]
["S3i160101","Proposed changes to address Note 5, 6","Rogers Communications","Edward O'Leary",24518,"CR","","Approval","Proposed changes to address Note 5, 6 in SA70 SP request to SP150835","","6","7.2","Release 13\t33.106 v13.2.0",0,"agreed","2016-01-28T15:50:04.447","2016-01-28T15:55:16.803","S3i160090","","Rel-13","33.106","13.2.0","LI13","0151","2","F","SP-160050","","","","",""]
["S3i160102","LS on impact on S8HR of regulations implementing WTO GATS Annex on Telecommunications","SPRINT Corporation","Greg Schumacher",35113,"LS out","","Agreement","LS on impact on S8HR of regulations implementing WTO GATS Annex on Telecommunications","","11","10","Continued Discussion and New Business",0,"approved","2016-01-28T15:56:22.790","2016-02-02T00:25:06.537","S3i160098","","Rel-14","","","","","","",""]
["S3i160103","Text changes to address Note 7, 8 in Annex B","SA3LI Chair","Alex Leadbeater",23753,"CR","","Approval","Proposed changes to address Note 7, 8 in Annex B in SA70 SP request to SP150835","","6","7.2","Release 13\t33.106 v13.2.0",0,"agreed","2016-02-05T09:41:26.617","2016-02-05T09:49:48.217","S3i160100","","Rel-13","33.106","13.2.0","LI13","0152","3","F","SP-160050","","","","",""]
["S3i160104","New version of TR 33.827 0.0.2 from SA 3 LI #60","SPRINT Corporation","Greg Schumacher",35113,"other","","Agreement","Baseline incorporating the agreed Tdocs from SA3 LI #60.","","11","10","Continued Discussion and New Business",0,"available","2016-02-09T01:56:00.487","2016-02-09T02:29:51.873","","","Rel-14","","0.0.2","","","","","","","","","",""]
["S3i160105","SA3LI MCC Support","3GPP SA3","Mirko Cano Soveri",41957,"LS in","","","","","4","6","Generic incoming Liaisons",0,"reserved","2016-04-27T15:23:08.627",null,"","","","","","","","","","","","","","",""]

{"sheet":"CR_Packs_List","index":1,"n_rows":1,"n_cols":11,"rows_kept":1,"cut":false,"hidden":false,"merged":[]}
["CR Pack TDoc #","WG TDoc #","WG TDoc decision","CR Individual TSG decision","Spec #","CR #","CR revision #","CR category","Release","Version","CR title"]

{"sheet":"Parameters","index":2,"n_rows":24,"n_cols":4,"rows_kept":24,"cut":false,"hidden":true,"merged":[]}
["Types of Tdocs","Possible statuses of Tdocs","Categories"]
[]
["agenda","reserved","A","Decision"]
["Work Plan","available","B","Agreement"]
["LS in","revised","C","Approval"]
["LS out","agreed","D","Information"]
["pCR","conditionally agreed","E","Discussion"]
["draftCR","approved","F","Action"]
["CR","conditionally approved",null,"Endorsement"]
["CR pack","partially approved",null,"Presentation"]
["ToR","treated"]
["WID new","endorsed"]
["WID revised","replied to"]
["SID new","merged"]
["SID revised","not pursued"]
["WI status report","postponed"]
["WI exception request","noted"]
["TS or TR cover","not concluded"]
["draft TS","withdrawn"]
["draft TR","reissued"]
["report"]
["discussion"]
["response"]
["other"]