[{"name":"R5-244439","title":"Specification and usage of conditions in IMS messages","source":"MCC TF160","contact":"Olivier Genoud","contact-id":58316,"tdoctype":"discussion","for":"Agreement","abstract":"The following list summarises the proposals for prose changes of clauses 2 and 3. Basically the proposed changes don't affect the TTCN implementation but align the prose to TTCN, except proposal 3.2 which depending on the RAN5 decision may cause a TTCN change._x000D_\nList of proposals:_x000D_\nProposal 2.1.1:\tIn general conditions specifying a RAN type shall be removed from specific message contents except for fall-back scenarios where the RAN type may be kept for clarification._x000D_\nProposal 2.1.2:\tConditions corresponding to PICS shall be removed from specific message contents._x000D_\nProposal 2.1.3:\tConditions specifying the direction in which a message is sent shall be removed from specific message contents._x000D_\nProposal 2.1.4:\tClarification shall be added to 34.229-1 that unless specified otherwise by a test case IMS security is applied when the UE supports it (34.229-2 A.6a\/2: pc_IMS_Sec)._x000D_\n? Only if the UE does not support IMS security GIBA may be used instead (34.229-2 A.6a\/1: pc_IMS_GIBA_Sec). This is what is implemented in TTCN (f_IMS_PTC_Init)._x000D_\n? In general, conditions specifying the security scheme shall be removed from specific message content except for GIBA specific test cases._x000D_\nProposal 2.2.3:\tA2 (Response for a non-emergency registration) shall be declared as default in A.1.3, so that there is no need any more to specify it in test cases and procedures._x000D_\nProposal 2.2.6-1:\tClarification to be added to condition A4 (INVITE creating a dialog) of A.2.1 that A4 shall be applied unless specified otherwise by the test case or test procedure._x000D_\nProposal 2.2.6-2:\tWording of A5 in A.2.1 to be changed to \"re-INVITE within a dialog\"; A32 to be removed from A.2.1 and replaced by A5 in test cases and test procedures._x000D_\nProposal 2.2.6-3:\tWording of A11 in A.2.1 to be changed to \"INVITE for creating a video stream\"_x000D_\nProposal 2.2.9:\tA3 (ACK for 2xx response) shall be declared as default in A.2.7, so that there is no need any more to specify it in test cases and procedures._x000D_\nProposal 2.2.11-1:\tA4 (INVITE creating a dialog) shall be declared as default in A.2.9, so that there is no need any more to specify it in test cases and procedures: A4 shall be applied implicitly unless A5 is specified explicitly by a specific message content of a test case or test procedure._x000D_\nProposal 2.2.11-2:\tA8 shall be changed to \"INVITE for creating a video session\" in A.2.9._x000D_\nProposal 2.2.16-1:\tConditions A1\/A2\/A3\/A4 (Response sent by SS\/UE for INVITE\/UPDATE, IMS security\/GIBA) for A.3.1 shall be applied implicitly, i.e. there is no need to specify these conditions in references to A.3.1._x000D_\nProposal 2.2.16-2:\tConditions A19\/A20 (Response sent by SS\/UE for INVITE) for A.3.1 shall be applied implicitly, i.e. there is no need to specify these conditions in references to A.3.1._x000D_\nProposal 2.2.16-3:\tA clarification shall be added to condition A8 (Any response sent by the UE within a dialog, except for CANCEL requests), that in context of A8 the only case where a 200 OK is not sent within a dialog is a 200 OK for a SIP MESSAGE request (which does not initiate a dialog according to RFC 3428)._x000D_\nProposal 2.2.16-4:\tCondition A23 (Response sent for re-INVITE within an established dialog) shall be specified explicitly in references to A.3.1._x000D_\nProposal 2.2.16-5:\tConditions A5 (Any response sent by the UE within a dialog) shall be removed from A.3.1 and from all references to A.3.1._x000D_\n....","secretary_remarks":"","agenda_item_sort_order":1194,"ainumber":"6.6.6.6","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":44390,"status":"noted","reservation_date":"2024-08-06 14:57:05","uploaded":"2024-08-09 12:48:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5__104_Maastricht\/Docs\/R5-244439.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]