<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.14">
<TITLE>Saratoga was RE: [e2e] HARQ</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>HARQ is just a name for combining ARQ with FEC. Since ARQ (without FEC - see RFC3366) can be done over FEC in a separate higher layer anyway, this is arguably implementation detail to try and increase efficiency by closely combining the two, with incremental redundancy varying repeats to increase likelihood of correct reception from combining coded frames.<BR>
<BR>
Yes, Saratoga uses NACKs. It's designed for high utilisation of otherwise unused links in private networks. Two Saratoga peers can multiplex multiple flows between them. Allocation of link capacity between multiple nodes can be done by a MAC layer, or by a coarse scheduling algorithm; this depends on the scenario, and is not specified. Congestion control is optional and not specified; when you own the link, the traffic and the nodes, you can rely on knowledge of your environment and scheduling without congestion control presuming that every errored packet is a loss - again, to try and increase efficiency. Or you could reimplement TCP-Friendly Rate Control (TFRC) to make Saratoga behave like TCP - but DCCP, SCTP and TCP already do that; Saratoga is intended to be useful in environments where those protocols become performance-limited by the prevailing terrestrial-shared-Internet assumptions that make them so useful elsewhere. Saratoga's strengths are TFRC's weaknesses, and vice versa.<BR>
<BR>
L.<BR>
<BR>
Saratoga: <A HREF="http://www.ee.surrey.ac.uk/Personal/L.Wood/dtn/">http://www.ee.surrey.ac.uk/Personal/L.Wood/dtn/</A><BR>
<BR>
<<A HREF="http://www.ee.surrey.ac.uk/Personal/L.Wood/">http://www.ee.surrey.ac.uk/Personal/L.Wood/</A>><L.Wood@surrey.ac.uk><BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Detlef Bosau [<A HREF="mailto:detlef.bosau@web.de">mailto:detlef.bosau@web.de</A>]<BR>
Sent: Mon 2007-08-27 16:31<BR>
To: Wood L Dr (Electronic Eng)<BR>
Cc: end2end-interest@postel.org<BR>
Subject: Re: [e2e] HARQ<BR>
<BR>
L.Wood@surrey.ac.uk wrote:<BR>
><BR>
> See <A HREF="http://en.wikipedia.org/wiki/Hybrid_ARQ">http://en.wikipedia.org/wiki/Hybrid_ARQ</A><BR>
><BR>
;-)<BR>
<BR>
I looked at this page before.<BR>
<BR>
However, the difference between "old" ARQ and HARQ I becomes not quite<BR>
clear to me.<BR>
<BR>
> .<BR>
><BR>
> Saratoga: <A HREF="http://www.ee.surrey.ac.uk/Personal/L.Wood/dtn/">http://www.ee.surrey.ac.uk/Personal/L.Wood/dtn/</A><BR>
><BR>
<BR>
<BR>
So, you flood the receiver with a well defined set of blocks and the<BR>
receiver reports any blocks which are missing?<BR>
At least, this appears to be the basic idea. Is this correct?<BR>
<BR>
Will this work when there blocks of several flows mixed, as it happens<BR>
on an air interface in mobile networks?<BR>
<BR>
Detlef<BR>
<BR>
--<BR>
Detlef Bosau Mail: detlef.bosau@web.de<BR>
Galileistrasse 30 Web: <A HREF="http://www.detlef-bosau.de">http://www.detlef-bosau.de</A><BR>
70565 Stuttgart Skype: detlef.bosau<BR>
Mobile: +49 172 681 9937<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>