Re: [MMUSIC] Offer/Answer PT Questions - text proposal

[Christer Holmberg <[e-mail]>]

Hi,

I put together some text:

"The scope of a mapping from a particular dynamic payload type number to a codec 
(or codec configuration) is for a given RTP media flow direction within a session. 
The same dynamic payload type number can be mapped to another codec in another RTP 
media flow direction within the same session. The mapping MUST NOT change to a different
coded (or coded configuration) for the duration of a session. Eventhough not recommended, 
for a given direction, multiple dynamic payload type numbers can be mapped to the 
same codec (or codec configuration). 

Note that a mapping has been created once an endpoint
has sent and offer or answer, describing the mapping for a given direction. Even if the
offer or answer is rejected or discarded, or if RTP media associated with the mapping is never
sent, the mapping MUST NOT change for the given direction within the session.

Within an offer or answer, the mapping is for the RTP media flow direction towards the offerer/answerer,
unless the media flow is indicated as 'sendonly' in which case the mapping is for the media flow direction
from the offerer/answerer."

Note that the text probably needs some fine tuning, but please take a look and see whether you are ok with the approach, and whether you think the text covers the issues we've discovered.

Regards,

Christer