Skip to main content

Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: Internet Architecture Board <>,
    RFC Editor <>, 
    mmusic mailing list <>, 
    mmusic chair <>
Subject: Protocol Action: 'Session Description Protocol (SDP) 
         Format for Binary Floor Control Protocol (BFCP) Streams' to 
         Proposed Standard 

The IESG has approved the following document:

- 'Session Description Protocol (SDP) Format for Binary Floor Control 
   Protocol (BFCP) Streams '
   <draft-ietf-mmusic-sdp-bfcp-04.txt> as a Proposed Standard

This document is the product of the Multiparty Multimedia Session Control 
Working Group. 

The IESG contact persons are Allison Mankin and Jon Peterson.

A URL of this Internet-Draft is:

Ballot Text

Technical Summary
    This document specifies how to describe Basic Floor Control
    Protocol (BFCP) streams in SDP session descriptions.
    User agents using the offer/answer model to establish
    BFCP streams use this format in their offers and their answers.
    BFCP is defined by an accompanying specification from the
    XCON working group.  This document also describes
    key management and security principles for BFCP establishment,
    using existing protocol capabilities available through SDP.
Working Group Summary
   There was strong working group consensus behind this draft.
Protocol Quality
  The protocol has been reviewed by the MMUSIC working group. It
  defines a number of new SDP parameters within the existing framework. 
  The new parameters are not controversial.

  Allison Mankin has acted as the Area Director for the document in order
  to coordinate this document with the XCON BFCP document.  Colin Perkins is
  the WG Chair shepherd for this document.  The Editor, Gonzalo Camarillo,
  took  the initiative in shepherding the Discuss comments.

Note to RFC Editor
 Replace Reference 3 (RFC 2234) with a reference to RFC 4234.

RFC Editor Note