[{"name":"S2-181419","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-180007 from S2#125. Response drafted in S2-182012. Final response in S2-183029.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15160,"status":"replied to","reservation_date":"2018-01-29 17:29:47","uploaded":"2018-02-01 17:35:41","revisionof":"S2-180007","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"-","lsoriginalls":"R2-1712051","lsreply":"S2-183029","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181419.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181420","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":"Action","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-180015 from S2#125. Response drafted in S2-182012. Final response in S2-183029.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15170,"status":"replied to","reservation_date":"2018-01-29 17:29:47","uploaded":"2018-02-01 17:35:41","revisionof":"S2-180015","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"R2-1714125","lsreply":"S2-183029","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181420.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181427","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":"Postponed S2-180049 from S2#125. Response drafted in S2-182012.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15150,"status":"available","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-01 17:35:41","revisionof":"S2-180049","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"S3-173520","lsreply":"S2-183029","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181427.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181436","title":"LS from CT WG1: LS on selectively disabling legacy radio access","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks SA WG1 for their LS on selectively disabling legacy radio access. CT WG1 has discussed the LS as well as the associated SA WG1 agreed CR and has the following questions: Question 1: The SA WG1 agreed CR is against TS 22.011, and was agreed under TEI16, however SA WG1's LS only mentions the 5GS Phase 2 Work Item. Do the requirements agreed by SA WG1 apply only to 5GS, or do they also apply to EPS? Question 2: Can the user re-allow a radio technology that has been disallowed by the HPLMN? Question 3: Can the HPLMN re-allow a radio technology that has been disallowed by the user? Question 4: Shall the radio technologies disallowed by the HPLMN be re-allowed upon power-cycle or when the USIM is disabled? Question 5: Can the HPLMN disallow a radio technology included by the user in the 'User Controlled PLMN Selector with Access Technology' data file in the USIM? Question 6: Can the user disallow a radio access technology included by the HPLMN in the 'Operator Controlled PLMN S","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":15200,"status":"noted","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG3, SA WG2, RAN WG2, CT WG4","lsoriginalls":"C1-180711","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181436.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181451","title":"LS from SA WG3: LS on SBI Design and its Security Implications","source":"SA WG3","contact":"Hans Christian Rudolph","contact-id":72672,"tdoctype":"LS in","for":"Information","abstract":"1.1 Rationale Within the context of designing the Service Based Interface (SBI) for 5G, SA WG3 has previously expressed the desire to apply application layer security to the N32 interface between PLMN operators for the interconnect (LS to CT WG4 in S3-173527). SA WG3 has more detailed understanding of a potential security solution for SBA in general and for N32 security in particular. SA WG3 has identified dependencies on the SBI design. SA WG3 will only be able to complete the specification of a security solution for SBA and N32 interface after CT WG3 and CT WG4 define messages, information elements and data structures transmitted over the N32 interface. In particular SA WG3 would like to ask CT WG3 and CT WG4 to consider the guidelines outlined in Section 1.2 when designing SBI. Furthermore, CT WG3 and CT WG4 could help SA WG3 getting a better understanding of design decisions, allowing SA WG3 to conclude on the security solution for SBA and N32 for Release 15. To this end, SA WG3 as","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":15210,"status":"noted","reservation_date":"2018-01-30 08:57:46","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, CT WG4","Cc":"SA WG2","lsoriginalls":"S3-180389","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181451.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181611","title":"Updates to the Security Edge Protection Proxy description","source":"Ericsson, Telecom Italia","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","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.  Replaced NOTE with normative text to clarify the behaviour of the SEPPs between PLMNs.","secretary_remarks":"Revision of approved DRAFTCR S2-181398. Revised to S2-182788.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15230,"status":"revised","reservation_date":"2018-02-13 13:29:42","uploaded":"2018-02-20 01:46:36","revisionof":"S2-181398","revisedto":"S2-182788","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":45.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181611.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181677","title":"Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated?, Ericsson?","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation of a PDU session, determines the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information and PCC, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of endorsed DRAFTCR S2-181304. Confirm sources. Revised in S2-182005.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15080,"status":"revised","reservation_date":"2018-02-14 15:36:26","uploaded":"2018-02-18 17:03:56","revisionof":"S2-181304","revisedto":"S2-182005","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":66.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181677.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181778","title":"Configure AMF to periodically re-allocate 5G-GUTI","source":"Apple, Inc.","contact":"Krisztian Kiss","contact-id":57762,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UE may request the AMF to periodically re-allocate the 5G-GUTI, the AMF may adjust the UE requested 5G-GUTI lifetime to a network accepted value. The 5G-TMSI should be generated using cryptographically strong pseudo-randomness.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15060,"status":"postponed","reservation_date":"2018-02-18 04:58:04","uploaded":"2018-02-18 05:23:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":94.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181778.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181779","title":"Configure AMF to periodically re-allocate 5G-GUTI","source":"Apple, Inc.","contact":"Krisztian Kiss","contact-id":57762,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UE may request the AMF to periodically re-allocate the 5G-GUTI, the AMF may adjust the UE requested 5G-GUTI lifetime to a network accepted value.","secretary_remarks":"Not Handled","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15070,"status":"not treated","reservation_date":"2018-02-18 05:02:41","uploaded":"2018-02-18 05:23:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":120.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181779.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181852","title":"LS from RAN WG3: Reply LS on User Plane Security Policy","source":"RAN WG3","contact":"Liwei Qiu","contact-id":45572,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank SA WG3 for the LS on user plane security policy. RAN WG3 has discussed the support of user plane security for NR-RAN in Rel-15 and agreed that in Rel-15 it is feasible to include an indicator to specify whether UP integrity protection is required or not during PDU session establishment. RAN WG3 has assumed that such indicator is signaled on a per-PDU-session basis. RAN WG3 has endorsed the attached pCRs. Action: RAN WG3 kindly requests SA WG3\/SA WG2 to take the above into account and provide feedback if needed.","secretary_remarks":"Update of S2-181483 to add attachments. Noted in parallel session.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15140,"status":"noted","reservation_date":"2018-02-19 10:33:34","uploaded":"2018-02-19 10:37:54","revisionof":"S2-181483","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG2","Cc":"CT WG3","lsoriginalls":"R3-180637","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181852.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182005","title":"Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation of a PDU session, determines the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information and PCC, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-181677 (Revision of endorsed DRAFTCR S2-181304). Revised to S2-182785.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15090,"status":"revised","reservation_date":"2018-02-19 19:37:47","uploaded":"2018-02-19 19:43:04","revisionof":"S2-181677","revisedto":"S2-182785","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":66.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182005.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182009","title":"User plane security policy","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Addition of User Plane Security Enforcement information in the N2 SM info provided to RAN during UP connection activation.  The User Plane Security Policy is optionally provided by PCF to SMF, in case dyanmic PCC is supported.","secretary_remarks":"Revision of endorsed principles DRAFTCR S2-181261. Revised to S2-182786.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15120,"status":"revised","reservation_date":"2018-02-19 20:18:46","uploaded":"2018-02-20 13:18:46","revisionof":"S2-181261","revisedto":"S2-182786","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":184.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182009.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182012","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-18abcd, S2-18abcd","secretary_remarks":"Revision of postponed LS OUT S2-181259. Response to S2-181427, S2-181419 and S2-181420. Revised to S2-182787.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15180,"status":"revised","reservation_date":"2018-02-19 20:38:12","uploaded":"2018-02-20 13:18:46","revisionof":"S2-181259","revisedto":"S2-182787","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_126_Montreal\/Docs\/S2-182012.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182138","title":"LS from SA WG1: Reply LS on selectively disabling legacy radio technologies","source":"SA WG1","contact":"Krister S\u00e4llberg","contact-id":11978,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for their LS, and would like to provide the background info that this originated by an LS from SA WG3 (S3-172144) where SA WG3 had considered what will happen when an operator discontinues its GSM network while the subscribers of that operator still have GSM capable UEs which will be subject for some attacks by e.g. false base stations. Such operator could hope that subscribers manually configure the UE to disable GSM. Currently, legacy UEs have MMI user settings that gives the user some possibility to disable radio technologies. This is proprietary by the phone manufacturer and may not have a setting to just disable GSM. Thereby specifying requirements for UE configuration of selective disabling of radio technology Rel-16 introduces a more consistent MMI user setting. In addition, to make it possible for the home operator to make sure that all UEs (of all types) will disallow use of e.g. GSM, SA WG1 introduced service requirements to specify a secure mechanism whe","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":15220,"status":"noted","reservation_date":"2018-02-20 08:39:22","uploaded":"2018-02-20 09:17:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3, SA WG2, RAN WG2, CT WG4","lsoriginalls":"S1-180634","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182138.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182248","title":"Clarification on inter-PLMN Control Plane signaling","source":"Deutsche Telekom AG","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes some updates to the agreed changes in CR0045 to 23.501 in S2-181611 to clarify that all control plane messages in inter-PLMN signalling are transferred via the SEPP.","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":15250,"status":"noted","reservation_date":"2018-02-20 13:28:00","uploaded":"2018-02-20 13:39:31","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182248.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182785","title":"Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Nokia, Nokia Shangai Bell, Qualcomm Incorporated, Ericssson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation of a PDU session, determines the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information and PCC, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-182005. Revised to S2-182897.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15100,"status":"revised","reservation_date":"2018-02-28 21:27:59","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182005","revisedto":"S2-182897","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":66.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182785.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182786","title":"User plane security policy","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Addition of User Plane Security Enforcement information in the N2 SM info provided to RAN during UP connection activation.  The User Plane Security Policy is optionally provided by PCF to SMF, in case dyanmic PCC is supported.","secretary_remarks":"Revision of S2-182009. Revised to S2-182991.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15130,"status":"revised","reservation_date":"2018-02-28 21:28:00","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182009","revisedto":"S2-182991","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":184.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182786.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182787","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-18abcd, S2-18abcd","secretary_remarks":"Revision of S2-182012. This was left for e-mail approval. Approved. Revised to remove 'draft' in S2-183029.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15190,"status":"revised","reservation_date":"2018-02-28 21:28:01","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182012","revisedto":"S2-183029","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_126_Montreal\/Docs\/S2-182787.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182788","title":"Updates to the Security Edge Protection Proxy description","source":"Ericsson, Telecom Italia, Deutsche Telekom AG","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","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.  Replaced NOTE with normative text to clarify the behaviour of the SEPPs between PLMNs.","secretary_remarks":"Revision of S2-181611. 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":15240,"status":"agreed","reservation_date":"2018-02-28 21:28:01","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181611","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":45.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182788.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182897","title":"Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Nokia, Nokia Shangai Bell, Qualcomm Incorporated, Ericssson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation of a PDU session, determines the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information and PCC, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-182785. Revised to S2-182990.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15110,"status":"revised","reservation_date":"2018-03-02 14:40:40","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182785","revisedto":"S2-182990","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":66.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182897.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182990","title":"Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection","source":"Nokia, Nokia Shangai Bell, Qualcomm Incorporated, Ericssson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduces a mechanism where the SMF, upon creation of a PDU session, determines the UP security policy to be delivered as a request to the NG-RAN based on UE subscription information and PCC, enabling the HPLMN a degree of control on the activation of the UP integrity protection.","secretary_remarks":"Revision of S2-182897. This CR was agreed.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15111,"status":"agreed","reservation_date":"2018-03-05 10:37:25","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182897","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":66.0,"crrevision":4.0,"crcategory":"C","tsg_crp":"SP-180092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182990.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182991","title":"User plane security policy","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Addition of User Plane Security Enforcement information in the N2 SM info provided to RAN during UP connection activation.  The User Plane Security Policy is optionally provided by PCF to SMF, in case dyanmic PCC is supported.","secretary_remarks":"Revision of S2-182786. This CR was agreed.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15131,"status":"agreed","reservation_date":"2018-03-05 10:37:26","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182786","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":184.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182991.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-183029","title":"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-182990, S2-182991","secretary_remarks":"e-mail revision of S2-182787. e-mail approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":15191,"status":"approved","reservation_date":"2018-03-09 15:42:06","uploaded":"2018-03-09 15:47:54","revisionof":"S2-182787","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181427","lsto":"SA WG3, RAN WG2, RAN WG3","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-183029.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]