IETF Logo Mail Archive

Re: [RAM] The mapping problem: rendezvous points?

Spencer Dawkins <spencer@mcsr-labs.org> Tue, 08 May 2007 23:32 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlZAh-00015K-A1; Tue, 08 May 2007 19:32:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlZAg-00015F-3Q for ram@iab.org; Tue, 08 May 2007 19:32:42 -0400
Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlZAe-0004LS-Sm for ram@iab.org; Tue, 08 May 2007 19:32:42 -0400
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JHQ00IJ9XEGOY@usaga01-in.huawei.com> for ram@iab.org; Tue, 08 May 2007 16:32:40 -0700 (PDT)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JHQ00MOEXDHHC@usaga01-in.huawei.com> for ram@iab.org; Tue, 08 May 2007 16:32:40 -0700 (PDT)
Date: Tue, 08 May 2007 18:30:24 -0500
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [RAM] The mapping problem: rendezvous points?
To: David Conrad <drc@virtualized.org>, Dave Thaler <dthaler@windows.microsoft.com>
Message-id: <1b5a01c791c8$e5535940$6601a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <8F47F550-6224-4AFF-8359-CBA98D3F2FAB@muada.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA470@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <9C228355-9425-4C66-A9A7-47498490E3B1@virtualized.org> <271CF87FD652F34DBF877CB0CB5D16FC054EA59D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <86588E66-ACED-4DD2-B286-3DA5B2518B1A@virtualized.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ram@iab.org
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

> Dave,
>
> On May 8, 2007, at 1:27 PM, Dave Thaler wrote:
>> Applications generally work fine with random loss.
>> They work less well with _deterministic_ loss.
>
> I would've thought the opposite would be true.

Dave,

I've heard variations on the "deterministic loss" thing in several places 
recently, and I don't understand all the context, but people have usually 
been talking about deterministic loss AT THE BEGINNING of a TCP connection, 
or AT THE BEGINNING of an MPEG stream where you're losing complete images 
and then all you receive for a while is deltas from the image you lost.

Are you talking about more than this?

Spencer 



_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram

v2.23.0 | Report a Bug | By Email