[{"name":"R5-212014","title":"Reply LS on failing initial registration without Retry-After header field","source":"TSG WG CT1","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Response to: LS R5-206259 on failing initial registration without Retry-After header field from RAN5.\nCT1 thanks RAN5 for their LS on failing initial registration without Retry-After header field. CT1 would like to provide the following answer to RAN5\u2019s question:\nIn the scenario described by RAN5, UE shall follow interpretation B i.e. attempt consecutive (second) initial registration to next available P-CSCF (not on current P-CSCF).\nCT1 agreed CR C1-210576 with clarification on receiving a 4xx, 5xx (except 503) or 6xx response without Retry-After header field to the REGISTER request.\nActions: To TSG RAN WG5: TSG CT WG1 asks RAN5 group to take the above response into account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":549,"ainumber":"6.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":201400,"status":"noted","reservation_date":"2021-04-20 09:12:21","uploaded":"2021-04-20 09:27:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-206259","lsto":"","Cc":"","lsoriginalls":"C1-210577","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_91_Electronic\/Docs\/R5-212014.zip","group":"R5","meeting":"R5-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-212015","title":"LS Response on inconsistency in specifying handling of MCPTT SIP 183 (Session Progress) response in TS 24.379","source":"TSG WG CT1","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Response to: LS R5-206258 on \" LS on inconsistency in specifying handling of MCPTT SIP 183 (Session Progress) response in TS 24.379\". Release: Release 13 and later.\nCT1 thanks RAN5 for their LS on inconsistency in specifying handling of MCPTT SIP 183 (Session Progress) response in 3GPP TS 24.379 (R5-206258\/C1-207490).\nCT1 has reviewed this matter and introduced new steps for both the private and ambient call (Rel-13 onwards) procedures, specifying the handling of MCPTT SIP 183 (Session Progress) response in the Controlling MCPTT Function. Additionally, the group call procedure for handling 183 response has been corrected for related identified issues.  \nCT1 has agreed to the following CRs for 3GPP TS 24.379, specifying the handling of a SIP 183 (Session Progress) response in private call procedures.\n- C1-211398 (Its mirror CRs: C1-211400 (Rel-14), C1-211402 (Rel-15), C1-211404 (Rel-16) and C1-211406 (Rel-17)) - Private Call and Ambient Call Procedures\nActions: To RAN5: 3GPP TSG CT WG1 asks RAN5 to consider the above information into account in your work.","secretary_remarks":"LS R5-206258 on \" LS on inconsistency in specifying handling of MCPTT SIP 183 (Session Progress) response in TS 24.379\"","agenda_item_sort_order":549,"ainumber":"6.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":201500,"status":"noted","reservation_date":"2021-04-20 09:12:22","uploaded":"2021-04-20 09:27:38","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-206258","lsto":"","Cc":"","lsoriginalls":"C1-211408","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_91_Electronic\/Docs\/R5-212015.zip","group":"R5","meeting":"R5-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]