[{"name":"S6-161280","title":"3GPP SA6 MCData and MCVideo work prioritisation","source":"TCCA","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"Summary of liaison\nThis liaison statement is intended to provide TCCA CCBG\u2019s members view on the 3GPP SA6 MCdata and MCVideo work prioritisation. The priotisation spreadsheet provided by Yannick Lair, SA6 chairman was fulfilled in the CCBG plenary meetin","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":12800,"status":"noted","reservation_date":"2016-10-20 08:59:37","uploaded":"2016-10-21 07:06:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161280.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-161281","title":"LS on Predictable pre-emption of media flows","source":"CT3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nCT3 has discussed the solutions to support adding the pre-emption control information in Rx reference point. CT3 noticed that several requirements are not clear enough, if implemented, in Stage 3.\n\nCT3 would like to ask SA2 to a","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":12810,"status":"noted","reservation_date":"2016-10-21 06:55:31","uploaded":"2016-10-21 07:06:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"C3-163346","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161281.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-161287","title":"LS on protection of RTCP transported media control messages, RTCP APP transported pre-established session control messages and MBMS subchannel control messages","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"1\t. Overall description\nTS 33.179 does not specify:\n1)\tprotection of media control messages, i.e. RTCP SR packets, RTCP RR packets, and RTCP SDES packets specified in RFC3550 section 6.4 and RFC3550 section 6.5;\n2)\tprotection of pre-established session","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":12870,"status":"noted","reservation_date":"2016-10-31 12:53:51","uploaded":"2016-10-31 13:14:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"C1-164680","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161287.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-161288","title":"LS on Floor override without using floor revoke","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. \tOverall description\nThe procedure, in subclause 10.9.1.3.2.2 of TS 23.179 v13.3.0:\n\u2022\tis not clear whether the overridden participant receives the  audio packets of the overriding participant; and\n\u2022\tdoes not specify the behaviour of the floor contro","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":12880,"status":"replied to","reservation_date":"2016-10-31 12:55:20","uploaded":"2016-10-31 13:14:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA1","lsoriginalls":"C1-164844","lsreply":"S6-161458, S6-161458, S6-161520","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161288.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-161289","title":"LS on Mission Critical Push-To-Talk (MCPTT) requirements not covered in OMA-TS-XDM_Group-V1_1","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"1. \tOverall description\n3GPP TSG CT WG1 has been working on Mission Critical Push-To-Talk (MCPTT) enabler.\nMCPTT enabler defines (among other features) half-duplex communication among members of a MCPTT group.\nThe administration of the MCPTT groups is","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":12890,"status":"noted","reservation_date":"2016-10-31 12:56:59","uploaded":"2016-10-31 13:14:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"C1-164877","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161289.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-161451","title":"MCData prioritization and questions","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overview\nSA3 is working towards defining a security solution for MCData within the timeframe afforded in Release 14.  While some basic security architecture is being developed for MCData in SA3, further advancement of this service depends on two prim","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":145100,"status":"replied to","reservation_date":"2016-11-13 08:49:10","uploaded":"2016-11-13 09:40:37","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"S3-162003","lsreply":"S6-161488, S6-161612","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161451.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-161452","title":"LS on Terminology used by SA6 for Mission Critical Service","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nIn attempting to update our Rel-13 specification to be applicable to Rel-14, SA3 is unsure of the correct terminology that should be used to describe the Mission Critical Service. It is not clear to SA3 how SA1's terminology align","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":145200,"status":"replied to","reservation_date":"2016-11-13 09:10:42","uploaded":"2016-11-13 09:40:37","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"S3-162082","lsreply":"S6-161489, S6-161489, S6-161555, S6-161621","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161452.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-161453","title":"Reply LS on protection of RTCP transported control messages","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"1. Overall Description:\nSA3 thanks CT1 for its LS on the protection of RTCP transported control messages (C1-164680). CT1 asserts that the following functionality is not specified in TS 33.179:\n\n1)\tprotection of media control messages, i.e. RTCP SR pac","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":145300,"status":"noted","reservation_date":"2016-11-13 09:12:45","uploaded":"2016-11-13 09:40:37","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"S3-161997","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161453.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-161455","title":"Reply LS on Call back requirement clarification","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"1. Overall Description:\nSA1 thanks SA6 for the Liaison Statement S6-161228\/S1-163174 on the addition of a new Interworking requirement between LTE and non-LTE systems. Interworking between LTE and non-LTE systems remains a critical capability required by","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":145500,"status":"noted","reservation_date":"2016-11-13 22:52:46","uploaded":"2016-11-13 22:56:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"S1-163426","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161455.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-161456","title":"LS on MCVideo - Video Push requirements","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA1 thanks SA6 for their LS S6-161272, S1-163177 concerning MCVideo - Video Push requirements.\nSA1 would like to provide the following answers to your question:\n\nDuring the Rel-14 Stage 2 work of MCVideo in SA6 i.e. related to","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":12900,"status":"noted","reservation_date":"2016-11-14 14:04:51","uploaded":"2016-11-14 14:10:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"S1-163411","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_014_Reno\/Docs\/S6-161456.zip","group":"S6","meeting":"S6-14","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]