RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 4 records.

Status: Reported (1)

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

Source of RFC: xcon (rai)

Errata ID: 4120

Status: Reported
Type: Editorial

Reported By: Christian Groves
Date Reported: 2014-09-21

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.

Status: Held for Document Update (3)

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

Source of RFC: xcon (rai)

Errata ID: 1450

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2008-06-15
Held for Document Update by: Robert Sparks

Section 8.4, pg.27 says:

The 5th and the 6th paragraph on pg.27 both contain the clause:

   ...
   When using SDP offer/answer exchange to negotiate ...

It should say:

Both instances should say
either:

   ...
   When using SDP offer/answer exchanges to negotiate ...
                                       ^
or (less preferable):

   ...
   When using SDP an offer/answer exchange to negotiate ...
                  ^^^

Notes:

Grammar

Errata ID: 1451

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2008-06-15
Held for Document Update by: Robert Sparks

Section 9.3,1st para says:

                                           [...].  This kind of
|  operation is called "1st party signaling" and they do not affect the
   state of other participants in the conference.

It should say:

                                           [...].  This kind of
|  operation is called "1st party signaling" and it does not affect the
   state of other participants in the conference.
                                                 ^^^^^^^

Notes:

Grammar: "they do" does not match "This kind of operation".

Errata ID: 1452

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2008-06-15
Held for Document Update by: Robert Sparks

Section 9.6,2nd para says:

   Figure 15 provides an example of one user "Alice" who's chairing a
   fixed length conference with "Bob" and "Carol".  The configuration is
|  such that only the chair is providing a warning when there are only
                                     ^^^
   10 minutes left in the conference.  At that time, "Alice" is moved
   into a sidebar created by the conferencing system and only "Alice"
   receives the announcement.

It should say:

   Figure 15 provides an example of one user "Alice" who's chairing a
   fixed length conference with "Bob" and "Carol".  The configuration is
|  such that only the chair is provided a warning when there are only
                                     ^^
   10 minutes left in the conference.  At that time, "Alice" is moved
   into a sidebar created by the conferencing system and only "Alice"
   receives the announcement.

Notes:

Typo distorting the proper sense of the text.
See also Figure 15 -- the warning is sent *to* "Alice".

Report New Errata



Search RFCs
Advanced Search
×