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

Colin Perkins <csp@csperkins.org> Mon, 04 July 2005 08:49 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpMe0-0004Yz-Tj; Mon, 04 Jul 2005 04:49:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpMdy-0004YY-Mz for avt@megatron.ietf.org; Mon, 04 Jul 2005 04:49: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 EAA08333 for <avt@ietf.org>; Mon, 4 Jul 2005 04:49:32 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DpN4T-0004nc-6n for avt@ietf.org; Mon, 04 Jul 2005 05:17:00 -0400
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63571 helo=[192.168.0.2]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42) id 1DpMdb-0008Mc-6l; Mon, 04 Jul 2005 09:49:11 +0100
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD6011A03EF@aclmsg.corp.audiocodes.com>
References: <79B4F738DDD4EF4F85A4641A0FE5EFD6011A03EF@aclmsg.corp.audiocodes.com>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <651BD409-AD1A-4BA6-825F-318B13A83817@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] T.38 over RTP: RTP Sequence Number
Date: Mon, 04 Jul 2005 09:49:05 +0100
To: Vladimir Ulybin <Vladimir@audiocodes.com>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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

On 3 Jul 2005, at 15:44, Vladimir Ulybin wrote:
> Possibly I used the term "retransmission" non-correctly for T.38 over
> RTP. In the draft-ietf-avt-rtp-retransmission-11.txt, the term
> "retransmission" is applied to packets retransmitted as a response  
> onto
> the request of packet receiver detected packet lost. Such  
> retransmission
> reduces a reliability of fax relay, because enlarges the round-trip
> delay of fax commands and responses.
>
> But I assume a simple packet repetition following an original packet
> transmission to improve a reliability of delivering important T.30
> commands or responses. This repetition shall be done without any  
> request
> on retransmission from remote side. In T.38 UDPTL protocol the packet
> repetition is widely used by different gateway vendors.

As Magnus says, the RFC 2733 FEC format is appropriate, or the  
retransmission draft I suggested.

> Taking into account for T.38-over-RTP that
>
> 1. Fax relay is asynchronous communication having long periods of  
> packet
> absence;
> 2. The redundancy and repetition of important fax packets  
> significantly
> improves the fax session reliability;
> 3. Incrementing RTP sequence number for repeated T.38 packets  
> cannot be
> accepted;
> 4. Reliability of fax session has a much higher priority vs. a correct
> RTCP statistics;
>
> 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.

Not if you wish to be compatible with RTP: RTP requires the sequence  
numbers to be unique.

Colin

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