name: BFCP
full_form: Binary Floor Control Protocol
context: Two cases are considered in this subclause: e2ae security between UE and IMS Access GW and e2e security between UE and conference server. e2ae security: When participating in conferences, IMS UEs may use e2ae security for RTP based traffic and/or for MSRP, as specified in the main body of the present document, and/or for BFCP, as specified in the following. For BFCP that may be used in conferences, e2ae security shall be supported in the same way as for MSRP, as specified in the main body of the present document. The only differences are: 1) e2ae security for BFCP uses individual indications "e2ae-security for BFCP supported by the UE" and "e2ae-security for BFCP supported by the network" during registration (the syntax is to be defined in the corresponding stage 3 specification); compare clause 7.1.2 . 2) In the SDP, security for a BFCP media stream is specified by using the transport âTCP/TLS/BFCPâ, NOTE 1: Application of e2ae security for RTP, MSRP and/or BFCP is not visible to the
description: Binary Floor Control Protocol (BFCP) is a protocol used in conferencing based on SIP signalling security. It enables secure communication between User Equipment (UE) and conference servers, supporting end-to-end (e2ae) security for Binary Floor Control Protocol traffic.
explanation: The text explicitly states that BFCP is a protocol used in conferencing and describes its function in securing communication within conferences.
section_title: G.2	Security for conferencing based on SIP signalling security
biotag_Context: O,O,O,O,O,O,O,O,O,O,B-Device,O,B-Network,O,B-Network Function,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network,B-Device,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,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,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,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,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Protocol,O,O,O,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,I-Protocol,O