[alto] IMPORTANT: Suggestions for IETF 109 ALTO meeting

Vijay Gurbani <vijay.gurbani@gmail.com> Thu, 05 November 2020 15:36 UTC

Return-Path: <vijay.gurbani@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A9D93A1349 for <alto@ietfa.amsl.com>; Thu, 5 Nov 2020 07:36:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 43e_4cS5z_Yk for <alto@ietfa.amsl.com>; Thu, 5 Nov 2020 07:36:46 -0800 (PST)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 975023A17F7 for <alto@ietf.org>; Thu, 5 Nov 2020 07:36:10 -0800 (PST)
Received: by mail-yb1-xb33.google.com with SMTP id o70so1710184ybc.1 for <alto@ietf.org>; Thu, 05 Nov 2020 07:36:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=VvEROnrtlC3j+iR638hIsGUSjXq3R6Bombo9gBLQ61U=; b=IRwncZDyEKVU6VocuGn94clR/R1J01nuFyZO5iq/yRQdqRkLD0WwTA4sNdEee4wOn1 4oP0cEJxxjjwkoUxi//6XHWdosDaU1atGwQTNRl8TWUztpZ05xty4EKK6QWWJYzK26cV qHLM7KZ4j1OFwIllAiS2WZtLbctZgSAm9fFrwASoGoaAsid/oUJb7ibUDWECbM5uQM19 Yjj3T1mkLpLNXubFT+HMD7rlq3c9mTlVu73Yvf3Cn2SllJjtw4PsQ7OjCvKMSgjQCoMA opT7jwStS5Heb6xNRrh8qSWx4bLkEGJmLJCV9ZFy8yMG7z6tOQ9V0JruV6YDlBp9WWBW xy6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=VvEROnrtlC3j+iR638hIsGUSjXq3R6Bombo9gBLQ61U=; b=FozWjO4b2Yg6A3ljsIDaBqJ6sxfDSQya5CH5E2r+ehheNcqtVpx2Z8lSNw3odTxhWj Sckl+d02bleJwmICgCb/5x3fZb+FYY5bJoP+2aXqKI+Et+fb2/KlwtqHW8Iy/8w9vxN/ SyMlW9dXFPaGULziUlk98dRLZDSZ3PyCY/gVamx/A8JTyQW5wedIHxq/9tsgrO1DqECu K92f3X0dECv0KirVHru+Q0/CiQHl3ILrBLGfYnJySsDVgtE+mT1/sayhg84tul1v+qQB POkxclqnrhWCa4IEQmvoXqvGuysl2nq0/4LQgtpyPG+0Csw9FcEGDAwZWlLWhgiB9zap ONrg==
X-Gm-Message-State: AOAM532TqZG6IOh/6MKOzBFvLUDDzF4DKfrxE79l1XDfTHwlEqsKBidA HYarh3Ak4E32bgycjPuhSz1a0dfEEEsPQACOYMtVpvKRqkE=
X-Google-Smtp-Source: ABdhPJwRqdaJbZ00euyJaJWxtubsdumjtKkZJjOmQJZoGSck/2/mtUvBJbCsfhZrlFA1sQ8Tr3AxQuIEbrXOEVvkKXE=
X-Received: by 2002:a25:cf08:: with SMTP id f8mr3813535ybg.433.1604590564616; Thu, 05 Nov 2020 07:36:04 -0800 (PST)
MIME-Version: 1.0
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Thu, 05 Nov 2020 09:35:34 -0600
Message-ID: <CAMMTW_KL8jtKk3wrUUgdjNh7zPk0jVyKaqrfr+o7=+CAWG9ouA@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009d2cff05b35ddad1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/f7y2jh4qjAtZKbyPbk2pLr7wEOU>
Subject: [alto] IMPORTANT: Suggestions for IETF 109 ALTO meeting
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2020 15:36:48 -0000

All: We plan to devote most of the time during our IETF 109 slot to charter
discussions.

Approaching the rechartering discussion in the manner we did during IETF
108 was not very conducive as most of the time was spent in 10 - 16 slide
shows. The WG decided that we will hold a virtual interim to make progress
towards 3-5 items that can be chartered under a new charter.  Clearly a
virtual interim did not happen, but work towards winnowing down the charter
items has been going on in the Wed meeting that a subset of the WG
organizes weekly.

The intent of the meeting slot in IETF 109 will be to make progress towards
rechartering, which concretely implies that we have some charter text to
discuss and that this includes 3-5 milestones that the rechartered WG will
decide to pursue.

Writing a charter text is an art form, so my advice to the Wed meeting
group will be to devote the remaining meetings to come up with a candidate
charter text.  It won't be perfect, but it will be a starting point to host
discussions on re-chartering during IETF 109.  Please make sure that you
have 3-5 deliverables in the charter along with reasonable milestones.
Each piece of work that goes into a charter should have some thoughts
behind it, or some candidate drafts.

I don't expect IETF 109 to be the end of charter discussion, but rather it
will be the first formal introduction of the WG to the charter and should
kick off the process to arrive at a charter that has consensus of all
relevant parties involved.

Please let Jan and me know if there are any questions.

Thanks,

- vijay