Re: [AVTCORE] IANAs payload type number registry and RFC 5761

[Magnus Westerlund <[e-mail]>]

WG,

This is what I intended to send to IANA. If you have feedback on this,
please send it ASAP.


AVTCORE WG requests that IANA adds the below note to the registry:

RTP Payload types (PT) for standard audio and video encodings
http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-1

The current note reads:

Note

    The RFC "RTP Profile for Audio and Video Conferences with Minimal
    Control" [RFC3551] specifies an initial set "payload types".  This
    list maintains and extends that list.

The WG requests that this is change to:

Note

    The RFC "RTP Profile for Audio and Video Conferences with Minimal
    Control" [RFC3551] specifies an initial set "payload types".  This
    list maintains and extends that list.

    The registry is closed, see RFC 3551.  No additional registrations
    will be done. The payload types that have a static mapping are the
    below ones (0-34).

    The "Reserved for RTCP conflict avoidance" in this table is not up
    to date. [RTCP Control Packet types (PT)] below lists the RTCP
    types that has actually been registered. Subtract 128 from the
    RTCP Packet Type value to find the corresponding PT value with
    collision risk. For further information see RFC 5761.

    If you seek guidance on which PT values to use for assigning
    dynamic payload types, then that is present in RFC 3551 (Section 3)
    and RFC 5761 (Section 4).


Note, if possible I would request that "[RTCP Control Packet types
(PT)]" is made into ling with the following URL:

http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-4