[alto] Work items for re-chartering
"Vijay K. Gurbani" <vkg@bell-labs.com> Thu, 23 January 2014 19:10 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 404EA1A019E for <alto@ietfa.amsl.com>; Thu, 23 Jan 2014 11:10:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 GT6LQ7NFhC58 for <alto@ietfa.amsl.com>; Thu, 23 Jan 2014 11:10:27 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 372F81A0197 for <alto@ietf.org>; Thu, 23 Jan 2014 11:10:27 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s0NJAP6c000577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Thu, 23 Jan 2014 13:10:25 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s0NJAP1L031875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Thu, 23 Jan 2014 13:10:25 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s0NJAPrb021329 for <alto@ietf.org>; Thu, 23 Jan 2014 13:10:25 -0600 (CST)
Message-ID: <52E16952.8040102@bell-labs.com>
Date: Thu, 23 Jan 2014 13:11:14 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: [alto] Work items for re-chartering
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: <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: Thu, 23 Jan 2014 19:10:33 -0000
Folks: Over the last few IETFs, Enrico and I have solicited feedback during face-to-face meetings, WG sessions, hallway conversations, ALTO mailing list and private conversations on how to move ahead with respect to adopting new work items. As we begin the charter discussions, we have identified seven work items to propose as additions to the charter. The first four of these work items are fairly uncontroversial. The last three are work items that have a monumental mind share in the ALTO working group and have been found to be extremely useful in controlled networks (e.g., VPNs). However, we have to take some care in defining these such that we do not duplicate the functionality available elsewhere (e.g., general routing) in ALTO, nor do we take on an aspect that the working group does not fully understand. Here are the seven items up for discussion: 1. Anycast-based server discovery (Presented by Reinaldo Penno in IETF 86 and appears to have some support for adoption.) 2. Third-party server discovery (Sebastian Kiesel et al. have been driving this work and it also appears to have support.) 3. Incremental ALTO map updates (Side meeting held during IETF 86; two proposals have been studied. One way forward is to use an ALTO-specific incremental update that may be more efficient, and the second approach is to simply use JSON patch.) 4. Server-initiated update notifications (Jan Seedorf and Enrico Marocco have suggested the use of Websockets; HTTP/2.0 may provide some mitigation as well.) 5. Extensions to annotate PIDs with properties (e.g., geographical locations). (Useful as an extension in controlled environments, e.g., VPNs where IP addresses are not the only form of identification. Some drafts, including draft-roome-alto-pid-properties has already started work in this direction.) 6. Extensions for cost metrics. (Some drafts, including draft-wu-alto-json-te, have started work in this direction.) 7. An ALTO format for encoding graphs. (draft-ietf-alto-protocol already recognizes the need to provide topology details that are useful in controlled environments. Richard Yang, Greg Bernstein and others have been working on the need and use cases for such an encoding. draft-yang-alto-topology is a good start. Projects like OpenDayLight and NetworkX (Python) have JSON models for graph representation. Some concrete examples of how we envision encoding graphs will be useful during list discussion.) We will like to understand whether the working group believe such additional deliverables, if included in an updated charter proposal, would allow people to do the extension work that has been repeatedly proposed. (Clarification: we are explicitly asking whether people could find such an update acceptable. We understand that anyone will have a preferred flavor of the above.) We are at a point where show of support by whoever is interested is essential for moving forward. If it turns out to be positive, Enrico and I will subsequently circulate actual text, including milestones, for a rechartering request. 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] Work items for re-chartering Vijay K. Gurbani
- Re: [alto] Work items for re-chartering Jan Seedorf
- Re: [alto] Work items for re-chartering Y. Richard Yang
- Re: [alto] Work items for re-chartering Qin Wu
- Re: [alto] Work items for re-chartering Reinaldo Penno (repenno)
- Re: [alto] Work items for re-chartering Y. Richard Yang
- Re: [alto] Work items for re-chartering Dhruv Dhody
- Re: [alto] Work items for re-chartering Songhaibin (A)
- Re: [alto] Work items for re-chartering Cao,Zhen
- Re: [alto] Work items for re-chartering Sebastian Kiesel
- Re: [alto] Work items for re-chartering Sebastian Kiesel
- Re: [alto] Work items for re-chartering Scharf, Michael (Michael)
- Re: [alto] Work items for re-chartering Scharf, Michael (Michael)
- Re: [alto] Work items for re-chartering RANDRIAMASY, SABINE (SABINE)
- Re: [alto] Work items for re-chartering Vijay K. Gurbani
- Re: [alto] Work items for re-chartering Peterson, Jon
- Re: [alto] Work items for re-chartering Reinaldo Penno (repenno)
- Re: [alto] Work items for re-chartering Wendy Roome
- Re: [alto] Work items for re-chartering Reinaldo Penno (repenno)
- Re: [alto] Work items for re-chartering Scharf, Michael (Michael)
- Re: [alto] Work items for re-chartering Greg Bernstein
- Re: [alto] Work items for re-chartering Greg Bernstein
- Re: [alto] Work items for re-chartering QIN WU
- Re: [alto] Work items for re-chartering QIN WU
- Re: [alto] Work items for re-chartering QIN WU
- Re: [alto] Work items for re-chartering Scharf, Michael (Michael)
- Re: [alto] Work items for re-chartering Vijay K. Gurbani
- Re: [alto] Work items for re-chartering Greg Bernstein
- Re: [alto] Work items for re-chartering Greg Bernstein
- Re: [alto] Work items for re-chartering Jan Medved (jmedved)
- Re: [alto] Work items for re-chartering Vijay K. Gurbani
- Re: [alto] Work items for re-chartering Greg Bernstein
- Re: [alto] Work items for re-chartering Y. Richard Yang