Re: [MMUSIC] BUNDLE: Session bandwidth (Re: comments on draft-ietf-mmusic-sdp-bundle-negotiation-01)

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Fri, 14 December 2012 17:29 UTC

From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [MMUSIC] BUNDLE: Session bandwidth (Re: comments on draft-ietf-mmusic-sdp-bundle-negotiation-01)
Thread-Index: AQHNu2yZJyuQHhZlfUCEbmtj3UUmnZfbqLRggDniooCAAzujsA==
Date: Fri, 14 Dec 2012 17:29:44 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828046EB88F@xmb-aln-x08.cisco.com>
References: <92B7E61ADAC1BB4F941F943788C088281048DF@xmb-aln-x08.cisco.com> <5097DF12.2020209@alvestrand.no> <92B7E61ADAC1BB4F941F943788C08828107CCF@xmb-aln-x08.cisco.com> <50C8548B.5040306@ericsson.com>
In-Reply-To: <50C8548B.5040306@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: Session bandwidth (Re: comments on draft-ietf-mmusic-sdp-bundle-negotiation-01)
Precedence: list

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Wednesday, December 12, 2012 1:55 AM
> To: Charles Eckel (eckelcu)
> Cc: Harald Alvestrand; mmusic@ietf.org
> Subject: Re: [MMUSIC] BUNDLE: Session bandwidth (Re: comments on draft-
> ietf-mmusic-sdp-bundle-negotiation-01)
> 
> Hi,
> 
> Going through old emails. One important comment:
> 
> On 2012-11-05 21:04, Charles Eckel (eckelcu) wrote:
> >>
> >> Last time I looked b=CT was scoped to a whole conference ("supplied for
> >> the session"), while b=AS was scoped to a single RTP session. But I may
> >> be misinterpreting RFC 4566 section 5.8.
> >
> > I recommend using b=TIAS, as defined in RFC 3890. This parameter may be
> used at either the session or the media level, and it scope accordingly.
> > What needs to be avoided is summing up the b=TIAS/AS values from the
> bundled media lines and using that as that bandwidth for the bundle even if
> it exceeds the b=TIAS/AS/CT value from the session level.
> >
> 
> I would note that TIAS has no definition in Offer/Answer context. It is
> soley defined for Declarative usage. Yes, I know it is being used in O/A
> contexts, but I still don't understand how a receiver can state the
> actual packet rate to be used by the sender to enable correct calculation.

Agreed, TIAS is a declaration of the maximum bandwidth the declarer is willing to receive. It does not say anything about what the declarer is going to send. The same is true for AS and CT. 
If we want something that indicates the maximum bandwidth the declarer is planning to send, we would need to extend an existing attribute or define a new attribute.
However, the restriction I mentioned above regarding bundled streams not violating limits declared by the corresponding b=TIAS/AS/CT attributes still applies.

Cheers,
Charles


> Cheers
> 
> Magnus Westerlund
 >
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> 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] comments on draft-ietf-mmusic-sdp-bundle… Charles Eckel (eckelcu)
[MMUSIC] BUNDLE: Session bandwidth (Re: comments … Harald Alvestrand
Re: [MMUSIC] BUNDLE: Session bandwidth (Re: comme… Charles Eckel (eckelcu)
Re: [MMUSIC] BUNDLE: Session bandwidth (Re: comme… Harald Alvestrand
Re: [MMUSIC] BUNDLE: Session bandwidth (Re: comme… Charles Eckel (eckelcu)
Re: [MMUSIC] BUNDLE: Session bandwidth (Re: comme… Magnus Westerlund
Re: [MMUSIC] BUNDLE: Session bandwidth (Re: comme… Charles Eckel (eckelcu)
Re: [MMUSIC] BUNDLE: Session bandwidth (Re: comme… Magnus Westerlund