datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams
draft-ietf-bfcpbis-rfc4583bis-09

Document type: Active Internet-Draft (bfcpbis WG)
Document stream: IETF
Last updated: 2014-02-14
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: Mary Barnes

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

BFCPbis Working Group                                       G. Camarillo
Internet-Draft                                                  Ericsson
Obsoletes: 4583 (if approved)                              T. Kristensen
Intended status: Standards Track                                   Cisco
Expires: August 19, 2014                               February 15, 2014

   Session Description Protocol (SDP) Format for Binary Floor Control
                        Protocol (BFCP) Streams
                    draft-ietf-bfcpbis-rfc4583bis-09

Abstract

   This document specifies how to describe Binary Floor Control Protocol
   (BFCP) streams in Session Description Protocol (SDP) descriptions.
   User agents using the offer/answer model to establish BFCP streams
   use this format in their offers and answers.

   This document obsoletes RFC 4583.  Changes from RFC 4583 are
   summarized in Section 12.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 19, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Camarillo & Kristensen   Expires August 19, 2014                [Page 1]
Internet-Draft                    BFCP                     February 2014

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Fields in the 'm' Line . . . . . . . . . . . . . . . . . . . .  3
   4.  Floor Control Server Determination . . . . . . . . . . . . . .  4
   5.  The 'confid' and 'userid' SDP Attributes . . . . . . . . . . .  6
   6.  Association between Streams and Floors . . . . . . . . . . . .  6
   7.  BFCP Version Negotiation . . . . . . . . . . . . . . . . . . .  7
   8.  BFCP Connection Management . . . . . . . . . . . . . . . . . .  8
     8.1.  TCP Connection Management  . . . . . . . . . . . . . . . .  8
   9.  Authentication . . . . . . . . . . . . . . . . . . . . . . . .  8
   10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   12. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 12
     12.1. Registration of SDP 'proto' Values . . . . . . . . . . . . 12
     12.2. Registration of the SDP 'floorctrl' Attribute  . . . . . . 12
     12.3. Registration of the SDP 'confid' Attribute . . . . . . . . 13
     12.4. Registration of the SDP 'userid' Attribute . . . . . . . . 13
     12.5. Registration of the SDP 'floorid' Attribute  . . . . . . . 13
     12.6. Registration of the SDP 'bfcpver' Attribute  . . . . . . . 14
   13. Changes from RFC 4583  . . . . . . . . . . . . . . . . . . . . 14
   14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
   15. Normative References . . . . . . . . . . . . . . . . . . . . . 15
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17

Camarillo & Kristensen   Expires August 19, 2014                [Page 2]
Internet-Draft                    BFCP                     February 2014

1.  Introduction

   As discussed in the BFCP (Binary Floor Control Protocol)
   specification [8], a given BFCP client needs a set of data in order
   to establish a BFCP connection to a floor control server.  This data
   include the transport address of the server, the conference
   identifier, and the user identifier.

   One way for clients to obtain this information is to use an offer/

[include full document text]