Re: [MMUSIC] Draft-ietf-mmusic-rfc4566bis-05: session-level attributes

["Miguel A. Garcia" <[e-mail]>]

Resent. I wanted to include Ali in the discussion, but I failed at first 
time.

/Miguel

On 28/08/2012 10:40, Miguel A. Garcia wrote:
> Hi Paul,
>
> perhaps you are thinking of the Bandwidth modifier for SDP, RFC 3890.
> Section 6.2.2. says:
>
>     A new session and media level bandwidth modifier is defined:
>
>        b=TIAS:<bandwidth-value> ; see section 6.6 for ABNF definition.
>
>     The Transport Independent Application Specific Maximum (TIAS)
>     bandwidth modifier has an integer bit-rate value in bits per second.
>     A fractional bandwidth value SHALL always be rounded up to the next
>     integer.  The bandwidth value is the maximum needed by the
>     application (SDP session level) or media stream (SDP media level)
>     without counting IP or other transport layers like TCP or UDP.
>
>     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.  This can normally only be
>     verified for stored media streams.
>
> Is this the example you were looking for?
>
> /Miguel
>
> On 27/08/2012 19:03, Paul Kyzivat wrote:
>> I've always thought this should be the way things work, for all
>> attributes. But somewhere I came across an attribute (sorry, don't
>> remember which one) where the attribute at session level means something
>> different than the attribute at media level, and so can't be treated as
>> a default for media level. (E.g. the session level is an aggregate limit
>> for something, while the media level is a limit for a single m-line.)
>>
>> Am I just dreaming this? Or can someone identify specific attributes
>> that behave this way?
>

-- 
Miguel A. Garcia
[phone]
Ericsson Spain