Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]
Laird Popkin <laird@pando.com> Fri, 13 June 2008 15:38 UTC
Return-Path: <p2pi-bounces@ietf.org>
X-Original-To: p2pi-archive@ietf.org
Delivered-To: ietfarch-p2pi-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 518463A68F2; Fri, 13 Jun 2008 08:38:10 -0700 (PDT)
X-Original-To: p2pi@core3.amsl.com
Delivered-To: p2pi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB20E3A68F2 for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 08:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.265
X-Spam-Level:
X-Spam-Status: No, score=-10.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_COI=-8, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fq08kgxonrVO for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 08:38:07 -0700 (PDT)
Received: from dkny.pando.com (dkny.pando.com [67.99.55.163]) by core3.amsl.com (Postfix) with ESMTP id 5B8A53A6804 for <p2pi@ietf.org>; Fri, 13 Jun 2008 08:38:07 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by dkny.pando.com (Postfix) with ESMTP id 66AF7E10C32; Fri, 13 Jun 2008 11:38:39 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
Received: from dkny.pando.com ([127.0.0.1]) by localhost (dkny.pando.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEjJ8nbqBk1Q; Fri, 13 Jun 2008 11:38:13 -0400 (EDT)
Received: from [10.178.101.188] (unknown [32.137.88.217]) by dkny.pando.com (Postfix) with ESMTP id F38D2E10C31; Fri, 13 Jun 2008 11:38:11 -0400 (EDT)
From: Laird Popkin <laird@pando.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
In-Reply-To: <20080613152734.GA25170@nic.fr>
X-Mailer: iPhone Mail (4A102)
References: <565621476.393261213359293462.JavaMail.root@dkny.pando.com> <4852862D.9030202@telecomitalia.it> <20080613151246.GA20314@nic.fr> <485290D5.1010909@alcatel-lucent.com> <20080613152734.GA25170@nic.fr>
Message-Id: <F91975DA-943F-4390-AF68-8ACD5EEE7940@pando.com>
Mime-Version: 1.0 (iPhone Mail 4A102)
Date: Fri, 13 Jun 2008 11:37:17 -0400
Cc: "p2pi@ietf.org" <p2pi@ietf.org>
Subject: Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]
X-BeenThere: p2pi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: P2P Infrastructure Discussion <p2pi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2pi>
List-Post: <mailto:p2pi@ietf.org>
List-Help: <mailto:p2pi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
Very interesting reading, thanks! - Laird Popkin, CTO, Pando Networks http://www.pandonetworks.com 520 Broadway, 10th Floor, NY, NY, 10012 laird@pando.com, 646/465-0570. Sent from my iPhone. Apologies in advance for typo's. On Jun 13, 2008, at 11:27 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote: > On Fri, Jun 13, 2008 at 10:23:01AM -0500, > Vijay K. Gurbani <vkg@alcatel-lucent.com> wrote > a message of 34 lines which said: > >> I am sorry but could you please expand on "ICS"? > > Sorry, Internet Coordinates Systems as in > <http://www.imconf.net/imc-2003/papers/p310-lim11.pdf> or similar > works. > _______________________________________________ > p2pi mailing list > p2pi@ietf.org > https://www.ietf.org/mailman/listinfo/p2pi _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement [W… Stephane Bortzmeyer
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement [W… Stephane Bortzmeyer
- Re: [p2pi] Refining the ALTO problem statement [W… Stephane Bortzmeyer
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement [W… Y. R. Yang
- Re: [p2pi] Refining the ALTO problem statement [W… Stephane Bortzmeyer
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi