[AVTCORE] FW: I-D Action: draft-wu-avtcore-dynamic-pt-usage-02.txt

Qin Wu <bill.wu@huawei.com> Fri, 25 October 2013 04:00 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6CD9A11E821E for <avt@ietfa.amsl.com>; Thu, 24 Oct 2013 21:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.144
X-Spam-Status: No, score=-6.144 tagged_above=-999 required=5 tests=[AWL=-0.145, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ZeVRQaTp2SfH for <avt@ietfa.amsl.com>; Thu, 24 Oct 2013 21:00:17 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) by ietfa.amsl.com (Postfix) with ESMTP id ABFCF11E81EA for <avt@ietf.org>; Thu, 24 Oct 2013 21:00:16 -0700 (PDT)
Received: from (EHLO lhreml204-edg.china.huawei.com) ([]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZL23759; Fri, 25 Oct 2013 04:00:14 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com ( by lhreml204-edg.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Fri, 25 Oct 2013 05:00:06 +0100
Received: from NKGEML406-HUB.china.huawei.com ( by lhreml404-hub.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Fri, 25 Oct 2013 05:00:11 +0100
Received: from NKGEML501-MBS.china.huawei.com ([]) by nkgeml406-hub.china.huawei.com ([]) with mapi id 14.03.0146.000; Fri, 25 Oct 2013 12:00:02 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "avt@ietf.org" <avt@ietf.org>
Thread-Topic: I-D Action: draft-wu-avtcore-dynamic-pt-usage-02.txt
Thread-Index: AQHOzkNpG0zmgLYpiEO8yjE9N/VRfpoEzrvw
Date: Fri, 25 Oct 2013 04:00:01 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C0F489@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [AVTCORE] FW: I-D Action: draft-wu-avtcore-dynamic-pt-usage-02.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 04:00:21 -0000

We have made a minor update to draft-wu-avtcore-dyanmic-pt-usage
Based on comments we received so far.
The diff is:

The reasons to have such document are two:
a. We need a document to clarify how to update IANA registry for Dynamic payload type number allocation to reflect RFC5761.

b. We need a document to provide additional guidelines for Dynamic payload type usage as follows:

(1) New payload formats(e.g.,H.264,VP8) MUST use dynamic payload type number assignment. 
Each new payload format MUST be named as "encoding name" by a registered media subtype defined in the "RTP Payload Format media types" registry. 
The "encoding name" in the RTP payload type registry is also registered as a media subtype under the media type "audio" or "video" in the "RTP Payload Format media types" registry.

(2) Provide order for dynamic payload type number allocation
I. first use values in the range [96-127]for dynamic payload types
II. Then use codes below 96
O Unassigned payload type numbers [35-63] 
O Followed by [20-24], 27,[29-30].
O Use the reserved values 1,2,19 (see [RFC3551]for reserved values)
O And 64, 65 (see [RFC5761]for reserved value)if H.261 FIR or H.261 NACK is not used in the WebRTC context
  Warning:  potentially cause collisions with legacy use
O Override the static types[0, 3-18,25,26,28,31-34] and map encodings to these defined static payload type
   Warning: cause problems for applications that ignore the mapping in the signaling and assume a specific payload format
         based on the Payload Type

(3) In the case when multiplexing RTP and RTCP are not used, the range [66-95] is used
Caution: better to use the pt numbers that are not conflicting with the currently assigned RTCP values

Let us know if you think these reasons make sense.

-----Original Message-----
From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Monday, October 21, 2013 5:53 PM
To: i-d-announce@ietf.org
Subject: I-D Action: draft-wu-avtcore-dynamic-pt-usage-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Guideline for dynamic payload type number usage policy
	Author(s)       : Qin Wu
                          Roni Even
                          Rachel Huang
	Filename        : draft-wu-avtcore-dynamic-pt-usage-02.txt
	Pages           : 8
	Date            : 2013-10-21

   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".

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:

I-D-Announce mailing list
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt