[{"name":"S2-1906843","title":"LS from SA WG3: Reply LS on usage of EPLMNs","source":"SA WG3","contact":"Joonwoong Kim","contact-id":66512,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks SA WG2 for their LS on EHPLMN usage highlighting potential security issues. In replay to the questions, SA WG3 has agreed the following answers: a) SA WG2 politely request guidance from SA WG3 on whether they have security concerns about the allocation of a UE Capability ID by a Serving PLMN for use in the EPLMNs signaled by that Serving PLMN [SA WG3 Reply] -> SA WG3 discussed several potential threats and concluded that for security reasons the UE Capability ID should not be associated with an EPLMN. b) SA 2 politely invite SA 3 to review the use of EPLMNs by these other features [SA WG3 Reply] -> SA WG3 discussed this issue and wishes to review these issues further before responding. SA WG3 will inform SA WG2 of the results, when the review has progressed. Action: SA WG3 asks SA WG2 group to take the above guidance into account when they update their specifications.","secretary_remarks":"Postponed S2-1905815 from S2#133. Noted in parallel session","agenda_item_sort_order":59,"ainumber":"6.28","ainame":"Optimisations on UE radio capability signalling (RACS)","tdoc_agenda_sort_order":24570,"status":"noted","reservation_date":"2019-06-10 18:36:16","uploaded":"2019-06-11 14:48:56","revisionof":"S2-1905815","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-191599","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906843.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906856","title":"LS from CT WG3: Reply LS on EPS architecture supporting RACS","source":"CT WG3","contact":"Wenliang Xu","contact-id":67079,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 thanks SA WG2 for their LS on EPS architecture supporting RACS. In the LS, SA WG2 asked the follows to CT WG3: In EPS the UCMF has the same function as in 5GS, interfaces the MME and AS, optionally via SCEF. For interfaces UCMF-SCEF and UCMF-AS, SA WG2 assume that these can be specified as the corresponding interfaces in the 5GS RACS architecture but invite CT WG3 to provide feedback. In CT WG3 understanding, the new UCMF service for Manufacturer-assigned UE Radio Capability ID and UE Radio Capability Information used by the consumer NEF and AF can be re-used by the EPS for consumer SCEF and AS, correspondingly. CT WG3 will take responsibility for the interfaces including T8\/N33 and SBI Nucmf Provisioning for Manufacturer-assigned UE Radio Capability ID and UE Radio Capability Information. Action: CT WG3 kindly asks SA WG2 to take above answer into consideration.","secretary_remarks":"Response drafted in S2-1907820. Final response in S2-1907923","agenda_item_sort_order":59,"ainumber":"6.28","ainame":"Optimisations on UE radio capability signalling (RACS)","tdoc_agenda_sort_order":24580,"status":"replied to","reservation_date":"2019-06-10 18:36:16","uploaded":"2019-06-12 11:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-192328","lsreply":"S2-1907923","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906856.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906857","title":"LS from CT WG4: Reply LS on EPS architecture supporting RACS","source":"CT WG4","contact":"yong yang","contact-id":59744,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for their LS (S2-1904505) on EPS architecture supporting RACS. It is CT WG4's understanding that the services offered by the UCMF via the HTTP\/2 based SBI can be consumed by the AMF, and by the MME if the UCMF\/UCME is also deployed in the EPC; i.e. alternative A can be used. In addition, MMEs may use an EPS legacy type interface\/protocol towards the UCME; i.e. alternative B can also be used. CT WG4 has agreed to specify a new application (S17-AP) protocol on top of UDP using a TLV (Type, Length, Value) syntax for the definition of the different message types and information elements, for S17 reference points between the UCME and the MME. Action: CT WG4 kindly asks SA WG2 to take the above information into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":59,"ainumber":"6.28","ainame":"Optimisations on UE radio capability signalling (RACS)","tdoc_agenda_sort_order":24590,"status":"noted","reservation_date":"2019-06-10 18:36:16","uploaded":"2019-06-12 11:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-192365","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906857.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907820","title":"[DRAFT] Reply LS to CT WG4: Reply LS on EPS architecture supporting RACS","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To CT WG4. CC: CT WG3 saying that we want to keep the UCMF name.","secretary_remarks":"Created at meeting. Response to S2-1906856. Revised in parallel session to S2-1907923.","agenda_item_sort_order":59,"ainumber":"6.28","ainame":"Optimisations on UE radio capability signalling (RACS)","tdoc_agenda_sort_order":24600,"status":"revised","reservation_date":"2019-07-04 09:08:02","uploaded":"2019-07-04 09:17:56","revisionof":"","revisedto":"S2-1907923","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"RACS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907820.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907923","title":"Reply LS on EPS architecture supporting RACS","source":"SA WG2","contact":"Mikael Wass","contact-id":42217,"tdoctype":"LS out","for":"Approval","abstract":"To CT WG4. CC: CT WG3 saying that we want to keep the UCMF name.","secretary_remarks":"Revision of S2-1907820. Agreed in parallel session. This was Block approved","agenda_item_sort_order":59,"ainumber":"6.28","ainame":"Optimisations on UE radio capability signalling (RACS)","tdoc_agenda_sort_order":24610,"status":"approved","reservation_date":"2019-07-04 09:09:50","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1907820","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"RACS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1906856","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907923.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]