RE: [AVT] -Bursty packet loss for text. - Was: How is SDP a=fmtp used for RFC 2198?
"Alan Clark" <alan@telchemy.com> Fri, 09 April 2004 11:07 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22326 for <avt-archive@odin.ietf.org>; Fri, 9 Apr 2004 07:07:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBtqm-0001K2-6H for avt-archive@odin.ietf.org; Fri, 09 Apr 2004 07:07:09 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i39B78iL005082 for avt-archive@odin.ietf.org; Fri, 9 Apr 2004 07:07:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBtqf-0001HJ-VY; Fri, 09 Apr 2004 07:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBtqO-0001GP-Sq for avt@optimus.ietf.org; Fri, 09 Apr 2004 07:06:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22280 for <avt@ietf.org>; Fri, 9 Apr 2004 07:06:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBtqJ-0007Ca-00 for avt@ietf.org; Fri, 09 Apr 2004 07:06:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBtpG-00073e-00 for avt@ietf.org; Fri, 09 Apr 2004 07:05:35 -0400
Received: from telchemy.com ([66.155.69.251]) by ietf-mx with esmtp (Exim 4.12) id 1BBtn6-0006jh-00 for avt@ietf.org; Fri, 09 Apr 2004 07:03:20 -0400
Received: from telws116 [68.155.203.61] by telchemy.com with ESMTP (SMTPD32-8.05) id A2512660154; Fri, 09 Apr 2004 07:00:33 -0400
From: Alan Clark <alan@telchemy.com>
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>, Randell Jesup <rjesup@wgate.com>
Cc: avt@ietf.org, paulej@packetizer.com, magnus.westerlund@ericsson.com, Colin Perkins <csp@csperkins.org>
Subject: RE: [AVT] -Bursty packet loss for text. - Was: How is SDP a=fmtp used for RFC 2198?
Date: Fri, 09 Apr 2004 07:02:32 -0400
Message-ID: <BGEKJNNFCPJKLLMMDMELIEHEDHAA.alan@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <BHEHLFPKIPMLPFNFAHJKIECDEDAA.gunnar.hellstrom@omnitor.se>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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
Bursts of consecutive loss are, as you suggest, relatively infrequent and are usually due to link failures (see paper from Boutremans). Sparse bursts are however very common - typically up to 1-2 seconds of 20-30% loss density (see www . voiptroubleshooter.com/voiptr_burstloss.htm) Alan Clark Telchemy -----Original Message----- From: avt-admin@ietf.org [mailto:avt-admin@ietf.org]On Behalf Of Gunnar Hellstrom Sent: Friday, April 09, 2004 1:16 AM To: Randell Jesup Cc: avt@ietf.org; paulej@packetizer.com; magnus.westerlund@ericsson.com; Colin Perkins Subject: RE: [AVT] -Bursty packet loss for text. - Was: How is SDP a=fmtp used for RFC 2198? You said: > This assumes totally independant loss. The reality is > that loss is > pretty strongly _not_ independant; i.e. the conditional probability of > losing packet N+1 after losing packet N is high, and typically way higher > than the base loss probability p (probability of losing packet N > if packet > N-1 was received). The text packetization avoids loading the network and avoids bursty packet loss by recommending 300 ms between transmissions. So, you collect typed characters during 300 ms and then form a packet and transmit. If nothing is typed, nothing is transmitted. The observations on bursty packet loss pattern you refer to are made on audio transmission, where packets are sent with 20-30 ms intervals. That gives a very different probability for influence by bursts of packet loss. Figures for common lengths of bursts I have seen have indicated that bursts over 50 ms are rare. So, I feel quite safe with the calculation being reasonably accurate without taking burstiness into account. Regards ------------------------------------------- Gunnar Hellstrom Omnitor AB Renathvagen 2 SE 121 37 Johanneshov SWEDEN +46 8 556 002 03 Mob: +46 708 204 288 www.omnitor.se Gunnar.Hellstrom@Omnitor.se -------------------------------------------- > -----Original Message----- > From: avt-admin@ietf.org [mailto:avt-admin@ietf.org]On Behalf Of Randell > Jesup > Sent: Thursday, April 08, 2004 9:32 PM > To: Gunnar Hellstrom > Cc: Colin Perkins; magnus.westerlund@ericsson.com; > paulej@packetizer.com; avt@ietf.org > Subject: Re: [AVT] How is SDP a=fmtp used for RFC 2198? > > > "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se> writes: > >3. Each generation of redundant info gives quite good > reliability increase. > > > >Look at this calculation: > > > >For RFC2793bis text transport in text form, this is the theory: > > > >Assume that the risk of loosing a packet is p > >The risk of loosing also next text packet is also p > > > >The bad case is only when both are lost. The likelihood for > that is p*p . > > > >You can check with 50% loss and sending two packets. There are > totally four > >outcomes. > > > >lost -not lost > >lost - lost > >not lost - lost > >not lost - not lost > > > >Only one out of four is unsuccessful. that is 25%. > > > >0.5 * 0.5 = 0.25 the probability calculation is valid. > > > >If you add one more redundancy level, the likelihood of all > three lost is > >p*p*p > > > >With real figures, 20% packet loss and three transmissions give > 0.2 * 0.2 * > >0.2 = 0.008 =0.8%total loss. > > This assumes totally independant loss. The reality is > that loss is > pretty strongly _not_ independant; i.e. the conditional probability of > losing packet N+1 after losing packet N is high, and typically way higher > than the base loss probability p (probability of losing packet N > if packet > N-1 was received). I.e. bursts are not an unusual type of loss. > > From numbers I've seen, the conditional probability for a second > packet to be lost (loss burst size >= 2) on the internet is around 15% or > more (with a p~= 1%). > > Of course these values are way lower than the 50% or 20% > mentioned > above, but they're also heavily dependant on the physical links > traversed. > (a 3GPP link may be much worse). > > -- > Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team > rjesup@wgate.com > "The fetters imposed on liberty at home have ever been forged > out of the weapons > provided for defence against real, pretended, or imaginary > dangers from abroad." > - James Madison, 4th US president (1751-1836) > > > _______________________________________________ > Audio/Video Transport Working Group > avt@ietf.org > https://www1.ietf.org/mailman/listinfo/avt > > _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Comments on draft-ietf-avt-rfc2793bis-03.txt Magnus Westerlund
- RE: [AVT] Comments on draft-ietf-avt-rfc2793bis-0… Gunnar Hellstrom
- [AVT] How is SDP a=fmtp used for RFC 2198? Magnus Westerlund
- RE: [AVT] How is SDP a=fmtp used for RFC 2198? Gunnar Hellstrom
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Magnus Westerlund
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Colin Perkins
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Colin Perkins
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Tim Melanchuk
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Colin Perkins
- RE: [AVT] How is SDP a=fmtp used for RFC 2198? Gunnar Hellstrom
- RE: [AVT] How is SDP a=fmtp used for RFC 2198? Gunnar Hellstrom
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Magnus Westerlund
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Randell Jesup
- RE: [AVT] -Bursty packet loss for text. - Was: Ho… Gunnar Hellstrom
- RE: [AVT] -Bursty packet loss for text. - Was: Ho… Alan Clark
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Colin Perkins