The Binary Floor Control Protocol (BFCP) Parameters
Created
- 2006-01-30
Last Updated
- 2023-08-25
Available Formats
Attributes
Registration Procedure(s)
- Specification Required
Expert(s)
- Brian Rosen, Tom Kristensen
Reference
- RFC 8855: The Binary Floor Control Protocol (BFCP)
Note
Specification must be a standards-track RFC.
Available Formats
| Type | Attribute | Reference |
|---|---|---|
| 1 | BENEFICIARY-ID | RFC 8855 |
| 2 | FLOOR-ID | RFC 8855 |
| 3 | FLOOR-REQUEST-ID | RFC 8855 |
| 4 | PRIORITY | RFC 8855 |
| 5 | REQUEST-STATUS | RFC 8855 |
| 6 | ERROR-CODE | RFC 8855 |
| 7 | ERROR-INFO | RFC 8855 |
| 8 | PARTICIPANT-PROVIDED-INFO | RFC 8855 |
| 9 | STATUS-INFO | RFC 8855 |
| 10 | SUPPORTED-ATTRIBUTES | RFC 8855 |
| 11 | SUPPORTED-PRIMITIVES | RFC 8855 |
| 12 | USER-DISPLAY-NAME | RFC 8855 |
| 13 | USER-URI | RFC 8855 |
| 14 | BENEFICIARY-INFORMATION | RFC 8855 |
| 15 | FLOOR-REQUEST-INFORMATION | RFC 8855 |
| 16 | REQUESTED-BY-INFORMATION | RFC 8855 |
| 17 | FLOOR-REQUEST-STATUS | RFC 8855 |
| 18 | OVERALL-REQUEST-STATUS | RFC 8855 |
Primitives
Registration Procedure(s)
- Specification Required
Expert(s)
- Brian Rosen, Tom Kristensen
Reference
- RFC 8855: The Binary Floor Control Protocol (BFCP)
Note
Specification must be a standards-track RFC.
Available Formats
| Type | Primitive | Reference |
|---|---|---|
| 1 | FloorRequest | RFC 8855 |
| 2 | FloorRelease | RFC 8855 |
| 3 | FloorRequestQuery | RFC 8855 |
| 4 | FloorRequestStatus | RFC 8855 |
| 5 | UserQuery | RFC 8855 |
| 6 | UserStatus | RFC 8855 |
| 7 | FloorQuery | RFC 8855 |
| 8 | FloorStatus | RFC 8855 |
| 9 | ChairAction | RFC 8855 |
| 10 | ChairActionAck | RFC 8855 |
| 11 | Hello | RFC 8855 |
| 12 | HelloAck | RFC 8855 |
| 13 | Error | RFC 8855 |
| 14 | FloorRequestStatusAck | RFC 8855 |
| 15 | FloorStatusAck | RFC 8855 |
| 16 | Goodbye | RFC 8855 |
| 17 | GoodbyeAck | RFC 8855 |
Request Statuses
Registration Procedure(s)
- Specification Required
Expert(s)
- Brian Rosen, Tom Kristensen
Reference
- RFC 8855: The Binary Floor Control Protocol (BFCP)
Note
Specification must be a standards-track RFC.
Available Formats
Error Codes
Registration Procedure(s)
- Specification Required
Expert(s)
- Brian Rosen, Tom Kristensen
Reference
- RFC 8855: The Binary Floor Control Protocol (BFCP)
Note
Specification must be a standards-track RFC.
Available Formats
| Type | Meaning | Reference |
|---|---|---|
| 1 | Conference Does Not Exist | RFC 8855 |
| 2 | User Does Not Exist | RFC 8855 |
| 3 | Unknown Primitive | RFC 8855 |
| 4 | Unknown Mandatory Attribute | RFC 8855 |
| 5 | Unauthorized Operation | RFC 8855 |
| 6 | Invalid Floor ID | RFC 8855 |
| 7 | Floor Request ID Does Not Exist | RFC 8855 |
| 8 | You have Already Reached the Maximum Number of Ongoing Floor Requests for This Floor | RFC 8855 |
| 9 | Use TLS | RFC 8855 |
| 10 | Unable to Parse Message | RFC 8855 |
| 11 | Use DTLS | RFC 8855 |
| 12 | Unsupported Version | RFC 8855 |
| 13 | Incorrect Message Length | RFC 8855 |
| 14 | Generic Error | RFC 8855 |