Connection Establishment in the Binary Floor Control Protocol (BFCP)
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: Internet Architecture Board <firstname.lastname@example.org>, RFC Editor <email@example.com>, xcon mailing list <firstname.lastname@example.org>, xcon chair <email@example.com> Subject: Protocol Action: 'Connection Establishment in the Binary Floor Control Protocol (BFCP)' to Proposed Standard The IESG has approved the following document: - 'Connection Establishment in the Binary Floor Control Protocol (BFCP) ' <draft-ietf-xcon-bfcp-connection-06.txt> as a Proposed Standard This document is the product of the Centralized Conferencing Working Group. The IESG contact persons are Cullen Jennings and Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-xcon-bfcp-connection-06.txt
Technical Summary This document specifies how a Binary Floor Control Protocol (BFCP) client establishes a connection to a BFCP floor control server outside the context of an offer/answer exchange. Client and server authentication are based on Transport Layer Security (TLS). Working Group Summary This document is a product of the XCON working group. Its contents have been uncontroversial in working group discussions. Document Quality Eric Rescorla reviewed the document from a security perspective. Based on his feedback, the client authentication mechanism was changed from one based loosely on HTTP digest authentication to the use of TLS with pre-shared keys. Adam Roach has reviewed the document for quality. Personnel Adam Roach is the Document Shepherd for this document. Cullen Jennings is the responsible Area Director. Note to RFC Editor OLD: If possible, passphrases are preferable to passwords. NEW: If possible, passphrases are preferable to passwords. It is RECOMMENDED that implementations support, at minimum, 16-character passwords or passphrases.