draft-ietf-mmusic-sdp-bfcp-03.txt   rfc4583.txt 
MMUSIC Working Group G. Camarillo Network Working Group G. Camarillo
Internet-Draft Ericsson Request for Comments: 4583 Ericsson
Expires: June 2, 2006 November 29, 2005 Category: Standards Track November 2006
Session Description Protocol (SDP) Format for Binary Floor Control
Protocol (BFCP) Streams
draft-ietf-mmusic-sdp-bfcp-03.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at Session Description Protocol (SDP) Format for
http://www.ietf.org/ietf/1id-abstracts.txt. Binary Floor Control Protocol (BFCP) Streams
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 2, 2006. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The IETF Trust (2006).
Abstract Abstract
This document specifies how to describe BFCP streams in SDP session This document specifies how to describe Binary Floor Control Protocol
descriptions. User agents using the offer/answer model to establish (BFCP) streams in Session Description Protocol (SDP) descriptions.
BFCP streams use this format in their offers and their answers. User agents using the offer/answer model to establish BFCP streams
use this format in their offers and answers.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology .....................................................2
3. Fields in the 'm' Line . . . . . . . . . . . . . . . . . . . . 3 3. Fields in the 'm' Line ..........................................2
4. Floor Control Server Determination . . . . . . . . . . . . . . 4 4. Floor Control Server Determination ..............................3
5. The 'confid' and 'userid' SDP Attributes . . . . . . . . . . . 6 5. The 'confid' and 'userid' SDP Attributes ........................5
6. Association between Streams and Floors . . . . . . . . . . . . 6 6. Association between Streams and Floors ..........................5
7. TCP Connection Management . . . . . . . . . . . . . . . . . . 7 7. TCP Connection Management .......................................5
8. Authentication . . . . . . . . . . . . . . . . . . . . . . . . 7 8. Authentication ..................................................6
9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. Examples ........................................................7
10. Security Considerations . . . . . . . . . . . . . . . . . . . 9 10. Security Considerations ........................................8
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 11. IANA Considerations ............................................8
11.1. Registration of the 'TCP/BFCP' and 'TCP/TLS/BFCP' SDP 11.1. Registration of the 'TCP/BFCP' and 'TCP/TLS/BFCP'
'proto' values . . . . . . . . . . . . . . . . . . . . . 9 SDP 'proto' Values ........................................8
11.2. Registration of the SDP 'floorctrl' Attribute . . . . . . 10 11.2. Registration of the SDP 'floorctrl' Attribute .............8
11.3. Registration of the SDP 'confid' Attribute . . . . . . . 10 11.3. Registration of the SDP 'confid' Attribute ................9
11.4. Registration of the SDP 'userid' Attribute . . . . . . . 10 11.4. Registration of the SDP 'userid' Attribute ................9
11.5. Registration of the SDP 'floorid' Attribute . . . . . . . 11 11.5. Registration of the SDP 'floorid' Attribute ..............10
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 12. Acknowledgements ..............................................10
13. Normative References . . . . . . . . . . . . . . . . . . . . . 11 13. Normative References ..........................................10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . . . 14
1. Introduction 1. Introduction
As discussed in the BFCP (Binary Floor Control Protocol) As discussed in the BFCP (Binary Floor Control Protocol)
specification [8], a given BFCP client needs a set of data in order specification [8], a given BFCP client needs a set of data in order
to establish a BFCP connection to a floor control server. These data to establish a BFCP connection to a floor control server. These data
include the transport address of the server, the conference include the transport address of the server, the conference
identifier, and the user identifier. identifier, and the user identifier.
One way for clients to obtain this information consists of using an One way for clients to obtain this information is to use an
offer/answer [4] exchange. This document specifies how to encode offer/answer [4] exchange. This document specifies how to encode
this information in the SDP session descriptions which are part of this information in the SDP session descriptions that are part of
such an offer/answer exchange. such an offer/answer exchange.
User agents typically use the offer/answer model to establish a User agents typically use the offer/answer model to establish a
number of media streams of different types. Following this model, a number of media streams of different types. Following this model, a
BFCP connection is described as any other media stream by using an BFCP connection is described as any other media stream by using an
SDP 'm' line, possibly followed by a number of attributes encoded in SDP 'm' line, possibly followed by a number of attributes encoded in
'a' lines. 'a' lines.
2. Terminology 2. Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED", In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as
described in BCP 14, RFC 2119 [1] and indicate requirement levels for described in BCP 14, RFC 2119 [1] and indicate requirement levels for
compliant implementations. compliant implementations.
3. Fields in the 'm' Line 3. Fields in the 'm' Line
This Section describes how to generate an 'm' line for a BFCP stream. This section describes how to generate an 'm' line for a BFCP stream.
According to the SDP specification [11], the 'm' line format is the According to the SDP specification [11], the 'm' line format is the
following: following:
m=<media> <port> <transport> <fmt> ... m=<media> <port> <transport> <fmt> ...
The media field MUST have a value of "application". The media field MUST have a value of "application".
The port field is set following the rules in [7]. Depending on the The port field is set following the rules in [7]. Depending on the
value of the 'setup' attribute (disccused in Section 7), the port value of the 'setup' attribute (discussed in Section 7), the port
field contains the port the remote endpoint will initiate its TCP field contains the port to which the remote endpoint will initiate
connection to, or is irrelevant (i.e., the endpoint will initiate the its TCP connection or is irrelevant (i.e., the endpoint will initiate
connection towards the remote endpoint) and should be set to a value the connection towards the remote endpoint) and should be set to a
of 9, which is the discard port. Since BFCP only runs on top of TCP, value of 9, which is the discard port. Since BFCP only runs on top
the port is always a TCP port. A port field value of zero has the of TCP, the port is always a TCP port. A port field value of zero
standard SDP meaning (i.e., rejection of the media stream). has the standard SDP meaning (i.e., rejection of the media stream).
We define two new values for the transport field: TCP/BFCP and TCP/ We define two new values for the transport field: TCP/BFCP and
TLS/BFCP. The former is used when BFCP runs directly on top of TCP TCP/TLS/BFCP. The former is used when BFCP runs directly on top of
and the latter is used when BFCP runs on top of TLS, which in turn TCP, and the latter is used when BFCP runs on top of TLS, which in
runs on top of TCP. turn runs on top of TCP.
The fmt (format) list is ignored for BFCP. The fmt list of BFCP m The fmt (format) list is ignored for BFCP. The fmt list of BFCP 'm'
lines SHOULD contain a single "*" character. lines SHOULD contain a single "*" character.
The following is an example of an 'm' line for a BFCP connection: The following is an example of an 'm' line for a BFCP connection:
m=application 50000 TCP/TLS/BFCP * m=application 50000 TCP/TLS/BFCP *
4. Floor Control Server Determination 4. Floor Control Server Determination
When two endpoints establish a BFCP stream, they need to determine When two endpoints establish a BFCP stream, they need to determine
which of them acts as a floor control server. The most common which of them acts as a floor control server. In the most common
scenario consists of a client establishing a BFCP stream with scenario, a client establishes a BFCP stream with a conference server
conference server that acts as the floor control server. Floor that acts as the floor control server. Floor control server
control server determination is straight forward because one endpoint determination is straight forward because one endpoint can only act
can only act as a client and the other can only act as a floor as a client and the other can only act as a floor control server.
control server.
However, there are scenarios where both endpoints could act as a However, there are scenarios where both endpoints could act as a
floor control server. For example, is a two-party session that floor control server. For example, in a two-party session that
involves an audio stream and a shared whiteboard, the endpoints need involves an audio stream and a shared whiteboard, the endpoints need
to decide which party will be acting as the floor control server. to decide which party will be acting as the floor control server.
Furthermore, there are situations where both the offerer and the Furthermore, there are situations where both the offerer and the
answerer act as both clients and floor control servers in the same answerer act as both clients and floor control servers in the same
session. For example, in a two-party session that involves an audio session. For example, in a two-party session that involves an audio
stream and a shared whiteboard, one party acts as the floor control stream and a shared whiteboard, one party acts as the floor control
server for the audio stream and the other acts as the floor control server for the audio stream and the other acts as the floor control
server for the shared whiteboard. server for the shared whiteboard.
We define the 'floorctrl' SDP media-level attribute to perform floor We define the 'floorctrl' SDP media-level attribute to perform floor
control determination. Its Augmented BNF syntax [2] is: control determination. Its Augmented BNF syntax [2] is:
floor-control-attribute = "a=floorctrl:" role *(SP role) floor-control-attribute = "a=floorctrl:" role *(SP role)
role = "c-only" / "s-only" / "c-s" role = "c-only" / "s-only" / "c-s"
The offerer includes this attribute to state all the roles it would The offerer includes this attribute to state all the roles it would
be willing to perform: be willing to perform:
c-only: The offerer would be willing to only act as a floor control c-only: The offerer would be willing to act as a floor control
client. client only.
s-only: The offerer would be willing to only act as a floor control
server. s-only: The offerer would be willing to act as a floor control
server only.
c-s: The offerer would be willing to act both as a floor control c-s: The offerer would be willing to act both as a floor control
client and as a floor control server. client and as a floor control server.
If an 'm' line in an offer contains a 'floorctrl' attribute, the If an 'm' line in an offer contains a 'floorctrl' attribute, the
answerer MUST include one in the corresponding 'm' line in the answerer MUST include one in the corresponding 'm' line in the
answer. The answerer includes this attribute to state which role the answer. The answerer includes this attribute to state which role the
answerer will perform. That is, the answerer chooses one of the answerer will perform. That is, the answerer chooses one of the
roles the offerer is willing to perform and generates an answer with roles the offerer is willing to perform and generates an answer with
the corresponding role for the answerer. Table 1 shows the the corresponding role for the answerer. Table 1 shows the
corresponding roles for an answerer depending on the offerer's role. corresponding roles for an answerer, depending on the offerer's role.
+---------+----------+ +---------+----------+
| Offerer | Answerer | | Offerer | Answerer |
+---------+----------+ +---------+----------+
| c-only | s-only | | c-only | s-only |
| s-only | c-only | | s-only | c-only |
| c-s | c-s | | c-s | c-s |
+---------+----------+ +---------+----------+
Table 1: Roles Table 1: Roles
The following are the description of the roles when chosen by an The following are the descriptions of the roles when they are chosen
answere:. by an answerer:
c-only: The answerer will act as a floor control client. c-only: The answerer will act as a floor control client.
Consequently, the offerer will act as a floor control server. Consequently, the offerer will act as a floor control server.
s-only: The answerer will act as a floor control server. s-only: The answerer will act as a floor control server.
Consequently, the offerer will act as a floor control client. Consequently, the offerer will act as a floor control client.
c-s: The answerer will act both as a floor control client and as a c-s: The answerer will act both as a floor control client and as a
floor control server. Consequently, the offerer will also act floor control server. Consequently, the offerer will also act
both as a floor control client and as a floor control server as both as a floor control client and as a floor control server.
well.
Endpoints which use the offer/answer model to establish BFCP Endpoints that use the offer/answer model to establish BFCP
connections MUST support the 'floorctrl' attribute. A floor control connections MUST support the 'floorctrl' attribute. A floor control
server acting as an offerer or as an answerers SHOULD include this server acting as an offerer or as an answerer SHOULD include this
attribute in its session descriptions. attribute in its session descriptions.
If the 'floorctrl' attribute is not used in an offer/answer exchange, If the 'floorctrl' attribute is not used in an offer/answer exchange,
by default the offerer and the answerer will act as a floor control by default the offerer and the answerer will act as a floor control
client and as a floor control server respectively. client and as a floor control server, respectively.
The following is an example of a 'floorctrl' attribute in an offer. The following is an example of a 'floorctrl' attribute in an offer.
When this attribute appears in an answer, it only carries one role: When this attribute appears in an answer, it only carries one role:
a=floorctrl:c-only s-only c-s a=floorctrl:c-only s-only c-s
5. The 'confid' and 'userid' SDP Attributes 5. The 'confid' and 'userid' SDP Attributes
We define the 'confid' and the 'userid' SDP media-level attributes. We define the 'confid' and the 'userid' SDP media-level attributes.
These attributes attributes are used by a floor control server to These attributes are used by a floor control server to provide a
provide a client with a conference ID and a user ID respectively. client with a conference ID and a user ID, respectively. Their
Their Augmented BNF syntax [2] is: Augmented BNF syntax [2] is:
confid-attribute = "a=confid:" conference-id confid-attribute = "a=confid:" conference-id
conference-id = token conference-id = token
userid-attribute = "a=userid:" user-id userid-attribute = "a=userid:" user-id
user-id = token user-id = token
The confid and the userid attributes carry the integer representation The 'confid' and the 'userid' attributes carry the integer
of a conference ID and a user ID respectively. representation of a conference ID and a user ID, respectively.
Endpoints which use the offer/answer model to establish BFCP Endpoints that use the offer/answer model to establish BFCP
connections MUST support the confid and the userid attributes. A connections MUST support the 'confid' and the 'userid' attributes. A
floor control server acting as an offerer or as an answerers SHOULD floor control server acting as an offerer or as an answerer SHOULD
include these attributes in its session descriptions. include these attributes in its session descriptions.
6. Association between Streams and Floors 6. Association between Streams and Floors
We define the floorid SDP media-level attribute. Its Augmented BNF We define the 'floorid' SDP media-level attribute. Its Augmented BNF
syntax [2] is: syntax [2] is:
floor-id-attribute = "a=floorid:" token [" mstrm:" token *(SP token)] floor-id-attribute = "a=floorid:" token [" mstrm:" token *(SP token)]
The floorid attribute is used in BFCP 'm' lines. It defines a floor The 'floorid' attribute is used in BFCP 'm' lines. It defines a
identifier and, possibly, associates it with one or more media floor identifier and, possibly, associates it with one or more media
streams. The token representing the floor ID is the integer streams. The token representing the floor ID is the integer
representation of the Floor ID to be used in BFCP. The token representation of the Floor ID to be used in BFCP. The token
representing the media stream is a pointer to the media stream, which representing the media stream is a pointer to the media stream, which
is identified by an SDP label attribute [9] is identified by an SDP label attribute [9].
Endpoints which use the offer/answer model to establish BFCP Endpoints that use the offer/answer model to establish BFCP
connections MUST support the 'floorid' and the 'label' attributes. A connections MUST support the 'floorid' and the 'label' attributes. A
floor control server acting as an offerer or as an answerer SHOULD floor control server acting as an offerer or as an answerer SHOULD
include these attributes in its session descriptions. include these attributes in its session descriptions.
7. TCP Connection Management 7. TCP Connection Management
The management of the TCP connection used to transport BFCP is The management of the TCP connection used to transport BFCP is
performed using the 'setup' and 'connection' attributes as defined in performed using the 'setup' and 'connection' attributes, as defined
[7]. in [7].
The 'setup' attribute indicates which of the endpoints (client or The 'setup' attribute indicates which of the endpoints (client or
floor control server) initiates the TCP connection. The 'connection' floor control server) initiates the TCP connection. The 'connection'
attribute handles TCP connection reestablishment. attribute handles TCP connection reestablishment.
The BFCP specification [8] describes a number of situations when the The BFCP specification [8] describes a number of situations when the
TCP connection between a client and the floor control server needs to TCP connection between a client and the floor control server needs to
be reestablished. However, that specification does not describe the be reestablished. However, that specification does not describe the
reestablishment process because this process depends on how the reestablishment process because this process depends on how the
connection was established in the first place. BFCP entities using connection was established in the first place. BFCP entities using
the offer/answer model follow the following rules. the offer/answer model follow the following rules.
When the existing TCP connection is reseted following the rules in When the existing TCP connection is reset following the rules in [8],
[8], the client SHOULD generate an offer towards the floor control the client SHOULD generate an offer towards the floor control server
server in order to reestablish the connection. If a TCP connection in order to reestablish the connection. If a TCP connection cannot
cannot deliver a BFCP message and times out, the entity that deliver a BFCP message and times out, the entity that attempted to
attempted to send the message (i.e., the one that detected the TCP send the message (i.e., the one that detected the TCP timeout) SHOULD
timeout) SHOULD generate an offer in order to reestablish the TCP generate an offer in order to reestablish the TCP connection.
connection.
Endpoints which use the offer/answer model to establish BFCP Endpoints that use the offer/answer model to establish BFCP
connections MUST support the 'setup' and the 'connection' attributes. connections MUST support the 'setup' and 'connection' attributes.
8. Authentication 8. Authentication
When a BFCP connection is established using the offer/answer model, When a BFCP connection is established using the offer/answer model,
it is assumed that the offerer and the answerer authenticate each it is assumed that the offerer and the answerer authenticate each
other using some mechanism. Once this mutual authentication takes other using some mechanism. Once this mutual authentication takes
place, all the offerer and the answerer need to make sure is that the place, all the offerer and the answerer need to ensure is that the
entity they are receiving BFCP messages from is the same as the one entity they are receiving BFCP messages from is the same as the one
that generated the previous offer or answer. that generated the previous offer or answer.
When SIP is used to perform an offer/answer exchange, the initial When SIP is used to perform an offer/answer exchange, the initial
mutual authentication takes place at the SIP level. Additionally, mutual authentication takes place at the SIP level. Additionally,
SIP uses S/MIME [6] to provide an integrity protected channel with SIP uses S/MIME [6] to provide an integrity-protected channel with
optional confidentiality for the offer/answer exchange. BFCP takes optional confidentiality for the offer/answer exchange. BFCP takes
advantage of this integrity protected offer/answer exchange to advantage of this integrity-protected offer/answer exchange to
perform authentication. Within the offer/answer exchange, the perform authentication. Within the offer/answer exchange, the
offerer and the answerer exchange the fingerprints of their self- offerer and answerer exchange the fingerprints of their self-signed
signed certificates. These self-signed certificates are then used to certificates. These self-signed certificates are then used to
establish the TLS connection that will carry BFCP traffic between the establish the TLS connection that will carry BFCP traffic between the
offerer and the answerer. offerer and the answerer.
BFCP clients and floor control servers follow the rules in [10] BFCP clients and floor control servers follow the rules in [10]
regarding certificate choice and presentation. This implies that regarding certificate choice and presentation. This implies that
unless a 'fingerprint' attribute is included in the session unless a 'fingerprint' attribute is included in the session
description, the certificate provided at the TLS-level MUST either be description, the certificate provided at the TLS-level MUST either be
directly signed by one of the other party's trust anchors or be directly signed by one of the other party's trust anchors or be
validated using a certification path that terminates at one of the validated using a certification path that terminates at one of the
other party's trust anchors [5]. Endpoints which use the offer/ other party's trust anchors [5]. Endpoints that use the offer/answer
answer model to establish BFCP connections MUST support the model to establish BFCP connections MUST support the 'fingerprint'
'fingerprint' attribute and SHOULD include it in their session attribute and SHOULD include it in their session descriptions.
descriptions.
When TLS is used, once the underlaying TCP connection is established, When TLS is used, once the underlaying TCP connection is established,
the answerer acts as the TLS server regardless of its role (passive the answerer acts as the TLS server regardless of its role (passive
or active) in the TCP establishment procedure. or active) in the TCP establishment procedure.
9. Examples 9. Examples
For the purpose of brevity, the main portion of the session For the purpose of brevity, the main portion of the session
description is omitted in the examples, which only show 'm' lines and description is omitted in the examples, which only show 'm' lines and
their attributes. their attributes.
skipping to change at page 9, line 16 skipping to change at page 8, line 7
a=setup:active a=setup:active
a=connection:new a=connection:new
a=fingerprint:SHA-1 \ a=fingerprint:SHA-1 \
3D:B4:7B:E3:CC:FC:0D:1B:5D:31:33:9E:48:9B:67:FE:68:40:E8:21 3D:B4:7B:E3:CC:FC:0D:1B:5D:31:33:9E:48:9B:67:FE:68:40:E8:21
a=floorctrl:c-only a=floorctrl:c-only
m=audio 55000 RTP/AVP 0 m=audio 55000 RTP/AVP 0
m=video 55002 RTP/AVP 31 m=video 55002 RTP/AVP 31
10. Security Considerations 10. Security Considerations
The BFCP [8], SDP [11], and the offer/answer [4] specifications The BFCP [8], SDP [11], and offer/answer [4] specifications discuss
discuss security issues related to BFCP, SDP, and the offer/answer security issues related to BFCP, SDP, and offer/answer, respectively.
respectively. In addition, [7] and [10] discuss security issues In addition, [7] and [10] discuss security issues related to the
related to the establishment of TCP and TLS connections using an establishment of TCP and TLS connections using an offer/answer model.
offer/answer model.
BFCP assumes an initial integrity-protected channel used to exchange BFCP assumes that an initial integrity-protected channel is used to
self-signed certificates between a client and the floor control exchange self-signed certificates between a client and the floor
server. For session descriptions carried in SIP [3], S/MIME [6] is control server. For session descriptions carried in SIP [3], S/MIME
the natural choice to provide such a channel. [6] is the natural choice to provide such a channel.
11. IANA Considerations 11. IANA Considerations
The following sections instruct the IANA to perform a set of actions.
11.1. Registration of the 'TCP/BFCP' and 'TCP/TLS/BFCP' SDP 'proto' 11.1. Registration of the 'TCP/BFCP' and 'TCP/TLS/BFCP' SDP 'proto'
values Values
This section instructs the IANA to register the following two new The IANA has registered the following two new values for the SDP
values for the SDP 'proto' field under the Session Description 'proto' field under the Session Description Protocol (SDP) Parameters
Protocol (SDP) Parameters registry: registry:
+--------------+-----------+ +--------------+-----------+
| Value | Reference | | Value | Reference |
+--------------+-----------+ +--------------+-----------+
| TCP/BFCP | RFCxxxx | | TCP/BFCP | RFC4583 |
| TCP/TLS/BFCP | RFCxxxx | | TCP/TLS/BFCP | RFC4583 |
+--------------+-----------+ +--------------+-----------+
Table 2: Values for the SDP 'proto' field Table 2: Values for the SDP 'proto' field
[Note to the RFC editor: please, replace RFCxxxx with the RFC number
that this document will be assigned.]
11.2. Registration of the SDP 'floorctrl' Attribute 11.2. Registration of the SDP 'floorctrl' Attribute
This section instructs the IANA to register the following SDP att- The IANA has registered the following SDP att-field under the Session
field under the Session Description Protocol (SDP) Parameters Description Protocol (SDP) Parameters registry:
registry:
Contact name: Gonzalo.Camarillo@ericsson.com Contact name: Gonzalo.Camarillo@ericsson.com
Attribute name: floorctrl Attribute name: floorctrl
Long-form attribute name: Floor Control Long-form attribute name: Floor Control
Type of attribute Media level Type of attribute: Media level
Subject to charset: No Subject to charset: No
Purpose of attribute: The 'floorctrl' attribute is used to perform Purpose of attribute: The 'floorctrl' attribute is used to perform
floor control server determination. floor control server determination.
Allowed attribute values: 1*("c-only" / "s-only" / "c-s") Allowed attribute values: 1*("c-only" / "s-only" / "c-s")
11.3. Registration of the SDP 'confid' Attribute 11.3. Registration of the SDP 'confid' Attribute
This section instructs the IANA to register the following SDP att- The IANA has registered the following SDP att-field under the Session
field under the Session Description Protocol (SDP) Parameters Description Protocol (SDP) Parameters registry:
registry:
Contact name: Gonzalo.Camarillo@ericsson.com Contact name: Gonzalo.Camarillo@ericsson.com
Attribute name: confid Attribute name: confid
Long-form attribute name: Conference Identifier Long-form attribute name: Conference Identifier
Type of attribute Media level Type of attribute: Media level
Subject to charset: No Subject to charset: No
Purpose of attribute: The 'confid' attribute carries the integer Purpose of attribute: The 'confid' attribute carries the integer
representation of a Conference ID. representation of a Conference ID.
Allowed attribute values: A token Allowed attribute values: A token
11.4. Registration of the SDP 'userid' Attribute 11.4. Registration of the SDP 'userid' Attribute
This section instructs the IANA to register the following SDP att- This section instructs the IANA to register the following SDP
field under the Session Description Protocol (SDP) Parameters att-field under the Session Description Protocol (SDP) Parameters
registry: registry:
Contact name: Gonzalo.Camarillo@ericsson.com Contact name: Gonzalo.Camarillo@ericsson.com
Attribute name: userid Attribute name: userid
Long-form attribute name: User Identifier Long-form attribute name: User Identifier
Type of attribute Media level Type of attribute: Media level
Subject to charset: No Subject to charset: No
Purpose of attribute: The 'userid' attribute carries the integer Purpose of attribute: The 'userid' attribute carries the integer
representation of a User ID. representation of a User ID.
Allowed attribute values: A token Allowed attribute values: A token
11.5. Registration of the SDP 'floorid' Attribute 11.5. Registration of the SDP 'floorid' Attribute
This section instructs the IANA to register the following SDP att- This section instructs the IANA to register the following SDP att-
field under the Session Description Protocol (SDP) Parameters field under the Session Description Protocol (SDP) Parameters
registry: registry:
Contact name: Gonzalo.Camarillo@ericsson.com Contact name: Gonzalo.Camarillo@ericsson.com
Attribute name: floorid Attribute name: floorid
Long-form attribute name: Floor Identifier Long-form attribute name: Floor Identifier
Type of attribute Media level Type of attribute: Media level
Subject to charset: No Subject to charset: No
Purpose of attribute: The 'floorid' attribute associates a floor Purpose of attribute: The 'floorid' attribute associates a floor
with one or more media streams. with one or more media streams.
Allowed attribute values: Tokens Allowed attribute values: Tokens
12. Acknowledgments 12. Acknowledgements
Joerg Ott, Keith Drage, Alan Johnston, Eric Rescorla, Roni Even, and Joerg Ott, Keith Drage, Alan Johnston, Eric Rescorla, Roni Even, and
Oscar Novo provided useful ideas for this document. Oscar Novo provided useful ideas for this document.
13. Normative References 13. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [2] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 4234, October 2005.
[3] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., [3] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, June 2002. Session Initiation Protocol", RFC 3261, June 2002.
[4] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with [4] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
Session Description Protocol (SDP)", RFC 3264, June 2002. Session Description Protocol (SDP)", RFC 3264, June 2002.
[5] Housley, R., Polk, W., Ford, W., and D. Solo, "Internet X.509 [5] Housley, R., Polk, W., Ford, W., and D. Solo, "Internet X.509
Public Key Infrastructure Certificate and Certificate Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile", RFC 3280, April 2002. Revocation List (CRL) Profile", RFC 3280, April 2002.
[6] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions [6] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions
(S/MIME) Version 3.1 Certificate Handling", RFC 3850, (S/MIME) Version 3.1 Certificate Handling", RFC 3850, July
July 2004. 2004.
[7] Yon, D. and G. Camarillo, "TCP-Based Media Transport in the [7] Yon, D. and G. Camarillo, "TCP-Based Media Transport in the
Session Description Protocol (SDP)", RFC 4145, September 2005. Session Description Protocol (SDP)", RFC 4145, September 2005.
[8] Camarillo, G., "The Binary Floor Control Protocol (BFCP)", [8] Camarillo, G., Ott, J., and K. Drage, "The Binary Floor Control
draft-ietf-xcon-bfcp-05 (work in progress), July 2005. Protocol (BFCP)", RFC 4582, November 2006.
[9] Levin, O. and G. Camarillo, "The SDP (Session Description [9] Levin, O. and G. Camarillo, "The Session Description Protocol
Protocol) Label Attribute", (SDP) Label Attribute", RFC 4574, July 2006.
draft-ietf-mmusic-sdp-media-label-01 (work in progress),
January 2005.
[10] Lennox, J., "Connection-Oriented Media Transport over the [10] Lennox, J., "Connection-Oriented Media Transport over the
Transport Layer Security (TLS) Protocol in the Session Transport Layer Security (TLS) Protocol in the Session
Description Protocol (SDP)", draft-ietf-mmusic-comedia-tls-05 Description Protocol (SDP)", RFC 4572, July 2006.
(work in progress), September 2005.
[11] Handley, M., "SDP: Session Description Protocol", [11] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
draft-ietf-mmusic-sdp-new-25 (work in progress), July 2005. Description Protocol", RFC 4566, July 2006.
Author's Address Author's Address
Gonzalo Camarillo Gonzalo Camarillo
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
Finland Finland
Email: Gonzalo.Camarillo@ericsson.com EMail: Gonzalo.Camarillo@ericsson.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST,
AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 14, line 29 skipping to change at page 12, line 46
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Acknowledgement
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 64 change blocks. 
187 lines changed or deleted 157 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/