[{"name":"S2-187635","title":"LS from SA WG3: LS on TLS and inter PLMN routing","source":"SA WG3","contact":"Christine Jost","contact-id":49662,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to inform SA WG2 and CT WG4 about an issue with TLS termination and inter-PLMN routing and provide SA WG3's solution recommendation. According to TS 33.501, clause 13.1, transport security inside one PLMN is based on TLS. For service invocation between different PLMNs, the SEPP needs to terminate TLS in order to modify requests and responses. However, according to TS 29.500, clause 6.1.4.3, the FQDN in the Request URL contains the FQDN of the remote PLMN. With the current agreements in TS 33.501 and TS 29.500, in order to terminate TLS, the SEPP needs to provide a certificate on behalf of the remote PLMN. 'Solution #8: Inter PLMN routing and TLS: Solution Options' in the attached S3-181957 describes three different solution options for the problem. SA WG3 prefers the option described in 4.3.8.3: 'Using local SEPP FQDN in request URL'. With this solution option, the request URL would point to the next hop instead of the final target and the real target FQDN used for ro","secretary_remarks":"Postponed S2-186324 from SA2#128. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12520,"status":"noted","reservation_date":"2018-07-30 07:31:41","uploaded":"2018-07-30 07:49:43","revisionof":"S2-186324","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4","Cc":"","lsoriginalls":"S3-181956","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187635.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187636","title":"LS from SA WG3: LS response on Initial NAS message protection","source":"SA WG3","contact":"Anand Palanigounder","contact-id":26706,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG1 for their reply LS on Initial NAS message protection (C1-183727\/ S3-182086). In their LS, CT WG1 ask SA WG3 the following questions: Question#1 to SA WG3: What are technical problems resolved by this SA WG3 feature and what real benefits gained from this SA WG3 feature given the identified cleartext IEs? Question#2 to SA WG2, SA WG3: What are the criteria determining which IEs should be ciphered or be sent in the clear? Question#3 to SA WG3: Whether initial NAS message protection is mandatory or optional for the UE and\/or the network? Question#4 to SA WG3: Which UE security related IEs should be sent in the clear? SA WG3 would like to provide the following responses to the questions: Response to Question 1: one of the major goals of the 5GS security is to enhance the security compared to 4G. To minimize the risk that an attacker may misuse the IEs sent in the clear in the initial NAS message(s), SA WG3 decided to confidentiality protect (i.e., cipher) all the IEs t","secretary_remarks":"Postponed S2-186336 from SA2#128. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12540,"status":"noted","reservation_date":"2018-07-30 07:31:41","uploaded":"2018-07-30 07:49:43","revisionof":"S2-186336","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"S3-182087","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187636.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187651","title":"LS from CT WG4: LS on Nausf_SoRProtection service","source":"CT WG4","contact":"Julien Bournelle","contact-id":41373,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 observes for the new Nausf_SoRProtection service the UDM has to discover the correct AUSF to render the mentioned service. CT WG4 kindly requests SA WG2 to provide related solution. CT WG4 also notes SA LS (SP-180621) which wants the feature to be completed in Rel-15 and given that CT WG4 and SA WG2 meeting are during the same week, we request SA WG2 to provide the response as early as possible. Action: CT WG4 asks SA WG2 to take this information into account and to update the clause related to AUSF discovery and selection in 3GPP TS 23.501.","secretary_remarks":"Response drafted in S2-187694. Final response in S2-189035","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12570,"status":"replied to","reservation_date":"2018-07-30 09:25:20","uploaded":"2018-07-30 09:27:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3","lsoriginalls":"C4-185319","lsreply":"S2-189035, S2-189035","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187651.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187653","title":"LS from CT WG4: LS OUT on TLS and inter PLMN routing","source":"CT WG4","contact":"Sridhar Bhaskaran","contact-id":71776,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks SA WG3 for their LS response on TLS and inter PLMN routing. CT WG4 further investigated the impacts to CT WG4 specifications due to the SA WG3 suggested solution 'Using local SEPP FQDN in request URL' and CT WG4 identified the following impacts. 1. Specification of a custom HTTP header in 3GPP TS 29.500 2. Specification of SEPP behaviour on receiving this custom HTTP header, in 3GPP TS 29.500. As indicated in the earlier CT WG4 response, CT WG4 would like to consider this solution as the last resort solution as it impacts the basics of HTTP routing specified in IETF RFC 7230 and it also makes it mandatory for the NF service consumer (application) to be aware of the URI of the SEPP. In view of that CT WG4 did a detailed analysis of the various solution options provided by SA WG3 and would like to highlight the following points: 1. The disadvantages of the bump in TLS solution as highlighted by SA WG3, are already encountered by CDN providers and corporate HTTP proxies and","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":12530,"status":"noted","reservation_date":"2018-07-30 09:25:20","uploaded":"2018-07-30 09:27:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"C4-185493","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187653.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187654","title":"LS from CT WG6: Response to Reply LS on AUSF\/UDM instance selection and SUCI parameters","source":"CT WG6","contact":"Sergi Espi","contact-id":74299,"tdoctype":"LS in","for":"Information","abstract":"CT WG6 would like to thank CT WG4 for the LS on Reply LS on AUSF\/UDM instance selection and SUCI parameters. CT WG6 has taken into account the structure of the SUCI on their work on the attached CRs. CT WG6 would like to draw the attention that despite the definition of the structure of the SUCI, CT WG6 observes that the coding of the different fields of the SUCI is not completed. As a consequence, there are still many 'Editor's notes', which rely on the definition of the coding. CT WG6 considers this part essential to be completed during the Rel-15 timeframe in order to guarantee the completion of the 5G work item and to guarantee the interoperability of the implementations.","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":12630,"status":"noted","reservation_date":"2018-07-30 09:25:20","uploaded":"2018-07-30 09:27:51","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG3, SA WG2, CT WG1","lsoriginalls":"C6-180361","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187654.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187659","title":"LS from SA WG3LI: LS Out for 5G slices roaming","source":"SA WG3LI","contact":"Pierre Courbon","contact-id":52806,"tdoctype":"LS in","for":"Information","abstract":"SA WG3-LI have reviewed the information and would like to provide feedback to GSMA on LI requirement for international roaming for 5G with slicing. SA WG3-LI has reviewed the GSMA report on 'an introduction to network slicing': https:\/\/www.gsma.com\/futurenetworks\/wp-content\/uploads\/2017\/11\/GSMA-An-Introduction-to-Network-Slicing.pdf {...} For the first scenario, 'standardised Slices types', SA WG3-LI have not identified any specific LI issues. However, the VPLMN LI capabilities may require access to services usages in the VPLMN without direct assistance of HPLMN similar to LI requirements applied to SH8R, Therefore, any encryption schemes would need to be selected accordingly. For the second scenario, 'Network slicing blueprint export', SA WG3-LI consider that it may be possible to meet LI requirements using this approach. On the assumption that blueprints are based on standard GSMA templates supported by all operators and the HPLMN is configuring standard capabilities, then it should","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":12510,"status":"noted","reservation_date":"2018-07-30 09:25:20","uploaded":"2018-07-30 09:27:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG SA, SA WG1, SA WG2, SA WG3, ETSI ISG NFV SEC, GSMA WSOLU","lsoriginalls":"S3i180376","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187659.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187693","title":"Specify AUSF selection by UDM","source":"Samsung, T-Mobile USA","contact":"Andy Bennett","contact-id":70253,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds that the mechanism used by the UDM to select an AUSF is to use the NRF, unless there is local configuration data, or AUSF information stored from a previous successful authentication.","secretary_remarks":"Revised in parallel session to S2-188671.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12580,"status":"revised","reservation_date":"2018-08-07 08:25:18","uploaded":"2018-08-14 13:13:46","revisionof":"","revisedto":"S2-188671","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":548.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187693.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187694","title":"[DRAFT] Reply on Nausf_SoRProtection service","source":"Samsung Electronics Nordic AB","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"Response to LS from CT WG4 asking SA WG2 to specify how the UDM discovers the correct AUSF to support the Nausf_SoRProtection service.","secretary_remarks":"Response to S2-187651. Revised in parallel session to S2-188672.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12610,"status":"revised","reservation_date":"2018-08-07 08:29:23","uploaded":"2018-08-14 13:13:46","revisionof":"","revisedto":"S2-188672","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187694.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187823","title":"Modifications to Registration Procedure for initial NAS security support","source":"Qualcomm","contact":"Faccin Stefano","contact-id":60610,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified in the Registration procedure that, if the UE has no stored 5G context, the UE provides only the NAS security parameters agreed together with SA WG3.","secretary_remarks":"Revision of (unhandled) S2-186662 from S2#128. Replaced by S2-188270. WITHDRAWN","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12550,"status":"withdrawn","reservation_date":"2018-08-12 23:06:54","uploaded":null,"revisionof":"S2-186662","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":564.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187833","title":"Resolving Editor's note related to Security","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a reference to TS 33.501 which describes in clause 8.4.2 how the AMF derives a mapped 5G security context.","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":12650,"status":"agreed","reservation_date":"2018-08-12 23:32:27","uploaded":"2018-08-14 13:21:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":648.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180720","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187833.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188270","title":"Modifications to Registration Procedure for initial NAS security support","source":"Qualcomm Incorporated, KPN, Deutsche Telekom","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified in the Registration procedure that, if the UE has no stored 5G context, the UE provides only the NAS security parameters agreed together with SA WG3.","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":12560,"status":"postponed","reservation_date":"2018-08-14 10:31:08","uploaded":"2018-08-14 13:36:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":717.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188270.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188286","title":"Correction on security for interworking","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Change SUPI mentioned in Reason for change to SUCI 2. Change Identity mentioned in Reason for change to Identification.","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":12660,"status":"agreed","reservation_date":"2018-08-14 11:08:42","uploaded":"2018-08-14 14:13:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":720.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180722","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188286.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188671","title":"Specify AUSF selection by UDM","source":"Samsung, T-Mobile USA","contact":"Andy Bennett","contact-id":70253,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds that the mechanism used by the UDM to select an AUSF is to use the NRF, unless there is local configuration data, or AUSF information stored from a previous successful authentication.","secretary_remarks":"Revision of S2-187693. Revised in parallel session to S2-188939.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12590,"status":"revised","reservation_date":"2018-08-21 05:57:51","uploaded":"2018-08-26 10:17:51","revisionof":"S2-187693","revisedto":"S2-188939","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":548.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188671.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188672","title":"[DRAFT] Reply on Nausf_SoRProtection service","source":"Samsung Electronics Nordic AB","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"Response to LS from CT WG4 asking SA WG2 to specify how the UDM discovers the correct AUSF to support the Nausf_SoRProtection service.","secretary_remarks":"Revision of S2-187694. This was left for e-mail approval. e-mail revision 1 approved. Revised to S2-189035.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12620,"status":"revised","reservation_date":"2018-08-21 05:57:53","uploaded":"2018-08-26 10:17:51","revisionof":"S2-187694","revisedto":"S2-189035","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188672.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188939","title":"Specify AUSF selection by UDM","source":"Samsung, T-Mobile USA","contact":"Andy Bennett","contact-id":70253,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds that the mechanism used by the UDM to select an AUSF is to use the NRF, unless there is local configuration data, or AUSF information stored from a previous successful authentication.","secretary_remarks":"Revision of S2-188671. This CR was agreed","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12600,"status":"agreed","reservation_date":"2018-08-26 08:40:49","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188671","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":548.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180715","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188939.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189035","title":"Reply to CT WG4 LS on Nausf_SoRProtection service","source":"SA WG2","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: SA WG3. Attachment: S2-188939","secretary_remarks":"e-mail revision 1 of S2-188672. e-mail approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12621,"status":"approved","reservation_date":"2018-08-31 11:20:52","uploaded":"2018-08-31 11:27:51","revisionof":"S2-188672","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-187651","lsto":"CT WG4","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189035.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]