errata logo graphic

Found 2 records.

Status: Held for Document Update (1)

RFC4583, "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams", November 2006

Source of RFC: mmusic (rai)

Errata ID: 712

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2006-12-30
Held for Document Update by: Robert Sparks

 

(1)  [clarification]

Section 4 of RFC 4583, near the top of page 4, says:

   If an 'm' line in an offer contains a 'floorctrl' attribute, the
   answerer MUST include one in the corresponding 'm' line in the
   answer.  [...]

It should better say:

   If a SDP media description in an offer contains a 'floorctrl'
   attribute, the answerer accepting that media MUST include one in the
   corresponding media description of the answer.  [...]


(2)  [clarification]

Section 6 of RFC 4583, on mid-page 5, says:

   The 'floorid' attribute is used in BFCP 'm' lines.  [...]

It should better say:

   The 'floorid' attribute is used in the SDP media description for BFCP
   media.  [...]


Please comment.

It should say:

[not submitted]

Notes:

It's always the abuse of language, talking about an SDP attribute
as being used "in" an SDP 'm' line, where in fact the attribute is
just a media-level attribute, occurring as a standalone line in an
SDP media description, i.e. the SDP part introduced by the particular
'm' line.

This is, at best, a bit confusing.

from pending


Status: Rejected (1)

RFC4583, "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams", November 2006

Source of RFC: mmusic (rai)

Errata ID: 4111

Status: Rejected
Type: Editorial

Reported By: Christian Groves
Date Reported: 2014-09-14
Rejected by: Richard Barnes
Date Rejected: 2014-09-21

Section 9 says:

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

...

It should say:

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 mstrm:10
   a=floorid:2 mstrm:11
   m=audio 50002 RTP/AVP 0
   a=label:10
   m=video 50004 RTP/AVP 31
   a=label:11

...

Notes:

In section 6 of the RFC the ABNF for the "floorid" attribute is:
floor-id-attribute = "a=floorid:" token [" mstrm:" token *(SP token)]

The text string " mstrm:" is used to reference the media stream rather than "m-stream" that appears in the examples.
--VERIFIER NOTES--
The error noted in the erratum is already being addressed in a document that will obsolete this RFC.


Report New Errata