15.3. RTP profile and payload format specifications
When conventional protocols are designed, they are generalized to accommodate the additional functionality of their applications. For RTP, this is achieved through modifications and additions to the existing headers as needed by an application. Therefore, RTP for a particular application, like audio, requires one or more companion documents: namely, a profile specification document and a payload format specification document.
15.3.1. Profile specification
In [RFC3550] the following fields have been identified as possible items to be defined by an application profile specification: RTP data header, payload types (codecs), RTP data header additions, RTP data header extensions, RTCP application-specific packet types, RTCP report interval (see Section 15.2.2), SR/RR extensions, SDES use, security services and algorithm, string (password) to encryption key mapping, congestion control behaviour, underlying protocol, RTP and RTCP mapping to transport-level addresses and encapsulation of multiple RTP packets in a lower layer packet.
15.3.2. Payload format specification
A payload format specification for an RTP application defines how a particular payload is carried in RTP.
Get The IMS: IP Multimedia Concepts And Services, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
