[alto] Update on ALTO deployment considerations and map calculation draft
"Vijay K. Gurbani" <vkg@bell-labs.com> Thu, 19 November 2015 21:25 UTC
Return-Path: <vkg@bell-labs.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 3290A1B35BE for <alto@ietfa.amsl.com>; Thu, 19 Nov 2015 13:25:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.002
X-Spam-Level:
X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 NXQ9q8CVHbcl for <alto@ietfa.amsl.com>; Thu, 19 Nov 2015 13:25:26 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (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 1F5741B35BB for <alto@ietf.org>; Thu, 19 Nov 2015 13:25:25 -0800 (PST)
Received: from us70tusmtp1.zam.alcatel-lucent.com (unknown [135.5.2.63]) by Websense Email Security Gateway with ESMTPS id 08868F09D53FA for <alto@ietf.org>; Thu, 19 Nov 2015 21:25:19 +0000 (GMT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id tAJLPLMW022047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <alto@ietf.org>; Thu, 19 Nov 2015 21:25:22 GMT
Received: from [135.185.238.169] (shoonya.ih.lucent.com [135.185.238.169]) by umail.lucent.com (8.13.8/TPES) with ESMTP id tAJLPK3n019811 for <alto@ietf.org>; Thu, 19 Nov 2015 15:25:21 -0600 (CST)
To: IETF ALTO <alto@ietf.org>
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Message-ID: <564E3E40.3050905@bell-labs.com>
Date: Thu, 19 Nov 2015 15:25:20 -0600
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/alto/4NU4DdkQFYvk1ZTp10_CxaeBMi4>
Subject: [alto] Update on ALTO deployment considerations and map calculation draft
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: Thu, 19 Nov 2015 21:25:28 -0000
Folks: A quick update. You may recall that I had asked [1] the authors of draft- ietf-alto-deployments and draft-seidel-alto-map-calculation to determine whether portions from the latter draft could be included in the former. There seem to be reasonable agreement on the list that the inclusion would be a good thing. The question was whether we will issue a new WGLC for the deployment draft if it includes text from the map-calculation draft. Michael Scharf (editor of the deployment draft) is taking the lead in determining the shape of the inclusion. He will coordinate with Hans (author of the map calculation draft) and advise the working group soon as to next steps. I expect this to be soon (within days instead of months). As soon as we hear from Michael, we will move ahead with the deployment draft. [1] https://mailarchive.ietf.org/arch/msg/alto/wCdNIO6AxWUYns2A8z39oiXYBxU Thanks, - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq
- [alto] Update on ALTO deployment considerations a… Vijay K. Gurbani