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

[Qin Wu <[e-mail]>]

Hi, Magnus:
I agree with your comments below and will remove section 3.

Regards!
-Qin
-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Magnus Westerlund
Sent: Tuesday, September 03, 2013 8:49 PM
To: Roni Even
Cc: 'Colin Perkins'; [e-mail]
Subject: Re: [AVTCORE] New Version Notification for draft-wu-avtcore-dynamic-pt-usage-00.txt

Hi,

I have also looked at this. I think the introduction needs to be much
clearer on what this document's purpose is. To my understanding it is
two fold:
1. Clarify to implementors that yes you can use the payload types in the
lower range for dynamic, including the overriding the static ones.
2. Update the closed IANA registry to actually combine the different set
of changes and make the current state clear.

Based on that I don't see a need to update RFC 3551 in the way section 3
does it.

Maybe I have misunderstood the drivers behind it, but the above is what
I have gotten from the public list discussions I have read.

Cheers

Magnus

On 2013-09-02 13:55, Roni Even wrote:
> Hi Colin,
> The major motivation is to update the closed IANA registry
> http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-para
> meters-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.
> 
> 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 
> 
> Roni
> 
>> -----Original Message-----
>> From: Colin Perkins [mailto:[e-mail]]
>> Sent: 02 September, 2013 1:07 PM
>> To: Roni Even
>> Cc: [e-mail] 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 <[e-mail]> 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: [e-mail] [mailto:[e-mail]]
>>> 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 [e-mail]
>>> https://www.ietf.org/mailman/listinfo/avt
>>
>>
>>
>> --
>> Colin Perkins
>> http://csperkins.org/
>>
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> [e-mail]
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  [phone]
Färögatan 6                | Mobile [phone]
SE-164 80 Stockholm, Sweden| mailto: [e-mail]
----------------------------------------------------------------------

_______________________________________________
Audio/Video Transport Core Maintenance
[e-mail]
https://www.ietf.org/mailman/listinfo/avt