Re: [AVT] T.38 over RTP: RTP Sequence Number
Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 20 July 2005 07:48 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dv9K1-0006kS-9G; Wed, 20 Jul 2005 03:48:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dv9K0-0006kN-BV for avt@megatron.ietf.org; Wed, 20 Jul 2005 03:48:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13398 for <avt@ietf.org>; Wed, 20 Jul 2005 03:48:50 -0400 (EDT)
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dv9nn-0005JT-CQ for avt@ietf.org; Wed, 20 Jul 2005 04:19:39 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 3E925C53; Wed, 20 Jul 2005 09:48:44 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Wed, 20 Jul 2005 09:48:43 +0200
Received: from [147.214.34.40] ([147.214.34.40]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Wed, 20 Jul 2005 09:48:43 +0200
Message-ID: <42DE01DA.8080405@ericsson.com>
Date: Wed, 20 Jul 2005 09:48:42 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vladimir Ulybin <Vladimir@audiocodes.com>
Subject: Re: [AVT] T.38 over RTP: RTP Sequence Number
References: <79B4F738DDD4EF4F85A4641A0FE5EFD60126EB68@aclmsg.corp.audiocodes.com>
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD60126EB68@aclmsg.corp.audiocodes.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jul 2005 07:48:43.0249 (UTC) FILETIME=[7383BE10:01C58CFF]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
Cc: "Paul E. Jones" <paulej@packetizer.com>, Colin Perkins <csp@csperkins.org>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
Hi, I think a lot of the problems you are having is based on the fact you are using RFC 2198 for something it wasn't designed for. It was designed and works as intended for audio payloads that relies on a single data block (ADU) per timestamp. The formats that fulfill this can for synchronization and detecting duplicates rely solely on timestamp. It uses the RTP timestamp primarily to detect when discontinuous transmissions occur. RFC 2198 doesn't have full sequence number recovery due to the fact that it wasn't needed for all the audio payloads one was considering to use. Also the solution RFC 2198 employs aren't suitable at all when the payloads become larger than half of the MTU. If you want sequence number recovery, less hassle with timestamps and so: Use RFC 2733 FEC resolves these issue. Or rather the updated version as RFC 2733 has some issues. Unfortunately we haven't finished this update yet, but we are getting close. Vladimir Ulybin wrote: > Let consider an option to update the "draft-jones-avt-audio-t38-05.txt" > or write a new draft for T.38 over RTP. This is an ITU defined RTP payload format. I agree that it has issues and some of them could have been avoided if ITU had involved AVT in the loop earlier when it was under proposal. However it is ITU that has change control of it. > > I think the problems opened in our discussions > - repetition of T.38 packets and If you are using RTP you have certain rules to follow. These involve the fact that packets can't be repeated using the same RTP sequence number. This requires solution like the RTP Retransmission format or the use of 2733 FEC. > - excessive complexity of T.38 over RTP caused by timestamps > (non-required by T.38) As Colin says RTP timestamps must be set in RTP. However one can make them simple to only indicate time of transmission. This would be simpler if people hadn't insisted on making it go over the same RTP session as audio. FAX isn't audio and it shouldn't be handled the same way as audio packets. Thus it should go in its own RTP session where it can be given somewhat different treatment. Yes, audio/t38 should in fact be image/t38 or possibly application/t38. Then as I said, stop using RFC 2198 and your timestamp issues mostly goes away. Cheers Magnus Westerlund Multimedia Technologies, Ericsson Research EAB/TVA/A ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Colin Perkins
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Magnus Westerlund
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Colin Perkins
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Colin Perkins
- RE: [AVT] T.38 over RTP: RTP Sequence Number Paul E. Jones
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- RE: [AVT] T.38 over RTP: RTP Sequence Number Paul E. Jones
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Colin Perkins
- RE: [AVT] T.38 over RTP: RTP Sequence Number Paul E. Jones
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Colin Perkins
- RE: [AVT] T.38 over RTP: RTP Sequence Number Oren Peleg
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Colin Perkins
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Magnus Westerlund
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- RE: [AVT] T.38 over RTP: RTP Sequence Number Paul E. Jones
- RE: [AVT] T.38 over RTP: RTP Sequence Number Paul E. Jones
- RE: [AVT] T.38 over RTP: RTP Sequence Number Oren Peleg
- Re: [AVT] T.38 over RTP: RTP Sequence Number Colin Perkins
- RE: [AVT] T.38 over RTP: RTP Sequence Number Oren Peleg
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- RE: [AVT] T.38 over RTP: RTP Sequence Number Paul E. Jones
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Magnus Westerlund
- Re: [AVT] T.38 over RTP: RTP Sequence Number lazzaro
- RE: [AVT] T.38 over RTP: RTP Sequence Number Vladimir Ulybin
- Re: [AVT] T.38 over RTP: RTP Sequence Number Magnus Westerlund