[AVT] RTP over TCP.

"Ethen Bommaiah" <ethen@kasenna.com> Wed, 08 May 2002 17:48 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 NAA18364 for <avt-archive@odin.ietf.org>; Wed, 8 May 2002 13:48:22 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA17710 for avt-archive@odin.ietf.org; Wed, 8 May 2002 13:48:30 -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 NAA17691; Wed, 8 May 2002 13:48:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17662 for <avt@optimus.ietf.org>; Wed, 8 May 2002 13:48:15 -0400 (EDT)
Received: from kasenna.com (mail.kasenna.com [208.253.201.4]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18357 for <avt@ietf.org>; Wed, 8 May 2002 13:48:07 -0400 (EDT)
Received: (qmail 7213853 invoked from network); 8 May 2002 17:47:44 -0000
Received: from madras.kasenna.wan (HELO madras) (10.10.4.112) by mail.kasenna.wan with SMTP; 8 May 2002 17:47:44 -0000
From: Ethen Bommaiah <ethen@kasenna.com>
To: avt@ietf.org
Date: Wed, 08 May 2002 10:45:47 -0700
Message-ID: <NFBBLHFFKDBKBBHDMDEJCEMLCAAA.ethen@kasenna.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Subject: [AVT] RTP over TCP.
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
Content-Transfer-Encoding: 7bit

Hi,

I was looking at the RTP FAQ page at
http://www.cs.columbia.edu/~hgs/rtp/faq.html
Under "Why doesn't RTP have a length field ?", it mentions: "If RTP is used
with a
protocol that is not message-based (e.g., TCP) or if it is desirable to
carry several RTP
packets in one lower-layer PDU (e.g., for aggregation of streams), it is
trivial to define
a profile that prefixes the RTP header by a 16 or 32-bit length field,
depending on the
desired tradeoff between overhead and maintaining word alignment."

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.

Thanks,
Ethen


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