Re: [AVT] RTP over TCP. Wed, 15 May 2002 13:36 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id JAA03586 for <>; Wed, 15 May 2002 09:36:14 -0400 (EDT)
Received: (from daemon@localhost) by (8.9.1a/8.9.1) id JAA19794 for; Wed, 15 May 2002 09:36:27 -0400 (EDT)
Received: from (localhost []) by (8.9.1a/8.9.1) with ESMTP id GAA02331; Wed, 15 May 2002 06:00:48 -0400 (EDT)
Received: from (odin []) by (8.9.1a/8.9.1) with ESMTP id GAA02274 for <>; Wed, 15 May 2002 06:00:37 -0400 (EDT)
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id GAA23449; Wed, 15 May 2002 06:00:21 -0400 (EDT)
Received: from ( []) by (Postfix) with ESMTP id 1EA583B433; Wed, 15 May 2002 12:00:34 +0200 (MET DST)
Received: from (localhost []) by (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 ( []) by (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 <>
Cc:,, Ross Finlayson <>, Ram Kordale <>
Subject: Re: [AVT] RTP over TCP.
X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000
Message-ID: <>
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_="
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Audio/Video Transport Working Group <>

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 ?


Philippe Gentric
Software Architect
Philips MP4Net

"Peter Westerink" <>
Sent by:
05/14/2002 22:03

        To:     Ram Kordale <>
Ross Finlayson <>
(bcc: Philippe Gentric/MP4-SUR/CE/PHILIPS)
        Subject:        Re: [AVT] RTP over TCP.


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


                      Ram Kordale   
                      <kordale@kasenna.        To:       Ross Finlayson 
                      com>                     cc:       <>, 
                      Sent by:                 Subject:  Re: [AVT] RTP 
over TCP. 
                      05/14/2002 03:50   


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

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


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
>>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

Audio/Video Transport Working Group

Audio/Video Transport Working Group