Re: [MMUSIC] Simulcast worries: What bitrate? (from the WEBRTC list)
Magnus Westerlund <magnus.westerlund@ericsson.com> Fri, 23 October 2015 13:37 UTC
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 115BC1A0119 for <mmusic@ietfa.amsl.com>; Fri, 23 Oct 2015 06:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FKzS6_SFmDDu for <mmusic@ietfa.amsl.com>; Fri, 23 Oct 2015 06:37:03 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33B881A010F for <mmusic@ietf.org>; Fri, 23 Oct 2015 06:37:03 -0700 (PDT)
X-AuditID: c1b4fb30-f79626d000006adf-a6-562a37fddc08
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id E1.D1.27359.DF73A265; Fri, 23 Oct 2015 15:37:01 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.41) with Microsoft SMTP Server id 14.3.248.2; Fri, 23 Oct 2015 15:37:00 +0200
To: Adam Roach <adam@nostrum.com>, Harald Alvestrand <harald@alvestrand.no>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <56279638.9030007@alvestrand.no> <5628F926.7060304@nostrum.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <562A37FC.1010805@ericsson.com>
Date: Fri, 23 Oct 2015 15:37:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5628F926.7060304@nostrum.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDLMWRmVeSWpSXmKPExsUyM+Jvre5fc60wg8lP5Sz2/F3EbnGsr4vN YuryxywOzB5XJlxh9Viy5CeTx6ydT1gCmKO4bFJSczLLUov07RK4Mj4t2stSsJa34tSmz8wN jK+5uhg5OSQETCT+3pjMCGGLSVy4t56ti5GLQ0jgKKPEy2cvWUASQgLLGSW2nbIEsYUFfCX+ vP7ADGKLCBRJ3Dp1mw2ixlvixtUJYDabgIXEzR+NYDavgLbEzMsbmUBsFgFVifmvv4AtExWI kXi/aRUjRI2gxMmZT8B2cQLVn9z/Gqieg4NZwF7iwdYykDCzgLxE89bZzBCrtCUamjpYJzAK zELSPQuhYxaSjgWMzKsYRYtTi5Ny042M9FKLMpOLi/Pz9PJSSzYxAsP04JbfBjsYXz53PMQo wMGoxMO7YIpmmBBrYllxZe4hRgkOZiURXmMzrTAh3pTEyqrUovz4otKc1OJDjNIcLErivM1M D0KFBNITS1KzU1MLUotgskwcnFINjPPij93/+8T145upYd6v2DQ9Nwk7nTs1bbKu+LpH09Mi pnqclWTSZYwSr2Y7Xcdz5KHCEmet2Zwv5ikLruQXfHKPT6U2953UU90omXWclyfWGa3JXr4t g/WS1qKcZAuxiTtmLVFzmhKwzFDv6FUFgdaQM3olHh+Vw5vbV01g9e/x4oh+tOiotRJLcUai oRZzUXEiALL1vC9PAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/WmYBbYbdRCOORhwwFd4O1_8Tlb4>
Subject: Re: [MMUSIC] Simulcast worries: What bitrate? (from the WEBRTC list)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 23 Oct 2015 13:37:05 -0000
Den 2015-10-22 kl. 16:56, skrev Adam Roach: > On 10/21/15 08:42, Harald Alvestrand wrote: >> I'd be happier if we could say "this is the same bitrate as b=TEAS" or >> something like that - if an implementation has to stick to multiple >> definitions of bitrate for the same media flow, which will happen with >> a=rid .. max-br and b= in the same message, it would be nice to be able >> to use the same counters. > > I'm good either way. We can keep this as-is, or add a reference to > RFC3890. Anyone want to speak for or against moving over to the RFC3890 > definition of bandwidth? Hi, I am of the opinion (having authored RFC 3890) that we should use a more well defined bit-rate definition than what is in TIAS. In fact the current definition is well matching that of TIAS, with the additional constraints of a measuring interval. I think this is the minimal improvement we should do. I can argue for an even more specific bandwidth definitions. My personal position is that the stream specific ones (SMT and SLT) in our SDP bandwidth proposal (now expired) actually makes sense to be used with RID: https://www.ietf.org/archive/id/draft-westerlund-mmusic-sdp-bw-attribute-02.txt Cheers Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ----------------------------------------------------------------------
- [MMUSIC] Simulcast worries: What bitrate? (from t… Harald Alvestrand
- Re: [MMUSIC] Simulcast worries: What bitrate? (fr… Adam Roach
- Re: [MMUSIC] Simulcast worries: What bitrate? (fr… Magnus Westerlund
- Re: [MMUSIC] Simulcast worries: What bitrate? (fr… Adam Roach