Subject: Re: [MEDIACTRL] MRB-PUB-1

From: "Lorenzo Miniero" <[email-masked]>
Date: Fri, 05 Jun 2009 17:36:03 +0200

Dear all,

this is the first mail of a list: Chris and I are figuring
out what should be in both interfaces, and we need your
thoughts on each of them.

So, first issue, active RTP sessions... we agreed they
should be part of the publishing interface. Is our view of
its representation good enough for you, or do you think
something else is needed? In particular, we propose a double
representation for each session, since we notify the amount
of both decodings and encodings occurring on the MS, rather
than just notifying the number of active sessions in
general. We thought this might be a good idea considering
that decodings and decodings consume different resources,
and a MS could have monodirectional sessions with some UACs.

Do you deem this more detailed information valuable, or
would you prefer just a reporting of active sessions as a
whole?

Thanks,
Lorenzo and Chris

----- Original Message -----
Da : Chris Boulton <[email-masked]>
A : [email-masked]
Oggetto : [MEDIACTRL] MRB-PUB-1
Data : Fri, 05 Jun 2009 15:40:53 +0100

> MediaCtrl-ID: MRB-PUB-1
> 
> Interface Name: Publishing
> 
> Property Name: Active RTP Sessions
> 
> Description:
> 
> Provides a representation of RTP sessions between an
> endpoint and a  logical media server instance. The details
> are conveyed in a list  showing the active codec type (for
> example G711, H.264) and the  associated number of active
> streaming sessions. The figure provided is  split into two
> parts. The first part represents the number of incoming 
> Active RTP Sessions (decoding) while the second part
> represents the  outgoing Active RTP sessions (encoding).
> The figures provide a snap shot  of current usage and
> should only be used as guidance when making  resource
> decisions.
> 
> Type: A list of codecs (String) and associated number of
> active  instances of that codec (positive integer).
> 
> Example:
> 
> G711 – 10/20
> 
> H.264 – 6/10
> 
> 
> Please provide comments on this interface property and let
> us know if it  triggers any thoughts on additional
> information that could be included  in the interface. This
> information will be used as the basis for text in  the
> next version of the draft.
> _______________________________________________ MEDIACTRL
> mailing list [email-masked]
> https://www.ietf.org/mailman/listinfo/mediactrl
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/mediactrl