[{"name":"C1-243419","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34190,"status":"postponed","reservation_date":"2024-05-20 09:12:56","uploaded":"2024-05-20 13:02:28","revisionof":"","revisedto":"","release":"Rel-14","crspec":24.282,"crspecversion":"14.10.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":421.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243419.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243422","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34220,"status":"postponed","reservation_date":"2024-05-20 09:14:17","uploaded":"2024-05-20 13:03:58","revisionof":"","revisedto":"","release":"Rel-15","crspec":24.282,"crspecversion":"15.9.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":422.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243422.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243426","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34260,"status":"postponed","reservation_date":"2024-05-20 09:15:26","uploaded":"2024-05-20 13:05:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":24.282,"crspecversion":"16.10.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":423.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243426.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243428","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34280,"status":"postponed","reservation_date":"2024-05-20 09:16:39","uploaded":"2024-05-20 13:11:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":24.282,"crspecversion":"17.10.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":424.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243428.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243430","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34300,"status":"postponed","reservation_date":"2024-05-20 09:17:44","uploaded":"2024-05-20 13:22:27","revisionof":"","revisedto":"","release":"Rel-18","crspec":24.282,"crspecversion":"18.6.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":425.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243430.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243444","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34440,"status":"postponed","reservation_date":"2024-05-20 09:20:32","uploaded":"2024-05-20 14:41:29","revisionof":"","revisedto":"","release":"Rel-14","crspec":24.481,"crspecversion":"14.7.1","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":81.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243444.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243447","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34470,"status":"postponed","reservation_date":"2024-05-20 09:21:31","uploaded":"2024-05-20 14:41:30","revisionof":"","revisedto":"","release":"Rel-15","crspec":24.481,"crspecversion":"15.6.2","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":82.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243447.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243450","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34500,"status":"postponed","reservation_date":"2024-05-20 09:22:37","uploaded":"2024-05-20 14:41:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":24.481,"crspecversion":"16.4.1","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":83.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243450.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243453","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34530,"status":"postponed","reservation_date":"2024-05-20 09:23:53","uploaded":"2024-05-20 19:25:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":24.481,"crspecversion":"17.6.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":84.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243453.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243454","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34540,"status":"postponed","reservation_date":"2024-05-20 09:25:03","uploaded":"2024-05-20 19:25:13","revisionof":"","revisedto":"","release":"Rel-18","crspec":24.481,"crspecversion":"18.1.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":85.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/TSGC1_149_India\/Docs\/C1-243454.zip","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243456","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34560,"status":"postponed","reservation_date":"2024-05-20 09:30:28","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-14","crspec":24.483,"crspecversion":"14.11.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":175.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243457","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34570,"status":"postponed","reservation_date":"2024-05-20 09:31:57","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":24.483,"crspecversion":"15.9.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":176.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243459","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34590,"status":"withdrawn","reservation_date":"2024-05-20 09:32:26","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":24.483,"crspecversion":"15.9.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":177.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243460","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34600,"status":"postponed","reservation_date":"2024-05-20 09:33:52","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-16","crspec":24.483,"crspecversion":"16.8.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":178.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243462","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34620,"status":"postponed","reservation_date":"2024-05-20 09:35:28","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-17","crspec":24.483,"crspecversion":"17.7.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":179.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C1-243468","title":"Correction of SDS to allow indication of text charset","source":"Sepura Ltd","contact":"Kit Kilgour","contact-id":86238,"tdoctype":"CR","for":"Agreement","abstract":"3GPP has requirements to enable use of different character sets for SDS, including those of different length encodings. Support for this is not currently in the specifications creating a FASMO risk if two clients use different character set encoding. This","secretary_remarks":"","agenda_item_sort_order":30,"ainumber":"14.1","ainame":"Rel-14 Mision Critical Work Items and issues:","tdoc_agenda_sort_order":34680,"status":"postponed","reservation_date":"2024-05-20 09:36:52","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-18","crspec":24.483,"crspecversion":"18.3.0","workitem":[{"winame":"MCImp-MCDATA-CT"}],"crnumber":180.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"C1","meeting":"C1-149","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]