[{"name":"S2-180007","title":"LS from RAN WG2: LS on usage of user plane integrity protection for DRB","source":"RAN WG2","contact":"Keiichi Kubota","contact-id":43471,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed the technical challenge for the support of integrity protection for DRBs and would like to share RAN WG2 view on the support of integrity protection for DRBs. In RAN WG2#99 Berlin meeting, RAN WG2 made the following agreement: - UP integrity protection can be configured on a per radio bearer (i.e. per DRB) basis. - MAC-I field is not present for a DRB for which integrity protection is not configured. As stated in the RAN WG2 agreements, one Data Radio Bearer (DRB) could be configured to support data integrity protection, which means the MAC-I field would be present after the PDCP payload. Therefore, the transmitter should process the PDCP SDU with the granularity packet by packet to perform data integrity protection. Support of data integrity for user plane over Uu interface causes 1) additional OTA overhead and impacts UE and system throughput performance; and 2) increased need for computation in both UE and network. According to our study on the SA WG3 specifica","secretary_remarks":"Postponed S2-178230 from SA WG2#124. This LS was postponed. Revised at S2#126 in S2-181419.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13870,"status":"revised","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178230","revisedto":"S2-181419","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"-","lsoriginalls":"R2-1712051","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180007.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180014","title":"LS from SA WG3: LS on inclusion of the Security Edge Protection Proxy into the 5G architecture","source":"SA WG3","contact":"Hans Christian Rudolph","contact-id":72672,"tdoctype":"LS in","for":"Action","abstract":"At its last meeting SA WG3 has agreed on certain security principles for Release 15 regarding the notion of a Service Based Architecture (SBA). One core element was the inclusion of a network edge proxy for interconnection, c.f. example Figure 1, whose functional aspects are currently being defined in SA WG3. In order to assure a secure and consistent solution for 5G, SA WG3 would like to request SA WG2 to include said network element, proposed to be called Security Edge Protection Proxy (SEPP), into their architecture description. Action: SA WG3 kindly asks SA WG2 to take above information into account and to include the Security Edge Protection Proxy into its architecture.","secretary_remarks":"Postponed S2-178411 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14110,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178411","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-173437","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180014.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180015","title":"LS from RAN WG2: LS on maximum data rate of user plane integrity protected data","source":"RAN WG2","contact":"Keiichi Kubota","contact-id":43471,"tdoctype":"LS in","for":"Information","abstract":"As RAN WG2 LS (R2-1712051) mentioned, RAN WG2 sees a need to limit the use-cases of the user plan integrity protection only for DRB, whose traffic is of low data rate (such as IoT application but not for eMBB). Then RAN WG2 has further discussed the potential maximum data rate of integrity protected data in RAN WG2#100 Reno meeting. This time, RAN WG2 made the following agreement: 1 UE capability to be added for the maximum aggregate data rate per UE of user plane integrity protected data for DRBs. 2 Lowest possible value for the data rate is 64 kbps  Question to SA WG3: Does SA WG3 see any problem with the RAN WG2 agreed lowest possible value for the user plane integrity protected data rate? Please note that there is consensus at RAN plenary that features with hardware impact need to be completed by December 2017. Therefore we would greatly appreciate if the question is answered in this meeting week so that RAN WG2 can finalize the UE requirement by then.","secretary_remarks":"Postponed S2-178412 from SA WG2#124. This LS was postponed. Revised at S2#126 in S2-181420.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13880,"status":"revised","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178412","revisedto":"S2-181420","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"R2-1714125","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180015.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180042","title":"LS from SA WG1: Reply LS on selectively disabling legacy radio access","source":"SA WG1","contact":"Betsy Covell","contact-id":68109,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks SA WG3 for their LS selective disabling of legacy radio. In response, SA WG1 has agreed the attached CR to introduce the service requirements for selectively disabling a radio access technology at the UE.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13860,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, CT WG1, RAN WG2","lsoriginalls":"S1-174601","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180042.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180049","title":"LS from SA WG3: LS on User Plane Security Policy","source":"SA WG3","contact":"Ahmad Muhanna","contact-id":73852,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 has discussed the use of UP security policy and agreed that UP security policy is communicated from SMF to the gNB for enforcement. In addition, SA WG3 understands that user plane security policy can be statically configured in SMF or downloaded dynamically during PDU session setup. For Rel-15, SA WG3 expects the user plane security policy to at least include whether UP integrity protection is required or not. Further information may be added in future releases. SA WG3 would like SA WG2 and RAN WG3 to consider the option of allowing the SMF to dynamically download the UP security policy. In addition, SA WG3 would like to ask SA WG2 and RAN WG3 the following questions. SA WG3 Questions: 1. SA WG3 would like to know whether the SMF will be able to dynamically download the user plane security policy. 2. SA WG3 would like to know whether the SMF will be able to statically configure the user plane security policy. 3. SA WG3 would like to ask whether the SMF will be able to dynamicall","secretary_remarks":"Responses drafted in S2-180056, S2-180189, S2-180410 and S2-180594. This LS was postponed. Revised at S2#126 in S2-181427.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13890,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181427","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"S3-173520","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180049.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180055","title":"23.501: Updates to the security clause (User Plane Security Policy)","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The SEAF functionality described in TS 33.501 [29] is supported by the AMF","secretary_remarks":"Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13960,"status":"not treated","reservation_date":"2018-01-06 09:27:40","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180055.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180056","title":"[draft] Reply LS on User Plane Security Policy","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on User Plane Security Policy","secretary_remarks":"Response to S2-180049. Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14010,"status":"not treated","reservation_date":"2018-01-06 09:27:40","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG3, CT WG3, RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180056.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180186","title":"Discussion on way forward for support of integrity protection for user plane","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"discussion","for":"Agreement","abstract":"The paper addresses the issues raised in LSs from RAN WG2 (S2-180007 and S2-180015, both postponed from SA WG2 #124) and from SA WG3 (S2-180049) and proposes a solution for UP security policy determination and delivery to the NG-RAN","secretary_remarks":"Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13900,"status":"not treated","reservation_date":"2018-01-12 23:50:38","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180186.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180187","title":"23.501: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revised to S2-181198.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13920,"status":"revised","reservation_date":"2018-01-12 23:53:18","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"S2-181198","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180187.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180188","title":"23.502: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13970,"status":"not treated","reservation_date":"2018-01-12 23:55:38","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180188.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180189","title":"[Draft] LS response on User Plane Security Policy","source":"Qualcomm Europe Inc.(Italy)","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"The LS address the aspects raised in the SA WG3 LS and raised also in RAN WG2 LS on the use of UP integrity protections.","secretary_remarks":"Response to S2-180049 Revised to S2-181197.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14020,"status":"revised","reservation_date":"2018-01-12 23:59:23","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"S2-181197","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180189.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180240","title":"23.501: Updates to the Security Edge Protection Proxy description","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that the message filtering and policing by the SEPP is achieved without requiring updates of SLAs between the two PLMNs.","secretary_remarks":"Revised to S2-181184.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14070,"status":"revised","reservation_date":"2018-01-14 21:18:22","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-181184","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180240.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180409","title":"23.502: User plane security policy","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Addition of User Plane Security Policy in the N2 SM info provided to RAN during UP connection activation.  The UP Sec. Policy is optionally provided by PCF to SMF, in case dynamic PCC is supported.","secretary_remarks":"Revised to S2-181199.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13980,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:41:41","revisionof":"","revisedto":"S2-181199","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180409.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180410","title":"[draft] Reply LS on User Plane Security Policy","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a reply to the SA WG3 LS on User Plane Security Policy","secretary_remarks":"Response to S2-180049. Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14050,"status":"not treated","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:52:43","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180410.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180472","title":"23.501: UDM discovery clarifications","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove Editor's note Remove example for discovery based on GPSI for PCF.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14120,"status":"approved","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:30:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180472.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180522","title":"23.501: Removing Editor's Note in clause 6.3.8 (UDM discovery function)","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Removing Editor's Note on whether SUCI needs to be considered during the UDM discovery depends on the conclusion of SA WG3 work.","secretary_remarks":"Covered by S2-180472. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14130,"status":"noted","reservation_date":"2018-01-16 04:54:13","uploaded":"2018-01-16 10:45:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180522.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180593","title":"Discussion on the LS sent by SA WG3","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution give a discussion relates to the LS received from CT WG1 on '5G service request procedure'","secretary_remarks":"Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13910,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180593.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180594","title":"[draft] Reply LS to SA WG3 on User Plane Security Policy","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply to CT WG1 to response the issue of UP security policy","secretary_remarks":"Response to S2-180049. Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14060,"status":"not treated","reservation_date":"2018-01-16 06:52:30","uploaded":"2018-01-16 11:30:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180594.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181184","title":"23.501: Updates to the Security Edge Protection Proxy description","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that the message filtering and policing by the SEPP is achieved without requiring updates of SLAs between the two PLMNs.","secretary_remarks":"Revision of S2-180240. Revised to S2-181366.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14080,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180240","revisedto":"S2-181366","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181184.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181197","title":"[Draft] LS response on User Plane Security Policy","source":"SA WG2","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, RAN WG2, RAN WG3. CC: CT WG3. Attachments: S2-181198, S2-181199","secretary_remarks":"Revision of S2-180189. Revised to S2-181259.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14030,"status":"revised","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180189","revisedto":"S2-181259","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181197.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181198","title":"23.501: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-180187. Revised to S2-181260.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13930,"status":"revised","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180187","revisedto":"S2-181260","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181198.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181199","title":"23.502: User plane security policy","source":"Ericsson, Qualcomm Incorporated","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Addition of User Plane Security Policy in the N2 SM info provided to RAN during UP connection activation.  The UP Sec. Policy is optionally provided by PCF to SMF, in case dynamic PCC is supported.","secretary_remarks":"Revision of S2-180409. Revised to S2-181261.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13990,"status":"revised","reservation_date":"2018-01-24 15:03:36","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180409","revisedto":"S2-181261","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181199.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181259","title":"[Draft] LS response on User Plane Security Policy","source":"SA WG2","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, RAN WG2, RAN WG3. CC: CT WG3. Attachments: S2-181198, S2-181199","secretary_remarks":"Revision of S2-181197. This LS was postponed in parallel session.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14040,"status":"postponed","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181197","revisedto":"S2-182012","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181259.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181260","title":"23.501: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated, Nokia, Nokia Shangai Bell","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-181198. Revised to S2-181304.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13940,"status":"revised","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181198","revisedto":"S2-181304","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181260.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181261","title":"23.502: User plane security policy","source":"Ericsson, Qualcomm Incorporated, Nokia, Nokia Shangai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Addition of User Plane Security Policy in the N2 SM info provided to RAN during UP connection activation.  The UP Sec. Policy is optionally provided by PCF to SMF, in case dynamic PCC is supported.","secretary_remarks":"Revision of S2-181199. Principles of this proposal were endorsed. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14000,"status":"noted","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181199","revisedto":"S2-182009","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181261.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181304","title":"23.501: Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Qualcomm Incorporated, Nokia, Nokia Shangai Bell, Ericsson","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation\/modification of a PDU session, or upon user plane establishment for a PDU session, determined the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-181260. This was Endorsed.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":13950,"status":"endorsed","reservation_date":"2018-01-25 14:56:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181260","revisedto":"S2-181677","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181304.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181366","title":"23.501: Updates to the Security Edge Protection Proxy description","source":"Ericsson, Telecom Italia","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that the message filtering and policing by the SEPP is achieved without requiring updates of SLAs between the two PLMNs.","secretary_remarks":"Revision of S2-181184. For e-mail approval. e-mail revision 3 approved. Revised to S2-181398.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14090,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181184","revisedto":"S2-181398","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181366.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181398","title":"23.501: Updates to the Security Edge Protection Proxy description","source":"Ericsson, Telecom Italia","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that the message filtering and policing by the SEPP is achieved without requiring updates of SLAs between the two PLMNs.","secretary_remarks":"e-mail revision 3 of S2-181366. Approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":14100,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181366","revisedto":"S2-181611","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181398.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]