Re: [MEDIACTRL] Re: Requirements Comment

I would strongly suggest people review RFC 4722 and draft-saleem-msml-02 for
the use of SIP dialog identifiers for addressing legs.

On 3/21/07 7:46 PM, "Steve Buko" <steve.buko@dialogic.com> wrote:

> |Again, the media server needs
> |to give an application-level representation of the leg, but most likely
> |(i.e., not bloody likely) not the RTP IP address / port number.
> 
> Agreed, regarding the representation of the leg.
> 
> I think the most "open" way for this to be accomplished is for the media
> control "protocol" to define the process by which the AS and MS generate
> an identifier that is associated with each call leg.
> 
> I'm not sure that this should be tied to RTP for this representation
> though.  Doing so will limit the use of our work to RTP only use cases
> when there really isn't a good reason to do so.  At the end of the day,
> the AS simply wants to control the media operations for a particular
> call leg.  It needs an identifier for that call.
> 
> If we do this right and define an extensible procedure for defining this
> call leg identification, our work could be used in many scenarios other
> than SIP/RTP.
> 
> 
> Steve Buko
> 
> 
> |-----Original Message-----
> |From: Eric Burger [mailto:eburger@bea.com]
> |Sent: Wednesday, March 21, 2007 7:13 PM
> |To: Diego B; mediactrl@ietf.org
> |Subject: Re: [MEDIACTRL] Re: Requirements Comment
> |
> |Nope, RTP is the only transport to be supported.  MSRP relays are
> |fundamentally different from Media Servers.  Again, the media server
> |needs
> |to give an application-level representation of the leg, but most likely
> |(i.e., not bloody likely) not the RTP IP address / port number.
> |
> 

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

_______________________________________________
MEDIACTRL mailing list
MEDIACTRL@ietf.org
https://www1.ietf.org/mailman/listinfo/mediactrl
Supplemental Web Site:
http://www.standardstrack.com/ietf/mediactrl