RE: [MMUSIC] Questions/Comments on draft-ietf-mmusic-sdp-bwparam-03.txt

emre.aksu@nokia.com Thu, 12 June 2003 11:14 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 HAA03301 for <mmusic-archive@odin.ietf.org>; Thu, 12 Jun 2003 07:14:41 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CBEE710198 for mmusic-archive@odin.ietf.org; Thu, 12 Jun 2003 07:14:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CBEEm10195 for <mmusic-web-archive@optimus.ietf.org>; Thu, 12 Jun 2003 07:14:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03293 for <mmusic-web-archive@ietf.org>; Thu, 12 Jun 2003 07:14:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QPzy-0000hh-00 for mmusic-web-archive@ietf.org; Thu, 12 Jun 2003 07:12:06 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QPzy-0000he-00 for mmusic-web-archive@ietf.org; Thu, 12 Jun 2003 07:12:06 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CBE7m10185; Thu, 12 Jun 2003 07:14:07 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CBDYm10167 for <mmusic@optimus.ietf.org>; Thu, 12 Jun 2003 07:13:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03282 for <mmusic@ietf.org>; Thu, 12 Jun 2003 07:13:31 -0400 (EDT)
From: emre.aksu@nokia.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QPzK-0000hR-00 for mmusic@ietf.org; Thu, 12 Jun 2003 07:11:26 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 19QPzJ-0000hO-00 for mmusic@ietf.org; Thu, 12 Jun 2003 07:11:26 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h5CBDV906428 for <mmusic@ietf.org>; Thu, 12 Jun 2003 14:13:31 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T62c8c5f465ac158f23078@esvir03nok.nokia.com>; Thu, 12 Jun 2003 14:13:31 +0300
Received: from esebe015.NOE.Nokia.com ([172.21.138.54]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Thu, 12 Jun 2003 14:13:30 +0300
Received: from trebe006.NOE.Nokia.com ([172.22.232.181]) by esebe015.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Thu, 12 Jun 2003 14:12:45 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [MMUSIC] Questions/Comments on draft-ietf-mmusic-sdp-bwparam-03.txt
Date: Thu, 12 Jun 2003 14:12:44 +0300
Message-ID: <B519AC26B144EF479CFB036F7B84E7C8013C4F02@trebe006.europe.nokia.com>
Thread-Topic: [MMUSIC] Questions/Comments on draft-ietf-mmusic-sdp-bwparam-03.txt
Thread-Index: AcMwzSeFuXK//wydR2W7QRkPoBKXswAA2mLQ
To: magnus.westerlund@ericsson.com, mmusic@ietf.org
X-OriginalArrivalTime: 12 Jun 2003 11:12:45.0590 (UTC) FILETIME=[8CDAFB60:01C330D3]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5CBDYm10168
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi Magnus,

> The session level value is bit redundant. It is simply the sum of all 
> media streams and reflect the total amount of bandwidth needed to 
> accommodate this session. This can of course be calculated by 
> a receiver.
> 

Also, in the <draft-ietf-mmusic-sdp-bwparam-03.txt>, in section 6.2.3, Usage rules section, it is stated that:
"...The session level value, if present, MUST be the sum of all media level values.".

I believe this is a true statement for constant bitrate streams. But what about VBR cases? At least for RTP usage, the definition of bandwidth is for max bandwidth consumption over a 1 second sliding window, right? Hence, max bandwidth consumption at session level may be smaller or equal to the sum of these max bandwidths at media levels. And if the client is making resource reservation for QoS purposes, then there may possibly be a redundant amount of bandwidth allocation if the session level bandwidth is simply the absolute sum. Therefore, I believe that the session level TIAS bandwidth value MAY be smaller than the sum of the media level TIAS values. 

I guess for unicast case, a possible way to see the session level bandwidth consumption is during the hinting process of the data at the server side.

Regards,
Emre

Emre Baris Aksu
Nokia Mobile Phones



> -----Original Message-----
> From: ext Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: 12 June, 2003 13:22
> To: Geetha Srikantan
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] Questions/Comments on
> draft-ietf-mmusic-sdp-bwparam-03.txt
> 
> 
> Hi,
> 
> Thanks for the comments.
> 
> Geetha Srikantan wrote:
> > I have a few questions and comments on 
> draft-ietf-mmusic-sdp-bwparam-03.txt:
> > 
> > 1. Page 9, the last few lines - What is the difference 
> between 'RTP-based media  
> >    stream' and 'RTP transport' here? It's not very clear 
> when the session level  
> >    TIAS value can be used.
> 
> There is no difference, I can change the RTP-based media 
> stream to "RTP 
> transported media stream".
> 
> The session level value is bit redundant. It is simply the sum of all 
> media streams and reflect the total amount of bandwidth needed to 
> accommodate this session. This can of course be calculated by 
> a receiver.
> 
> > 
> > 2. Section 6.2.3, 2nd paragraph - it would be good to 
> clarify that this entire 
> >    paragraph refers to the media level values.
> >    This paragraph is a little confusing to read..it might 
> help to mention
> >    explicitly that it is RECOMMENDED to use both the AS and 
> TIAS fields;
> >    AS for backwards compatibility, older implementations 
> would ignore the TIAS 
> >    field; TIAS would be recognized by newer and compliant 
> implementations,
> >    which must ignore the AS value.
> 
> No, It does not only apply for the media level, but both 
> levels. AS can 
> be present at both levels, if one includes it at either level one is 
> recommended to include TIAS also.
> 
> I don't quite understand what you mean with confusing to read. The 
> information you ask for is there: "..., it is RECOMMENDED to also 
> include the "AS" modifier when using "TIAS"". Do you have a more 
> concrete proposal on how reformulate the paragraph?
> 
> >    
> > 3. 6.3, 2nd paragraph - here too it might help clarity to 
> assert the 'MUST NOT' 
> >    case , before the 'MAY' case.
> 
> So you would like to be reformulated into something like this:
> 
> "At the SDP session level, the maxprate value MUST be the sum of all 
> media-level packet rates. The "maxprate" attribute MUST NOT 
> be present 
> at session level if the media streams use different transport. The 
> attribute MAY be present if the media streams use the same 
> transport. If 
>   the attribute is present at the session level it SHOULD also be 
> present at the media level for all media streams."
> 
> Is that better? If not please provide concrete proposals of 
> the paragraph.
> 
> 
> >    
> > 4. 6.3, is there any ambiguity in the last paragraph? For 
> instance, is it ok to
> >    *not* have maxprate if one or the other of TIAS or the 
> max packet rate 
> >    for the transport is not available?
> 
> Yes, if one can't derive a packet rate due to for example non packet 
> based transport then its ok. However if you use TIAS and have a 
> transport like IP/UDP/RTP you shall have it. Perhaps I should 
> reformulate the sentence to be more strict and explanatory.
> 
> >    
> > 5. It would be great to have a complete example of SDP 
> using TIAS and maxprate
> >    attributes.   
> >    
> 
> Yes, you are correct. I will look into it.
> 
> 
> 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@ericsson.com
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic