[{"name":"S1-162136","title":"Draft Reply LS on alternative authentication methods","source":"ORANGE","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answers: Q1: both are possible   Q2: some clarifications are provided, as requested   Q3: to manage access to public 3GPP networks, there is no need for alternative authentication methods or different type of credentials,   Q4: Alternative authentication methods may be relevant at the service\/application layer.","secretary_remarks":"There are different views on Q2.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40102,"status":"noted","reservation_date":"2016-08-11 22:06:08","uploaded":"2016-08-12 19:41:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG1_Serv\/Docs\/S1-162136.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162190","title":"Reply LS on alternative authentication methods and different types of credentials considerations for NextGen network","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"A different set of answers is provided by Qualcom.","secretary_remarks":"For Oberthur, the wording of the answer of Q3 is unclear: \"Alternative authentication methods \": \"alternative to what\"?   For Vodafone, the answer to Q4 is presenting the glass as half empty when it can be presented as half full: more cases and their requirements are to be defined when identified.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40103,"status":"revised","reservation_date":"2016-08-12 15:08:59","uploaded":"2016-08-12 20:41:09","revisionof":"","revisedto":"S1-162248","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG1_Serv\/Docs\/S1-162190.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162191","title":"Reply LS on normal emergency call for UE in eCall only mode","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to answer that: \"SA1 would like to respond that a UE in eCall only mode is not allowed to initiate a non-eCall IMS emergency call (e.g. an IMS emergency call for \"police\" type of emergency service). \"emergency call\" in TS 22.101 subclause 10.7 means \"eCall type of emergency call\".\"","secretary_remarks":"Agreed. A CR is to be created in S1-162260. The proposed LS is revised to include the proposed CR.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40502,"status":"revised","reservation_date":"2016-08-12 15:08:59","uploaded":"2016-08-12 20:41:09","revisionof":"","revisedto":"S1-162261","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG1_Serv\/Docs\/S1-162191.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162196","title":"Reply LS on Questions on alternative authentication methods and different types of credentials considerations for NextGen network","source":"Nokia","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Another set of answers is provided.","secretary_remarks":"The same comment on the use of the word \"alternative\" applies: it is unclear in the context it is used (alternative to what?).   The SA3 LI chair clarified that SA3 spent a lot of time on this topic.   The basic question is that \"is an IMSI-derived identity the only way to access the system?\". Also, if something different to AKA is needed, this has to be clearly mentioned by SA1.   Intel proposes to have further SMARTER discussions during this week before the answer is provided to SA3.   For Oberthur, the key question is indeed to define what are the methods needed, so the use of the word \"alternative\" is really the key problem.   For NEC and Ericsson, the requirements have to be further fine-tuned. For this, different cases have to be identified and specific requirements might have to be defined for each case.    To this respect, for NEC, \"Subscriber of the operator\" versus \"not subscriber\" might be a better wording for classification than \"IoT\" or not.   Several companies agree that the requirements related to authentication are not clear and detailed enough at this stage.   The SA3 LI chair indicated to SA1 that SA3 is expecting some clear guidance on all the possible ways to authenticate a user\/device in 5G: e.g. UICC-based only, UICC-based and something else, etc.   The preferred solution would be to attach the SMARTER TS in the reply LS.   The Qualcom proposal is the one to be used as a basis for drafting the answer - but the text has to be completely redrafted offline.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40104,"status":"noted","reservation_date":"2016-08-12 18:38:11","uploaded":"2016-08-12 21:11:06","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG1_Serv\/Docs\/S1-162196.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162199","title":"[DRAFT] Reply LS to SA4 on Codec for MCVideo","source":"Motorola Solutions","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Provides response to LS IN from SA4 (S4-160843) on Codec from MCVideo, providing the requested explanations.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40504,"status":"revised","reservation_date":"2016-08-12 19:27:43","uploaded":"2016-08-12 19:38:52","revisionof":"","revisedto":"S1-162262","release":"Rel-14","crspec":22.281,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG1_Serv\/Docs\/S1-162199.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162203","title":"LS on Comparison of TETRA, MCPTT, and North American LMR Terminology","source":"ATIS LMR\/LTE Interworking Ad hoc","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"Resubmission of S1-161247","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40505,"status":"noted","reservation_date":"2016-09-12 16:05:57","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162203.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162204","title":"Reply LS Regarding LTE support for V2X services","source":"SP-160150","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"Resubmission of S1-161257.   This is TTC's feedback on 3GPP TR 22.885 v2.0.0 reviewed by the members of Smart-Car SWG.","secretary_remarks":"Proposed answer in S1-162252.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40206,"status":"noted","reservation_date":"2016-09-12 16:05:57","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162204.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162205","title":"Reply LS on \"Next Generation\" Security Requirements","source":"S3-161182","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40098,"status":"noted","reservation_date":"2016-09-12 16:05:57","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162205.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162206","title":"LS on Questions on alternative authentication methods and different types of credentials considerations for NextGen network","source":"S3-161159","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"Four questions are asked in the filed of security and authentication methods for 5G.   Q1: SA3 asks SA1 to clarify whether the industrial factory owner operates its own 3GPP system for the factory services, whether it uses the MNO network or both scenarios are possible.   Q2: SA3 asks SA1 to clarify which deployment scenarios are envisioned in order to allow SA3 to define appropriate alternative authentication methods and different types of credentials, if needed   Q3: SA3 asks SA1 to clarify if those alternative authentication methods and different types of credentials are to be used to access the 3GPP network or the 3rd party service (e.g. factory service.)   Q4: SA3 asks SA1 to clarify whether those potential security considerations are to be taken into account only for authentication of subscriptions for IoT devices or also for subscribers who are human users, such as factory employees or both.","secretary_remarks":"There are 3 proposed answers to this LS: S1-162136, S1-162190 and S1-162196","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40101,"status":"noted","reservation_date":"2016-09-12 16:05:57","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162206.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162207","title":"LS to SA6 and SA1 on discreet listening and recording for MCPTT","source":"S3-161230","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"A set of question is asked by SA3 to SA1 and SA6.","secretary_remarks":"Proposed answer in S1-162264.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40506,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162207.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162208","title":"LS on normal emergency call for UE in eCall only mode","source":"C1-163875","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"CT1 asks SA1 to answer the following question:   Is a UE in eCall only mode allowed to initiate a non-eCall IMS emergency call (e.g. an IMS emergency call for \"police\" type of emergency service), in case such UE is equipped with an MMI and the user happens to dial an emergency call ?","secretary_remarks":"Proposed answer in S1-162191.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40501,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162208.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162209","title":"LS response to SA4 on progress of FS_xMBMS study item","source":"C3-162236","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40098,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162209.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162210","title":"Response Liaison Statement on 5G Capabilities and Requirements","source":"S3-161154","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40204,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162210.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162211","title":"LS on \"Next Generation\" Security Requirements","source":"S2-164280","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40098,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162211.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162212","title":"LS on Key capabilities and issues to be addressed for 5G","source":"NGMN Alliance","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"To ensure that the capabilities delivered by 5G are meaningful and timely, NGMN BPG invites 3GPP to consider the perspectives mentioned in the attached paper in defining the requirements and technology for 5G.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40201,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162212.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162213","title":"LS on progress of FS_xMBMS study item","source":"S4-160837","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"SA4 asked SA1, SA2, SA3, SA6 and CT3 to review the attached draft Technical Report on the study on \"MBMS Extensions for Provisioning and Content Ingestion\" and provide any feedback, in particular as it relates to any of your group's work areas.","secretary_remarks":"Proposed answer in S1-162265.   To state that a 3rd party API was done.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40507,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162213.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162214","title":"LS on the Codec for MCVideo","source":"S4-160843","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"SA4 asks SA1 to clarify the requirements for MC Video UE Clients in terms of encoding and decoding video frame size and frame rate. SA4 also asks SA1 to clarify the position with regard to \"tiering\" of MC Video UE clients and networks implementing MC Video and, depending upon the outcome, indicate which requirements apply to the different MC Video UE client and network tiers.","secretary_remarks":"Proposed answer in S1-162199.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40504,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162214.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162215","title":"Liaison Statement on 5G Capabilities and Requirements","source":"GSMA N2020_001","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"The GSMA's \"Network 2020 4G Evolution to 5G\" Execution Team, formed of 23 Operator members, is driven by commercial requirements to further develop the mobile network business model whilst ensuring that technical interoperability is sustained and that public policy and regulatory aspects are supported.    Network 2020 would like to inform 3GPP about this ongoing work to help mobile operators understand how network capabilities that are used for providing mobile services might evolve in the 5G era.   Specific areas of focus are:    Communication Services; Identities, Numbering and Addressing; Roaming; Interconnection; Security ; Network Orchestration","secretary_remarks":"The Chair reminded that company's contributions are invited.   Proposed acknowledgement LS in S1-162249.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40203,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162215.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162216","title":"LS on I-WLAN handling and specification withdrawal","source":"SP-160508","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"SA have decided on a path forward for handling I-WLAN specifications.   Specifications relating to I-WLAN not yet created for Rel-13 will not be created. All I-WLAN specifications apart from 33.234 will not be created in Release-14. A Specific handling within SA for Release-13 is defined and explained: SA1 is to create a CR to void the Release-13 version of TS 22.234 of technical content. Please replace Clauses \"Introduction\" & 1 with information about the discontinuation of the I-WLAN feature & alter Clause 2 to retain only references to the latest versions of I-WLAN specifications.","secretary_remarks":"This is done in S1-162185.   No need to answer since the CR will be sent to SA anyway.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40508,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162216.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162217","title":"Vertical industry application perspectives and implications for 5G","source":"NGMN Alliance","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"The NGMN Requirements and Architecture (P1) group has now developed its initial views on the vertical industry application perspectives and implications for 5G in growing interaction with, engagement of, and input from the verticals industries. NGMN P1 would like to share a document summarizing its current views on a number of selected vertical industry use cases.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40202,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162217.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162218","title":"Reply LS on \"Next Generation\" Security Requirements for RAN","source":"S3-160833","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40098,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162218.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162219","title":"LS on V2V Authorization","source":"R3-161540","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40305,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162219.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162220","title":"Reply LS on IMS Network Requirements regarding the provision of call progress indications","source":"C1-163118","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40601,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162220.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162221","title":"LS on eCall over IMS questions","source":"C1-162773","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40503,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162221.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162222","title":"Reply LS on EPC procedures for providing eNB with V2X authorization information","source":"R2-164498","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40306,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162222.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162223","title":"LS on Password based service activation for IMS Multimedia Telephony service (PWDIMS-CT)","source":"S3-160776","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40602,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162223.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162224","title":"Reply LS on V2X message characteristics","source":"S3-160777","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"No action for SA1.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40098,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162224.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162225","title":"LS on Clarification to privacy requirements","source":"S3-160789\/S1-161574","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"Attachement missing.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40301,"status":"revised","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"S1-162269","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162225.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162248","title":"Reply LS to SA3 on alternative authentication methods and different types of credentials considerations for NextGen network","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"This version includes the views from all interested companies in SA1.   It specifies in particular that \"The requirements for alternative authentication methods for network access is only intended for machine type devices used for e.g. IoT and industry automation.\"","secretary_remarks":"This should be re-written to be more restricted to non-human users.   Telecom Italia proposes to keep only the last 2 sentences in Question 1 (saying \"yes, both options are possible\"). This is accepted.   Architectural examples should be moved out but at the same time, some explanations have to be kept in the LS.   On Q2, the answer is slightly different from what the question is asking, but this is the closest SA1 can reach by consensus.   On Q3, there is no consensus on the sentence \"There is also a possible deployment scenario where alternative authentication methods are used at an overlay network for a service. \" so it should be deleted. Same with \"The first requirement above is about the network access and\"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40103,"status":"revised","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162190","revisedto":"S1-162526","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162248.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162249","title":"[DRAFT] LS on Response Liaison Statement to GSMA on 5G Capabilities and Requirements","source":"SA1","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answer to S1-162215\/GSMA N2020_001.   SA1 ask the \"GSMA Network 2020 4G Evolution to 5G Execution Team\" to provide any further 5G requirements, or refinements to the requirements stated in S1-162215, in the future.","secretary_remarks":"SA3 to be replaced by \"SA1\" in the first sentence.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40203,"status":"revised","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"S1-162527","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162249.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162252","title":"Reply LS to TTC (cc ARIB, SA) regarding LTE support for V2X services\/SP-160150\/f S1-161257","source":"SA1","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"SA1 is currently working on Stage-1 V2X Study (FS_eV2X) in Release 15 and expecting its Normative Work to follow. SA1 would like to encourage direct participations in this ongoing standardisation activity through 3GPP individual membership.","secretary_remarks":"The sentence \"By the nature \u2026\" can be deleted.   The LS is also proposed to be simplified.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40206,"status":"revised","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"S1-162529","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162252.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162259","title":"LS on MCPTT over LTE feature addition through modification of TS 22.280 requirements","source":"SP-160469","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"SA asks SA6 to use the approved TS 22.280 for Release 14, and asks SA1 to consider a CR in the SA1#75 meeting to provide traceability for the feature addition.","secretary_remarks":"S1-162009 is the corresponding contribution.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40603,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162259.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162260","title":"Clarification of mobility management procedures for UEs in eCall mode","source":"Deutsche Telekom","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"CR to reflect the clarification in S1-162191.","secretary_remarks":"Add clauses affected on the cover page.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40502,"status":"revised","reservation_date":"2016-09-12 16:05:45","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"S1-162532","release":"Rel-14","crspec":22.101,"crspecversion":"14.3.0","workitem":[{"winame":"EIEI"}],"crnumber":519.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162260.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162261","title":"Reply LS to CT1 (cc SA2) on normal emergency call for UE in eCall only mode","source":"SA1\/t-mobile","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"The CR clarifying the requirement is sent to CT1, as per their request,","secretary_remarks":"The attachment is the previous version of the CR.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40502,"status":"revised","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162191","revisedto":"S1-162533","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162261.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162262","title":"[DRAFT] Reply LS to SA4 (cc SA6) on Codec for MCVideo","source":"Motorola Solutions","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Some rewording is proposed for clarification purposes.","secretary_remarks":"Revision marks to be agreed.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40504,"status":"revised","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162199","revisedto":"S1-162534","release":"Rel-14","crspec":22.281,"crspecversion":"","workitem":[{"winame":"MCImp-MCVideo"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162262.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162264","title":"Reply LS to SA3 on questions on discreet listening and recording for MCPTT","source":"SA1","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed LS reply to SA6 and SA1 on discreet listening and recording for MCPTT\/S3-161230\/S1-162207","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40506,"status":"agreed","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162264.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162265","title":"[DRAFT] LS to SA4 (cc SA2, SA3, SA6, CT3) on progress of FS_xMBMS study item","source":"SA1\/NEC","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answer to S1-162213","secretary_remarks":"Clean-up needed.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40507,"status":"revised","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"","revisedto":"S1-162535","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162265.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162269","title":"LS on Clarification to privacy requirements","source":"S3-160789\/S1-161574","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40301,"status":"noted","reservation_date":"2016-09-12 16:05:58","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162225","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162269.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162526","title":"Reply LS to SA3 on alternative authentication methods and different types of credentials considerations for NextGen network","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"There are still some concerns in particular from AT&T.   This was further edited while projecting.","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40103,"status":"revised","reservation_date":"2016-09-12 16:05:59","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162248","revisedto":"S1-162555","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162526.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162527","title":"LS on Response Liaison Statement to GSMA on 5G Capabilities and Requirements","source":"SA1","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answer to S1-162215\/GSMA N2020_001","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40203,"status":"agreed","reservation_date":"2016-09-12 16:05:59","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162249","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162527.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162529","title":"Reply LS to TTC (cc ARIB, SA) regarding LTE support for V2X services\/SP-160150\/f S1-161257","source":"SA1","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40206,"status":"agreed","reservation_date":"2016-09-12 16:05:59","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162252","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162529.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162532","title":"Clarification of mobility management procedures for UEs in eCall mode","source":"Deutsche Telekom","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40502,"status":"agreed","reservation_date":"2016-09-12 16:05:55","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162260","revisedto":"","release":"Rel-14","crspec":22.101,"crspecversion":"14.3.0","workitem":[{"winame":"EIEI"}],"crnumber":519.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-160541","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162532.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162533","title":"Reply LS to CT1 (cc SA2) on normal emergency call for UE in eCall only mode","source":"SA1\/t-mobile","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40502,"status":"agreed","reservation_date":"2016-09-12 16:05:59","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162261","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162533.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162534","title":"Reply LS to SA4 (cc SA6) on Codec for MCVideo","source":"SA1\/Motorola Solutions","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40504,"status":"agreed","reservation_date":"2016-09-12 16:05:59","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162262","revisedto":"","release":"Rel-14","crspec":22.281,"crspecversion":"","workitem":[{"winame":"MCImp-MCVideo"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162534.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162535","title":"LS to SA4 (cc SA2, SA3, SA6, CT3) on progress of FS_xMBMS study item","source":"SA1\/NEC","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40507,"status":"agreed","reservation_date":"2016-09-12 16:05:59","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162265","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162535.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162555","title":"Reply LS to SA3 on alternative authentication methods and different types of credentials considerations for NextGen network","source":"SA1\/Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"2555 was agreed as the result of online drafting, but the chairman made a mistake and uploaded a wrong version of the LS reflecting earlier online drafting.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40103,"status":"revised","reservation_date":"2016-09-12 16:05:59","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162526","revisedto":"S1-162559","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162555.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-162559","title":"Reply LS to SA3 on alternative authentication methods and different types of credentials considerations for NextGen network","source":"SA1\/Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"4","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":40103,"status":"agreed","reservation_date":"2016-09-12 16:05:59","uploaded":"2016-09-12 16:07:25","revisionof":"S1-162555","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_75_SanFrancisco\/docs\/S1-162559.zip","group":"S1","meeting":"S1-75","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]