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

Qin Wu <bill.wu@huawei.com> Mon, 09 September 2013 03:22 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 062A111E816E for <avt@ietfa.amsl.com>; Sun, 8 Sep 2013 20:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.532
X-Spam-Level:
X-Spam-Status: No, score=-6.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mz+FCuMt5TYt for <avt@ietfa.amsl.com>; Sun, 8 Sep 2013 20:22:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 755D711E8171 for <avt@ietf.org>; Sun, 8 Sep 2013 20:22:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AXC05648; Mon, 09 Sep 2013 03:22:09 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 9 Sep 2013 04:21:17 +0100
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 9 Sep 2013 04:21:20 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.141]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0146.000; Mon, 9 Sep 2013 11:21:12 +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-01.txt
Thread-Index: AQHOrP36Y17XfzdixUKk9tRd8K9NcJm8uiQw
Date: Mon, 9 Sep 2013 03:21:12 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43BEB795@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.149]
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-01.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: Mon, 09 Sep 2013 03:22:16 -0000

Here is the update of draft-wu-avtcore-dynamic-pt-usage-01 based on comments received on the list so far.
Changes include:
1. Remove section 3 for update to RFC3551.
2. Clarification for the purpose of this document in the abstract and introduction section.
3. Update "Use of Dynamic payload type" section and add a table to clarify what is updated in the registry.
The diff is:
http://www.ietf.org/rfcdiff?url2=draft-wu-avtcore-dynamic-pt-usage-01

Regards!
-Qin
-----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, September 09, 2013 9:43 AM
To: i-d-announce@ietf.org
Subject: I-D Action: draft-wu-avtcore-dynamic-pt-usage-01.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-01.txt
	Pages           : 13
	Date            : 2013-09-08

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


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-wu-avtcore-dynamic-pt-usage

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-wu-avtcore-dynamic-pt-usage-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-wu-avtcore-dynamic-pt-usage-01


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:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt