draft-ietf-mmusic-sdp-bfcp-01.txt   draft-ietf-mmusic-sdp-bfcp-02.txt 
MMUSIC Working Group G. Camarillo MMUSIC Working Group G. Camarillo
Internet-Draft Ericsson Internet-Draft Ericsson
Expires: November 5, 2005 May 4, 2005 Expires: January 19, 2006 July 18, 2005
Session Description Protocol (SDP) Format for Binary Floor Control Session Description Protocol (SDP) Format for Binary Floor Control
Protocol (BFCP) Streams Protocol (BFCP) Streams
draft-ietf-mmusic-sdp-bfcp-01.txt draft-ietf-mmusic-sdp-bfcp-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 5, 2005. This Internet-Draft will expire on January 19, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
This document specifies how to describe BFCP streams in SDP session This document specifies how to describe BFCP streams in SDP session
descriptions. User agents using the offer/answer model to establish descriptions. User agents using the offer/answer model to establish
BFCP streams use this format in their offers and their answers. BFCP streams use this format in their offers and their answers.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Fields in the m Line . . . . . . . . . . . . . . . . . . . . . 3 3. Fields in the 'm' Line . . . . . . . . . . . . . . . . . . . . 3
4. Floor Control Server Determination . . . . . . . . . . . . . . 4 4. Floor Control Server Determination . . . . . . . . . . . . . . 4
5. The 'confid' and 'userid' SDP Attributes . . . . . . . . . . . 4 5. The 'confid' and 'userid' SDP Attributes . . . . . . . . . . . 6
6. Association between Streams and Floors . . . . . . . . . . . . 5 6. Association between Streams and Floors . . . . . . . . . . . . 6
7. TCP Connection Management . . . . . . . . . . . . . . . . . . 5 7. TCP Connection Management . . . . . . . . . . . . . . . . . . 7
8. Authentication . . . . . . . . . . . . . . . . . . . . . . . . 6 8. Authentication . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1 Mutual Authentication Using Certificates and TLS . . . . . 6 8.1 Mutual Authentication Using Certificates and TLS . . . . . 8
8.2 Client Authentication at the BFCP Level . . . . . . . . . 7 8.2 Client Authentication at the BFCP Level . . . . . . . . . 8
8.2.1 Generating a Shared Secret . . . . . . . . . . . . . . 7 8.2.1 Generating a Shared Secret . . . . . . . . . . . . . . 8
8.2.2 The 'nonce' Attribute . . . . . . . . . . . . . . . . 8 8.2.2 The 'nonce' Attribute . . . . . . . . . . . . . . . . 9
9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1 Example Using TLS . . . . . . . . . . . . . . . . . . . . 8 9.1 Example Using TLS . . . . . . . . . . . . . . . . . . . . 10
9.2 Example Using the 'crypto' Attribute . . . . . . . . . . . 9 9.2 Example Using the 'crypto' Attribute . . . . . . . . . . . 11
10. Security Considerations . . . . . . . . . . . . . . . . . . 10 10. Security Considerations . . . . . . . . . . . . . . . . . . 11
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . 10 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . 12
11.1 Registration of the 'TCP/BFCP' and 'TCP/TLS/BFCP' SDP 11.1 Registration of the 'TCP/BFCP' and 'TCP/TLS/BFCP' SDP
'proto' values . . . . . . . . . . . . . . . . . . . . . . 11 'proto' values . . . . . . . . . . . . . . . . . . . . . . 12
11.2 Registration of the SDP 'confid' Attribute . . . . . . . . 11 11.2 Registration of the SDP 'floorctrl' Attribute . . . . . . 12
11.3 Registration of the SDP 'userid' Attribute . . . . . . . . 11 11.3 Registration of the SDP 'confid' Attribute . . . . . . . . 13
11.4 Registration of the SDP 'floorid' Attribute . . . . . . . 12 11.4 Registration of the SDP 'userid' Attribute . . . . . . . . 13
11.5 Registration of the SDP 'nonce' Attribute . . . . . . . . 12 11.5 Registration of the SDP 'floorid' Attribute . . . . . . . 14
11.6 Registration of the crypto-suites for 'TCP/BFCP' . . . . . 13 11.6 Registration of the SDP 'nonce' Attribute . . . . . . . . 14
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 13 11.7 Registration of the crypto-suites for 'TCP/BFCP' . . . . . 15
13. Normative References . . . . . . . . . . . . . . . . . . . . 13 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 15
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 14 13. Normative References . . . . . . . . . . . . . . . . . . . . 15
Intellectual Property and Copyright Statements . . . . . . . . 15 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . 18
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 consists of using an
offer/answer [5] exchange. This document specifies how to encode offer/answer [5] exchange. This document specifies how to encode
this information in the SDP session descriptions which are part of an this information in the SDP session descriptions which are part of
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 [2] and indicate requirement levels for described in BCP 14, RFC 2119 [2] 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.
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 (disccused in Section 7), the port
skipping to change at page 4, line 9 skipping to change at page 4, line 11
standard SDP meaning (i.e., rejection of the media stream). 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 TCP/
TLS/BFCP. The former is used when BFCP runs directly on top of TCP TLS/BFCP. The former is used when BFCP runs directly on top of TCP
and the latter is used when BFCP runs on top of TLS, which in turn and the latter is used when BFCP runs on top of TLS, which in turn
runs on top of TCP. 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 20000 TCP/TLS/BFCP * m=application 20000 TCP/TLS/BFCP *
4. Floor Control Server Determination 4. Floor Control Server Determination
The 'confid' and the 'userid' attributes are used by a floor control When two endpoints establish a BFCP stream, they need to determine
server to provide a client with a conference ID and a user ID. In which of them acts as a floor control server. The most common
the context of an offer/answer exchange, the entity including these scenario consists of a client establishing a BFCP stream with
attributes is the floor control server. conference server that acts as the floor control server. Floor
control server determination is straight forward because one endpoint
can only act as a client and the other can only act as a floor
control server.
The most common scenario consists of a client establishing a BFCP However, there are scenarios where both endpoints could act as a
stream with a floor control server. In this case, there is only one floor control server. For example, is a two-party session that
floor control server (the offerer or the answerer). However, there involves an audio stream and a shared whiteboard, the endpoints need
are scenarios where both the offerer and the answerer are both to decide which party will be acting as the floor control server.
clients and floor control servers. For example, in a two-party
session that involves an audio stream and a shared whiteboard, one Furthermore, there are situations where both the offerer and the
party acts as the floor control server for the audio stream and the answerer act as both clients and floor control servers in the same
other acts as the floor control server for the shared whiteboard. In session. For example, in a two-party session that involves an audio
such a case, both the offerer and the answerer would include the stream and a shared whiteboard, one party acts as the floor control
'confid' and the 'userid' attributes in their respective session server for the audio stream and the other acts as the floor control
descriptions. server for the shared whiteboard.
We define the 'floorctrl' SDP media-level attribute to perform floor
control determination. Its Augmented BNF syntax [3] is:
floor-control-attribute = "a=floorctrl:" role *(SP role)
role = "c-only" / "s-only" / "c-s"
The offerer includes this attribute to state all the roles it would
be willing to perform:
c-only: The offerer would be willing to only act as a floor control
client.
s-only: The offerer would be willing to only act as a floor control
server.
c-s: The offerer would be willing to act both as a floor control
client and as a floor control server.
If an 'm' line in an offer contains a 'floorctrl' attribute, the
answerer MUST include one in the corresponding 'm' line in the
answer. The answerer includes this attribute to state which role the
answerer will perform. That is, the answerer chooses one of the
roles the offerer is willing to perform and generates an answer with
the corresponding role for the answerer. Table 1 shows the
corresponding roles for an answerer depending on the offerer's role.
+---------+----------+
| Offerer | Answerer |
+---------+----------+
| c-only | s-only |
| s-only | c-only |
| c-s | c-s |
+---------+----------+
Table 1: Roles
The following are the description of the roles when chosen by an
answere:.
c-only: The answerer will act as a floor control client.
Consequently, the offerer 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.
c-s: The answerer will act both as a floor control client and as a
floor control server. Consequently, the offerer will also act
both as a floor control client and as a floor control server as
well.
Endpoints which use the offer/answer model to establish BFCP
connections MUST support the 'floorctrl' attribute. A floor control
server acting as an offerer or as an answerers SHOULD include this
attribute in its session descriptions.
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
client and as a floor control server respectively.
The following is an example of a 'floorctrl' attribute in an offer.
When this attribute appears in an answer, it only carries one role:
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 attributes are used by a floor control server to
provide a client with a conference ID and a user ID respectively. provide a client with a conference ID and a user ID respectively.
Their Augmented BNF syntax [3] is: Their Augmented BNF syntax [3] is:
confid-attribute = "a=confid: " conference-id confid-attribute = "a=confid: " conference-id
conference-id = token conference-id = token
skipping to change at page 5, line 32 skipping to change at page 7, line 11
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 in
[7]. [7].
The setup attribute indicates which of the endpoints (client or floor The 'setup' attribute indicates which of the endpoints (client or
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 reseted following the rules in
skipping to change at page 7, line 36 skipping to change at page 9, line 13
The possible values for the crypto-suite field are defined within the The possible values for the crypto-suite field are defined within the
context of a transport; TCP/BFCP in our case. Within the context of context of a transport; TCP/BFCP in our case. Within the context of
TCP/BFCP, we define the following value for the crypto-suite field: TCP/BFCP, we define the following value for the crypto-suite field:
+-----------+-----------------+ +-----------+-----------------+
| Value | BFCP Identifier | | Value | BFCP Identifier |
+-----------+-----------------+ +-----------+-----------------+
| HMAC-SHA1 | 0 | | HMAC-SHA1 | 0 |
+-----------+-----------------+ +-----------+-----------------+
Table 1: Values for the crypto-suite field in TCP/BFCP Table 2: Values for the crypto-suite field in TCP/BFCP
The IANA registry for Digest Algorithms in BFCP contains references The IANA registry for Digest Algorithms in BFCP contains references
to the specifications that describe the usage of each digest to the specifications that describe the usage of each digest
algorithm (identified by its BFCP identifier) in BFCP. algorithm (identified by its BFCP identifier) in BFCP.
The key-params field SHOULD use the 'inline' key method followed by a The key-params field SHOULD use the 'inline' key method followed by a
base64-encoded [6] unguessable secret [1]. base64-encoded [6] unguessable secret [1].
The use of the optional session-params field is for further study. The use of the optional session-params field is for further study.
skipping to change at page 9, line 10 skipping to change at page 10, line 27
9.1 Example Using TLS 9.1 Example Using TLS
The following is an example of an offer sent by a conference server The following is an example of an offer sent by a conference server
to a client. to a client.
m=application 20000 TCP/TLS/BFCP * m=application 20000 TCP/TLS/BFCP *
a=setup:passive a=setup:passive
a=connection:new a=connection:new
a=fingerprint:SHA-1 \ a=fingerprint:SHA-1 \
4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
a=floorctrl:s-only
a=confid:4321 a=confid:4321
a=userid:1234 a=userid:1234
a=floorid:1 m-stream:10 a=floorid:1 m-stream:10
a=floorid:2 m-stream:11 a=floorid:2 m-stream:11
m=audio 20000 RTP/AVP 0 m=audio 20000 RTP/AVP 0
a=label:10 a=label:10
m=video 30000 RTP/AVP 31 m=video 30000 RTP/AVP 31
a=label:11 a=label:11
Note that due to RFC formatting conventions, this document splits SDP Note that due to RFC formatting conventions, this document splits SDP
across lines whose content would exceed 72 characters. A backslash across lines whose content would exceed 72 characters. A backslash
character marks where this line folding has taken place. This character marks where this line folding has taken place. This
backslash and its trailing CRLF and whitespace would not appear in backslash and its trailing CRLF and whitespace would not appear in
actual SDP content. actual SDP content.
The following is the answer returned by the user. The following is the answer returned by the user.
m=application 9 TCP/TLS/BFCP * m=application 9 TCP/TLS/BFCP *
a=setup:active a=setup:active
a=connection:new a=connection:new
a=fingerprint:SHA-1 \
3D:B4:7B:E3:CC:FC:0D:1B:5D:31:33:9E:48:9B:67:FE:68:40:E8:21
a=floorctrl:c-only
m=audio 25000 RTP/AVP 0 m=audio 25000 RTP/AVP 0
m=video 35000 RTP/AVP 31 m=video 35000 RTP/AVP 31
9.2 Example Using the 'crypto' Attribute 9.2 Example Using the 'crypto' Attribute
The following is an example of an offer sent by a conference server The following is an example of an offer sent by a client to a
to a client. In this case, TLS is not used to perform mutual conference server. In this case, TLS is not used to perform mutual
authentication. The 'crypto' attribute is used to generate a shared authentication. The 'crypto' attribute is used to generate a shared
secret between the client and the floor control server. secret between the client and the floor control server.
m=application 9 TCP/BFCP *
a=setup:active
a=connection:new
a=crypto:1 HMAC-SHA1 inline:c2hhcmVkLXNlY3JldA==
a=floorctrl:c-only
m=audio 25000 RTP/AVP 0
m=video 35000 RTP/AVP 31
The following is the answer returned by the conference server.
m=application 20000 TCP/BFCP * m=application 20000 TCP/BFCP *
a=setup:passive a=setup:passive
a=connection:new a=connection:new
a=crypto:1 HMAC-SHA1 inline:c2hhcmVkLXNlY3JldA== a=crypto:1 HMAC-SHA1 inline:c2hhcmVkLXNlY3JldA==
a=nonce:5736 a=nonce:5736
a=floorctrl:s-only
a=confid:4321 a=confid:4321
a=userid:1234 a=userid:1234
a=floorid:1 m-stream:10 a=floorid:1 m-stream:10
a=floorid:2 m-stream:11 a=floorid:2 m-stream:11
m=audio 20000 RTP/AVP 0 m=audio 20000 RTP/AVP 0
a=label:10 a=label:10
m=video 30000 RTP/AVP 31 m=video 30000 RTP/AVP 31
a=label:11 a=label:11
The following is the answer returned by the participant.
m=application 9 TCP/BFCP *
a=setup:active
a=connection:new
a=crypto:1 HMAC-SHA1 inline:c2hhcmVkLXNlY3JldA==
m=audio 25000 RTP/AVP 0
m=video 35000 RTP/AVP 31
10. Security Considerations 10. Security Considerations
The BFCP [8], SDP [11], and the offer/answer [5] specifications The BFCP [8], SDP [11], and the offer/answer [5] specifications
discuss security issues related to BFCP, SDP, and the offer/answer discuss security issues related to BFCP, SDP, and the offer/answer
respectively. In addition, [7] and [10] discuss security issues respectively. In addition, [7] and [10] discuss security issues
related to the establishment of TCP and TLS connections using an related to the establishment of TCP and TLS connections using an
offer/answer model. offer/answer model.
An issue which is discussed in the previous specifications and is of An issue which is discussed in the previous specifications and is of
particular importance for this specification relates to the usage of particular importance for this specification relates to the usage of
skipping to change at page 11, line 19 skipping to change at page 12, line 37
values for the SDP 'proto' field under the Session Description values for the SDP 'proto' field under the Session Description
Protocol (SDP) Parameters registry: Protocol (SDP) Parameters registry:
+--------------+-----------+ +--------------+-----------+
| Value | Reference | | Value | Reference |
+--------------+-----------+ +--------------+-----------+
| TCP/BFCP | RFCxxxx | | TCP/BFCP | RFCxxxx |
| TCP/TLS/BFCP | RFCxxxx | | TCP/TLS/BFCP | RFCxxxx |
+--------------+-----------+ +--------------+-----------+
Table 2: Values for the SDP 'proto' field Table 3: Values for the SDP 'proto' field
[Note to the RFC editor: please, replace RFCxxxx with the RFC number [Note to the RFC editor: please, replace RFCxxxx with the RFC number
that this document will be assigned.] that this document will be assigned.]
11.2 Registration of the SDP 'confid' Attribute 11.2 Registration of the SDP 'floorctrl' Attribute
This section instructs the IANA to register the following SDP att-
field under the Session Description Protocol (SDP) Parameters
registry:
Contact name: Gonzalo.Camarillo@ericsson.com
Attribute name: floorctrl
Long-form attribute name: Floor Control
Type of attribute Media level
Subject to charset: No
Purpose of attribute: The 'floorctrl' attribute is used to
perform floor control server determination.
Allowed attribute values: 1*("c-only" / "s-only" / "c-s")
11.3 Registration of the SDP 'confid' 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: confid Attribute name: confid
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.3 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 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: userid Attribute name: userid
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.4 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
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
11.5 Registration of the SDP 'nonce' Attribute 11.6 Registration of the SDP 'nonce' 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: nonce Attribute name: nonce
Long-form attribute name: Nonce
Type of attribute Media level Type of attribute Media level
Subject to charset: No Subject to charset: No
Purpose of attribute: The 'nonce' attribute carried a nonce to be Purpose of attribute: The 'nonce' attribute carried a nonce to
used in the media stream (e.g., in the BFCP connection). be used in the media stream (e.g., in the BFCP connection).
Allowed attribute values: A token Allowed attribute values: A token
11.6 Registration of the crypto-suites for 'TCP/BFCP' 11.7 Registration of the crypto-suites for 'TCP/BFCP'
This section instructs the IANA to register the 'TCP/BFCP' media This section instructs the IANA to register the 'TCP/BFCP' media
transport under the SDP Security Description registry. The key transport under the SDP Security Description registry. The key
methods supported is "inline". The reference for the SDP security methods supported is "inline". The reference for the SDP security
description for 'TCP/BFCP' is this document. description for 'TCP/BFCP' is this document.
The following crypto-suite needs to be registered under the 'TCP/ The following crypto-suite needs to be registered under the 'TCP/
BFCP' transport: BFCP' transport:
+-----------+-----------------+ +-----------+-----------------+
| Value | BFCP Identifier | | Value | BFCP Identifier |
+-----------+-----------------+ +-----------+-----------------+
| HMAC-SHA1 | 0 | | HMAC-SHA1 | 0 |
+-----------+-----------------+ +-----------+-----------------+
Table 3: Values for the crypto-suite field in TCP/BFCP Table 4: Values for the crypto-suite field in TCP/BFCP
The IANA registry for Digest Algorithms in BFCP contains references The IANA registry for Digest Algorithms in BFCP contains references
to the specifications that describe the usage of each digest to the specifications that describe the usage of each digest
algorithm (identified by its BFCP identifier) in BFCP. algorithm (identified by its BFCP identifier) in BFCP.
At this point, there are no session parameters defined for the 'TCP/ At this point, there are no session parameters defined for the 'TCP/
BFCP' media transport. Consequently, the IANA does not need to BFCP' media transport. Consequently, the IANA does not need to
create a session parameter subregistry under 'TCP/BFCP'. create a session parameter subregistry under 'TCP/BFCP'.
12. Acknowledgments 12. Acknowledgments
Joerg Ott, Keith Drage, Alan Johnston, and Eric Rescorla provided Joerg Ott, Keith Drage, Alan Johnston, Eric Rescorla, Roni Even, and
useful ideas for this document. Oscar Novo provided useful ideas for this document.
13. Normative References 13. Normative References
[1] Eastlake, D., Crocker, S., and J. Schiller, "Randomness [1] Eastlake, D., Crocker, S., and J. Schiller, "Randomness
Recommendations for Security", RFC 1750, December 1994. Recommendations for Security", RFC 1750, December 1994.
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement [2] 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.
[3] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [3] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
skipping to change at page 14, line 20 skipping to change at page 16, line 24
Session Description Protocol (SDP)", RFC 3264, June 2002. Session Description Protocol (SDP)", RFC 3264, June 2002.
[6] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", [6] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings",
RFC 3548, July 2003. RFC 3548, July 2003.
[7] Yon, D., "Connection-Oriented Media Transport in the Session [7] Yon, D., "Connection-Oriented Media Transport in the Session
Description Protocol (SDP)", draft-ietf-mmusic-sdp-comedia-10 Description Protocol (SDP)", draft-ietf-mmusic-sdp-comedia-10
(work in progress), November 2004. (work in progress), November 2004.
[8] Camarillo, G., "The Binary Floor Control Protocol (BFCP)", [8] Camarillo, G., "The Binary Floor Control Protocol (BFCP)",
draft-ietf-xcon-bfcp-03 (work in progress), January 2005. draft-ietf-xcon-bfcp-04 (work in progress), May 2005.
[9] Levin, O. and G. Camarillo, "The SDP (Session Description [9] Levin, O. and G. Camarillo, "The SDP (Session Description
Protocol) Label Attribute", Protocol) Label Attribute",
draft-levin-mmmusic-sdp-media-label-00 (work in progress), draft-levin-mmmusic-sdp-media-label-00 (work in progress),
July 2004. July 2004.
[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-02 Description Protocol (SDP)", draft-ietf-mmusic-comedia-tls-04
(work in progress), October 2004. (work in progress), July 2005.
[11] Handley, M., "SDP: Session Description Protocol", [11] Handley, M., "SDP: Session Description Protocol",
draft-ietf-mmusic-sdp-new-24 (work in progress), February 2005. draft-ietf-mmusic-sdp-new-24 (work in progress), February 2005.
[12] Andreasen, F., Baugher, M., and D. Wing, "Session Description [12] Andreasen, F., "Session Description Protocol Security
Protocol Security Descriptions for Media Streams", Descriptions for Media Streams",
draft-ietf-mmusic-sdescriptions-09 (work in progress), draft-ietf-mmusic-sdescriptions-11 (work in progress),
February 2005. June 2005.
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
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/