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

Lars Eggert <lars.eggert@nokia.com> Wed, 09 May 2007 22:31 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 1Hluge-0007Rj-BI; Wed, 09 May 2007 18:31:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hlugc-0007Re-NK for ram@iab.org; Wed, 09 May 2007 18:31:06 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hlugb-0000G3-4X for ram@iab.org; Wed, 09 May 2007 18:31:06 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l49MV016014422; Thu, 10 May 2007 01:31:01 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 May 2007 01:31:00 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 May 2007 01:30:59 +0300
Received: from [192.168.2.16] (essapo-nirac253205.europe.nokia.com [10.162.253.205]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l49MUtwP030891; Thu, 10 May 2007 01:30:56 +0300
In-Reply-To: <F2F9AE97-7599-42BB-A542-A4B33AC3FD18@virtualized.org>
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> <4641750A.9010906@cisco.com> <283D52E5-AD3A-40FA-B81C-27DD950176CA@virtualized.org> <3DF89B6B-0CC4-4C60-9519-80CF5FECCE9B@nokia.com> <F2F9AE97-7599-42BB-A542-A4B33AC3FD18@virtualized.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <F3A8A33D-614D-4E6F-9741-61FFBB42E40C@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [RAM] The mapping problem: rendezvous points?
Date: Wed, 09 May 2007 14:30:46 -0800
To: ext David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 09 May 2007 22:31:00.0485 (UTC) FILETIME=[B8606B50:01C79289]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
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>
Content-Type: multipart/mixed; boundary="===============1491266632=="
Errors-To: ram-bounces@iab.org

On 2007-5-9, at 14:20, ext David Conrad wrote:
> On May 9, 2007, at 3:05 PM, Lars Eggert wrote:
>> Don't forget that pretty much all our transport protocols work by  
>> gathering information about the transmission path (RTT, bandwidth,  
>> etc.) by running statistics over the packets they send.
>
> Yes, but you left out the part about those protocols having  
> mechanisms to detect and recover from connectivity degradation  
> (e.g., slow start).

I'm not saying that they will break - I am saying that there is a  
danger of additional inefficiencies.

> However, this is largely irrelevant as in any rational pull-based  
> mapping mechanism, the mapping information would be cached for all  
> but the initial packet.

That may be so, but it means that the behavior of the caching scheme  
will become important.

In any event, experimentation with the proposed schemes will  
hopefully result in a better understanding of what the effects are.

>> More specifically, with LISP-like proposals and TCP, potential  
>> issues are things like a 3-second timeout if the first (SYN)  
>> packet is dropped.
>
> I'll ask again:  how does this ARP thing work again?

First off, all the ARP implementations I know of queue the packet  
during the loopkup, i.e., no loss. Second, the duration of an ARP  
lookup vs. the end-to-end RTT is typically miniscule. This is not so  
with LISP-like schemes.

Lars


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