[{"name":"CP-173114","title":"LS on V1 and V2 reference points","source":"5GAA WG2","contact":"Heejin Kim","contact-id":71611,"tdoctype":"LS in","for":"Information","abstract":"5GAA WG2 respectfully asks 3GPP SA to consider specifying a means of provisioning PC5 parameters for V2X via V1 and V2 interfaces.\nFurthermore, 5GAA WG2 is aware of 3GPP SA6 working in the area of Application Layer Support for V2X Services.  As a consequence, 5GAA WG2 would kindly ask 3GPP SA to keep 5GAA WG2 informed of any plans or other developments in this area of work.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:29:33","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA2, SA6, CT","lsoriginalls":"5GAA_A-170278","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173114.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173115","title":"Reply LS on the number of bearers","source":"CT1","contact":"Lalith Kumar","contact-id":60520,"tdoctype":"LS in","for":"Information","abstract":"CT1 would like to confirm that it would be feasible to extend EPS bearer IDs support to maximum of 15. Following impacts are identified so far:\n1.\tBelow IE needs changes:\na.\tEPS bearer context status IE reserved bits EBI (1) to EBI (4) shall be used. \nb.\tEPS Bearer ID reserved values EBI (1) to EBI (4) should be used.\n2.\tInterworking with A\/Gb or Iu mode.\n3.\tIndication of UE capability of supporting this new EPS bearer IDs.\n4.\tInterworking between legacy UE and new MME or between legacy MME and new UE. \n\nCT1 will inform SA2 if any other impacts are identified.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:33:20","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-176693\/ C1-173846","lsto":"SA2, RAN2","Cc":"CT4, RAN, CT, SA, SA1","lsoriginalls":"C1-174658","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173115.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173116","title":"LS on Status of Specifications Covering Requirements for IoT Modules","source":"CT1","contact":"Mikael Wass","contact-id":40034,"tdoctype":"LS in","for":"Information","abstract":"For the above specifications, support for LTE-M and NB-IoT was first added in Release 13, although please note that further releases also contain additional feature enhancements and corrections. \n3GPP CT1 would also point out that the above only is relevant to specifications for IoT Modules that are under the control of CT1 (responsible for the 3GPP specifications that define the User Equipment - Core network L3 radio\/core network protocols).  Further specifications within 3GPP RAN2, RAN5 and SA3 groups may be relevant related to radio interface definition, test case definitions and security related aspects.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:36:22","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-175067\/ TSGIoT03_0xx","lsto":"GSMA TSGIoT Subgroup","Cc":"3GPP TSG SA WG3, 3GPP TSG RAN WG2, 3GPP TSG RAN WG5, 3GPP TSG CT","lsoriginalls":"C1-175380","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173116.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173117","title":"Reply LS on 5G Charging Study Phase 1 on N4","source":"CT4","contact":"Yong Yang","contact-id":42295,"tdoctype":"LS in","for":"Information","abstract":"CT4 would like to inform SA5 that CT4 has decided to use the same protocol \u2013 Packet Forwarding Control Protocol which is used for Sx interface for N4, with some additions to support new 5G functionalities. PFCP already supports all the charging functionalities specified by SA5 for EPC.  \n\nCT4 would like to kindly remind SA5 that any new requirement that might impact the N4 protocol should be provided early enough, to allow CT4 to complete its Rel-15 protocol specification by June, 2018.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:40:12","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5","Cc":"SA2, CT, SA","lsoriginalls":"C4-175223","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173117.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173118","title":"Reply LS on the number of bearers","source":"CT4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"GTP-C currently allows to encode a maximum of 16 NSAPI values and 11 EPS Bearer Identity values. \n\n5 other values exist for the EPS bearer identity, but 1 value has a specific semantic and 4 values are \"reserved\" which could result in legacy entities rejecting messages with these values according to GTP-C error handling requirements. \n\nIt is possible to extend the maximum number of EPS bearer identities to 15 in Rel-15, with protocol changes potentially impacting the MME, SGW and PGW.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:42:35","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-176693","lsto":"SA2","Cc":"CT1, RAN2, RAN, CT, SA, SA1","lsoriginalls":"C4-175345","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173118.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173119","title":"LS Reply to 3GPP SA2 on Status Icon related to 5G","source":"GSM Association Future Networks Programme","contact":"Dongwook Kim","contact-id":66121,"tdoctype":"LS in","for":"Information","abstract":"3GPP SA2 and RAN2 are asked to: \n\u2022\tTake into consideration the above requirement regarding service indicators in the User Interface.\n\u2022\tVerify that the UE has all the information needed to determine which state it is in and the associated complexity and impact for such determination (e.g battery consumption, signalling and so on)","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:46:31","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-175303","lsto":"3GPP SA2, 3GPP RAN2","Cc":"3GPP SA, 3GPP SA1, 3GPP RAN, 3GPP CT1 , 3GPP CT","lsoriginalls":"LS reply to 3GPP SA2 onStatusIcon","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173119.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173120","title":"LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS   ON THE SCHEDULE FOR UPDATING RECOMMENDATION ITU-R M.2012  TO REVISION 4","source":"ITU Working Party 5D","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"This liaison provides guidance to External Organizations regarding updates of the terrestrial radio interfaces in the development of Revision 4 of Recommendation ITU-R M.2012 \u201cDetailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-Advanced (IMT-Advanced)\u201d.\nConfirmed meeting dates of WP 5D for 2018 and 2019 will be published on the ITU website (http:\/\/www.itu.int\/events\/upcomingevents.asp?sector=ITU-R&lang=en).","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:49:27","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"LS_EOs_5D_758_temp388r1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173120.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173121","title":"Further progress in development of the ITU-R Recommendation for the terrestrial components of the IMT-2020 radio interface(s)","source":"ITU Working Party 5D","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:51:23","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"LS_EOs_5D_758_temp394r1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173121.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173122","title":"Reply LS on the number of bearers","source":"RAN2","contact":"Sudeep Palat","contact-id":63872,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:53:45","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-176693","lsto":"SA2, CT1","Cc":"RAN, CT, SA, SA1, CT4","lsoriginalls":"R2-1712066","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173122.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173123","title":"LS on IMT-2020 submission","source":"RAN","contact":"Hans van der Veen","contact-id":12696,"tdoctype":"LS in","for":"Information","abstract":"TSG RAN has agreed on the name, format and schedule of the 3GPP IMT-2020 submission to ITU-R, which is captured in the attached document (RP-172098).","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:57:06","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA, RAN1, RAN2, RAN4, RAN5","Cc":"CT RAN6","lsoriginalls":"RP-172099","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173123.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173124","title":"Reply LS on the number of bearers","source":"SA2","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 has identified two potential alternative options for progressing the work. \nOption 1 would be to increase the number of EPS bearers to 11. In this case there would be no NAS impact and no work necessary in SA2. \nOption 2 would be to increase the number of EPS bearers to 15 or to align with number of bearers in NR subject to RAN2 decision. In this case there would be NAS impacts and work in SA2.\n\nSA2\u2019s preference is for a single option, i.e. Option 2. SA2 would also like to recommend completion within Release 15, subject to TSG approval.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 10:59:09","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R2-1712066, C1-174658, C4-175345","lsto":"RAN2, CT1, CT4, RAN, SA, CT","Cc":"SA1","lsoriginalls":"S2-179536","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173124.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173125","title":"LS on indicating service continuity usage of the additional IPv6 prefix in Router Advertisement","source":"SA2","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS in","for":"Information","abstract":"SA2 respectfully asks IETF Internet Area, DMM and 6MAN to provide feedback on any IETF work related to delivery of IP address type (according to IETF draft \"draft-ietf-dmm-ondemand-mobility-12\") in the Router Advertisement message.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 11:02:02","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF Internet Area, DMM, 6MAN","Cc":"CT, SA","lsoriginalls":"S2-179625","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173125.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173126","title":"LS on Available End-to-End Services over MBMS","source":"FSCOM","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 11:04:54","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"AE_enTV-MI_MTV"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA2, SA, CT3, CT","lsoriginalls":"S4-171020","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173126.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173127","title":"LS on Integration of northbound APIs with CAPIF","source":"SA6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Information","abstract":"TS 23.222 contains detailed specification of the common aspects of the API framework and the interactions with the CAPIF core function from both the API invoker and the API exposing function. TS 23.222 also includes an informative annex \u201cCAPIF relationship with network exposure aspects of 3GPP systems\u201d that shows CAPIF relationship with SCEF\/NEF, and possible integration models.Your review of this annex, and any feedback would help us in identifying any missing aspects to achieve better alignment in integration of CAPIF with the specification(s) of northbound APIs in 3GPP SA WG2.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 11:07:33","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"CAPIF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"SA, CT, SA4, CT3","lsoriginalls":"S6-171851","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173127.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173128","title":"LS on Establishment of SAE Cellular V2X Technical Committee and Associated Task Forces","source":"SAE C-V2X TC","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"The SAE C-V2X welcomes mutual consideration and communication as we jointly standardize applicable interoperability and performance specifications to fully leverage 4G LTE and 5G cellular radio access technologies.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 11:09:44","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, C-ITS, C-SAE, ISO TC204, IEEE 1609 WG, ETSI TC-ITS, IETF IPWAVE WG, ARIB, TTA, 5GAA, ITE, AASHTO (NTCIP Joint Committee, NEMA), ITU-T CITS, ITU-R SG5 WP5A SWG-ITS, ATIS, ITS Korea,, ERTICO, ITS Japan, ITS Canada","Cc":"","lsoriginalls":"SAE 12112017-1 - LS Announcing SAE C-V2X final","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173128.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173129","title":"LS on IPv6 work items","source":"ITU-T SG20","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"ITU-T SG20 would like to invite your experts to share and submit any relevant information and documents on the above-mentioned work items, including more specifically:\n-\tAny examples, models and use cases of IPv6 subnet addressing plans encompassing Internet of Things;\n-\tAny recommendations on IPv6 subnet addressing plan design.\nWe would appreciate very much receiving such inputs by 28 January 2018. \nITU-T SG20 looks forward to cooperating with the experts and to benefit from expertise in this domain.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 11:12:15","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA, 3GPPP, IPv6 Forum, IETF, ETSI IP6","Cc":"","lsoriginalls":"sp16-sg20-oLS-00060","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173129.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173130","title":"LS reply to ITU-T SG2 on Evolution of IMSI format and E.212 Recommendation","source":"GSM Association Technology Group","contact":"David Hutton","contact-id":33294,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-11 11:15:00","uploaded":"2017-12-11 11:16:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, 3GPP, WBA","Cc":"ITU-T SG20, SG13, SG3","lsoriginalls":"TG5 Doc 012","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173130.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173144","title":"This LS is a request for the status of specifications covering requirements for IoT modules","source":"GSMA","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"GSMA TSGIoT kindly asks for information regarding the state of current specifications covering requirements for IoT modules.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-12 08:44:36","uploaded":"2017-12-12 08:46:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG SMT, 3GPP CT1, 3GPP CT Plenary","Cc":"","lsoriginalls":"TSGIoT03_002_v3","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173144.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-173157","title":"LS on Removal of 'over LTE' limitation from Mission Critical Specifications","source":"SA1","contact":"Kees Verweij","contact-id":12756,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-12-18 10:55:43","uploaded":"2017-12-19 10:08:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"MCOver"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, SA3, SA4, SA5, SA6, CT1, CT3, CT4, CT6, RAN1, RAN2, RAN3, RAN4, RAN5, RAN6","Cc":"SA, CT, RAN","lsoriginalls":"S1- 174542","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_78_Lisbon\/Docs\/CP-173157.zip","group":"CP","meeting":"CP-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]