Re: [alto] FW: I-D Action:draft-stiemerling-alto-deployments-05.txt

"Schmidt, Christian 1. (NSN - DE/Munich)" <christian.1.schmidt@nsn.com> Fri, 29 October 2010 07:15 UTC

Return-Path: <christian.1.schmidt@nsn.com>
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 DE9813A6A09 for <alto@core3.amsl.com>; Fri, 29 Oct 2010 00:15:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level:
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599]
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 cNhGyGTDnFkh for <alto@core3.amsl.com>; Fri, 29 Oct 2010 00:15:57 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 90A323A693E for <alto@ietf.org>; Fri, 29 Oct 2010 00:15:55 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o9T7Hl4n032420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 29 Oct 2010 09:17:47 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o9T7Hjjf012032; Fri, 29 Oct 2010 09:17:47 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Oct 2010 09:17:46 +0200
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
Date: Fri, 29 Oct 2010 09:17:44 +0200
Message-ID: <C58FFCAAA14F454A85AFB7C1C2F862C4011C8861@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E84E7B8FF3F2314DA16E48EC89AB49F0755F19@PALLENE.office.hd>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [alto] FW: I-D Action:draft-stiemerling-alto-deployments-05.txt
Thread-Index: AQHLdFOOwvH6xKrFtEmwaRB9nuBsAZNXfiowgAAKzgA=
References: <E84E7B8FF3F2314DA16E48EC89AB49F0755F19@PALLENE.office.hd>
From: "Schmidt, Christian 1. (NSN - DE/Munich)" <christian.1.schmidt@nsn.com>
To: ext Martin Stiemerling <Martin.Stiemerling@neclab.eu>, alto@ietf.org
X-OriginalArrivalTime: 29 Oct 2010 07:17:46.0793 (UTC) FILETIME=[62FF4990:01CB7739]
Subject: Re: [alto] FW: I-D Action:draft-stiemerling-alto-deployments-05.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: Fri, 29 Oct 2010 07:15:59 -0000

Hi Martin,

a short question concerning the map-based approach:

"The main assumption for map-based approaches is that the information
provided in these maps is static for a longer period of time, where this
period of time refers to days, but not hours or even minutes. This
assumption is fine, as long as the network operator does not change any
parameter, e.g., routing within the network and to the upstream peers,
IP address assignment stays stable (and thus the mapping to the
partitions).  However, there are several cases where this assumption is
not valid, as:
   1.  ISPs reallocate IPv4 subnets from time to time;
   2.  ISPs reallocate IPv4 subnets on short notice;
   3.  IP prefix blocks may be assigned to a single DSLAM which serves a
variety of access networks."

What about mobile peers? How do they fit into a map-based approach?

Christian








-----Original Message-----
From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
ext Martin Stiemerling
Sent: Friday, October 29, 2010 8:37 AM
To: alto@ietf.org
Subject: [alto] FW: I-D Action:draft-stiemerling-alto-deployments-05.txt

Dear all,

There is a slightly updated version of the deployment considerations
draft. 

Rich Alimi, Richard Yang, Xianghui Sun, Sebastian and me will come up
with a joint proposal how to evolve the document at the next IETF. 

Any comments are appreciated!

  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: i-d-announce-bounces@ietf.org [mailto:i-d-announce-
> bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org
> Sent: Monday, October 25, 2010 4:45 PM
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-stiemerling-alto-deployments-05.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 	Title           : ALTO Deployment Considerations
> 	Author(s)       : M. Stiemerling, S. Kiesel
> 	Filename        : draft-stiemerling-alto-deployments-05.txt
> 	Pages           : 29
> 	Date            : 2010-10-25
> 
> Many Internet applications are used to access resources, such as
> pieces of information or server processes, which are available in
> several equivalent replicas on different hosts.  This includes, but
> is not limited to, peer-to-peer file sharing applications.  The goal
> of Application-Layer Traffic Optimization (ALTO) is to provide
> guidance to these applications, which have to select one or several
> hosts from a set of candidates, that are able to provide a desired
> resource.  The protocol is under specification in the ALTO working
> group.  This memo discusses deployment related issues of ALTO for
> peer-to-peer and CDNs, some preliminary security considerations, and
> also initial guidance for application designers using ALTO.
> 
> A URL for this Internet-Draft is:
>
http://www.ietf.org/internet-drafts/draft-stiemerling-alto-deployments-
> 05.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.