[MEDIACTRL] Re: Requirements Comment
"Eric Burger" <eburger@bea.com> Tue, 20 March 2007 13:30 UTC
Return-path: <mediactrl-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTeQ3-0000Oo-EZ; Tue, 20 Mar 2007 09:30:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTeQ1-0000Oc-P1 for mediactrl@ietf.org; Tue, 20 Mar 2007 09:30:29 -0400
Received: from usremg02.bea.com ([66.248.192.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTePq-0000ND-1f for mediactrl@ietf.org; Tue, 20 Mar 2007 09:30:29 -0400
Received: from usremr01.bea.com (usremr01.bea.com [10.160.29.91]) by usremg02.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l2KDUFMn026499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <mediactrl@ietf.org>; Tue, 20 Mar 2007 06:30:16 -0700
Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by usremr01.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l2KDUErk021137 for <mediactrl@ietf.org>; Tue, 20 Mar 2007 06:30:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 20 Mar 2007 06:30:14 -0700
Message-ID: <E2839307E942954A846FD1125BE33A1A0344BCC9@repbex01.amer.bea.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Requirements Comment
Thread-Index: Acdq8f38/dUDzFPETTKHlMor7q/s/QAAeZNZ
From: Eric Burger <eburger@bea.com>
To: mediactrl@ietf.org
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2007.2.21.161433
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Subject: [MEDIACTRL] Re: Requirements Comment
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Control BOF Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1942324563=="
Errors-To: mediactrl-bounces@ietf.org
I missed that one. IMHO, the AS has no need nor right to know the RTP address of the endpoint nor the termination address of the media server. What is the use case? -- Sent from my wireless e-mail device. Sorry if terse. We all need lemonade: see <http://www.standardstrack.com/ietf/lemonade> for what lemonade is. -----Original Message----- From: Steve Buko <steve.buko@dialogic.com> To: Eric Burger; mediactrl@ietf.org <mediactrl@ietf.org> Sent: Tue Mar 20 06:16:38 2007 Subject: Requirements Comment I have a general issue regarding our current set of requirements and thought it might be a good idea to get a thread going on this prior to our Thursday meeting. draft-even-media-server-req-02.txt <http://www.standardstrack.com/ietf/mediactrl/draft-even-media-server-req-02.txt> states the following “10. The MS shall supply the media addresses (RTP transport address) to be used to the AS” draft-dolly-xcon-mediacntrlframe-03.txt <http://www.standardstrack.com/ietf/mediactrl/draft-dolly-xcon-mediacntrlframe-03.txt> states the following “REQ-MCP-11 - SIP/SDP SHALL be used to establish and modify RTP connections to a Media Server” In my view, we have two main problems to solve. 1) define a media control framework that will be used to transmit a given media control protocol. 2) define a media control protocol used to control a media server. I agree that the media control framework should use SIP/SDP to specify the protocol / transport used to negotiation the TCP port and transmit/receive the media control protocol. However, I would offer that the media control protocol defined by this group should be .. 1) call control signaling agnostic 2) media transport agnostic For this requirement … draft-even-media-server-req-02.txt <http://www.standardstrack.com/ietf/mediactrl/draft-even-media-server-req-02.txt> states the following “10. The MS shall supply the media addresses (RTP transport address) to be used to the AS” I don’t understand why the AS would need the media addresses and would like to think that the AS would like to control a media server that may not be using RTP in all scenarios. For this requirement … draft-dolly-xcon-mediacntrlframe-03.txt <http://www.standardstrack.com/ietf/mediactrl/draft-dolly-xcon-mediacntrlframe-03.txt> states the following “REQ-MCP-11 - SIP/SDP SHALL be used to establish and modify RTP connections to a Media Server” I agree that SIP/SDP should be used to establish/negotiate the TCP port/address used for media control transport, however I don’t think RTP comes into play from a media control framework perspective. My high level comment is that we should not limit the use of our media control protocol to media servers that only support SIP and RTP. Steve Buko _______________________________________________________________________ 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
- [MEDIACTRL] Requirements Comment Steve Buko
- [MEDIACTRL] Re: Requirements Comment Eric Burger
- RE: [MEDIACTRL] Requirements Comment Even, Roni
- RE: [MEDIACTRL] Re: Requirements Comment Steve Buko
- Re: [MEDIACTRL] Requirements Comment Lorenzo Miniero
- RE: [MEDIACTRL] Requirements Comment Steve Buko
- RE: [MEDIACTRL] Requirements Comment Steve Buko
- RE: [MEDIACTRL] Re: Requirements Comment Steve Buko
- RE: [MEDIACTRL] Re: Requirements Comment Even, Roni
- RE: [MEDIACTRL] Re: Requirements Comment gamunson
- RE: [MEDIACTRL] Re: Requirements Comment Steve Buko
- RE: [MEDIACTRL] Re: Requirements Comment gamunson
- RE: [MEDIACTRL] Re: Requirements Comment Steve Buko
- Re: [MEDIACTRL] Re: Requirements Comment Eric Burger
- RE: [MEDIACTRL] Re: Requirements Comment Even, Roni
- RE: [MEDIACTRL] Re: Requirements Comment Steve Buko
- Re: [MEDIACTRL] Re: Requirements Comment Eric Burger
- RE: [MEDIACTRL] Re: Requirements Comment Steve Buko
- Re: [MEDIACTRL] Re: Requirements Comment Eric Burger
- Re: [MEDIACTRL] Re: Requirements Comment Diego B
- RE: [MEDIACTRL] Re: Requirements Comment Even, Roni
- Re: [MEDIACTRL] Re: Requirements Comment Diego B
- RE: [MEDIACTRL] Re: Requirements Comment Even, Roni
- RE: [MEDIACTRL] Re: Requirements Comment Chris Boulton
- RE: [MEDIACTRL] Re: Requirements Comment Chris Boulton
- Re: [MEDIACTRL] Re: Requirements Comment Eric Burger
- Re: [MEDIACTRL] Re: Requirements Comment Spencer Dawkins
- Re: [MEDIACTRL] Re: Requirements Comment Diego B
- Re: [MEDIACTRL] Re: Requirements Comment Eric Burger
- RE: [MEDIACTRL] Re: Requirements Comment Steve Buko
- RE: [MEDIACTRL] Re: Requirements Comment Lorenzo Miniero
- Re: [MEDIACTRL] Re: Requirements Comment Eric Burger
- Re: [MEDIACTRL] Re: Requirements Comment Eric Burger
- Re: [MEDIACTRL] Re: Requirements Comment Diego B
- [MEDIACTRL] Requirements (current protocols) Adnan Saleem
- [MEDIACTRL] RE: Requirements (current protocols) Even, Roni
- [MEDIACTRL] RE: Requirements (current protocols) Adnan Saleem