[{"name":"SP-180257","title":"LS from SA WG3: Reply LS to LS on Secured Signalling-only connection","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks TSG RAN for the LS (RP-180590\/S3-181121) 'LS on secured Signalling-only connection'. SA WG3 would like to point out that the current 5G AS SMC procedure as described in TS33.501 allows the setup of RRC security without the setup of DRBs. It is up to SA WG2 and RAN WG3 groups to identify the scenarios which need RRC signalling only connection and how to trigger AS security setup. SA WG3 will have to evaluate the security aspects of such scenarios. SA WG3 believes, based on analogy with LTE, that at least MDT reporting and RRC redirect, are scenarios that should not be allowed until after RRC security activation. SA WG3 assumes that all RRC signalling are protected except RRC messages which will be in the exception list in TS38.331.","secretary_remarks":"Noted","agenda_item_sort_order":14,"ainumber":"7.3","ainame":"SA WG3 Report and Questions for Advice","tdoc_agenda_sort_order":11000,"status":"noted","reservation_date":"2018-05-04 14:36:17","uploaded":"2018-05-04 14:47:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, RAN WG3, RAN WG2, SA WG2","Cc":"TSG SA","lsoriginalls":"S3-181451","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_80\/Docs\/SP-180257.zip","group":"SP","meeting":"SP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180437","title":"SA WG3 Status report","source":"SA WG3 Chairman","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"report","for":"Information","abstract":"SA WG3 Status report to TSG SA#80","secretary_remarks":"Noted","agenda_item_sort_order":14,"ainumber":"7.3","ainame":"SA WG3 Report and Questions for Advice","tdoc_agenda_sort_order":10990,"status":"noted","reservation_date":"2018-06-01 10:44:44","uploaded":"2018-06-06 08:06:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_80\/Docs\/SP-180437.zip","group":"SP","meeting":"SP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180527","title":"LS from SA WG3: LS on User Plane Integrity Protection in LTE","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"As a result of the attached document (S3-181648), SA WG3 has discussed security issues that can be solved by Integrity Protection for the User Plane in LTE. SA WG3 kindly informs TSG SA plenary that it intends to bring a SID to the next plenary meeting on User Plane Integrity Protection and work on this topic accordingly. Action: SA WG3 asks TSG SA to note that this work is in progress.","secretary_remarks":"Noted","agenda_item_sort_order":14,"ainumber":"7.3","ainame":"SA WG3 Report and Questions for Advice","tdoc_agenda_sort_order":11010,"status":"noted","reservation_date":"2018-06-06 07:38:13","uploaded":"2018-06-06 08:27:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-R, ITU-T and ITU-D SGs, 3GPP TSGs, BBF, ETSI, GSMA, IEEE, IETF, MEF, NGNM, OASIS (TOSCA), oneM2M, ONF, ONAP, OSSDN, SCF, TM Forum, TTA, TSDSI","Cc":"","lsoriginalls":"S3-182072","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_80\/Docs\/SP-180527.zip","group":"SP","meeting":"SP-80","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]