Re: [AVT] RTP w/ TCP, RTP w/o RTCP ...
Jonathan Rosenberg <jdrosen@dynamicsoft.com> Sun, 01 December 2002 04:22 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18301 for <avt-archive@odin.ietf.org>; Sat, 30 Nov 2002 23:22:15 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gB14Oda05869 for avt-archive@odin.ietf.org; Sat, 30 Nov 2002 23:24:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB14O5v05852; Sat, 30 Nov 2002 23:24:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB14JSv05749 for <avt@optimus.ietf.org>; Sat, 30 Nov 2002 23:19:28 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18225 for <avt@ietf.org>; Sat, 30 Nov 2002 23:16:33 -0500 (EST)
Received: from dynamicsoft.com ([63.113.46.7]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gB14JLYH009774; Sat, 30 Nov 2002 23:19:21 -0500 (EST)
Message-ID: <3DE98DC2.7060907@dynamicsoft.com>
Date: Sat, 30 Nov 2002 23:19:14 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Lazzaro <lazzaro@CS.Berkeley.EDU>
CC: avt@ietf.org
Subject: Re: [AVT] RTP w/ TCP, RTP w/o RTCP ...
References: <200211300219.SAA25845@snap.CS.Berkeley.EDU>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
inline. John Lazzaro wrote: > Hi everyone, > > Work is proceeding on the MWPP "implementation guidelines" I-D > revision. The main body of the text is now finished (implementation > guidance for a two-party interactive session over unreliable unicast > UDP, with RTCP), and I'm starting to work on the Appendices which > cover other types of sessions. A few issues have come up: > > > [1] One Appendix focuses on how to send RTP w/o RTCP. Looking over the > mmusic I-Ds and RFCs, I couldn't find a way to express "I am sending > RTP w/o RTCP" in an SDP m= line. I was expecting the "RTCP attribute > in SDP" I-D (draft-ietf-mmusic-sdp4nat-03.txt) to have syntax for > "none", but it doesn't seem to (maybe I missed it). Try: http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-bw-05.txt > [2] Another Appendix focuses on how to send RTP over TCP. For the > special case of using RTSP and interleaved mode, sending RTP over TCP > is fully specified. I could just write this Appendix around RTSP. > > However, some MWPP users will be doing interactive work using TCP, > and so RTSP isn't the right session management tool for them, SIP is. > The draft-ietf-mmusic-sdp-comedia-04.txt document describes how to > create the SDP lines for specifying TCP, so I was going to base the > interactive story around that syntax. > > The open issue is the encapsulation of RTP and RTCP in the byte > stream. Section 7 of draft-ietf-avt-profile-new-12 doesn't specify a > standardized method for encapsulation, but rather says it is > "application dependent", and cites RTSP as an example. > > This would seem to indicate that there is a SIP-oriented I-D > somewhere, that standardizes a byte stream encapsulation for use with > draft-ietf-mmusic-sdp-comedia-04.txt. Does such a document exist? No. Comedia was meant for non-RTP applications primarily (at least where TCP is concerned). It used to be that you could use a certain character in the TCP stream (* maybe?) to frame RTP packets, but this was removed because no one implemented it. -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] RTP w/ TCP, RTP w/o RTCP ... John Lazzaro
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Jonathan Rosenberg
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... John Lazzaro
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Colin Perkins
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... John Lazzaro
- Archiving [was: [AVT] RTP w/ TCP, RTP w/o RTCP ] Chuck Harrison
- Re: Archiving [was: [AVT] RTP w/ TCP, RTP w/o RTC… Colin Perkins
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Jonathan Lennox
- RE: [AVT] RTP w/ TCP, RTP w/o RTCP ... Anders Klemets
- RE: [AVT] RTP w/ TCP, RTP w/o RTCP ... John Lazzaro
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Peter Westerink
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Chuck Harrison
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Colin Perkins
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Colin Perkins
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Ron Frederick
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Peter Westerink
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Lloyd Wood
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... John Lazzaro
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Ross Finlayson
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Colin Perkins
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Ron Frederick
- Re: [AVT] RTP w/ TCP, RTP w/o RTCP ... Stephen Casner
- Re: Archiving [was: [AVT] RTP w/ TCP, RTP w/o RTC… Stephen Casner