[alto] draft-ietf-alto-deployments-13
"SCHARF, Michael (Michael)" <michael.scharf@nokia.com> Wed, 20 January 2016 08:21 UTC
Return-Path: <michael.scharf@nokia.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7A411B3910 for <alto@ietfa.amsl.com>; Wed, 20 Jan 2016 00:21:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TUqDm6w9wfxQ for <alto@ietfa.amsl.com>; Wed, 20 Jan 2016 00:21:57 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D48DD1B390F for <alto@ietf.org>; Wed, 20 Jan 2016 00:21:56 -0800 (PST)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 486B9147948ED for <alto@ietf.org>; Wed, 20 Jan 2016 08:21:53 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u0K8LsK4030622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Wed, 20 Jan 2016 08:21:54 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u0K8LsfW003289 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <alto@ietf.org>; Wed, 20 Jan 2016 09:21:54 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.114]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Wed, 20 Jan 2016 09:21:54 +0100
From: "SCHARF, Michael (Michael)" <michael.scharf@nokia.com>
To: IETF ALTO <alto@ietf.org>
Thread-Topic: draft-ietf-alto-deployments-13
Thread-Index: AQHRU1uerwLn2dxDH0+NOaXx1MJE5w==
Date: Wed, 20 Jan 2016 08:21:53 +0000
Message-ID: <655C07320163294895BBADA28372AF5D485CF486@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/alto/vhGpuKwIfBJ76azGkKs6UjYzINA>
Subject: [alto] draft-ietf-alto-deployments-13
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jan 2016 08:21:59 -0000
Hi all, Based on a suggestion of the chairs I have looked into how to include parts of draft-seidel-alto-map-calculation in draft-ietf-alto-deployments. In general, draft-seidel-alto-map-calculation contains a useful and comprehensive deployment example as well as some lessons learnt. As far as I can tell, the example described in draft-seidel-alto-map-calculation seems realistic, and the resulting recommendations for ALTO deployments could be backed by other solutions to calculate ALTO maps. Thus, I think it would be useful to add significant parts of draft-seidel-alto-map-calculation to draft-ietf-alto-deployments, even if that document has already passed WGLC. The new version draft-ietf-alto-deployments-13 has three main changes: * There is a new Section 3.6. "Comprehensive Example for Map Calculation" taken from draft-seidel-alto-map-calculation with only minor editorial modifications * Section 3.2 has been updated in various paragraphs with additional material from draft-seidel-alto-map-calculation, as far as applicable * Hans Seidel has been added as co-author Please have a look at the new version -13 and let us know any feedback on the changes. I would like to ask the chairs to run a new WGLC in order to finally move this document forward. Thanks Michael -----Original Message----- From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of EXT internet-drafts@ietf.org Sent: Wednesday, January 20, 2016 9:00 AM To: i-d-announce@ietf.org Cc: alto@ietf.org Subject: I-D Action: draft-ietf-alto-deployments-13.txt 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 Deployment Considerations Authors : Martin Stiemerling Sebastian Kiesel Michael Scharf Hans Seidel Stefano Previdi Filename : draft-ietf-alto-deployments-13.txt Pages : 75 Date : 2016-01-19 Abstract: Many Internet applications are used to access resources such as pieces of information or server processes that 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 applications that have to select one or several hosts from a set of candidates, which are able to provide a desired resource. This memo discusses deployment related issues of ALTO. It addresses different use cases of ALTO such as peer-to-peer file sharing and CDNs and presents corresponding examples. The document also includes recommendations for network administrators and application designers planning to deploy ALTO, such recommendations how to generate ALTO map information. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-deployments/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-alto-deployments-13 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-deployments-13 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
- [alto] draft-ietf-alto-deployments-13 SCHARF, Michael (Michael)
- Re: [alto] draft-ietf-alto-deployments-13 Vijay K. Gurbani