RFC 5117, "RTP Topologies", January 2008

Note: This RFC has been obsoleted by RFC 7667

Errata ID: 1314
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-02-13
Held for Document Update by: Cullen Jennings

Section 3.4, pg.9 says:

         [...].  The CSRC Count (CC) and CSRC fields in the RTP header
|  are used to indicate the contributors of to the newly generated
   stream.  The SSRCs of the to-be-mixed streams on the Mixer input
   appear as the CSRCs at the Mixer output.  That output stream uses a
|  unique SSRC that identifies the Mixer's stream.  The CSRC are
   forwarded between the two domains to allow for loop detection and
   identification of sources that are part of the global session.  [...]

It should say:

         [...].  The CSRC Count (CC) and CSRC fields in the RTP header
|  are used to indicate the contributors to the newly generated
   stream.  The SSRCs of the to-be-mixed streams on the Mixer input
   appear as the CSRCs at the Mixer output.  That output stream uses a
|  unique SSRC that identifies the Mixer's stream.  The CSRCs are
   forwarded between the two domains to allow for loop detection and
   identification of sources that are part of the global session.  [...]

Notes:

Near the bottom of page 9:
a) s/of to/to/
^^^
b) s/The CSRC are/The CSRCs are/
^

Report New Errata