[MEDIACTRL] Requirements Comment

"Steve Buko" <steve.buko@dialogic.com> Tue, 20 March 2007 13:17 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 1HTeD8-0003hP-ER; Tue, 20 Mar 2007 09:17:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTeD6-0003hH-Id for mediactrl@ietf.org; Tue, 20 Mar 2007 09:17:08 -0400
Received: from mail.4smartphone.net ([66.45.56.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTeCi-0003Gp-Fz for mediactrl@ietf.org; Tue, 20 Mar 2007 09:17:08 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 20 Mar 2007 06:16:38 -0700
Message-ID: <919721B34BAAAA4D8EA04AAB8C98E045B650EA@snshbea106.4smartphone.snx>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Requirements Comment
Thread-Index: Acdq8f38/dUDzFPETTKHlMor7q/s/Q==
From: Steve Buko <steve.buko@dialogic.com>
To: Eric Burger <eburger@bea.com>, mediactrl@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 213cf0777a99c4ccdd94bb20659dd28c
Cc:
Subject: [MEDIACTRL] 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="===============0953464367=="
Errors-To: mediactrl-bounces@ietf.org

 

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-re
q-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-mediacntr
lframe-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-re
q-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-mediacntr
lframe-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

 

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