[{"name":"SP-180947","title":"LS from RAN WG2: Reply LS on initial NAS security agreements","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank SA WG3 on their LS on initial NAS security agreements. RAN WG2 noticed SA WG3 stated that 'SA WG3 interpret the guidance given by SA plenary means that RAN specifications shall only include S-NSSAI ciphered in RRC layer'. RAN WG2 would like to inform SA WG3 that in the current RRC specifications, the list of S-NSSAIs can only be sent in RRCConnectionSetupComplete (LTE\/5GC) and RRCSetupComplete (NR), i.e. 'Msg5' during RRC connection establishment procedure, without any encryption. It should be noted that the list of S-NSSAI is included in the above messages only if upper layer provides the information to RRC. RAN WG2 also would like to point out that release-15 specification is frozen and backwards incompatible change cannot be made any more.","secretary_remarks":"Noted","agenda_item_sort_order":7,"ainumber":"5","ainame":"Items for early consideration (Please contact the chairman in advance.)","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, CT WG1, RAN WG3, TSG SA","lsoriginalls":"R2-1816022","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180947.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180953","title":"LS from SA WG2: Reply LS on initial NAS security agreements","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to thank SA WG3 for their LS (S2-1810292\/S3-183066). Regarding encryption at NAS level: SA WG2 confirms the SA WG3 assumption that S-NSSAI and Last visited TAI can be encrypted. In contrast, SA WG2 concluded that the Moving from EPC parameter must be sent as cleartext. A TS 23.502 CR in S2-1811307 has been agreed clarifying these aspects. Regarding encryption at Access Stratum (AS) level: SA WG2 analyzed several solution proposals and concluded that with the existing security mechanism at AS level it is not possible for 3GPP access to achieve S-NSSAI privacy and optimal AMF selection simultaneously. The reason is that optimal AMF selection (for the cases when 5G-GUTI is not available or cannot be used) requires that UE indicate the S-NSSAI in RRC signalling before the UE context, including security, is installed in NG-RAN (e.g. as in the case of untrusted non-3GPP access). Indicating S-NSSAI in AS is also considered useful to provide RAN awareness of what slices the U","secretary_remarks":"Noted","agenda_item_sort_order":7,"ainumber":"5","ainame":"Items for early consideration (Please contact the chairman in advance.)","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, CT WG1","Cc":"RAN WG2, RAN WG3, TSG SA","lsoriginalls":"S2-1811568","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180953.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180954","title":"LS from SA WG3: LS on initial NAS security agreements","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA plenary for the LS (SP-180914\/S3-182884) on Guidance on initial NAS message protection. The LS tasks SA WG2, SA WG3 and CT WG1 with concluding on a solution for initial NAS security for Rel-15 for the December plenary. There was guidance from SA to cipher everything except for UE identity, e.g. GUTI\/SUCI. However, to retrieve security context and\/or establish security, the following IEs have to be sent in clear in addition to UE identity: Message information ( Extended Protocol discriminator, Security header type, Spare half octet, Message identity and Registration type information (similar information for other messages)), ngKSI, UE security capabilities, 4G TAU IE, Indication that UE is moving from EPC From SA WG3 perspective, there is no functional reason to send S-NSSAI or latest TAI in clear. Therefore, SA WG3 has prepared a draft CR (please see attached) removing those IEs from the cleartext elements and including them in the ciphered IEs. SA WG3 interpret the gu","secretary_remarks":"Noted","agenda_item_sort_order":7,"ainumber":"5","ainame":"Items for early consideration (Please contact the chairman in advance.)","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, RAN WG2, RAN WG3, TSG SA","Cc":"","lsoriginalls":"S3-183066","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180954.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180955","title":"LS from SA WG3: Reply LS to S2-1811543 on NSSAI in the Access Stratum","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks SA WG2 for the reply LS S2-1811543. Regarding encryption at NAS level: SA WG3 thanks for the confirmation and updating the SA WG2 specifications. Regarding encryption at Access Stratum (AS) level: SA WG3 discussed the two CRs attached in the LS S2-1811403 and S2-1811565. SA WG3 concluded that CR S2-1811403 always provides privacy while sending NSSAI. CR S2-1811565 supports privacy in default mode. But NSSAI is allowed to be sent in cleartext, only if both HPLMN and VPLMN allow it by policy, in RRC messages for the slices that don't require privacy protection of NSSAI by cryptographic means. With the above in mind, SA WG3 leaves up to SA WG2 to choose which of the CRs is most suitable for Rel-15 5GS.","secretary_remarks":"Noted","agenda_item_sort_order":7,"ainumber":"5","ainame":"Items for early consideration (Please contact the chairman in advance.)","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"RAN WG2, RAN WG3, TSG SA","lsoriginalls":"S3-183659","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180955.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181147","title":"LS from CT WG1: LS on protection of initial NAS messages","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":72074,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA for their LS on the guidance on initial NAS message protection. CT WG1 would like to inform SA about the following CT WG1 work progress on initial NAS message protection in Release 15: - the necessary changes ensuring that minimal information is sent in the clear at the NAS layer have been concluded in accordance with SA WG2 and SA WG3. The detailed CT WG1 agreements on initial NAS message protection can be found in the attached documents. CT WG1 will update its specification accordingly if further stage 2 requirements arise. Action: CT WG1 kindly requests SA to take the above CT WG1 work progress report into account.","secretary_remarks":"Noted","agenda_item_sort_order":7,"ainumber":"5","ainame":"Items for early consideration (Please contact the chairman in advance.)","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2018-12-04 05:07:32","uploaded":"2018-12-04 13:59:29","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, SA WG3, SA WG2","lsoriginalls":"C1-188925","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181147.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181203","title":"Time schedule of Release 17","source":"Ericsson","contact":"Krister S\u00e4llberg","contact-id":11978,"tdoctype":"discussion","for":"Decision","abstract":"Discussion of release 17 time Schedule and proposal on target completion dates for Stage 1, Stage 2 and Stage 3. Proposal: Ericsson proposes that the release schedule of Rel-17 has the following target dates based on a 15 months release circle: - Stage 1 target date September 2019 - Stage 2 target date September 2020 - Stage 3 target date March 2021 - ASN.1 target date June 2021","secretary_remarks":"Noted","agenda_item_sort_order":7,"ainumber":"5","ainame":"Items for early consideration (Please contact the chairman in advance.)","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2018-12-06 22:19:47","uploaded":"2018-12-06 22:30:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181203.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181224","title":"Way forward on time schedule of Release 17","source":"Ericsson","contact":"Tony Saboorian","contact-id":42208,"tdoctype":"discussion","for":"Endorsement","abstract":"Based on discussion of contribution SP-181203, SA plenary agreed to the following principles on time schedule of Rel-17: - The release schedule of Rel-17 aims for 15 months release cycle. This means that at the TSG meeting of completion of stage 3 for Rel-16 the target TSG for Rel-17 stage 3 completion is 15 month later. This is an ambition to have shorter releases and release dates will be discussed at future TSG meetings. - The target date for stage 1 is December 2019 where the Q4-2019 is focused on completion of Normative WIDs. - As a general principle, the stage 2 study items have a general target to complete 6 months earlier than the target date for normative stage 2 completion. At this time, it is expected that the target content of the release is discussed and agreed in SA plenary. - The target for stage 3 completion of CT specifications will have a coordinated stage 3 target date with RAN. This is primarily for aspects that has dependencies with RAN protocol specifications","secretary_remarks":"Created at meeting. Revised to SP-181243.","agenda_item_sort_order":7,"ainumber":"5","ainame":"Items for early consideration (Please contact the chairman in advance.)","tdoc_agenda_sort_order":10100,"status":"revised","reservation_date":"2018-12-13 08:20:42","uploaded":"2018-12-14 07:18:10","revisionof":"","revisedto":"SP-181243","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181224.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181243","title":"Way forward on time schedule of Release 17","source":"Ericsson","contact":"Tony Saboorian","contact-id":42208,"tdoctype":"discussion","for":"Endorsement","abstract":"Based on discussion of contribution SP-181203, SA plenary agreed to the following principles on time schedule of Rel-17: - The target date for stage 1 completion is December 2019, with all normative work results ready to be sent for information (more than 60 % completion) by Sept 2019. - It is expected that the 3GPP wide coordination to determine the focus areas of Rel-17 will be at TSG#86 (December 2019). - The target for stage 3 completion of CT specifications will have a coordinated stage 3 target date with RAN. This is primarily for aspects that has dependencies with RAN protocol specifications that are subject to follow on ASN.1 coding. Other CT specifications that are independent with RAN have an additional 3 months to complete the stage 3 work of the release.","secretary_remarks":"Revision of SP-181224. Revised to SP-181248.","agenda_item_sort_order":7,"ainumber":"5","ainame":"Items for early consideration (Please contact the chairman in advance.)","tdoc_agenda_sort_order":10110,"status":"revised","reservation_date":"2018-12-14 06:50:07","uploaded":"2018-12-14 14:37:54","revisionof":"SP-181224","revisedto":"SP-181248","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181243.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181248","title":"Way forward on time schedule of Release 17","source":"Ericsson","contact":"Tony Saboorian","contact-id":42208,"tdoctype":"discussion","for":"Endorsement","abstract":"Based on discussion of contribution SP-181203, SA plenary agreed to the following principles on time schedule of Rel-17: - It is expected that the 3GPP wide coordination to determine the focus areas of Rel-17 will be at TSG#86 (December 2019). - The target date for stage 1 completion is December 2019, with all normative work results to be at or more than 80 % completion by Sept 2019. - The target for stage 3 completion of CT specifications will have a coordinated stage 3 target date with RAN. This is primarily for aspects that has dependencies with RAN protocol specifications that are subject to follow on ASN.1 coding. Other CT specifications that are independent with RAN have an additional 3 months to complete the stage 3 work of the release.","secretary_remarks":"Revision of SP-181243. This was endorsed","agenda_item_sort_order":7,"ainumber":"5","ainame":"Items for early consideration (Please contact the chairman in advance.)","tdoc_agenda_sort_order":10120,"status":"endorsed","reservation_date":"2018-12-14 12:41:09","uploaded":"2018-12-14 14:37:55","revisionof":"SP-181243","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181248.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]