The%20Binary%20Floor%20Control%20Protocol%20(BFCP)%20draft-ietf-xcon-bfcp-00.txt

1
The Binary Floor Control Protocol
(BFCP)draft-ietf-xcon-bfcp-00.txt

• Gonzalo.Camarillo_at_ericsson.com

2
Additions to This Revision

• Explanatory text added to this revision putting
  BFCP into context
• Third-party floor requests are now supported
• Several clarifications
• Incorporated comments received on the mailing list

3
Issue Replay Protection

• Integrity implemented in the protocol
• Rely on TLS for replay protection
• Should we implement replay protection in the
  protocol as well?

4
Issue Privacy TLV

• Currently defined as a simple flag
• Do not disclose my identity to anybody
• Do we want more options?
• E.g., your identity can be disclosed to the
  chairs, but no to other users

5
Issue Mandatory TLVs Added by a Server

• Can a server add new mandatory TLVs
• We would need
• a capability negotiation mechanism or
• a way for clients to complain about unknown TLVs

6
Issue 3rd Party Floor Request Authorization

• Users need a means to authorize 3rd parties to
  request floors on their behalf
• Does CPCP support this?

7
Issue Different Payload Types

• Use the BFCP fixed header with payload types
  other than the TLVs
• E.g., XML notifications

8
Issue Floor Request Modification

• Users can modify ongoing floor requests (e.g.,
  new topic or new priority)
• Do we need this feature?

9
Issue SDP Format

• As a transport
• mapplication 20000 TCP/BFCP
• As a payload type
• mapplication 20000 TCP BFCP
• BFCP would need to be MIME registered

10
Issue Floor-Stream Mapping for Non-CPCP clients

• Label streams and reference them
• afloorid1 m-stream10
• Add floorid attributes to the m lines
• Other approach