Re: [AVT] T.38 over RTP: RTP Sequence Number

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 04 July 2005 07:21 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpLGq-0004es-3z; Mon, 04 Jul 2005 03:21:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpLGn-0004ek-Bx for avt@megatron.ietf.org; Mon, 04 Jul 2005 03:21:34 -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 DAA26526 for <avt@ietf.org>; Mon, 4 Jul 2005 03:21:32 -0400 (EDT)
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DpLhI-0006Fu-Fg for avt@ietf.org; Mon, 04 Jul 2005 03:48:58 -0400
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id A48EDE57; Mon, 4 Jul 2005 09:21:29 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Mon, 4 Jul 2005 09:21:28 +0200
Received: from [147.214.34.71] ([147.214.34.71]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Mon, 4 Jul 2005 09:21:28 +0200
Message-ID: <42C8E378.1070108@ericsson.com>
Date: Mon, 04 Jul 2005 09:21:28 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
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: <79B4F738DDD4EF4F85A4641A0FE5EFD6011A03EF@aclmsg.corp.audiocodes.com>
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD6011A03EF@aclmsg.corp.audiocodes.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Jul 2005 07:21:28.0685 (UTC) FILETIME=[FEA111D0:01C58068]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: 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

Vladimir Ulybin wrote:
> 
> I think we may use for RTP sequence number the same rules of
> incrementing as for T.38 UDPTL SN, i.e. increment SN per every new
> primary IFP packet and do not increment SN if a fax packet is repeated.
> 

There exist at least two possible ways of performing this without 
screwing up the RTCP statistics and fulfilling your other requirements:

The first one is to use FEC to provide the packet repetition. I would 
suggest that you use RFC 2733 to provide repetition in a smarter way. 
This way one FEC packet can cover a few RTP packets. If this is done 
using RFC 2198 packetization then you don't even need to run two RTP 
sessions.

The second is actually to use that Retransmission RTP payload format for 
repetitions. The payload format is really for repetitions and the spec 
provides with necessary information on bind and sync. Simple skip the 
NACK process.

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