[{"name":"CP-181137","title":"Reply LS on SoR mechanism","source":"CT1","contact":"Christian Herrero-Veron","contact-id":45210,"tdoctype":"LS in","for":"Information","abstract":"First of all, CT1 thank SA3-LI for their LS on SoR mechanism and the information provided.\nSecondly, CT1 would like to inform SA3-LI that CT1 have analyzed all information provided and decided not to use any message used for authentication procedure to convey the priority list to the roaming UE, and therefore avoiding any lawful interception (LI) incompatibility. \nFinally, CT1 have modified the solution (see attached CR) so that lawful interception (LI) incompatibilities are avoided.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-06-01 18:58:40","uploaded":"2018-06-01 19:17:52","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S3i180141","lsto":"3GPP SA WG3-LI (SA3-LI)","Cc":"3GPP SA WG1, 3GPP SA WG2, 3GPP SA WG3, 3GPP SA, 3GPP CT WG3, 3GPP CT","lsoriginalls":"C1-182829","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_80_La_Jolla\/Docs\/CP-181137.zip","group":"CP","meeting":"CP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-181138","title":"LS\/o on Invitation to update the information in the IMT2020 roadmap [to ITU study groups and external IMT-2020 liaison partners]","source":"JCA-IMT2020","contact":"Kimmo Kymalainen","contact-id":19464,"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":"2018-06-01 19:01:26","uploaded":"2018-06-01 19:17:52","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"JCA-IMT2020-O-005","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_80_La_Jolla\/Docs\/CP-181138.zip","group":"CP","meeting":"CP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-181139","title":"LS on Removal of LTE specific terminology from Group Communication System Enablers TS 22.468","source":"SA1","contact":"J\u00fcrgen Merkel","contact-id":68393,"tdoctype":"LS in","for":"Information","abstract":"3GPP SA1 would like to inform SA2, SA3, SA4, SA5, SA6, CT1, CT3, CT4, CT6, RAN1, RAN2, RAN3, RAN4, RAN5 and RAN6 that SA1 has agreed on the attached CRs that \n-\tchange the title of the stage 1 specification Group Communication System Enabler TS 22.468 by removing \"for LTE\"; and\n-\tapply related updates to the wording in the specifications to clarify that the requirements are applicable from LTE onwards.\nThe background of the changes is that Mission Critical user organisations intend to take advantage of the continuous evolution of 3GPP systems while enhancing MC Services, i.e. MCPTT, MCVideo and MCData which are based on 22.468 functionality, and adding new mission critical services over such continuously evolving 3GPP systems. The changes in the attached CR should make it clear that the requirements specified in 3GPP stage 1 Technical Specification of Group Communication System Enabler are not restricted to LTE.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-06-01 19:04:11","uploaded":"2018-06-01 19:17:52","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-181249","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_80_La_Jolla\/Docs\/CP-181139.zip","group":"CP","meeting":"CP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-181140","title":"LS on SoR mechanism","source":"S3-LI","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"\u2022\tThere is an LI requirement to capture all data sent to and from the target. Any exchange of data prior the authentication of the target UE will not meet LI requirements;\n\u2022\tThe mechanism creates a potential end-to-end encrypted channel between the UE and the HPLMN which could be extended to allow the delivery of information other than or in addition to preferred PLMN roaming list as intended by CT1. This creates a capability that could be exploited to bypass LI in future.\nTo meet LI requirements any mechanisms to be used must occur after successful authentication of the UE. Any mechanism selected by CT1 would need to either turn off end-to-end confidentiality protection (both end-to-end integrity and the VPLMN applied confidentiality over the RAN are acceptable) or to strictly limit the information (i.e. the preferred PLMN roaming list), sent to the UE using the SoR mechanism.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-06-01 19:06:45","uploaded":"2018-06-01 19:17:52","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S3-180557, C1-180761","lsto":"CT1, SA2, SA3","Cc":"CT, CT3, SA, SA1","lsoriginalls":"S3i180141","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_80_La_Jolla\/Docs\/CP-181140.zip","group":"CP","meeting":"CP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-181141","title":"LS reply to ITU-T SG5 (Q6\/5) (SG5-TD476-R2) on Energy Efficiency","source":"SA5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"This liaison answers Liaison Statement sp16-sg5-oLS-00052 from ITU-T SG5 Q6\/5 to 3GPP SA WG5.\n\n3GPP SA5 would like to thank ITU-T SG5 for their reply.\n\n3GPP SA5 would like to remind ITU-T SG5 that the responsibility matrix proposed by 3GPP SA5 is for discussion amongst concerned parties, and 3GPP SA5 welcomes any suggestions to improve it.\n\n3GPP SA5 would like to provide the following feedback to ITU-T SG5\u2019s comments \/ questions.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-06-01 19:10:52","uploaded":"2018-06-01 19:17:52","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SG5-TD476-R2","lsto":"ITU-T SG5 Q6\/5","Cc":"3GPP SA, 3GPP CT, 3GPP RAN, ETSI TC EE, ETSI TC ATTM, NGMN","lsoriginalls":"S5-182439","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_80_La_Jolla\/Docs\/CP-181141.zip","group":"CP","meeting":"CP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-181142","title":"Reply LS on V1 and V2 reference points","source":"SA Plenary","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"With respect to the 5GAA WG2 requests on provision PC5 parameters for V2X operations via V1 and V2 reference points, 3GPP SA approved the SA WG2 CR to TS 23.285 capturing the following points:\n1) The parameters for V2X communications over PC5 reference point may be also provisioned to the UE from the V2X Application Server via V1 reference point.\n2) The parameters for V2X communications over PC5 reference point may be also provided to the V2X Control Function from the V2X Application Server via V2 reference point.\n3) The parameters for V2X communications over PC5 reference point from V2X Control Function always takes precedence.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-06-01 19:13:19","uploaded":"2018-06-01 19:17:52","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"V2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-180003","lsto":"5GAA WG2","Cc":"3GPP SA WG2, 3GPP SA WG6, 3GPP CT","lsoriginalls":"SP-180233","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_80_La_Jolla\/Docs\/CP-181142.zip","group":"CP","meeting":"CP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-181143","title":"Reply LS on Statement on urgency of alignment of ETSI SSP with 3GPP release 15","source":"SA Plenary","contact":"David Hutton","contact-id":33294,"tdoctype":"LS in","for":"Information","abstract":"3GPP TSG SA would like to advise GSMA TG that SA3 are currently specifying the \u201cSecurity architecture and procedures for 5G System\u201d within 3GPP TS 33.501.  A Release 15 version of this specification has been approved in the TSG SA#79 plenary meeting in March 2018.  SA Plenary advise GSMA TG that there is currently no linkage between the Release 15 version of 3GPP TS 33.501 and ETSI SSP in the normative text.  However, 3GPP do not see that the work of ETSI SSP is Release dependent and\/or relevant to the 5G system only.\n\nAs indicated in 3GPP TS 33.501 clause 6.1.1 (Authentication Framework) \u201cThe USIM shall reside on a UICC. The UICC may be removable or non-removable\u201d.  However, it is acknowledged within an Editor\u2019s Note that \u201cThe SSP can be included as another solution where the USIM can reside on, if the SSP is defined in the Release 15 timeframe and if it complies with the security requirements defined in the present document\u201d.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-06-01 19:16:29","uploaded":"2018-06-01 19:17:52","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"GSMA TG Doc 07_022","lsto":"GSMA Technology Group, 3GPP SA3","Cc":"ETSI TC SCP, 3GPP CT, 3GPP CT6","lsoriginalls":"SP-180240","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_80_La_Jolla\/Docs\/CP-181143.zip","group":"CP","meeting":"CP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-181146","title":"LS out to CT4 on 5G GUTI and EPS Interworking","source":"SA2","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS in","for":"Discussion","abstract":"1)\t8 bits length AMF Region, \n2)\t10 bits length AMF Set ID, \n3)\t6 bits length AMF Pointer \n4)\t5G-TMSI of 32 bits length. \n\nSA2 also discussed about the need for standardizing which part of the 5G-S-TMSI is used for supporting PLMN differentiation for network sharing scenarios, however SA2 could not reach any agreement on this.\n\nSA2 also requests CT4 adopt the mapping rules for EPS \u2013 5GS interworking as agreed in TS 23.501 CR 0206:\n-\t5G <MCC> maps to EPS <MCC>\n-\t5G <MNC> maps to EPS <MNC>\n-\t5G <AMF Region ID> and 5G <AMF Set ID> maps to EPS <MMEGI> and part of EPS <MMEC>\n-\t5G <AMF Pointer> map to part of EPS <MMEC>\n-\t5G <5G-TMSI> maps to EPS <M-TMSI>","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-06-03 08:05:31","uploaded":"2018-06-03 08:07:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4, RAN3, SA5, CT","Cc":"CT1, SA, RAN2","lsoriginalls":"S2-186176","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_80_La_Jolla\/Docs\/CP-181146.zip","group":"CP","meeting":"CP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]