1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
|
<pre>Network Working Group G. Camarillo
Request for Comments: 4583 Ericsson
Category: Standards Track November 2006
<span class="h1">Session Description Protocol (SDP) Format for</span>
<span class="h1">Binary Floor Control Protocol (BFCP) Streams</span>
Status of This Memo
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 (C) The IETF Trust (2006).
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.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-2">2</a>
<a href="#section-3">3</a>. Fields in the 'm' Line ..........................................<a href="#page-2">2</a>
<a href="#section-4">4</a>. Floor Control Server Determination ..............................<a href="#page-3">3</a>
<a href="#section-5">5</a>. The 'confid' and 'userid' SDP Attributes ........................<a href="#page-5">5</a>
<a href="#section-6">6</a>. Association between Streams and Floors ..........................<a href="#page-5">5</a>
<a href="#section-7">7</a>. TCP Connection Management .......................................<a href="#page-5">5</a>
<a href="#section-8">8</a>. Authentication ..................................................<a href="#page-6">6</a>
<a href="#section-9">9</a>. Examples ........................................................<a href="#page-7">7</a>
<a href="#section-10">10</a>. Security Considerations ........................................<a href="#page-8">8</a>
<a href="#section-11">11</a>. IANA Considerations ............................................<a href="#page-8">8</a>
11.1. Registration of the 'TCP/BFCP' and 'TCP/TLS/BFCP'
SDP 'proto' Values ........................................<a href="#page-8">8</a>
<a href="#section-11.2">11.2</a>. Registration of the SDP 'floorctrl' Attribute .............<a href="#page-8">8</a>
<a href="#section-11.3">11.3</a>. Registration of the SDP 'confid' Attribute ................<a href="#page-9">9</a>
<a href="#section-11.4">11.4</a>. Registration of the SDP 'userid' Attribute ................<a href="#page-9">9</a>
<a href="#section-11.5">11.5</a>. Registration of the SDP 'floorid' Attribute ..............<a href="#page-10">10</a>
<a href="#section-12">12</a>. Acknowledgements ..............................................<a href="#page-10">10</a>
<a href="#section-13">13</a>. Normative References ..........................................<a href="#page-10">10</a>
<span class="grey">Camarillo Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
As discussed in the BFCP (Binary Floor Control Protocol)
specification [<a href="#ref-8" title=""The Binary Floor Control Protocol (BFCP)"">8</a>], a given BFCP client needs a set of data in order
to establish a BFCP connection to a floor control server. These 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/answer [<a href="#ref-4" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">4</a>] exchange. This document specifies how to encode
this information in the SDP session descriptions that are part of
such an offer/answer exchange.
User agents typically use the offer/answer model to establish a
number of media streams of different types. Following this model, a
BFCP connection is described as any other media stream by using an
SDP 'm' line, possibly followed by a number of attributes encoded in
'a' lines.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as
described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a> [<a href="#ref-1" title=""Key words for use in RFCs to Indicate Requirement Levels"">1</a>] and indicate requirement levels for
compliant implementations.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Fields in the 'm' Line</span>
This section describes how to generate an 'm' line for a BFCP stream.
According to the SDP specification [<a href="#ref-11" title=""SDP: Session Description Protocol"">11</a>], the 'm' line format is the
following:
m=<media> <port> <transport> <fmt> ...
The media field MUST have a value of "application".
The port field is set following the rules in [<a href="#ref-7" title=""TCP-Based Media Transport in the Session Description Protocol (SDP)"">7</a>]. Depending on the
value of the 'setup' attribute (discussed in <a href="#section-7">Section 7</a>), the port
field contains the port to which the remote endpoint will initiate
its TCP connection or is irrelevant (i.e., the endpoint will initiate
the connection towards the remote endpoint) and should be set to a
value of 9, which is the discard port. Since BFCP only runs on top
of TCP, the port is always a TCP port. A port field value of zero
has the standard SDP meaning (i.e., rejection of the media stream).
<span class="grey">Camarillo Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
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, and the latter is used when BFCP runs on top of TLS, which in
turn runs on top of TCP.
The fmt (format) list is ignored for BFCP. The fmt list of BFCP 'm'
lines SHOULD contain a single "*" character.
The following is an example of an 'm' line for a BFCP connection:
m=application 50000 TCP/TLS/BFCP *
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Floor Control Server Determination</span>
When two endpoints establish a BFCP stream, they need to determine
which of them acts as a floor control server. In the most common
scenario, a client establishes a BFCP stream with a 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.
However, there are scenarios where both endpoints could act as a
floor control server. For example, in a two-party session that
involves an audio stream and a shared whiteboard, the endpoints need
to decide which party will be acting as the floor control server.
Furthermore, there are situations where both the offerer and the
answerer act as both clients and floor control servers in the same
session. For example, in a two-party session that involves an audio
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 shared whiteboard.
We define the 'floorctrl' SDP media-level attribute to perform floor
control determination. Its Augmented BNF syntax [<a href="#ref-2" title=""Augmented BNF for Syntax Specifications: ABNF"">2</a>] 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 act as a floor control
client only.
s-only: The offerer would be willing to act as a floor control
server only.
<span class="grey">Camarillo Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
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 descriptions of the roles when they are chosen
by an answerer:
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.
Endpoints that 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 answerer 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
<span class="grey">Camarillo Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. The 'confid' and 'userid' SDP Attributes</span>
We define the 'confid' and the 'userid' SDP media-level attributes.
These attributes are used by a floor control server to provide a
client with a conference ID and a user ID, respectively. Their
Augmented BNF syntax [<a href="#ref-2" title=""Augmented BNF for Syntax Specifications: ABNF"">2</a>] is:
confid-attribute = "a=confid:" conference-id
conference-id = token
userid-attribute = "a=userid:" user-id
user-id = token
The 'confid' and the 'userid' attributes carry the integer
representation of a conference ID and a user ID, respectively.
Endpoints that use the offer/answer model to establish BFCP
connections MUST support the 'confid' and the 'userid' attributes. A
floor control server acting as an offerer or as an answerer SHOULD
include these attributes in its session descriptions.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Association between Streams and Floors</span>
We define the 'floorid' SDP media-level attribute. Its Augmented BNF
syntax [<a href="#ref-2" title=""Augmented BNF for Syntax Specifications: ABNF"">2</a>] is:
floor-id-attribute = "a=floorid:" token [" mstrm:" token *(SP token)]
The 'floorid' attribute is used in BFCP 'm' lines. It defines a
floor identifier and, possibly, associates it with one or more media
streams. The token representing the floor ID is the integer
representation of the Floor ID to be used in BFCP. The token
representing the media stream is a pointer to the media stream, which
is identified by an SDP label attribute [<a href="#ref-9" title=""The Session Description Protocol (SDP) Label Attribute"">9</a>].
Endpoints that use the offer/answer model to establish BFCP
connections MUST support the 'floorid' and the 'label' attributes. A
floor control server acting as an offerer or as an answerer SHOULD
include these attributes in its session descriptions.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. TCP Connection Management</span>
The management of the TCP connection used to transport BFCP is
performed using the 'setup' and 'connection' attributes, as defined
in [<a href="#ref-7" title=""TCP-Based Media Transport in the Session Description Protocol (SDP)"">7</a>].
<span class="grey">Camarillo Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
The 'setup' attribute indicates which of the endpoints (client or
floor control server) initiates the TCP connection. The 'connection'
attribute handles TCP connection reestablishment.
The BFCP specification [<a href="#ref-8" title=""The Binary Floor Control Protocol (BFCP)"">8</a>] describes a number of situations when the
TCP connection between a client and the floor control server needs to
be reestablished. However, that specification does not describe the
reestablishment process because this process depends on how the
connection was established in the first place. BFCP entities using
the offer/answer model follow the following rules.
When the existing TCP connection is reset following the rules in [<a href="#ref-8" title=""The Binary Floor Control Protocol (BFCP)"">8</a>],
the client SHOULD generate an offer towards the floor control server
in order to reestablish the connection. If a TCP connection cannot
deliver a BFCP message and times out, the entity that attempted to
send the message (i.e., the one that detected the TCP timeout) SHOULD
generate an offer in order to reestablish the TCP connection.
Endpoints that use the offer/answer model to establish BFCP
connections MUST support the 'setup' and 'connection' attributes.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authentication</span>
When a BFCP connection is established using the offer/answer model,
it is assumed that the offerer and the answerer authenticate each
other using some mechanism. Once this mutual authentication takes
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
that generated the previous offer or answer.
When SIP is used to perform an offer/answer exchange, the initial
mutual authentication takes place at the SIP level. Additionally,
SIP uses S/MIME [<a href="#ref-6" title=""Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling"">6</a>] to provide an integrity-protected channel with
optional confidentiality for the offer/answer exchange. BFCP takes
advantage of this integrity-protected offer/answer exchange to
perform authentication. Within the offer/answer exchange, the
offerer and answerer exchange the fingerprints of their self-signed
certificates. These self-signed certificates are then used to
establish the TLS connection that will carry BFCP traffic between the
offerer and the answerer.
BFCP clients and floor control servers follow the rules in [<a href="#ref-10" title=""Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)"">10</a>]
regarding certificate choice and presentation. This implies that
unless a 'fingerprint' attribute is included in the session
description, the certificate provided at the TLS-level MUST either 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
other party's trust anchors [<a href="#ref-5" title=""Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">5</a>]. Endpoints that use the offer/answer
<span class="grey">Camarillo Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
model to establish BFCP connections MUST support the 'fingerprint'
attribute and SHOULD include it in their session descriptions.
When TLS is used, once the underlaying TCP connection is established,
the answerer acts as the TLS server regardless of its role (passive
or active) in the TCP establishment procedure.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Examples</span>
For the purpose of brevity, the main portion of the session
description is omitted in the examples, which only show 'm' lines and
their attributes.
The following is an example of an offer sent by a conference server
to a client.
m=application 50000 TCP/TLS/BFCP *
a=setup:passive
a=connection:new
a=fingerprint:SHA-1 \
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=userid:1234
a=floorid:1 m-stream:10
a=floorid:2 m-stream:11
m=audio 50002 RTP/AVP 0
a=label:10
m=video 50004 RTP/AVP 31
a=label:11
Note that due to RFC formatting conventions, this document splits SDP
across lines whose content would exceed 72 characters. A backslash
character marks where this line folding has taken place. This
backslash and its trailing CRLF and whitespace would not appear in
actual SDP content.
The following is the answer returned by the client.
m=application 9 TCP/TLS/BFCP *
a=setup:active
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 55000 RTP/AVP 0
m=video 55002 RTP/AVP 31
<span class="grey">Camarillo Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
The BFCP [<a href="#ref-8" title=""The Binary Floor Control Protocol (BFCP)"">8</a>], SDP [<a href="#ref-11" title=""SDP: Session Description Protocol"">11</a>], and offer/answer [<a href="#ref-4" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">4</a>] specifications discuss
security issues related to BFCP, SDP, and offer/answer, respectively.
In addition, [<a href="#ref-7" title=""TCP-Based Media Transport in the Session Description Protocol (SDP)"">7</a>] and [<a href="#ref-10" title=""Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)"">10</a>] discuss security issues related to the
establishment of TCP and TLS connections using an offer/answer model.
BFCP assumes that an initial integrity-protected channel is used to
exchange self-signed certificates between a client and the floor
control server. For session descriptions carried in SIP [<a href="#ref-3" title=""SIP: Session Initiation Protocol"">3</a>], S/MIME
[<a href="#ref-6" title=""Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling"">6</a>] is the natural choice to provide such a channel.
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. IANA Considerations</span>
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Registration of the 'TCP/BFCP' and 'TCP/TLS/BFCP' SDP 'proto'</span>
<span class="h3"> Values</span>
The IANA has registered the following two new values for the SDP
'proto' field under the Session Description Protocol (SDP) Parameters
registry:
+--------------+-----------+
| Value | Reference |
+--------------+-----------+
| TCP/BFCP | <a href="./rfc4583">RFC4583</a> |
| TCP/TLS/BFCP | <a href="./rfc4583">RFC4583</a> |
+--------------+-----------+
Table 2: Values for the SDP 'proto' field
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Registration of the SDP 'floorctrl' Attribute</span>
The IANA has registered 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.
<span class="grey">Camarillo Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
Allowed attribute values: 1*("c-only" / "s-only" / "c-s")
<span class="h3"><a class="selflink" id="section-11.3" href="#section-11.3">11.3</a>. Registration of the SDP 'confid' Attribute</span>
The IANA has registered the following SDP att-field under the Session
Description Protocol (SDP) Parameters registry:
Contact name: Gonzalo.Camarillo@ericsson.com
Attribute name: confid
Long-form attribute name: Conference Identifier
Type of attribute: Media level
Subject to charset: No
Purpose of attribute: The 'confid' attribute carries the integer
representation of a Conference ID.
Allowed attribute values: A token
<span class="h3"><a class="selflink" id="section-11.4" href="#section-11.4">11.4</a>. Registration of the SDP 'userid' Attribute</span>
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: userid
Long-form attribute name: User Identifier
Type of attribute: Media level
Subject to charset: No
Purpose of attribute: The 'userid' attribute carries the integer
representation of a User ID.
Allowed attribute values: A token
<span class="grey">Camarillo Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
<span class="h3"><a class="selflink" id="section-11.5" href="#section-11.5">11.5</a>. Registration of the SDP 'floorid' Attribute</span>
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: floorid
Long-form attribute name: Floor Identifier
Type of attribute: Media level
Subject to charset: No
Purpose of attribute: The 'floorid' attribute associates a floor
with one or more media streams.
Allowed attribute values: Tokens
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Acknowledgements</span>
Joerg Ott, Keith Drage, Alan Johnston, Eric Rescorla, Roni Even, and
Oscar Novo provided useful ideas for this document.
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Normative References</span>
[<a id="ref-1">1</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-2">2</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", <a href="./rfc4234">RFC 4234</a>, October 2005.
[<a id="ref-3">3</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, June 2002.
[<a id="ref-4">4</a>] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
Session Description Protocol (SDP)", <a href="./rfc3264">RFC 3264</a>, June 2002.
[<a id="ref-5">5</a>] Housley, R., Polk, W., Ford, W., and D. Solo, "Internet X.509
Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile", <a href="./rfc3280">RFC 3280</a>, April 2002.
[<a id="ref-6">6</a>] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions
(S/MIME) Version 3.1 Certificate Handling", <a href="./rfc3850">RFC 3850</a>, July
2004.
<span class="grey">Camarillo Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
[<a id="ref-7">7</a>] Yon, D. and G. Camarillo, "TCP-Based Media Transport in the
Session Description Protocol (SDP)", <a href="./rfc4145">RFC 4145</a>, September 2005.
[<a id="ref-8">8</a>] Camarillo, G., Ott, J., and K. Drage, "The Binary Floor Control
Protocol (BFCP)", <a href="./rfc4582">RFC 4582</a>, November 2006.
[<a id="ref-9">9</a>] Levin, O. and G. Camarillo, "The Session Description Protocol
(SDP) Label Attribute", <a href="./rfc4574">RFC 4574</a>, July 2006.
[<a id="ref-10">10</a>] Lennox, J., "Connection-Oriented Media Transport over the
Transport Layer Security (TLS) Protocol in the Session
Description Protocol (SDP)", <a href="./rfc4572">RFC 4572</a>, July 2006.
[<a id="ref-11">11</a>] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", <a href="./rfc4566">RFC 4566</a>, July 2006.
Author's Address
Gonzalo Camarillo
Ericsson
Hirsalantie 11
Jorvas 02420
Finland
EMail: Gonzalo.Camarillo@ericsson.com
<span class="grey">Camarillo Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc4583">RFC 4583</a> SDP Format for BFCP Streams November 2006</span>
Full Copyright Statement
Copyright (C) The IETF Trust (2006).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, 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
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Camarillo Standards Track [Page 12]
</pre>
|
