[alto] IETF74 - Current status and agenda requests

Enrico Marocco <enrico.marocco@telecomitalia.it> Wed, 18 February 2009 20:30 UTC

Return-Path: <enrico.marocco@telecomitalia.it>
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 F415C28C1FA; Wed, 18 Feb 2009 12:30:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level:
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 dOLvGhyAxpeV; Wed, 18 Feb 2009 12:30:59 -0800 (PST)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by core3.amsl.com (Postfix) with ESMTP id 9379A28C205; Wed, 18 Feb 2009 12:30:58 -0800 (PST)
Received: from GRFHUB701BA020.griffon.local (10.188.101.111) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.1.336.0; Wed, 18 Feb 2009 21:31:05 +0100
Received: from [172.16.82.18] (163.162.180.246) by smtp.telecomitalia.it (10.188.101.114) with Microsoft SMTP Server (TLS) id 8.1.336.0; Wed, 18 Feb 2009 21:31:05 +0100
Message-ID: <499C7006.3070605@telecomitalia.it>
Date: Wed, 18 Feb 2009 21:31:02 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.17 (X11/20081018)
MIME-Version: 1.0
To: alto@ietf.org
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha1"; boundary="------------ms080501010809020802060405"
Cc: apps-discuss@ietf.org
Subject: [alto] IETF74 - Current status and agenda requests
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, 18 Feb 2009 20:31:00 -0000

Folks,

As you can see on the DRAFT agenda for the SF meeting, the ALTO working
group is going to meet in a 2-hour session on Thu March 26 (expect the
day to change!). Since the first deadlines are approaching fast, the
chairs would like to make the best use of meeting time to make progress
toward meeting them. Such deadlines concern the following documents:

+ problem statement: this is the milestone with higher priority (WGLC is
  supposed to start in April 09). The WG has not adopted a draft yet,
  but draft-marocco-alto-problem-statement is the strong candidate which
  has accompanied the charter in the WG creation process and which Eric
  and Jan have volunteered to take over from the original authors,
  integrating the comments received during the previous meetings and
  getting it into a much better shape. If you haven't read the latest
  version yet, please do so before the meeting, comment and help improve
  it further; or, if you really think you can't live with it, the
  meeting in SF will be probably your last chance to present an
  alternative;

+ requirements: draft-kiesel-alto-reqs was discussed during the last two
  meetings, but it seems there is still no fundamental agreement in the
  WG about the approach the requirements document should adopt. The
  situation has now been stale since Minneapolis: if you want to
  contribute to this work and have an opinion, this is the very right
  time to let the group hear it;

+ ALTO protocol: the time constraints are a bit more relaxed than for
  other documents, but here is where all the fun is! Some proposals have
  already been presented in Minneapolis and we plan to assign time to
  updates and to the more to come. People willing to contribute may do
  so reviewing and commenting on the various proposals, helping with the
  editing of existing documents (feel free to contact the authors, ask
  the chairs if unsure), or submitting their own drafts. (Advice from
  very personal experience: in case you decide to submit your
  contribution, look at the proposals already on the table and focus
  your effort on the pieces of a possible solution you are most
  interested in, explaining very well all the whys and the hows, rather
  than trying to specify THE protocol.)

Vijay, Jon and I are supposed to submit the preliminary agenda by March
11; if you want a slot, please send us a request by then.

-- 
Ciao,
Enrico