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

Colin Perkins <csp@csperkins.org> Tue, 03 September 2013 16:20 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 1608B21E8186 for <avt@ietfa.amsl.com>; Tue, 3 Sep 2013 09:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level:
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 BK-6atx6gcj9 for <avt@ietfa.amsl.com>; Tue, 3 Sep 2013 09:20:00 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [93.93.131.52]) by ietfa.amsl.com (Postfix) with ESMTP id 5CEC121F9C78 for <avt@ietf.org>; Tue, 3 Sep 2013 09:20:00 -0700 (PDT)
Received: from [130.209.247.112] (port=56332 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 1VGtKe-0002uC-Nb; Tue, 03 Sep 2013 17:19:57 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_3135E86A-5D69-4448-B3DF-91F8BAC00FAA"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <015a01cea7d3$62c3cbe0$284b63a0$@gmail.com>
Date: Tue, 3 Sep 2013 17:19:59 +0100
Message-Id: <5C7CBAD2-4340-4A7B-8D55-8E56AB2DE07E@csperkins.org>
References: <20130830162909.20422.68365.idtracker@ietfa.amsl.com> <008201cea59e$aa9fd3a0$ffdf7ae0$@gmail.com> <5EAB5396-57ED-4B29-9FEF-0CAF92F27052@csperkins.org> <015a01cea7d3$62c3cbe0$284b63a0$@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
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: Tue, 03 Sep 2013 16:20:05 -0000

Hi Roni,

On 2 Sep 2013, at 12:55, Roni Even <ron.even.tlv@gmail.com> wrote:
> Hi Colin,
> The major motivation is to update the closed IANA registry
> http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-1 that points to RFC 3551 and does not have the right allocations by referring to this document , I have the wrong pointer in the draft. This is based on the email thread started with the attached email.

I would have thought that could be resolved with an email to IANA, rather than a new draft, since all you're doing is updating the registry to match the published RFCs.

> The other reason is to clarify which payload types from the range 0-95 can be used for dynamic mapping and in what order. This is based on the MMUSIC session in Berlin and the open issue in section 3.2.1.2 of
> http://tools.ietf.org/id/draft-roach-mmusic-unified-plan-00.txt 

But, the draft just seems to repeat the guidelines in RFC 5761 and 3551. The only difference seems to be to give an explicit order in which the unassigned payload type numbers are to be used, which seems unnecessary.

Colin



> Roni
> 
>> -----Original Message-----
>> From: Colin Perkins [mailto:csp@csperkins.org]
>> Sent: 02 September, 2013 1:07 PM
>> To: Roni Even
>> Cc: avt@ietf.org WG
>> Subject: Re: [AVTCORE] New Version Notification for draft-wu-avtcore-
>> dynamic-pt-usage-00.txt
>> 
>> 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/
>> 
> 
> <Mail Attachment.eml>



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