name: OSCORE
full_form: Object Security for Constrained RESTful Environments
context: The OSCORE security context consists of the following parts: - OSCORE Master Secret (OMS): A shared key between the CoAP Client and CoAP Server. - Master Salt: A shared salt shared between the CoAP Client and CoAP Server. - UE-SID: The UE Sender Identifier - NAF-SID: The NAF Sender Identifier - OSCORE Version: The version of the OSCORE protocol - HKDF: HMAC-based Key Derivation Function - AEAD Algorithm: The algorithm used for encryption and integirty protection - OSCORE ID Context: An identifier which identifies the OSCORE context The OSCORE security context for the OSCORE Ua protocol shall have the following values: - OMS = OSCORE Master Secret = HKDF(Ks_(int/ext)_NAF, "GBA-OSCORE"), where Ks_(int/ext)_NAF is the shared key between the UE and NAF and it follows the semantics of this document for GBA i.e. Ks_(int/ext)_NAF refers to Ks_NAF from GBA_ME, Ks_int_NAF or Ks_ext_NAF from GBA_U. - Master Salt = Request Payload | Response Payload - UE Sender ID = UE-SID generated by CoAP
description: OSCORE (Object Security for Constrained RESTful Environments) is a protocol designed to provide end-to-end security for constrained networks and devices, particularly in the context of IoT and M2M communications. It is based on the CoAP (Constrained Application Protocol) and provides features such as encryption, integrity protection, and secure key exchange.
explanation: The text explicitly states OSCORE as a protocol built upon CoAP and outlines its functionalities like encryption, integrity protection, and secure key exchange, which are characteristic of protocols.
section_title: P.3.3	OSCORE Security context
biotag_Context: O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,B-Parameter,O,O,O,B-Network Function,O,B-Parameter,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,B-Parameter,O,O,O,O,O
biotag_Description: B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O