Re: [AVT] RTP over TCP.

philippe.gentric@philips.com Wed, 15 May 2002 13:36 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03586 for <avt-archive@odin.ietf.org>; Wed, 15 May 2002 09:36:14 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA19794 for avt-archive@odin.ietf.org; Wed, 15 May 2002 09:36:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA02331; Wed, 15 May 2002 06:00:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA02274 for <avt@optimus.ietf.org>; Wed, 15 May 2002 06:00:37 -0400 (EDT)
Received: from gw-nl3.philips.com (gw-nl3.philips.com [212.153.190.5]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23449; Wed, 15 May 2002 06:00:21 -0400 (EDT)
From: philippe.gentric@philips.com
Received: from smtpscan-nl3.philips.com (smtpscan-nl3.philips.com [130.139.36.23]) by gw-nl3.philips.com (Postfix) with ESMTP id 1EA583B433; Wed, 15 May 2002 12:00:34 +0200 (MET DST)
Received: from smtprelay-nl1.philips.com (localhost [127.0.0.1]) by smtpscan-nl3.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id MAA19660; Wed, 15 May 2002 12:00:33 +0200 (MET DST)
Received: from hbg001soh.diamond.philips.com (e1soh01.diamond.philips.com [130.143.165.45]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id MAA00163; Wed, 15 May 2002 12:00:31 +0200 (MET DST)
To: Peter Westerink <peterw@us.ibm.com>
Cc: avt@ietf.org, avt-admin@ietf.org, Ross Finlayson <finlayson@live.com>, Ram Kordale <kordale@kasenna.com>
Subject: Re: [AVT] RTP over TCP.
X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000
Message-ID: <OF93CE7A6F.E3D0B792-ONC1256BBA.00362771@diamond.philips.com>
Date: Wed, 15 May 2002 11:56:34 +0200
X-MIMETrack: Serialize by Router on hbg001soh/H/SERVER/PHILIPS(Release 5.0.9a |January 7, 2002) at 15/05/2002 12:01:26, Serialize complete at 15/05/2002 12:01:26
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 0036FCC3C1256BBA_="
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
X-BeenThere: avt@ietf.org

Ram, peter,

We would also support work on this issue.

(I cannot make committement on any implementation at this stage;-)

Maybe we could also consider the following option:

What exactly would prevent to interleave RTP in RTSP on TCP for some 
streams and use RTP/UDP for others ?


regards,

Philippe Gentric
Software Architect
Philips MP4Net
philippe.gentric@philips.com
http://www.mpeg-4.philips.com




"Peter Westerink" <peterw@us.ibm.com>
Sent by: avt-admin@ietf.org
05/14/2002 22:03

 
        To:     Ram Kordale <kordale@kasenna.com>
        cc:     avt@ietf.org
avt-admin@ietf.org
Ross Finlayson <finlayson@live.com>
kordale@kasenna.com
(bcc: Philippe Gentric/MP4-SUR/CE/PHILIPS)
        Subject:        Re: [AVT] RTP over TCP.
        Classification: 




Ram,

I believe such a profile existed in draft-ietf-avt-profile-new-09.txt, but
it was removed in version 10 because "there were no 2 implementations".
There were no technical reasons mentioned. The draft proposed prepending
each RTP packet with a 2-byte length and that's all.

IBM is interested in the same thing you're after, and I can assume there
are more MPEG-4 companies that also would want to send their BIFS and OD
streams reliably (albeit not guaranteed on-time) over TCP. With that we
should be able to come up with 2 implementations and hence re-instate the
profile?

      Peter




  
                      Ram Kordale   
                      <kordale@kasenna.        To:       Ross Finlayson 
<finlayson@live.com> 
                      com>                     cc:       <avt@ietf.org>, 
kordale@kasenna.com 
                      Sent by:                 Subject:  Re: [AVT] RTP 
over TCP. 
                      avt-admin@ietf.or   
                      g  
  
  
                      05/14/2002 03:50   
                      PM  
  
  



Ross,

Section 10.12 describes only the interleaving case. What about the case
where RTP and RTCP data need to be transferred on separate TCP 
connections?

This will need a separate profile. Does such a profile exist?

Thanks.
Ram

At 12:17 PM 5/8/2002 -0700, Ross Finlayson wrote:
>At 10:45 AM 5/8/02, Ethen Bommaiah wrote:
>>I was curious to know if there were any standard profiles that define
>>transferring RTP
>>packets over TCP. In particular, we were interested in transferring RTP
data
>>over TCP
>>while using RTSP as the control protocol.
>
>Yes - see section 10.12 of the RTSP specification (RFC 2326).  This
>defines how RTP packets may be carried over the RTSP (TCP) stream.  (This
>is actually not a new RTP 'profile', but instead, an optonal mechanism
>defined within RTSP.)
>
>         Ross.
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt






_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt