Re: [alto] I-D Action:draft-ietf-alto-protocol-06.txt
Martin Stiemerling <Martin.Stiemerling@neclab.eu> Wed, 27 October 2010 14:35 UTC
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: alto@core3.amsl.com
Delivered-To: alto@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53A8C3A6784 for <alto@core3.amsl.com>; Wed, 27 Oct 2010 07:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.039
X-Spam-Level:
X-Spam-Status: No, score=-102.039 tagged_above=-999 required=5 tests=[AWL=0.560, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 l-PsSRBU1Ljf for <alto@core3.amsl.com>; Wed, 27 Oct 2010 07:35:52 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 1041B3A6A38 for <alto@ietf.org>; Wed, 27 Oct 2010 07:35:52 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 977E22C0001B8; Wed, 27 Oct 2010 16:37:41 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WiZON9vm0BVt; Wed, 27 Oct 2010 16:37:41 +0200 (CEST)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.neclab.eu (Postfix) with ESMTP id 538252C0001B2; Wed, 27 Oct 2010 16:37:31 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.152]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0255.000; Wed, 27 Oct 2010 16:37:31 +0200
From: Martin Stiemerling <Martin.Stiemerling@neclab.eu>
To: Richard Alimi <rich@velvetsea.net>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] I-D Action:draft-ietf-alto-protocol-06.txt
Thread-Index: AQHLdNXYsdVBrGF+N0Wr5a8pkKLScpNU3sZQ
Date: Wed, 27 Oct 2010 14:37:31 +0000
Message-ID: <E84E7B8FF3F2314DA16E48EC89AB49F0755345@PALLENE.office.hd>
References: <20101025230004.2A6003A690C@core3.amsl.com> <AANLkTi=Cntt48kMfCw_zvD3nPgyF2t4JgKhMuZ0hBsc2@mail.gmail.com>
In-Reply-To: <AANLkTi=Cntt48kMfCw_zvD3nPgyF2t4JgKhMuZ0hBsc2@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.1.67]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [alto] I-D Action:draft-ietf-alto-protocol-06.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 14:35:54 -0000
Hi Rich, You have discussed the default cost in the ALTO protocol presentation during the IETF-78 meeting. Slide 4 of http://www.ietf.org/proceedings/78/slides/alto-8.pdf. I did only a quick check of the new draft but could only find default cost type but not the default costs for unknown entries. I have may missed it in the text. Thanks Martin martin.stiemerling@neclab.eu NEC Laboratories Europe - Network Research Division NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014 > -----Original Message----- > From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of > Richard Alimi > Sent: Tuesday, October 26, 2010 8:20 AM > To: alto@ietf.org > Subject: Re: [alto] I-D Action:draft-ietf-alto-protocol-06.txt > > Hi All, > > We have uploaded version -06 of the ALTO Protocol draft. Major updates > include: > - Fixed up some inconsistencies in the naming conventions used in the > protocol (e.g., consistently use hyphens) > - Substantially re-written and clarified section on ALTO Redistribution > - Redistribution no longer requires the same private key to be > deployed to each ALTO Server in a cluster (that is, ALTO Servers > sharing the same Service ID). The requirement is instead that their > certificate chains have a common root. > - IANA Considerations is filled out with mime-type registration and > definition of ALTO Cost Type registry > - Marked some of the text that was previously in the Discussion > section so that it can be moved to a more appropriate document (it is > moved to an appendix for now). There is now substantial interest in a > deployment considerations document; it appears this some of this text > would fit better over there. > > The full diff is here: > > http://www.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=http://tools.ietf.o > rg/id/draft-ietf-alto-protocol- > 05.txt&url2=http://tools.ietf.org/id/draft-ietf-alto-protocol-06.txt > > Feedback is welcomed! > > Thanks! > Rich > > On Mon, Oct 25, 2010 at 4:00 PM, <Internet-Drafts@ietf.org> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > This draft is a work item of the Application-Layer Traffic > Optimization Working Group of the IETF. > > > > > > Title : ALTO Protocol > > Author(s) : R. Alimi, et al. > > Filename : draft-ietf-alto-protocol-06.txt > > Pages : 65 > > Date : 2010-10-25 > > > > Networking applications today already have access to a great amount > > of Inter-Provider network topology information. For example, views > > of the Internet routing table are easily available at looking glass > > servers and entirely practical to be downloaded by clients. What is > > missing is knowledge of the underlying network topology from the ISP > > or Content Provider (henceforth referred as Provider) point of view. > > In other words, what a Provider prefers in terms of traffic > > optimization -- and a way to distribute it. > > > > The ALTO Service provides information such as preferences of network > > resources with the goal of modifying network resource consumption > > patterns while maintaining or improving application performance. > > This document describes a protocol implementing the ALTO Service. > > While such service would primarily be provided by the network (i.e., > > the ISP), content providers and third parties could also operate this > > service. Applications that could use this service are those that > > have a choice in connection endpoints. Examples of such applications > > are peer-to-peer (P2P) and content delivery networks. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-alto-protocol-06.txt > > > > Internet-Drafts are also available by anonymous FTP at: > > ftp://ftp.ietf.org/internet-drafts/ > > > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > > > > > > _______________________________________________ > > alto mailing list > > alto@ietf.org > > https://www.ietf.org/mailman/listinfo/alto > > > > > _______________________________________________ > alto mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto
- [alto] I-D Action:draft-ietf-alto-protocol-06.txt Internet-Drafts
- Re: [alto] I-D Action:draft-ietf-alto-protocol-06… Richard Alimi
- Re: [alto] I-D Action:draft-ietf-alto-protocol-06… Martin Stiemerling
- Re: [alto] I-D Action:draft-ietf-alto-protocol-06… Richard Alimi
- Re: [alto] I-D Action:draft-ietf-alto-protocol-06… Martin Stiemerling