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

Tony Li <tli@cisco.com> Tue, 08 May 2007 21:09 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 1HlWwE-0007yf-RD; Tue, 08 May 2007 17:09:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlWwE-0007yY-Ev for ram@iab.org; Tue, 08 May 2007 17:09:38 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlWwA-0008HI-TJ for ram@iab.org; Tue, 08 May 2007 17:09:38 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 08 May 2007 14:09:34 -0700
X-IronPort-AV: i="4.14,507,1170662400"; d="scan'208"; a="484394032:sNHT44934662"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l48L9YOh018248; Tue, 8 May 2007 14:09:34 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l48L9KZl020939; Tue, 8 May 2007 21:09:34 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 8 May 2007 14:09:33 -0700
Received: from [192.168.0.100] ([10.21.153.30]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 8 May 2007 14:09:33 -0700
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC054EA593@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
References: <8F47F550-6224-4AFF-8359-CBA98D3F2FAB@muada.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA470@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <62AFA8C7-FDD4-4FF2-B609-966081DDC0D1@cisco.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA593@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <B79E458E-F18C-4617-B953-F311E5623E9A@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: Re: [RAM] The mapping problem: rendezvous points?
Date: Tue, 08 May 2007 14:09:31 -0700
To: Dave Thaler <dthaler@windows.microsoft.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 08 May 2007 21:09:33.0284 (UTC) FILETIME=[2CF6FA40:01C791B5]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1529; t=1178658574; x=1179522574; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=tli@cisco.com; z=From:=20Tony=20Li=20<tli@cisco.com> |Subject:=20Re=3A=20[RAM]=20The=20mapping=20problem=3A=20rendezvous=20poi nts? |Sender:=20; bh=HZ35U6XGVCr4+QRlQJ7K8Xg6aReoQc3LBEEAGk8+APE=; b=TkOJq3LmNqVle/LYoAT4XmAKUI+mfSpxQLQowjT5WOWngJtLMp74H/1nUv86jX4K03r/mKkj Oln+HXbbjFV+l3xHLBWT/xEOomivpfsGqihu5RueWoZzXHAu8JgY4wpg;
Authentication-Results: sj-dkim-4; header.From=tli@cisco.com; dkim=pass (sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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,

> I agree there are hybrid cases possible, but what I was saying is  
> not a
> hybrid at all.
>
> In hybrid schemes it comes down to whether there is any case of "slow"
> or not.
>
> For example, in one class of hybrid schemes:
>
> PUSH is used to get log(N) information such that any packet can be
> immedidately forwarded upon arrival, and PULL is used in parallel to
> forwarding to obtain a more optimal destination for future traffic.
> This one is not problematic.


Since the first packet is forwarded with suboptimal information,  
there will be a certain amount of additional stretch.  In addition,  
when the optimal information arrives, the change in path can  
potentially cause packet reordering, which is definitely problematic  
for a variety of applications, as well as triggering slow start.


> PUSH is used to get some information, but there remain cases where
> a packet can arrive and PULL must be used before the packet can be
> forwarded (i.e. encapsulated) somewhere.  This one is problematic
> for the same reason as PULL.
>
> So as long as a hybrid is PUSH (not everything) with PULL _as an
> optimization_, I claim it's better than where PULL is _a necessity_  
> and
> PUSH is just an optimization.


I think that your claim is equivalent to saying that you prefer  
initial sub-optimality to initial latency.  I'm not yet convinced by  
this.  If the mapping client is in fact the host, it would seem that  
we could mask any initial latency.

Tony

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