Re: RE : [AVT] draft-ietf-avt-rtcp-report-extns-02.txt

Magnus Westerlund <magnus.westerlund@era.ericsson.se> Mon, 24 February 2003 08:07 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04253 for <avt-archive@odin.ietf.org>; Mon, 24 Feb 2003 03:07:23 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1O8Fn005846 for avt-archive@odin.ietf.org; Mon, 24 Feb 2003 03:15:49 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1O8FBp05830; Mon, 24 Feb 2003 03:15:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1O8Cdp05756 for <avt@optimus.ietf.org>; Mon, 24 Feb 2003 03:12:39 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04238 for <avt@ietf.org>; Mon, 24 Feb 2003 03:03:41 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (esealnt613.al.sw.ericsson.se [153.88.254.72]) by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h1O87YAv014725; Mon, 24 Feb 2003 09:07:34 +0100 (MET)
Received: from era.ericsson.se (research-nnng7k.ki.sw.ericsson.se [147.214.34.46]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id FDVNDPQ4; Mon, 24 Feb 2003 09:07:34 +0100
Message-ID: <3E59D2C6.80708@era.ericsson.se>
Date: Mon, 24 Feb 2003 09:07:34 +0100
X-Sybari-Trust: 995a2910 9ffcebbb 7a95d2f4 00000138
From: Magnus Westerlund <magnus.westerlund@era.ericsson.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Timur Friedman <timur.friedman@lip6.fr>
CC: avt@ietf.org
Subject: Re: RE : [AVT] draft-ietf-avt-rtcp-report-extns-02.txt
References: <02ad01c2dad3$ec6127e0$a648e384@lip6.fr>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Timur,

Comments below.

Timur Friedman wrote:

>I wonder, though, if it would be alright if we were to submit this as a
>subsequent draft.  The concern is that introducing a significant change
>at this point would make it difficult to proceed to working group last
>call at San Francisco.
>  
>

I think that signaling is fundamental enough to this draft that it 
warrants to put it in directly. I would also not like to delay this 
draft. I would like to see it submitted to the IESG before May. I think 
that is still possible, especially if you would add this functionality 
in a update that you can submit before mondays cut-off date. You can 
take my text and rework it into suitable text for your draft. Then we 
can have a healthy discussion on this in San Francisco. Then after the 
meeting update the draft if any comments has been given. The have a WG 
last call in early April. There is no need to either ask or have WG last 
calls in relations to meetings. It might even be better as people will 
have more time to read the document.

In my opinion the author of a draft can very much effect the time that a 
draft takes to finish. You can shave of many weeks by simple being quick 
to reply and create updates when needed. Then ensuring that the WG 
chairs perform there work and makes last calls, send it to IESG, etc. 
also speeds things up.

>If not having signalling means we should not propose a standard then of
>course we should wait.  But to my mind the extended reports are useful
>in themselves, and a proposed standard will allow important work to go
>forward.
>  
>
Yes, they are useful in applications that are of more conversational 
type. In these you can detect that the other party implements and send 
them. Then you can also send them. However in applications like 
on-demand streaming where media only flows one way it is not possible in 
a sensible way to make the receiver application aware of the servers 
desire to receive XR reports. Sending empty XR packets just to indicate 
support for XR formats seems wasteful of bandwidth.

Best Regards

Magnus Westerlund 

Multimedia Technologies, Ericsson Research ERA/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@era.ericsson.se



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt