MIME-Version: 1.0
In-Reply-To: <56095160.3040709@alum.mit.edu>
References: <55F15276.4030308@ericsson.com>
 <CAG371noODCX7Y7Thiyy9HK4XeOxJ4iqp89GsSkBV7oWspmeEmw@mail.gmail.com>
 <56095160.3040709@alum.mit.edu>
Date: Mon, 5 Oct 2015 18:15:22 +0300
Message-ID: <CAG371noDJDbR_=KeAD=ZVmNRn1i_Ps9-T092eBGB0g0xdAFzQw@mail.gmail.com>
From: "Ali C. Begen" <acbegen@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/QZ3WLEPw2R4N3n9KLLK3xNAkgxQ>
Cc: "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Making b=CT session level only -
 draft-ietf-mmusic-rfc4566bis
Precedence: list

Hi Paul

Yes the phrase is used twice but they are for different levels
(session and media). I think explicit text is the most straightforward
approach.
Or is the part that says "from the scope" not clear to you?



On Mon, Sep 28, 2015 at 5:40 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote=
:
> On 9/28/15 9:19 AM, Ali C. Begen wrote:
>>
>> Hi Magnus
>>
>> Here is my suggested text based on your input. Changes are in the CT
>> and AS definitions. Let me know if you are happy with this text.
>
>
> The following phrase is used twice: "... is different from the implicit
> value from the scope ...".
>
> I don't understand what this is trying to tell me. Can it be clarified? (=
I
> realize this is also used in the old text, but still it is a problem to m=
e.)
>
>         Thanks,
>         Paul
>
>
>> -acbegen
>>
>> 5.8.  Bandwidth ("b=3D")
>>
>>        b=3D<bwtype>:<bandwidth>
>>
>>     This OPTIONAL line denotes the proposed bandwidth to be used by the
>>     session or media.  The <bwtype> is an alphanumeric modifier giving
>>     the meaning of the <bandwidth> figure.  Two values are defined in
>>     this specification, but other values MAY be registered in the future
>>     (see Section 8 and [RFC3556], [RFC3890]):
>>
>>     CT If the bandwidth of a session is different
>>        from the bandwidth implicit from the scope, a "b=3DCT:..." line
>>        SHOULD be supplied for the session giving the proposed upper limi=
t
>>        to the bandwidth used (the "conference total" bandwidth).
>> Similarly, if
>>        the bandwidth of bundled media streams in an m line is different
>> from
>>        the implicit value from the scope, a "b=3DCT:..." line SHOULD be
>> supplied
>>        in the media level. The primary purpose of this is to give an
>> approximate idea as to
>>        whether two or more sessions (or bundled media streams) can
>> coexist simultaneously.
>>     Note that CT gives a total bandwidth figure for all the media at all
>>     endpoints.
>>
>>     AS The bandwidth is interpreted to be application specific (it will
>>        be the application's concept of maximum bandwidth).  Normally,
>>        this will coincide with what is set on the application's "maximum
>>        bandwidth" control if applicable.  For RTP-based applications, AS
>>        gives the RTP "session bandwidth" as defined in Section 6.2 of
>>        [RFC3550]. Note that AS gives a bandwidth figure for a single
>> media at a single
>>     endpoint, although there may be many endpoints sending simultaneousl=
y.
>>
>>     A prefix "X-" is defined for <bwtype> names.  This is intended for
>>     experimental purposes only.  For example:
>>
>>        b=3DX-YZ:128
>>
>>     Use of the "X-" prefix is NOT RECOMMENDED: instead new modifiers
>>     SHOULD be registered with IANA in the standard namespace.  SDP
>>     parsers MUST ignore bandwidth fields with unknown modifiers.
>>     Modifiers MUST be alphanumeric and, although no length limit is
>>     given, it is recommended that they be short.
>>
>>     The <bandwidth> is interpreted as kilobits per second by default.
>>     The definition of a new <bwtype> modifier MAY specify that the
>>     bandwidth is to be interpreted in some alternative unit (the "CT" an=
d
>>     "AS" modifiers defined in this memo use the default units).
>>
>> On Thu, Sep 10, 2015 at 12:50 PM, Magnus Westerlund
>> <magnus.westerlund@ericsson.com> wrote:
>>>
>>> Hi,
>>>
>>> The chairs have been nagging me about some action points that I got
>>> assigned
>>> in my absence at the IETF92 MMUSIC session. So lets try to settle them.
>>>
>>> The main question for one of them is if SDPbis should make the b=3DCT
>>> bandwidth modifier into a session level only parameter?
>>>
>>> So, it is clear that session level CT value is the total upper limit fo=
r
>>> bandwidth consumption, independent on direction incoming or outgoing fr=
om
>>> an
>>> endpoint for this Multimedia session.
>>>
>>> Note that I believe it to be Multi-media session rather than
>>> communication
>>> session. This is due to that SDP is used to describe a multi-media
>>> session.
>>>
>>> I would also note that for Offer/Answer it is not clear if the offer
>>> applies
>>> to the offerer or the answerer. This is due to the non-directionality
>>> declaration of CT. My personal interpretation is that the offer applies
>>> to
>>> the answerer and the answer applies to the offerer. But, this is one
>>> thing
>>> that should be clarified if anyone dares revise RFC 3264.
>>>
>>> Regarding CT on media level (m=3D) I think the interpretation of it als=
o
>>> here
>>> is not that unclear. It is just that it has no meaning in the pre-bundl=
e
>>> Offer/Answer context, where one had only one Media source in that RTP
>>> session the m=3D created. But if one looks at SDP/SAP usage then CT do =
make
>>> much more sense. In multi-party usages like multicast, defining an AS f=
or
>>> one media source a CT value for the aggregate across all session
>>> endpoints
>>> do make sense.
>>>
>>> Which leads me to want to clarify that CT on media level is possible an=
d
>>> has
>>> meaning but only in contexts where one m=3D line (or a bundle group of =
m=3D
>>> lines) may contain multiple media sources and thus media streams and
>>> therefore an aggregate limitation makes sense.
>>>
>>> If people agree with this I think we need to make some amendment both t=
o
>>> SDPbis and to Mux-attributes to make this clear.
>>>
>>> SDPbis (-15) says:
>>>
>>> 5.8.  Bandwidth ("b=3D")
>>>
>>>        b=3D<bwtype>:<bandwidth>
>>>
>>>     This OPTIONAL line denotes the proposed bandwidth to be used by the
>>>     session or media.  The <bwtype> is an alphanumeric modifier giving
>>>     the meaning of the <bandwidth> figure.  Two values are defined in
>>>     this specification, but other values MAY be registered in the futur=
e
>>>     (see Section 8 and [RFC3556], [RFC3890]):
>>>
>>>     CT If the bandwidth of a session or media in a session is different
>>>        from the bandwidth implicit from the scope, a "b=3DCT:..." line
>>>        SHOULD be supplied for the session giving the proposed upper lim=
it
>>>        to the bandwidth used (the "conference total" bandwidth).  The
>>>        primary purpose of this is to give an approximate idea as to
>>>        whether two or more sessions can coexist simultaneously.
>>>
>>>     AS The bandwidth is interpreted to be application specific (it will
>>>        be the application's concept of maximum bandwidth).  Normally,
>>>        this will coincide with what is set on the application's "maximu=
m
>>>        bandwidth" control if applicable.  For RTP-based applications, A=
S
>>>        gives the RTP "session bandwidth" as defined in Section 6.2 of
>>>        [RFC3550].
>>>
>>>     Note that CT gives a total bandwidth figure for all the media at al=
l
>>>     sites.  AS gives a bandwidth figure for a single media at a single
>>>     site, although there may be many sites sending simultaneously.
>>>
>>>     A prefix "X-" is defined for <bwtype> names.  This is intended for
>>>     experimental purposes only.  For example:
>>>
>>>        b=3DX-YZ:128
>>>
>>>     Use of the "X-" prefix is NOT RECOMMENDED: instead new modifiers
>>>     SHOULD be registered with IANA in the standard namespace.  SDP
>>>     parsers MUST ignore bandwidth fields with unknown modifiers.
>>>     Modifiers MUST be alphanumeric and, although no length limit is
>>>     given, it is recommended that they be short.
>>>
>>>     The <bandwidth> is interpreted as kilobits per second by default.
>>>     The definition of a new <bwtype> modifier MAY specify that the
>>>     bandwidth is to be interpreted in some alternative unit (the "CT" a=
nd
>>>     "AS" modifiers defined in this memo use the default units).
>>>
>>>
>>> I think this needs to be modified in a couple of different places.
>>>
>>> First I think the CT explanation text should be expanded to discuss thi=
s
>>> context of possible multiple streams in the context of one m=3D line, a=
nd
>>> that
>>> in that and only that case does media level make sense.
>>>
>>> Then I would like to move up the text in the note about CT into the mai=
n
>>> definition and change "sites" to "endpoints".
>>>
>>>
>>> And Mux-attributes (-10) says:
>>>
>>> 6.1.  RFC4566 - SDP: Session Description Protocol
>>>
>>>     [RFC4566] defines the Session Description Protocol (SDP) that is
>>>     intended for describing multimedia sessions for the purposes of
>>>     session announcement, session invitation, and other forms of
>>>     multimedia session initiation.
>>>
>>>     +------------+-----------------------------------+-------+---------=
-+
>>>     | Name       | Notes                             | Level | Mux     =
 |
>>>     |            |                                   |       | Category=
 |
>>>     +------------+-----------------------------------+-------+---------=
-+
>>>     | bwtype:CT  | Not Impacted                      | S     | NORMAL  =
 |
>>>     |            |                                   |       |         =
 |
>>>     | bwtype:AS  | For the media level usage, the    | B     | SUM     =
 |
>>>     |            | aggregate of individual bandwidth |       |         =
 |
>>>     |            | values is considered              |       |         =
 |
>>>     |            |                                   |       |         =
 |
>>>     +------------+-----------------------------------+-------+---------=
-+
>>>
>>>                            RFC4566 bwtype Analysis
>>>
>>>
>>> So here Level needs to be changed to B (Both). Then I would state that
>>> the
>>> Category should be IDENTICAL. I don't know what it would mean to have
>>> different CT values for different media sources in a bundle group.
>>>
>>> It might be worth adding a Note about CT, and why CT is much more usefu=
l
>>> in
>>> a bundle-group than on a non-bundled m=3D line.
>>>
>>> Comments on this?
>>>
>>> Magnus Westerlund
>>>
>>> ----------------------------------------------------------------------
>>> Services, Media and Network features, Ericsson Research EAB/TXM
>>> ----------------------------------------------------------------------
>>> Ericsson AB                 | Phone  +46 10 7148287
>>> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
>>> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>>> ----------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic