IETF Logo Mail Archive

Re: [p2pi] Information in an ALTO protocol

Reinaldo Penno <rpenno@juniper.net> Thu, 11 September 2008 18:31 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 3C74F3A68D1; Thu, 11 Sep 2008 11:31:29 -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 2150C3A68D1 for <p2pi@core3.amsl.com>; Thu, 11 Sep 2008 11:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 6dv5sjypbUcp for <p2pi@core3.amsl.com>; Thu, 11 Sep 2008 11:31:27 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id 56EAB3A67DF for <p2pi@ietf.org>; Thu, 11 Sep 2008 11:31:16 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP; Thu, 11 Sep 2008 11:31:16 PDT
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emsmtp02.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Sep 2008 11:30:38 -0700
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Sep 2008 11:30:38 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by emailwf1.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 11 Sep 2008 14:30:36 -0400
Received: from 172.23.1.107 ([172.23.1.107]) by proton.jnpr.net ([10.10.2.37]) with Microsoft Exchange Server HTTP-DAV ; Thu, 11 Sep 2008 18:30:36 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Thu, 11 Sep 2008 11:30:35 -0700
From: Reinaldo Penno <rpenno@juniper.net>
To: Laird Popkin <laird@pando.com>, Richard Woundy <Richard_Woundy@cable.comcast.com>
Message-ID: <C4EEB1DB.FD1E%rpenno@juniper.net>
Thread-Topic: [p2pi] Information in an ALTO protocol
Thread-Index: AckUPHrxeDMprWZEU0S9PAeLCWZaPA==
In-Reply-To: <244110379.257691221157568965.JavaMail.root@dkny.pando.com>
Mime-version: 1.0
X-OriginalArrivalTime: 11 Sep 2008 18:30:36.0924 (UTC) FILETIME=[7C16EBC0:01C9143C]
Cc: p2pi@ietf.org
Subject: Re: [p2pi] Information in an ALTO protocol
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

That was going to be my observation to Rich's point as well. I was wondering
if he was assuming some kind inter-ALTO communication. But even if existed
it would not be Internet wide.


On 9/11/08 11:26 AM, "Laird Popkin" <laird@pando.com> wrote:

> The other issue is that ALTO is anticipated to be used by ISPs to provide
> guidance to their own users. ALTO can't provide guidance to customers of other
> ISPs. So ISP A cannot tell the rest of the internet to pull data from ISP B
> but not ISP A.

_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi

v2.23.0 | Report a Bug | By Email