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

Dino Farinacci <dino@cisco.com> Thu, 10 May 2007 19:13 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 1HmE5G-0006zA-IJ; Thu, 10 May 2007 15:13:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmE4n-0006Sz-I1 for ram@iab.org; Thu, 10 May 2007 15:13:21 -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 1HmE1n-00080K-SB for ram@iab.org; Thu, 10 May 2007 15:10:17 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 10 May 2007 12:10:15 -0700
X-IronPort-AV: i="4.14,518,1170662400"; d="scan'208"; a="484970202:sNHT42193648"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l4AJAFfm001829; Thu, 10 May 2007 12:10:15 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4AJA0Zn004799; Thu, 10 May 2007 19:10:15 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 May 2007 12:10:12 -0700
Received: from [192.168.0.3] ([10.21.145.147]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 May 2007 12:10:12 -0700
In-Reply-To: <28B42D3F-BADD-4766-BEF7-5E8B1FBAC68E@nokia.com>
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> <F3A8A33D-614D-4E6F-9741-61FFBB42E40C@nokia.com> <85F8BDA4-1EAA-4043-8CDB-112CEF29B2BC@virtualized.org> <FD31231D-A190-41CB-AC4F-FB7871D7E695@cisco.com> <28B42D3F-BADD-4766-BEF7-5E8B1FBAC68E@nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <5666C4B7-BCD4-476F-BC14-C2517EBEEF89@cisco.com>
Content-Transfer-Encoding: 7bit
From: Dino Farinacci <dino@cisco.com>
Subject: Re: [RAM] The mapping problem: rendezvous points?
Date: Thu, 10 May 2007 12:10:12 -0700
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 10 May 2007 19:10:12.0276 (UTC) FILETIME=[D57F5F40:01C79336]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=374; t=1178824215; x=1179688215; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[RAM]=20The=20mapping=20problem=3A=20rendezvous=20poi nts? |Sender:=20; bh=uKCP6B0/bQeFrWIZjeZDoLx4zDvgwiVAuwzO2xMZDdQ=; b=jd3KctZgIlaOunHGt50SM/FZ+YwoItsupp2HU2k4nvjAPVIv21sZXNimD5ORs7aIk9ecaYQE ew0N5d37x4GUZTfIfO6ocuvpxtY2cO6QD7BDgT3Xb1PYs4v4/o2HBIAa;
Authentication-Results: sj-dkim-3; header.From=dino@cisco.com; dkim=pass (si g from cisco.com/sjdkim3002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
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

> That's a pretty unlikely scenario, but yes, the SYN of the second  
> connection would get dropped and it would take a 3-second timeout.  
> But the first one doesn't, which is the much more common case.

The point is these packet drops have gone unseen for decades. We  
shouldn't worry about solving problems like this. We have much bigger  
fish to fry.

Dino

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