Re: [MMUSIC] MMT bandwidth limits (Re: comments on draft-holmberg-mmusic-sdp-mmt-negotiation-00)

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 05 November 2012 23:58 UTC

Return-Path: <eckelcu@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B75FD21F845E for <mmusic@ietfa.amsl.com>; Mon, 5 Nov 2012 15:58:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level:
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=-3.367, BAYES_00=-2.599, GB_SUMOF=5, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_19=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lwylsaam7-58 for <mmusic@ietfa.amsl.com>; Mon, 5 Nov 2012 15:58:32 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id D9F3311E80A3 for <mmusic@ietf.org>; Mon, 5 Nov 2012 15:58:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3497; q=dns/txt; s=iport; t=1352159912; x=1353369512; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ThjsHL4w5CWOPZKewdpph2yw7TYwsfy9/1/GboMjSr4=; b=E6jXW1oIum/EwvHTggCy6cOW6h4JifBa2/b5eRBoxwoYEIVUM53LMvo3 7sb1nWs6TpeI1qKeBtlUr63cL0rosTdJI5k2YiCOipuVPcQ4aqF1kK3bM B5ooiXfMz3S1lhHEVKLLpkyUMRV+YlqvAyml8chni3p+WmN/oTZ0YcXkQ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHFRmFCtJV2b/2dsb2JhbABEwzKBCIIeAQEBAwEBAQEPASc0EAcEAgEIEQQBAQEKFAkHJwsUCQgCBAESCBqHYgYLmwKgEgSLfIN7gXlhA6RUgWuCYg2CGQ
X-IronPort-AV: E=Sophos;i="4.80,718,1344211200"; d="scan'208";a="139125360"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-3.cisco.com with ESMTP; 05 Nov 2012 23:58:31 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id qA5NwV8u024170 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 Nov 2012 23:58:31 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.25]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.001; Mon, 5 Nov 2012 17:58:30 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Harald Alvestrand <harald@alvestrand.no>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] MMT bandwidth limits (Re: comments on draft-holmberg-mmusic-sdp-mmt-negotiation-00)
Thread-Index: AQHNu5vn4unUpqCYCEaU5rC485NR+5fb6a2Q
Date: Mon, 05 Nov 2012 23:58:29 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828108043@xmb-aln-x08.cisco.com>
References: <92B7E61ADAC1BB4F941F943788C088281074BD@xmb-aln-x08.cisco.com> <7594FB04B1934943A5C02806D1A2204B024E1B@ESESSMB209.ericsson.se> <92B7E61ADAC1BB4F941F943788C0882810758B@xmb-aln-x08.cisco.com> <50982E6B.1010904@alvestrand.no>
In-Reply-To: <50982E6B.1010904@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.65.191]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19340.004
x-tm-as-result: No--60.435100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [MMUSIC] MMT bandwidth limits (Re: comments on draft-holmberg-mmusic-sdp-mmt-negotiation-00)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 23:58:32 -0000

> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On
> Behalf Of Harald Alvestrand
> Sent: Monday, November 05, 2012 4:24 PM
> To: mmusic@ietf.org
> Subject: [MMUSIC] MMT bandwidth limits (Re: comments on draft-
> holmberg-mmusic-sdp-mmt-negotiation-00)
> 
> On 11/05/2012 04:29 AM, Charles Eckel (eckelcu) wrote:
> > In the case of multiple m-lines, you can assign a bandwidth per m-line and
> have the session bandwidth cap the total bandwidth for the session. With
> anymedia and a single m-line, you lose the granularity you previously had at
> the m-line level and are left with specifying the bandwidth for the
> anymedia line as a whole.
> > For example, today I might offer the following for a video call with content
> sharing:
> >
> > v=0
> > o=anonymous 1240218157 1240218157 IN IP4 10.193.128.35
> > s=-
> > i=myUserAgent
> > c=IN IP4 10.193.128.35
> > b=TIAS:512000
> > t=0 0
> > m=audio 6000 RTP/AVP 0 18 101
> > a=rtpmap:0 PCMU/8000
> > a=rtpmap:18 G729/8000
> > a=rtpmap:101 telephone-event/8000
> > a=fmtp:101 0-15
> > m=video 6002 RTP/AVP 96
> > b=TIAS:512000
> > a=rtpmap:96 H264/90000
> > a=fmtp:96 profile-level-id=428014
> > a=content:main
> > m=video 6002 RTP/AVP 96
> > b=TIAS:256000
> > a=rtpmap:96 H264/90000
> > a=fmtp:96 profile-level-id=428014
> > a=content:slides
> >
> > In this case, depending on the answer, the audio will take between 8k and
> 64k, the main video can take the remainder of the 512k until content sharing
> starts, and once content sharing starts, the main video could drop down a bit
> to free some bandwidth for the content .
> > With mmt, all I can specify is 512k for the total. I cannot subdivide it per
> media stream as above. To do so, I would need to specify some new SDP
> and/or encode the SSRC values I plan to use in SDP.
> I'm curious - if I send this in an offer, is there any part of the SDP
> description that says that the respondent, when sending, should cut down
> on his video bandwidth if video + audio would otherwise be > 512K?
> 
> I don't see any "priority" flags in there.

There is no explicit priority. It is up to the application to decide. RFC 3890 does say:

   At the SDP session level, the TIAS value is the maximal amount of
   bandwidth needed when all declared media streams are used.  This MAY
   be less than the sum of all the individual media streams values.
   This is due to the possibility that not all streams have their
   maximum at the same point in time. 

> (another thing that confuses me a bit is how b= represents bandwidth in
> the 2 directions for a point-to-point session - if A sends an offer with
> session b=TIAS:512K, and B sends A an answer with session b=TIAS:512K,
> and they both start sending video at 300K, are they below the cap or
> above the cap?

That is fine. This is just a statement of the maximum bandwidth the implementation is willing to receive. The values can be asymmetric, and this is just a maximum. It does not indicate anything about how much the implementation will send.

Cheers,
Charles

> Again, it's probably clear to those who've been around here for a while)
 
>                  Harald
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic