1. Connection Establishment in BFCP draft-ietf-xcon-bfcp-connection-00
Connection Establishment in BFCP draft-ietf-xcon-bfcp-connection-00.txt

2. BFCP Connection Establishment
Using an offer/answer exchange
RFC 4583
Authentication based on TLS media
Exchange of certificate fingerprints
Without an offer/answer exchange
draft-ietf-xcon-bfcp-connection-00.txt
Digest-based client authentication is included
Server authentication relies on TLS certificates

3. Offer/answer-based Mechanism
Floor Participant
Floor Control Server
INVITE SIP/2.0
From: Conference tag=1245
To: Alice
Call-ID:a84b4c76e66710
CSeq: 1 INVITE
Content-Type: application/sdp
Content-Length: 142
v=0
o=conference IN IP
s=Session SDP t=
c=IN IP
m=application TCP/TLS/BFCP *
a=setup:passive
a=connection:new
a=fingerprint:SHA-1 \ 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:AB a=floorctrl:s-only
a=confid:4321
a=userid:1234
a=floorid:1 m-stream:10
m=audio 3456 RTP/AVP 0
a=label:10
SIP INVITE
ACK SIP/2.0
To: Conference
From: Alice tag=1245
Call-ID: a84b4c76e66710
CSeq: 1 ACK
Content-Length: 0
SIP/ OK
From: Conference tag=1245
To: alice
Call-ID: a84b4c76e66710
CSeq: 1 INVITE
Content-Type: application/sdp
Content-Length: 131
v=0
o=conference IN IP
s=Session SDP t=
c=IN IP
m=application 9 TCP/TLS/BFCP *
a=setup:active
a=connection:new
a=fingerprint:SHA-1 \ 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:AB
a=floorctrl:c-only
m=audio RTP/AVP 0
SIP 200 OK
SIP ACK
TCP SYN

4. No Offer/answer FloorQuery TransactionID: 254 UserID: 557 FloorID:543
Floor Participant
Floor Control Server
TCP connection establishment
FloorQuery
TransactionID: 254
UserID: 557
FloorID:543
FloorQuery
Error
TransactionID: 254
UserID: 557
FloorID:543
Error-Code: 10 (DIGEST Attribute Needed)
Digest Algortihm:HMAC-SHA1
Nonce:
Error
FloorQuery
TransactionID: 896
UserID: 557
FloorID:543
Nonce:
Digest:
FloorQuery

5. New Attributes DIGEST NONCE
ALGORITHM M
PADDING
DIGEST
……..
NONCE
NONCE VALUE M
Definition of Error Specific Details for Error Code 10 (DIGEST Attribute Needed)
ALGORITHM ID
ALGORITHM ID
ALGORITHM ID
ALGORITHM ID
……..
ALGORITHM ID
ALGORITHM ID

6. Open Issue: Provisioning
The data model needs to include:
Server’s transport address
Conference ID
User ID
draft-novo-xcon-common-data-model will be updated accordingly

7. Open Issue: DNS Procedures
Client gets the transport address of the server to perform an active TCP open
Do we allow FQDNs?
If so, which DNS procedures do we define?
SRV, A, AAAA...?

8. Open Issue: Connection Reestablishment
The server notices that the TCP connection is down (it cannot deliver a BFCP message)
Proposal: only clients reestablish TCP connections

9. Open Issue: Digest Usage
Do we want to recommend that only the first BFCP message over a TLS connection is authenticated using digest?
BFCP is designed to be bandwidth efficient
We got a set of comments about digest in the original IESG review of the BFCP spec
Next revision of the draft will incorporate them all