Guideline for dynamic payload type number usage policy
draft-wu-avtcore-dynamic-pt-usage-02

Document Type Expired Internet-Draft (individual)
Last updated 2014-04-24 (latest revision 2013-10-21)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-wu-avtcore-dynamic-pt-usage-02.txt

Abstract

The RTP Profile for Audio and Video Conferences with Minimal Control (RTP/AVP) is the basis for many other profiles, such as the Secure Real-time Transport Protocol (RTP/SAVP), the Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/ AVPF), and the Extended Secure RTP Profile for RTCP-Based Feedback (RTP/SAVPF). This document provides guidelines for payload type number usage policy when dynamic payload type allocation is used. Also this document updates closed IANA registry "RTP Payload types (PT) for standard audio and video encodings".

Authors

Qin Wu (sunseawq@huawei.com)
Roni Even (ron.even.tlv@gmail.com)
Rachel Huang (Rachel@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)