Connected: An Internet Encyclopedia
6.3.3 Extending the sender and receiver reports
Up:
Connected: An Internet Encyclopedia
Up:
Requests For Comments
Up:
RFC 1889
Up:
6. RTP Control Protocol -- RTCP
Up:
6.3 Sender and Receiver Reports
Prev: 6.3.2 RR: Receiver report RTCP packet
Next: 6.3.4 Analyzing sender and receiver reports
6.3.3 Extending the sender and receiver reports
6.3.3 Extending the sender and receiver reports
A profile should define profile- or application-specific extensions
to the sender report and receiver if there is additional information
that should be reported regularly about the sender or receivers. This
method should be used in preference to defining another RTCP packet
type because it requires less overhead:
- fewer octets in the packet (no RTCP header or SSRC field);
- simpler and faster parsing because applications running under
that profile would be programmed to always expect the extension
fields in the directly accessible location after the reception
reports.
If additional sender information is required, it should be included
first in the extension for sender reports, but would not be present
in receiver reports. If information about receivers is to be
included, that data may be structured as an array of blocks parallel
to the existing array of reception report blocks; that is, the number
of blocks would be indicated by the RC field.
Next: 6.3.4 Analyzing sender and receiver reports
Connected: An Internet Encyclopedia
6.3.3 Extending the sender and receiver reports