RFC 5239, "A Framework for Centralized Conferencing", June 2008

Errata ID: 4120
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Christian Groves
Date Reported: 2014-09-21
Verifier Name: Orie Steele
Date Verified: 2024-04-01

Section 8.4 says:

   ...
   A media session within a conferencing system can have any number of
   floors (0 or more) that are represented by the conference identifier.
   When using SDP offer/answer exchange to negotiate a floor control
   connection with the focus using the call signaling interface, the
   unique conference identifier is contained in the 'floorid' SDP
   attribute, as defined in [RFC4583], e.g., a=floorid:1 m-stream:10 .
   Each 'floorid' attribute, representing a unique floor, has an
   'm-stream' tag containing one or more identifiers.  The identifiers
   represent individual SDP media sessions (as defined using 'm=' from
   SDP) using the SDP 'Label' attribute, as defined in [RFC4574].

It should say:

   ...   
   A media session within a conferencing system can have any number of
   floors (0 or more) that are represented by the conference identifier.
   When using SDP offer/answer exchange to negotiate a floor control
   connection with the focus using the call signaling interface, the
   unique conference identifier is contained in the 'floorid' SDP
   attribute, as defined in [RFC4583], e.g., a=floorid:1 mstrm:10 .
   Each 'floorid' attribute, representing a unique floor, has an
   'mstrm' tag containing one or more identifiers.  The identifiers
   represent individual SDP media sessions (as defined using 'm=' from
   SDP) using the SDP 'Label' attribute, as defined in [RFC4574].

Notes:

In section 6 of the RFC4583 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 this section.

Report New Errata