* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Bfcpbis Status Pages

Binary Floor Control Protocol Bis (Active WG)
Art Area: Adam Roach, Alexey Melnikov, Ben Campbell | 2011-Nov-01 —  

2017-05-01 charter

Binary Floor Control Protocol Bis (bfcpbis)


 Current Status: Active

     Charles Eckel <eckelcu@cisco.com>
     Keith Drage <keith.drage@alcatel-lucent.com>

 Applications and Real-Time Area Directors:
     Ben Campbell <ben@nostrum.com>
     Alexey Melnikov <aamelnikov@fastmail.fm>
     Adam Roach <adam@nostrum.com>

 Applications and Real-Time Area Advisor:
     Adam Roach <adam@nostrum.com>

 Mailing Lists:
     General Discussion: bfcpbis@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/bfcpbis
     Archive:            https://mailarchive.ietf.org/arch/browse/bfcpbis/

Description of Working Group:

    The BFCPBIS working group is chartered to specify a revision of BFCP (RFC 4582) to support using both TCP and UDP as transports. The current version of BFCP only supports TCP, which when both endpoints are behind NATs or firewalls, has a lower success rate than using the ICE techniques with a UDP based transport for BFCP.  The need for video endpoints to work in these types of environments is driving a strong need to support a UDP based transport as well as TCP.

    This WG will create a revision of RFC 4582 which adds optional support for UDP to BFCP. The security when using UDP will be based on DTLS. The updated protocol will use an existing approach (e.g., stop and wait with a single outstanding transaction) to provide a reliable, congestion safe, and TCP friendly transport.

    In addition to providing a way for dealing with the reliable delivery of client-initiated transactions, the updated protocol will also be able to deliver server-initiated transactions reliably when needed. The WG will research the size of messages used and decide if fragmenting a request or response over multiple UDP packets is required.  The new protocol will be backwards compatible with RFC 4582 when used in TCP mode.

    The BFCPBIS WG will coordinate closely with the MMUSIC WG to create a revision of RFC 4583 specifying how BFCP is signaled in SDP so that it supports UDP as well as TCP transports.  This WG would ask the MMUSIC WG to add a milestone to create a revisions of  RFC 4583 to address signaling the use of UDP in SDP. The WG will coordinate with International Multimedia Telecommunications Consortium (IMTC) and other industry fora.

Goals and Milestones:
  Done     - Draft revision of RFC 4582 to IESG as Proposed Standard
  Nov 2016 - Draft revision of RFC 4583 to IESG as Proposed Standard
  Done     - Draft for BFCP over WebSocket to IESG as Proposed Standard
  Done     - Draft for SDP WebSocket Connection URI Attribute to IESG as Proposed Standard C

All charter page changes, including changes to draft-list, rfc-list and milestones:

Generated from PyHt script /wg/bfcpbis/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -