Re: [AVTCORE] New Version Notification for draft-wu-avtcore-dynamic-pt-usage-00.txt

Colin Perkins <csp@csperkins.org> Mon, 02 September 2013 10:07 UTC

Return-Path: <csp@csperkins.org>
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 0468F11E81D1 for <avt@ietfa.amsl.com>; Mon, 2 Sep 2013 03:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 5zdFB3Zx+28V for <avt@ietfa.amsl.com>; Mon, 2 Sep 2013 03:07:16 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [93.93.131.52]) by ietfa.amsl.com (Postfix) with ESMTP id ABDAA11E81D9 for <avt@ietf.org>; Mon, 2 Sep 2013 03:07:14 -0700 (PDT)
Received: from [130.209.247.112] (port=53140 helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1VGR2I-0003Oy-Sc; Mon, 02 Sep 2013 11:07:07 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <008201cea59e$aa9fd3a0$ffdf7ae0$@gmail.com>
Date: Mon, 2 Sep 2013 11:07:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EAB5396-57ED-4B29-9FEF-0CAF92F27052@csperkins.org>
References: <20130830162909.20422.68365.idtracker@ietfa.amsl.com> <008201cea59e$aa9fd3a0$ffdf7ae0$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Cc: "avt@ietf.org WG" <avt@ietf.org>
Subject: Re: [AVTCORE] New Version Notification for draft-wu-avtcore-dynamic-pt-usage-00.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, 02 Sep 2013 10:07:24 -0000

Roni,

Can you explain what's new in this draft? As far as I can tell, it just repeats the guidance in RFCs 3551 and 5761.

Colin



On 30 Aug 2013, at 17:33, Roni Even <ron.even.tlv@gmail.com> wrote:
> Hi,
> Apologize for the cross posting. Please comment only in avtcore mailing list
> 
> We have submitted a draft that clarifies the usage of dynamic payload type numbers.
> This is based on email discussion in MMUSIC 
> Thanks
> Roni Even
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
> Sent: 30 August, 2013 7:29 PM
> To: Qin Wu; Wenson Wu; Rachel Huang; Roni Even; Rachel Huang
> Subject: New Version Notification for draft-wu-avtcore-dynamic-pt-usage-00.txt
> 
> 
> A new version of I-D, draft-wu-avtcore-dynamic-pt-usage-00.txt
> has been successfully submitted by Qin Wu and posted to the IETF repository.
> 
> Filename:	 draft-wu-avtcore-dynamic-pt-usage
> Revision:	 00
> Title:		 Guideline for dynamic payload type number usage policy
> Creation date:	 2013-08-30
> Group:		 Individual Submission
> Number of pages: 5
> URL:             http://www.ietf.org/internet-drafts/draft-wu-avtcore-dynamic-pt-usage-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-wu-avtcore-dynamic-pt-usage
> Htmlized:        http://tools.ietf.org/html/draft-wu-avtcore-dynamic-pt-usage-00
> 
> 
> 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 updates RFC 3551 and provide guidelines
>   for payload type number usage policy.
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



-- 
Colin Perkins
http://csperkins.org/