name: AKA
full_form: Authentication and Key Agreement
context: under the assumption that the browser is not under the attacker's control. - IMS AKA Procedure (from Step 1 to Step 8) The IMS AKA procedure is performed as specified in section 6.1 with differences as explained below. HTTP Digest AKAv2 is used as defined in RFC 4169 [65] (instead of HTTP Digest AKA defined in RFC 3310 [17]) and no IPsec security association is set-up. The keys CK and IK shall not be forwarded by the S-CSCF to thee P-CSCF in SM4. Hence, any statements relating to the use of these keys in the eP-CSCF do not apply. The WebRTC IMS Client forwards necessary IMS AKA information to the UICC application in charge of the IMS AKA authentication for WebRTC. The ME applies access control policy to the WIC before granting the access to the UICC application in charge of the IMS AKA authentication for WebRTC. This UICC application sends back the results of the AUTHENTICATE command executed to perform the IMS AKA authentication, as defined in section 8 of this document. After
description: IMS AKA (Authentication and Key Agreement) is a procedure for authenticating users and establishing keys in the IP Multimedia Subsystem (IMS). It involves a series of steps, including the execution of an AUTHENTICATE command, to verify the user's identity and negotiate security parameters.
explanation: The context describes IMS AKA as a specific procedure within the IMS system, detailing its steps and interactions with other components. This classification is based on the procedural nature of IMS AKA, which involves a sequence of operations for authentication and key agreement.
section_title: X.2.3.3	Procedures
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,B-Protocol,O,O,O,O,O,O,O,O,B-Network,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Specification,O,O,O,O,B-Protocol,O,B-Protocol,O,O,B-Specification,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Parameter,O,B-Parameter,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,I-Device,O,O,B-Network,B-Protocol,O,O,O,B-Device,O,O,O,O,O,B-Network,B-Protocol,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Network,B-Protocol,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,B-Protocol,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Network,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O