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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 08 May 2007 22:44 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 1HlYPg-0005W3-7B; Tue, 08 May 2007 18:44:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlYPf-0005Vy-Al for ram@iab.org; Tue, 08 May 2007 18:44:07 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56] helo=stl-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlYPe-0007Yo-3K for ram@iab.org; Tue, 08 May 2007 18:44:07 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id l48Mi4Q3010310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 8 May 2007 17:44:05 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.13.6/8.13.6/DOWNSTREAM_RELAY) with ESMTP id l48Mi4oK026012; Tue, 8 May 2007 15:44:04 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.13.6/8.13.6/UPSTREAM_RELAY) with ESMTP id l48Mi2UD025950; Tue, 8 May 2007 15:44:04 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 8 May 2007 15:43:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [RAM] The mapping problem: rendezvous points?
Date: Tue, 08 May 2007 15:43:39 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED798@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC054EA694@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [RAM] The mapping problem: rendezvous points?
Thread-Index: AceRtT1Eh1h+wTjrRQak3DpFRm2C9AACFD9wAAENvVA=
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<B79E458E-F18C-4617-B953-F311E5623E9A@cisco.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA694@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Dave Thaler <dthaler@windows.microsoft.com>, Tony Li <tli@cisco.com>
X-OriginalArrivalTime: 08 May 2007 22:43:54.0956 (UTC) FILETIME=[5B9590C0:01C791C2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

> > 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.
> 
> The host is not incented to change to deal with routing scalability.
> That's why I like the LISP approach, as the changes are done in places
> (and by people) who actually experience the pain.

IPvLX gives IMHO a nice example of a map-and-encaps
architecture that locates the ITR as close as possible
to the application endpoints. But, it is still a router
even though it may be co-located with a host function.

When the ITR and application endpoints are in very close
proximity, I don't see a problem for the pull model.

Fred
fred.l.templin@boeing.com

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