[{"name":"S6-150268","title":"LS on Rel-13 MCPTT work","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"TSG CT, TSG RAN, TSG SA and PCG\/OP","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-04-16 17:58:47","uploaded":"2015-04-20 08:54:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_003_SanJoseDelCabo\/Docs\/S6-150268.zip","group":"S6","meeting":"S6-3","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-190534","title":"LS on Information on MEC work on 5G","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-03-26 14:12:13","uploaded":"2019-03-26 14:28:16","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA5, SA6","lsoriginalls":"S2-1902907","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_030_Newport_Beach\/Docs\/S6-190534.zip","group":"S6","meeting":"S6-30","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-190535","title":"LS on Information on MEC work on 5G","source":"SA","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-03-26 14:12:13","uploaded":"2019-03-26 14:28:16","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC","Cc":"SA2, SA5, SA6","lsoriginalls":"SP-190251","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_030_Newport_Beach\/Docs\/S6-190535.zip","group":"S6","meeting":"S6-30","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-190536","title":"Reply LS on D2D enabler for public safety communications in 5GS","source":"SA","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-03-26 14:12:13","uploaded":"2019-03-26 14:28:16","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_MCOver5GS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6, RAN","Cc":"SA2","lsoriginalls":"SP-190260","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_030_Newport_Beach\/Docs\/S6-190536.zip","group":"S6","meeting":"S6-30","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-190537","title":"LS on the availability of and requesting feedback on the stable draft TR 103 582 from ETSI STF555 - \"Study of use cases and communications involving IoT devices in emergency situations\"","source":"ETSI SC EMTEL","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-03-26 14:12:13","uploaded":"2019-03-26 14:28:16","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC SmartM2M, \nETSI TC SmartBAN, \nETSI TC TCCE, \n3GPP SA1, \n3GPP SA3,\n3GPP SA4, \n3GPP SA6, \noneM2M,\nGSMA","Cc":"","lsoriginalls":"EMTEL(19)000016","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_030_Newport_Beach\/Docs\/S6-190537.zip","group":"S6","meeting":"S6-30","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-190891","title":"LS on LI Impacts for LMR-LTE Interworking study","source":"SA3-LI","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-04-24 10:03:47","uploaded":"2019-04-24 12:20:45","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-190891.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-190925","title":"LS reply on PCF and NEF discovery for Edge Computing","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-05-09 09:15:01","uploaded":"2019-05-09 09:30:23","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-190925.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-190926","title":"Observations on standards and technical constraints from 3rd MCX remote Plugtests","source":"ETSI CTI","contact":"Saurav Arora","contact-id":62621,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-05-09 09:19:26","uploaded":"2019-05-09 09:30:23","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-190926.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191047","title":"NGMN 5G End-to-End Architecture Framework.","source":"NGMN Alliance","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"1. About the NGMN Alliance\nThe NGMN Alliance is an industry organization of leading world-wide Telecom Operators, Vendors and Research Institutes (see www.ngmn.org) and was founded by international network operators in 2006. Its objective is to ensure that the functionality and performance of next generation mobile network infrastructure, service platforms and devices will meet the requirements of operators and, ultimately, will satisfy end user demand and expectations. The NGMN Alliance will drive and guide the development of all future mobile broadband technology enhancements with a focus on 5G. The targets of these activities are supported by the strong and well-established partnership of worldwide leading operators, vendors, universities, and successful co-operations with other industry organisations.\n\n2. NGMN 5G Work-Programme, Requirements and Architecture \nIn September 2017 and in February 2018, the first version and the second version of the NGMN End-to-End Architecture Framework was published, building on and developing end-to-end architecture principles from the 2015 5G White Paper, which can support the standardisation and subsequent availability of 5G for 2020 and beyond. \n\n3. Intention of the LS and required actions\nNGMN is pleased to inform the recipient of this liaison statement for information sharing on the interim third version (v3.0) of the NGMN 5G End-to-End Architecture Framework that includes requirements together with descriptions and concepts associated with new topics.\n\nThe new topics include: \n?\tAutonomic networking\n?\tDistributed Ledger Technology\n?\tMinimization or avoidance of tunnelling\n?\tNetwork automation\n\nFurther enhancement, consideration, and review in the articulation of the related requirements together with updates that include security aspects, URLLC, and network data layer is planned for the final version in September 2019.\n\nThis NGMN liaison is intended for information sharing in terms of the new topics that have been introduced in the attached document. Please take this into account in the 5G architecture considerations.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":104700,"status":"noted","reservation_date":"2019-05-24 21:44:54","uploaded":"2019-05-24 21:57:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-191047.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191054","title":"LS on ETSI Plugtest standards Issues","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"1\t. Overall description\nCT1 have received reports from ETSI Plugtest 2 and ETSI Plugtest 3 regarding issues they have noted regarding 3GPP mission critical standards. CT1 intends to see that each of these issues is addressed appropriately and has performed a preliminary review of the issue statements to determine which 3GPP working group could take the lead in understanding and resolving each issue.\nThe table in the annex of this LS provides that preliminary review and indicates which issues could benefit from analysis by SA6 and SA3. CT1 requests SA6 and SA3 to:\n * 1.\texamine this table and determine whether you agree with our preliminary determination of the lead 3GPP working group for each issue,\n * 2.\tto inform CT1 whether SA6 and SA3 are willing to accept leadership on the issues indicated, and\n * 3.\tto provide any additional input on any of these issues regarding leadership or a technical response.\n\nIt is the intention of CT1 to gather technical responses for each issue and provide these responses to ETSI Plugtest.\nCT1 appreciates the assistance of SA6 and SA3 in helping to resolve these issues and thus to advance the usability of mission critical services.\n\n2. \tActions\nTo SA6 and SA3\nACTION: \t3GPP TSG CT WG1 respectfully asks SA6 and SA3 to perform the three actions noted.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9265,"status":"postponed","reservation_date":"2019-05-24 21:45:00","uploaded":"2019-05-24 21:57:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-191054.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191055","title":"LS on clarification for usage of MC Service emergency state for MCData service","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overall description\nTS 23.282 subclause 7.10 together with TS 23.280 subclause 10.10 only provide for MCData emergency alert initiation and MCData emergency alert cancel procedures (both for on-network and off-network) to MCData users. \nThese clauses leave unspecified several aspects regarding what should occur after completion of this procedure. For example, in TS 23.280 subclause 10.10.1.2.1, the statement in step 5 of the procedures says \u201cMC service group calls made to this MC service group by the MC service client 1 will be sent as emergency calls until the emergency state on the MC service client 1 is cancelled.\u201d However, in TS 23.282 there are no procedures for MCData emergency calls of any kind (group or individual). Similarly, in TS 23.280 subclause 10.10.1.2.1, there is the statement \u201cThis procedure will place the MC service client in the MC service emergency state if the MC service client is not already in that state.\u201d But in TS 23.282 there is no mention of the emergency state for an MCData client, nor what effect this condition could have on subsequent MCData calls once in this state.\nCT1 would like to ask SA6:\nQ1. Should the bearers of an MCData session, while the MCData client is in an emergency state, have elevated priority (and\/or pre-emption handling)?\nQ2. There are no procedures in TS 23.282 that allow for elevated priority in emergency data communications. Should File Distribution (FD) sessions and\/or Short Data Service (SDS) sessions somehow be marked as being in an emergency state and\/or be enabled for preferential (emergency) treatment by the system for delivery? \nQ3. If the answer to Q2 is YES, please provide the SA6 detail procedures to accomplish this through specification.\nQ4. If answer to Q2 is NO, please explain the rationale for excluding MCData from emergency handling in TS 23.282, especially in light of the reference to such treatment in TS 23.280 clause 10.10.1.2.1 step 5 from above.\nIn addition, please provide any other clarifications and\/or details for the usage of the emergency state by the MCData client within the MCData service.\n2\t. Actions\nTo 3GPP TSG SA WG6 \nACTION: \t3GPP TSG CT WG1 kindly asks 3GPP TSG SA WG6 group to provide answers and clarifications on the usage of MCData emergency state within the MCData service.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":105500,"status":"postponed","reservation_date":"2019-05-24 21:45:00","uploaded":"2019-05-24 21:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-191055.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191142","title":"LS reply on SCEF support for V2XAPP procedures","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA2 thanks SA6 for their LS on SCEF support for V2XAPP procedures and would like to reply as follows:\n-\tThe exposure of network status reports is already supported by the SCEF via the T8 interface, therefore the existing SCEF\/T8 based procedures defined in TS 23.682 and TS 29.122 can be reused.\n-\tThe monitoring of QoS by a 3rd party application server is partially supported by the SCEF using a status information message for bearer-level events. The SCEF does not support the real-time monitoring of AS session QoS. \n\n2. Actions:\nTo SA6 group.\nACTION: \tSA2 kindly asks SA6 to take the answer into account.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":114200,"status":"noted","reservation_date":"2019-05-24 21:46:16","uploaded":"2019-05-24 21:57:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-191142.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191262","title":"LS on ETSI Plugtest standards Issues","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"1\t. Overall description\nCT1 have received reports from ETSI Plugtest 2 and ETSI Plugtest 3 regarding issues they have noted regarding 3GPP mission critical standards. CT1 intends to see that each of these issues is addressed appropriately and has performed a preliminary review of the issue statements to determine which 3GPP working group could take the lead in understanding and resolving each issue.\nThe table in the annex of this LS provides that preliminary review and indicates which issues could benefit from analysis by SA6 and SA3. CT1 requests SA6 and SA3 to:\n * 1.\texamine this table and determine whether you agree with our preliminary determination of the lead 3GPP working group for each issue,\n * 2.\tto inform CT1 whether SA6 and SA3 are willing to accept leadership on the issues indicated, and\n * 3.\tto provide any additional input on any of these issues regarding leadership or a technical response.\n\nIt is the intention of CT1 to gather technical responses for each issue and provide these responses to ETSI Plugtest.\nCT1 appreciates the assistance of SA6 and SA3 in helping to resolve these issues and thus to advance the usability of mission critical services.\n\n2. \tActions\nTo SA6 and SA3\nACTION: \t3GPP TSG CT WG1 respectfully asks SA6 and SA3 to perform the three actions noted.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2019-06-17 08:44:25","uploaded":"2019-06-17 12:36:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"S6-191525","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_032_Roma\/Docs\/S6-191262.zip","group":"S6","meeting":"S6-32","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191263","title":"LS on clarification for usage of MC Service emergency state for MCData service","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overall description\nTS 23.282 subclause 7.10 together with TS 23.280 subclause 10.10 only provide for MCData emergency alert initiation and MCData emergency alert cancel procedures (both for on-network and off-network) to MCData users. \nThese clauses leave unspecified several aspects regarding what should occur after completion of this procedure. For example, in TS 23.280 subclause 10.10.1.2.1, the statement in step 5 of the procedures says \u201cMC service group calls made to this MC service group by the MC service client 1 will be sent as emergency calls until the emergency state on the MC service client 1 is cancelled.\u201d However, in TS 23.282 there are no procedures for MCData emergency calls of any kind (group or individual). Similarly, in TS 23.280 subclause 10.10.1.2.1, there is the statement \u201cThis procedure will place the MC service client in the MC service emergency state if the MC service client is not already in that state.\u201d But in TS 23.282 there is no mention of the emergency state for an MCData client, nor what effect this condition could have on subsequent MCData calls once in this state.\nCT1 would like to ask SA6:\nQ1. Should the bearers of an MCData session, while the MCData client is in an emergency state, have elevated priority (and\/or pre-emption handling)?\nQ2. There are no procedures in TS 23.282 that allow for elevated priority in emergency data communications. Should File Distribution (FD) sessions and\/or Short Data Service (SDS) sessions somehow be marked as being in an emergency state and\/or be enabled for preferential (emergency) treatment by the system for delivery? \nQ3. If the answer to Q2 is YES, please provide the SA6 detail procedures to accomplish this through specification.\nQ4. If answer to Q2 is NO, please explain the rationale for excluding MCData from emergency handling in TS 23.282, especially in light of the reference to such treatment in TS 23.280 clause 10.10.1.2.1 step 5 from above.\nIn addition, please provide any other clarifications and\/or details for the usage of the emergency state by the MCData client within the MCData service.\n2\t. Actions\nTo 3GPP TSG SA WG6 \nACTION: \t3GPP TSG CT WG1 kindly asks 3GPP TSG SA WG6 group to provide answers and clarifications on the usage of MCData emergency state within the MCData service.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2019-06-17 08:44:25","uploaded":"2019-06-17 12:36:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"S6-191407","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_032_Roma\/Docs\/S6-191263.zip","group":"S6","meeting":"S6-32","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191402","title":"LS response to CT1 on ETSI Plugtest standards issues","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-07-01 21:50:28","uploaded":"2019-07-01 21:55:52","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-193601","lsto":"CT1","Cc":"SA6","lsoriginalls":"S3-192332","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_032_Roma\/Docs\/S6-191402.zip","group":"S6","meeting":"S6-32","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191404","title":"LS to 3GPP SA6 on Study on Application Architecture for enabling Edge Applications","source":"ETSI ISG MEC","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-07-04 14:27:55","uploaded":"2019-07-04 14:38:54","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"MEC(19)000264r1","lsreply":"S6-191630, S6-191735, S6-191841, S6-191904, S6-191953","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_032_Roma\/Docs\/S6-191404.zip","group":"S6","meeting":"S6-32","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191626","title":"Reply to LS on application layer support for V2X services","source":"ETSI TC ITS","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"ETSI TC ITS would like to thank 3GPP TSG SA WG6 for the information related to the application layer support for V2X services work. \nETSI TC ITS will provide feedback on 3GPP TS 23.286, 3GPP TS 23.434 and the new study, if any.\n\nActions:\nTo 3GPP SA WG6, ETSI TC ITS kindly asks to take this information into account.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":16260,"status":"noted","reservation_date":"2019-07-31 15:55:51","uploaded":"2019-08-01 10:01:20","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"ITS(19)035030","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_033_Sophia_Antipolis\/Docs\/S6-191626.zip","group":"S6","meeting":"S6-33","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191707","title":"Reply LS on UAS-related terminology and model","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA1 thanks SA6 for their LS and the intent to clarify and improve the 3GPP UAS terminology and model description, for better alignment with what is used by the aviation industry. \n\nSA1 has discussed some related proposals and agreed to amend SA1 Rel-16 TS 22.125. As a result, the attached CRs were agreed during SA1#87.\n\n2. Actions:\nTo SA6\nACTION: \tSA1 asks SA6 to take the above information into account.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":17070,"status":"noted","reservation_date":"2019-08-26 09:52:04","uploaded":"2019-08-26 10:27:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S6-191612","lsto":"SA6","Cc":"","lsoriginalls":"S1-192817","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_033_Sophia_Antipolis\/Docs\/S6-191707.zip","group":"S6","meeting":"S6-33","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191708","title":"Liaison Statement from SC 29\/WG 11 to 3GPP SA 2 and SA 6 on NBMP [SC 29\/WG 11 N 18738]","source":"ISO IEC","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"to describe, deploy, and control\nmedia processing for their content in the network\/cloud.\nNBMP workflows are composed of multiple media processing tasks that are connected to build a direct\nacyclic graph to process incoming media and metadata from a media source and to produce processed\nmedia and metadata streams, which are subsequently published for consumption by media sinks.\nThe DIS specification brings several quality improvements and clarifications to the different functionalities\nof the NBMP standard.\nMPEG would like to invite you to consider NBMP for your future work on media processing and to share\nyour comments and thoughts on this version of the NBMP specification. You are also encouraged to\nsubscribe to the AHG mailing list at https:\/\/lists.aau.at\/mailman\/listinfo\/mpeg-nbmp.\nFor your information, our future meeting schedule is as follows:\n- 128th MPEG meeting on October 07-11, 2019 in Geneva, CH\n- 129th MPEG meeting on January 13-17, 2019 in Brussels, BE\nReferences\n[1] N18657, \u201cText of ISO\/IEC DIS 23090-8 Network-based Media Processing\u201d\nhttp:\/\/wg11.sc29.org\/doc_end_user\/documents\/127_Gothenburg\/wg11\/w18657.zip","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":17080,"status":"replied to","reservation_date":"2019-08-26 10:04:46","uploaded":"2019-08-26 10:27:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, SA6","Cc":"","lsoriginalls":"29n18316","lsreply":"S6-191795","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_033_Sophia_Antipolis\/Docs\/S6-191708.zip","group":"S6","meeting":"S6-33","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191794","title":"LS on restricting incoming private calls","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":17940,"status":"replied to","reservation_date":"2019-08-30 16:52:11","uploaded":"2019-08-30 16:57:36","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"C1-195062","lsreply":"S6-191805","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_033_Sophia_Antipolis\/Docs\/S6-191794.zip","group":"S6","meeting":"S6-33","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191929","title":"LS on clarifications regarding V2XAPP services","source":"CT3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":17950,"status":"postponed","reservation_date":"2019-09-08 21:02:16","uploaded":"2019-09-08 21:27:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"C3-193621","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_033_Sophia_Antipolis\/Docs\/S6-191929.zip","group":"S6","meeting":"S6-33","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192010","title":"NGMN 5G End-to-End Architecture Framework","source":"NGMN Alliance Project E2E Architecture Framework","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-10-04 09:58:18","uploaded":"2019-10-07 08:21:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA, SAG2, SA5, SA6, RAN, ETSI ISG PDL, ZSM, ITU-T SG13 and TM Forum","Cc":"","lsoriginalls":"190916","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192010.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192011","title":"LS reply to A-190116 3GPP SA6 application layer support for V2X services","source":"5GAA WG2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2019-10-04 09:58:18","uploaded":"2019-10-07 08:21:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, SA6","Cc":"","lsoriginalls":"S-190183","lsreply":"S6-192395","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192011.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192012","title":"LS on clarifications regarding V2XAPP services","source":"CT3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2019-10-04 09:58:18","uploaded":"2019-10-07 08:21:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"C3-193621","lsreply":"S6-192185","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192012.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192013","title":"LS on O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs","source":"O-RAN Alliance","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-10-04 09:58:18","uploaded":"2019-10-07 08:43:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA, CT, RAN, SA1, SA2, SA3, SA5, SA6, RAN1, RAN2, RAN3","Cc":"3GPP PCG","lsoriginalls":"ORAN_3GPP_Liaison_Statement_final","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192013.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192014","title":"LS on SG11 activities related to improvement of the SS7 security including for digital financial services","source":"ITU SG11","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-10-04 09:58:18","uploaded":"2019-10-07 08:43:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA, 3GPP; ITU FIGI SIT WG","Cc":"","lsoriginalls":"SG11-LS99","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192014.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192015","title":"Reply LS to \u201cO-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs\u201d","source":"SA","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-10-04 09:58:18","uploaded":"2019-10-07 08:43:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"O-RAN Alliance","Cc":"CT, RAN, SA1, SA2, SA3, SA5, SA6, RAN1, RAN2, RAN3","lsoriginalls":"SP-190947","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192015.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192020","title":"LS on how the IWF obtains key material for interworking group and private communications","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2019-10-25 10:10:53","uploaded":"2019-10-25 14:36:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"MCCI_CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3, SA6","Cc":"","lsoriginalls":"","lsreply":"S6-192194","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192020.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192023","title":"LS on clarifications regarding SEAL services","source":"CT3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2019-10-25 14:23:25","uploaded":"2019-10-25 14:36:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SA6","lsto":"","Cc":"","lsoriginalls":"","lsreply":"S6-192318","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192023.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192187","title":"LS reply from 3GPP SA5 to NGMN on 5G End-to-End Architecture Framework","source":"SA5","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-11-04 22:18:25","uploaded":"2019-11-04 22:33:28","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"NGMN","Cc":"RAN, SA, SA2, SA3, SA6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192187.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-192192","title":"LS on Testing and Certification of 3GPP Mission Critical features A GCF-TCCA Joint Approach to Develop and Manage MC Certification","source":"TCCA","contact":"Harald Ludwig","contact-id":14305,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-11-08 15:54:13","uploaded":"2019-11-08 15:55:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GCF SG","Cc":"SA6, CT1, RAN5, ETSI CTI, ETSI STF160, ETSI MCX Plugtests team, GSMA","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_034_Reno\/Docs\/S6-192192.zip","group":"S6","meeting":"S6-34","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200006","title":"LS on Unicast resource management with SIP core","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overall description\nCT1 are working on the stage 3 details of SEAL for network resource management and based on stage 2 in TS 23.434 the request for unicast resources at VAL service communication establishment procedure can use SIP core (see clause 14.3.3.2). For this case, the SIP protocol is used between the SNRM-S and the SIP core which later communicates with the PCRF\/PCF. It is CT1\u2019s understanding that the SIP core just copies the information received in the SIP MESSAGE request (sent to establish unicast resource) and interacts with the PCRF\/PCF. CT1 wonder if in stage 3 the SNRM-S can interact directly with the PCRF\/PCF.\n2. \tActions\nTo 3GPP TSG SA WG6\nACTION: \tCT1 kindly ask SA6 how the SIP core work with regards to unicast resource management.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":60,"status":"replied to","reservation_date":"2019-12-04 18:16:02","uploaded":"2019-12-05 15:21:22","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"C1-198613","lsreply":"S6-200163","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_035_Hyderabad\/Docs\/S6-200006.zip","group":"S6","meeting":"S6-35","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200007","title":"LS on Enquiries for supporting vertical applications","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. \tOverall description\nCT1 have the following enquires with regards to the work on supporting vertical applications:\n(1) \tCT1 have checked the stage 2 work in TS 23.434 clause 6.5.3.2 and 6.5.3.3 which indicate that SIP signalling is used (the use of SIP-1 and SIP-2 reference points and indication of communication of the TMGI for multicast operation). CT1 have the understanding that in the context of SEAL HTTP should be used instead of SIP signalling for resource management, and therefore:\nCT1 wonder whether it is correct SIP signalling or use HTTP or both for MBMS resource management.\n(2)\t CT1 have checked the stage 2 work in TS 23.434 clause 9.3.3 on Event-triggered location reporting procedure. In that procedure, the location reporting configuration message is sent from the server to the client. CT1 have the understanding that in the context of SEAL HTTP should be used for the event-triggered location reporting procedure, and therefore:\nCT1 ask SA6 to clarify how the location reporting configuration message can be used using HTTP methods.\n(3)\t CT1 have checked the stage 2 work in TS 23.434 and TS 23.286 and one aspect is that LMS should be able to leverage the MBMS to configure several LMCs at the same time. In addition to that, for V2AXAPP communication over V1-AE MBMS transport can be used.\nCT1 have the understanding that in the context of SEAL and V2XAPP HTTP is used. As TCP cannot be transmitted over MBMS (i.e., MBMS does not support acknowledgement from the client). QUIC with HTTP could be in principle a possibility but note that the use of QUIC is not part of 3GPP yet and a number of issues have been identified in 3GPP (see 3GPP TS 29.893 by CT4 so the use of QUIC seems not possible in Rel-16.\nCT1 ask SA6 to provide guidance on how to proceed for which protocol to use for signalling over MBMS.\n\n2. \tActions\nTo 3GPP TSG SA WG6\nACTION: \tCT1 kindly ask SA6 to provide answer to enquires outlined above in order to progress on the vertical applications work.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":70,"status":"replied to","reservation_date":"2019-12-04 18:16:02","uploaded":"2019-12-05 15:21:22","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"SEAL"},{"winame":"V2XAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"C1-198623","lsreply":"S6-200164","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_035_Hyderabad\/Docs\/S6-200007.zip","group":"S6","meeting":"S6-35","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200008","title":"LS to CT1 on 3rd ETSI MCX Remote Plugtest","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":80,"status":"noted","reservation_date":"2019-12-04 18:16:02","uploaded":"2019-12-05 15:21:22","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"MCXSec"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA6","lsoriginalls":"S3-194611","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_035_Hyderabad\/Docs\/S6-200008.zip","group":"S6","meeting":"S6-35","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200009","title":"LS on analysis of GSMA GST attributes","source":"SA5","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":90,"status":"noted","reservation_date":"2019-12-04 18:16:02","uploaded":"2019-12-05 15:21:22","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"MA5SLA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, RAN3, IETF","Cc":"SA, SA1, SA6, RAN2, GSMA 5GJA, ETSI ISG ZSM","lsoriginalls":"S5-197853","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_035_Hyderabad\/Docs\/S6-200009.zip","group":"S6","meeting":"S6-35","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200010","title":"Reply LS on Application Architecture for enabling Edge Applications","source":"SA5","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":72,"status":"replied to","reservation_date":"2019-12-04 18:16:02","uploaded":"2019-12-05 15:21:22","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-197479 [S6-192399]","lsto":"SA6","Cc":"SA2","lsoriginalls":"S5-197752","lsreply":"S6-200237","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_035_Hyderabad\/Docs\/S6-200010.zip","group":"S6","meeting":"S6-35","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200011","title":"LS on Split of work responsibilities between SA2 and SA6","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":74,"status":"replied to","reservation_date":"2019-12-04 18:16:02","uploaded":"2019-12-05 15:21:22","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_enh_EC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA","lsoriginalls":"S2-1912771","lsreply":"S6-200165","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_035_Hyderabad\/Docs\/S6-200011.zip","group":"S6","meeting":"S6-35","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200012","title":"LS on Control Room Workshop","source":"TCCA","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":78,"status":"noted","reservation_date":"2019-12-04 18:16:02","uploaded":"2019-12-05 15:21:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"LS on Control Room Workshop (from TCCA to 3GPP SA6)_v1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_035_Hyderabad\/Docs\/S6-200012.zip","group":"S6","meeting":"S6-35","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200058","title":"IoT API: Edge and Fog Computing","source":"oneM2M TP (meeting 43, December 2019)","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":76,"status":"noted","reservation_date":"2020-01-03 15:41:15","uploaded":"2020-01-03 16:02:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_035_Hyderabad\/Docs\/S6-200058.zip","group":"S6","meeting":"S6-35","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200967","title":"Reply LS on limiting the number of simultaneous log ins of an MCX user","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"1. Overall Description:\nSA1 thanks CT1 for their LS in C1-202819.\nSA1 have discussed the issue.\n\nWith respect to the question from CT1: \nDoes requirement [R-5.10-001a] of 3GPP TS 22.280 require that a different limit can be applied to each MCX User?\nSA1 have discussed the issue and the answer is No.\n\nThe existing requirement should be interpreted as meaning \"a single system limit per MCX service shall be applied to all users within the MCX service, which aligns with the existing stage 2 architecture defined by SA6 for Release 16 in TS 23.379.\"\nAttached you\u2019ll find the Release 16 and Release 17 (mirror) CRs to TS22.280 clarifying the existing requirement to be a system wide limit. One additional CR adds a new requirement in Rel-17 to allow for different limits per MCX user.\n\n2. Actions:\nTo CT1 group.\nACTION: \tSA1 asks CT1 to take the information provided into account for their further work.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9670,"status":"noted","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA6","lsoriginalls":"S1-202280","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200967.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200968","title":"Reply to LS on Clarification of the definition of a UAS","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA1 has considered the incoming LS from SA6 requesting clarification on stage 1 requirements, as copied below.\n\nThe text in the definition of a UAS and other normative text in TS 22.125 is not aligned with the informative Annex A. Further, it can be noted that there is text in the informative Annex A that is normative.\n\nSA1 has discussed the definition of a UAS and come to the conclusion that an update of TS 22.125 is needed, see the attached agreed CR.\n\n2. Actions:\nTo SA2 and SA6 groups.\nACTION: \tSA1 requests SA2 and SA6 to take the above into account in their work and update their specifications as necessary.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9680,"status":"noted","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, SA6","Cc":"","lsoriginalls":"S1-202267","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200968.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200969","title":"LS on requirement for 5GMSG in broadcast scenario","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA1 thanks SA6 for the question if requirement [R-5.5.2-002] applies to all UE types, i.e. UE B, UE C and UE D as defined in TS 22.262 or only to UE types that support the broadcast message.\n\nThe MSGin5G Service for MIoT needs to support broadcast message delivery in order to handle massive communications efficiently with a latency less than [500] ms as specified in requirement [R-5.5.2-001]. This requirement cannot be achieved with point-to-point message delivery. Therefore, the requirement applies to UEs that support the broadcast message.\n\n2. Actions:\nTo SA6 group.\nACTION:\tSA1 asks SA6 to take the above information into account.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9690,"status":"noted","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GMSG"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S1-202269","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200969.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200970","title":"Reply LS on Clarification of requirements for UAS application enablement","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA1 thanks SA6 for the LS requesting clarification on stage 1 requirements, copied bellow.\n\nSA6 has discussed potential key issues on:\n\n\u2022\tWhether and how to enable flight route support in 3GPP network\n\u2022\tWhether and how to control a UAV fly route under 3GPP network\n\u2022\tWhether and how to enable NOTAM\/TFR support under 3GPP network\n\nSA6 asks SA1 to kindly guide SA6 on the requirements for the use cases mentioned above and also the necessity to explicitly refer to application-aware parameters. SA6 kindly asks SA1 to update their specification if necessary.\n\nSA1 has discussed pointed out requirements [R-5.1-003] and [R-5.1-004] from TS 22.125:\n\n[R-5.1-003] The 3GPP system shall enable a UAS to send UTM the UAV data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner certification, take-off location, mission type, route data, operating status.\n\n[R-5.1-004] The 3GPP system shall enable a UAS to send UTM the UAV controller data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV controller, position, owner identity, owner address, owner contact details, owner certification, UAV operator identity, UAV operator license, UAV operator certification, UAV pilot identity, UAV pilot license, UAV pilot certification and flight plan.\n\nThese requirements are coming from use case for initial authorization to operate. The use case and derived requirements indicate 3GPP system shall enable data communication between UAS and UTM. Indicated parameters show by which means the UAV and UAV controller shall be identified and inform that list of identification data sent towards the UTM could be quite long.\nSA6 discussions on potential key issues described above which enable 3GPP to control UAV flight route and NOTAM\/TFR are outside the scope of the service requirements for UAS support in 3GPP.\n\n2. Actions:\nTo SA6 group.\nACTION: \tSA1 kindly asks SA6 to take the above information into account.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9700,"status":"noted","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA2","lsoriginalls":"S1-202270","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200970.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200971","title":"Reply LS on Application Architecture for enabling Edge Applications","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA2 thanks SA6 for the LS on Application Architecture for enabling Edge Applications (S2-2002608\/S6-192399), and would like to provide the following feedback. \nSA2 understood that the \u201cApplication architecture\u201d in clause 6.2 in TR 23.758 reuses SA2 defined reference points of EPS or 5GS for retrieval of network capability information. SA2 would like to highlight that SA2 supports Edge Computing specific functions only in 5GS.\nSA2 understood that some solutions in TR 23.758 have dependencies on SA2 work as listed in Table 11.3.1-1 of the TR. SA2 hasn\u2019t discussed whether any new SA2 features are needed to support these solutions. SA6 is welcome to send LS in case specific dependencies on SA2 are identified.\n2. Actions:\nTo SA6 group.\nACTION: \tSA2 kindly asks SA6 to take above feedback into consideration.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9710,"status":"noted","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_enh_EC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA3, SA5","lsoriginalls":"S2-2004386","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200971.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200972","title":"Reply LS on provisioning \"\"EDN connection info\"\" by Edge Configuration Server","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA2 thanks SA6 about the LS on provisioning \"EDN connection info\" by Edge Configuration Server (S2-2003201\/S6-200617). SA2 discussed the questions and agreed the following answers.\n\nQ1: SA6 kindly requests that SA2 comment on whether SA6\u2019s understanding that a UE Application may provide a DNN is correct?\n\nSA2 answer: SA2 considers the UE application mentioned in Q1 means upper layer to NAS (URSP handling) layer and SA2 confirms that the UE Application may provide a DNN that is used for matching Traffic descriptor(s) in the URSP rules.\n\nQ2: SA6 kindly requests that SA2 comment on how to handle the scenario when parameters provisioned by Edge Configuration Server create a conflict with URSP rules, ANDSP rules or UE local configuration?\n\nSA2 answer: According to TS 23.503, the association of an application to a PDU Session is based on either URSP (if provisioned by the operator) or UE Local Configuration. \nSA2 treats the parameters provisioned by Edge Configuration Server as UE Local Configuration. The handling precedence between URSP and UE Local Configuration is defined in TS 23.503 clause 6.1.2.2.1.\n\nQ3: SA6 kindly requests that SA2 comment on whether S-NSSAI can be provisioned by 3rd party via the application layer?\n\nSA2 answer: According to TS 23.503, the association between application traffic and S-NSSAI associated to a PDU Session (by evaluating either URSP or UE Local Configuration) should be controlled by the operator to ensure that only expected service traffic flows are transferred via a specific slice. The UE Local Configuration (e.g. the operator specific configuration including S-NSSAI) can be configured by the operator (or operator\u2019s contracted partner), however it is out of scope of SA2 how UE Local Configuration is configured in UE.\n\nAs an alternative to UE Local Configuration, some solutions are under discussion in TR 23.748 for Rel-17 to support the application layer (e.g. ECS) to influence the URSP rules that the network provisions to the UE. \n\n2. Actions:\nTo SA6 group.\nACTION: \tSA2 kindly asks SA6 to take above information into consideration.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9720,"status":"noted","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_enh_EC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S2-2004387","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200972.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200973","title":"Liaison from IETF Scope and goals of the  Drone Remote ID Protocol Working Group (DRIP) of the Internet Engineering Task Force (IETF)","source":"IETF DRIP","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"Dear Sir, \nThis email intents to share with 3GPP the scope and goals of the  Drone Remote ID Protocol Working Group (DRIP) of the Internet Engineering Task Force (IETF).\n\nThe remaining of this email contains a brief description of the DRIP Working Group as well as the IETF. \n\nIf you have any questions or concerns, feel free to contact us, we would be more than happy to take them into account.\n\nThe DRIP co-chairs: Mohammed Boucadair and Daniel Migault\nThe Internet Area Director: Eric Vyncke.\n\nFor the complete presentation please refer to the original LS available in S6-200973.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9730,"status":"postponed","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"IETF LS 9th June2020","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200973.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200974","title":"LS on SA5 Rel-17 work on SLA","source":"SA5","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"","abstract":"1. Overall Description:\nSA5 has cooperated with GSMA 5GJA on implementing NG.116 (v2.0) GST SLA attributes as network slice ServiceProfile attributes in the 3GPP Network Resource Model (NRM) (TS 28.541 clauses 6.3.3, 6.4.1) in the Rel-16 work item Management Aspects of 5G Service-Level Agreement. This work item has been finalised in Rel 16, and a continuing Rel-17 work item Enhancement of Management Aspects of 5G Service-Level Agreement (SP-200190) has been approved. In Rel-17, SA5 will continue working on implementing updated GST SLA attributes, as GSMA 5GJA will continue working on NG.116. \n\nIn addition, SA5 will work on breaking down SLA requirements to NetworkSliceSubnet to update the SliceProfile in the 3GPP NRM, which can provide clear requirements to CN, RAN and TN (TS 28.541 clauses 6.3.4, 6.4.1).\n\n2. Actions:\nTo GSMA 5GJA:\nSA5 respectfully requests GSMA 5GJA to take this information into account and provide feedback, if necessary.\n\nTo SA2 group:\nSA5 respectfully requests 3GPP SA2 to take this information into account and provide feedback, if necessary.\n\nTo RAN3 group:\nSA5 respectfully requests 3GPP RAN3 to take this information into account and provide feedback, if necessary.\n\nTo IETF TEAS WG:\nSA5 respectfully requests IETF TEAS WG to take this information into account and provide feedback, if necessary.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9740,"status":"noted","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"EMA5SLA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GJA, 3GPP SA2, RAN3, IETF TEAS WG","Cc":"3GPP SA, SA1, SA6, RAN2, ETSI ISG ZSM","lsoriginalls":"S5-203370","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200974.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200975","title":"LS on Key Management procedure in SEAL","source":"CT3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"1. \tOverall description\nAs specified in the clause 5.3 of TS 33.434 v0.4.0, the VAL server may request key material applicable to particular SEAL service, VAL client or user. CT3 seeks clarifications on SEAL KM Request message from VAL server to Key Management server, as specified in the clause 5.3.2. \nCT3 asks SA3 to clarify the following:\nQ1. Need clarity on the \u201cVersion\u201d information element. What is the purpose of this version? Is it used to identify a key version or a message version for the reference point? \nQ2. On ClientID that maps to the VAL client, there is no explicit requirement in TS 23.434 requiring a VAL server to support VAL client id. Is ClientID needed only for KM-UU? Or it is also applicable for KM-S reference point? \nQ3. Except for identifying the late requests and responses, is there any other requirement of date\/time in the KM request and the corresponding KM request response? \nQ4. As per SEAL KM request procedure, the KMS shall verify the SKMSUri is the SKM-S URI of the target SEAL KMS. It is not clear if the SKMSUri is the URI where the key information are storedor it is a URI on the target KMS that the receiving KMS needs to further use\/contact the target KMS via SEAL-E reference point by using the SkmsURI?\nQ5. In SEAL KM response message, why is \u201cPayload\u201d optional and what is the meaning of \u201cif the request does not require a payload\u201d in its description? Are these to indicate there is no provisioned key material specific to the VAL service, VAL user\/ue\/client in the SEAL KM request? If so, what is the expected behavior for the VAL server, VAL user\/ue\/client after receiving the response without key?\n\n2. \tActions\nTo SA WG3 group: \nACTION: \tCT3 kindly asks SA3 to answer the above questions.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9750,"status":"noted","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3","Cc":"SA6, CT1","lsoriginalls":"C3-203588","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200975.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200976","title":"LS to 3GPP RAN5 on Requirement for Mission Critical Services (MCX) Testing and Certification 3GPP Release level","source":"GCF-TCCA Joint Taskforce","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9760,"status":"noted","reservation_date":"2020-06-30 21:45:45","uploaded":"2020-06-30 23:28:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN5","Cc":"MCC TF160, 3GPP SA6","lsoriginalls":"MCC-JTF-20-062r2","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200976.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200977","title":"LS on location reporting triggers","source":"CT3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overall description\nAs defined in clause 9.3.5 of TS 23.434, the VAL server configures the location reporting trigger to the location management server to activate a location reporting procedure for obtaining the location information of location management client. It\u2019s unclear that whether it is a one-time configuration or not.\nAlso as defined in clause 9.3.6 of TS 23.434, the location management server may cancel the location reporting triggers configuration to the location management client. \nCT3 asks SA6 to clarify the following:\nQ1:\tIf the VAL server has configured the reporting event triggers to the location management server, can the VAL server update the configuration information later, e.g. extend Triggering criteria?\nQ2:\tIf the VAL server has configured the reporting event triggers to the location management server, can the VAL server cancel the configurations at a later time?\nAlso, in TS 29.549, for SS_GroupManagement API, CT3 updated \u201cConfigure_Group_Info\u201d service operation\u2019s name to \u201cUpdate_Group_Info\u201d. CT3 kindly asks SA6 to take this information into consideration and update their specification.\n\n2. \tActions\nTo SA WG6 group:\nACTION: \tCT3 kindly asks SA6 to answer above questions and update their specification if necessary.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9770,"status":"replied to","reservation_date":"2020-07-01 01:11:10","uploaded":"2020-07-01 01:14:17","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"C3-202441","lsreply":"S6-201259","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200977.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200978","title":"LS on limiting the number of simultaneous log ins of an MCX user","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9780,"status":"noted","reservation_date":"2020-07-01 01:11:11","uploaded":"2020-07-01 01:14:17","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"MONASTERY2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA1","Cc":"SA6","lsoriginalls":"C1-202819","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200978.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-200979","title":"5G capabilities exposure for factories of the future","source":"5G-ACIA","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"1. Overall Description:\nOver the last two years, 5G-ACIA has collected and analysed many industrial use cases. These use cases \u2013 as well as inferred communication service characteristics \u2013 have been documented by 3GPP in TS 22.104 and TS 22.261. 5G-ACIA has further refined and analysed operational use cases that are needed by factory operators to manage and maintain 5G-enabled devices and 5G Non-Public Networks (NPN) in a simple and efficient manner.\n \n5G-ACIA believes the service exposure requirements derived from the aforementioned operational use cases are valuable input for upcoming contributions addressing ongoing work in 3GPP, such as the study items documented in TR 23.700 and TR 23.745. These requirements have been published in the 5G-ACIA white paper Exposure of 5G capabilities for connected industries and automation applications (www.5g-acia.org\/publications), which is also attached to this LS.\n\nThis white paper focuses on operational use cases pertaining to device management, for example use cases that enable factory operators to manage the life cycle of devices, and e.g. to change and monitor the devices\u2019 connectivity. In order to execute these operational use cases efficiently, the industrial systems require a set of well standardised and published APIs that hide a great deal of 3GPP complexity and yet provide the needed flexibility to the factory operator.\nThese capabilities are needed by factories of the future and expected from 5G NPN and 5G-enabled devices. 5G-ACIA would like to highlight the importance of these refined requirements for industrial operations and would appreciate it very much, if 3GPP considered the provided information to ongoing and upcoming specification work.\n5G-ACIA would be eager to receive 3GPP\u2019s feedback on these new exposure interface requirements and related Stage-2 and Stage-3 work.\n\n2. Actions:\nTO             3GPP TSG SA \nACTION:   Consider the content of the white paper and advice any related 3GPP WG on needed study items or actions and provide feedback to 5G-ACIA on planned activities.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9790,"status":"noted","reservation_date":"2020-07-01 10:27:58","uploaded":"2020-07-01 11:13:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG SA","Cc":"3GPP SA1, SA2, SA3, SA5, SA6, CT3, IEC TC65, oneM2M TP, OPC Foundation, PI, IEEE TSN, TM Forum, ETG","lsoriginalls":"5G-ACIA-LS-2020-WI039","lsreply":"S6-201093, S6-201175","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_038-e\/Docs\/S6-200979.zip","group":"S6","meeting":"S6-38-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201339","title":"Liaison from IETF Scope and goals of the Drone Remote ID Protocol Working Group (DRIP) of the Internet Engineering Task Force (IETF)","source":"IETF DRIP","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-08-11 20:09:04","uploaded":"2020-08-11 20:16:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"IETF LS 9th June2020","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-e\/Docs\/S6-201339.zip","group":"S6","meeting":"S6-39-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201529","title":"Reply LS to LS to 3GPP RAN5 on Requirement for Mission Critical Services (MCX) Testing and Certification 3GPP Release level","source":"RAN5","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-08-27 16:42:24","uploaded":"2020-08-27 16:44:27","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GCF Mission Critical Agreement Group (MCAG)","Cc":"SA6","lsoriginalls":"R5-204364","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-e\/Docs\/S6-201529.zip","group":"S6","meeting":"S6-39-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201530","title":"LS on ETSI Plugtest reports","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2020-09-01 13:14:52","uploaded":"2020-09-01 13:42:03","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI Plugtests","Cc":"SA3, SA6","lsoriginalls":"C1-204693","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-e\/Docs\/S6-201530.zip","group":"S6","meeting":"S6-39-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201531","title":"LS on clarifications for authorised user learning about the users whose floor requests are queued","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2020-09-01 13:20:36","uploaded":"2020-09-01 13:42:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"C1-205510","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-e\/Docs\/S6-201531.zip","group":"S6","meeting":"S6-39-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201534","title":"LS on application layer impact of FS_enh_EC solution #16","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2020-09-03 17:58:16","uploaded":"2020-09-03 18:02:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S2-2005963","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-e\/Docs\/S6-201534.zip","group":"S6","meeting":"S6-39-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201535","title":"LS on IP address to GPSI translation","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2020-09-03 17:58:17","uploaded":"2020-09-03 18:02:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA3","lsoriginalls":"S2-2005923","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-e\/Docs\/S6-201535.zip","group":"S6","meeting":"S6-39-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201694","title":"LS on ETSI Plugtest reports","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":16940,"status":"noted","reservation_date":"2020-09-23 18:05:48","uploaded":"2020-09-24 21:33:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI Plugtests","Cc":"SA3, SA6","lsoriginalls":"C1-204693","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201694.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201695","title":"LS on clarifications for authorised user learning about the users whose floor requests are queued","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":16950,"status":"replied to","reservation_date":"2020-09-23 18:05:48","uploaded":"2020-09-24 21:33:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"C1-205510","lsreply":"S6-201730, S6-201911, S6-202007","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201695.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201696","title":"LS on application layer impact of FS_enh_EC solution #16","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":16960,"status":"revised","reservation_date":"2020-09-23 18:05:48","uploaded":"2020-09-24 21:33:40","revisionof":"","revisedto":"S6-201882","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S2-2005963","lsreply":"S6-201777, S6-201816, S6-201903","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201696.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201697","title":"LS on IP address to GPSI translation","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":16970,"status":"replied to","reservation_date":"2020-09-23 18:05:48","uploaded":"2020-09-24 21:33:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA3","lsoriginalls":"S2-2005923","lsreply":"S6-201813, S6-201971","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201697.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201698","title":"Response LS on 5GMSG requirement clarifications","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":16980,"status":"noted","reservation_date":"2020-09-23 18:05:49","uploaded":"2020-09-24 21:33:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S6-201315","lsto":"SA6","Cc":"","lsoriginalls":"S1-203273","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201698.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201699","title":"LS on 5GMSG store and forward","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":16990,"status":"noted","reservation_date":"2020-09-23 18:05:49","uploaded":"2020-09-24 21:33:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S6-200946","lsto":"SA6","Cc":"","lsoriginalls":"S1-203275","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201699.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201700","title":"Reply LS on security procedures for Edge Applications","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":16975,"status":"noted","reservation_date":"2020-09-23 18:05:49","uploaded":"2020-09-24 21:33:40","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S6-200945","lsto":"SA6","Cc":"","lsoriginalls":"S3-202087","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201700.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201701","title":"Reply LS on Key Management procedure in SEAL","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":17010,"status":"noted","reservation_date":"2020-09-23 18:05:49","uploaded":"2020-09-24 21:33:40","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"SA6, CT1","lsoriginalls":"S3-202177","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201701.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201702","title":"LS on Rel-17 schedule","source":"SA","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":17020,"status":"noted","reservation_date":"2020-09-23 18:05:49","uploaded":"2020-09-24 21:33:40","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA1, SA2, SA3, SA4, SA5, SA6, CT","Cc":"RAN","lsoriginalls":"SP-200888","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201702.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201714","title":"Support of UAVs in 3GPP system and interfacing with USS\/UTM","source":"ACJA (GSMA and GUTMA)","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":17015,"status":"noted","reservation_date":"2020-10-05 20:14:46","uploaded":"2020-10-05 20:24:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"SA6, SA3, SA1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201714.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201882","title":"LS on application layer impact of FS_enh_EC solution #16","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"Revision of the incoming LS to correct the incorrect TDoc number (S6-2011696) in the file name in the zip archive.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":16965,"status":"replied to","reservation_date":"2020-10-08 06:06:47","uploaded":"2020-10-08 06:18:08","revisionof":"S6-201696","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S2-2005963","lsreply":"S6-201777, S6-201816, S6-201748, S6-202025","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201882.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-201883","title":"Reply LS on ETSI Plugtest reports","source":"UPV\/EHU (ETSI MCX Plugtests)","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":17030,"status":"postponed","reservation_date":"2020-10-13 19:33:29","uploaded":"2020-10-13 19:45:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA3, SA6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_039-BIS-e\/Docs\/S6-201883.zip","group":"S6","meeting":"S6-39-bis-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]