[alto] ALTO@IETF-109

Jan Seedorf <ietf@j-f-s.de> Wed, 30 September 2020 11:29 UTC

Return-Path: <ietf@j-f-s.de>
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 806403A0C44 for <alto@ietfa.amsl.com>; Wed, 30 Sep 2020 04:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 X1MpSCOZWbGD for <alto@ietfa.amsl.com>; Wed, 30 Sep 2020 04:29:23 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.24]) (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 EFD453A0C40 for <alto@ietf.org>; Wed, 30 Sep 2020 04:29:22 -0700 (PDT)
Received: from JANs-MacBook-Pro.local ([94.134.89.195]) by mrelayeu.kundenserver.de (mreue109 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MkHEN-1kqYP33zuz-00khOb for <alto@ietf.org>; Wed, 30 Sep 2020 13:29:21 +0200
To: alto@ietf.org
From: Jan Seedorf <ietf@j-f-s.de>
Message-ID: <3a0f077d-040d-f90e-6743-e953b3c04aa0@j-f-s.de>
Date: Wed, 30 Sep 2020 13:29:20 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K1:WyffN+aMnsLubcYfEtUfaq81y35UZCOowDiAhicNxjEEte2MZt/ H2wHTUCv172BasgCptBmbnAc1oXgkjdIdAjnsvZAbS5u1cqr+3dzgZE2fSvkl6WDF5dOMD9 DWm0eku98ha+oGcqqq+yDJmGhxd+99TXRNRANaf04TSeB/XaR7o4ISQIu+7mR4D2AUqkOgz hBpPGfhtvtJpLOj8mLwZQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:U4RTao+Ka1o=:e1LYEYwH5zgHnES39mnDdQ fQ6FlSvE+SDgQZC0VQdSfSjZf5JxgYwbaK6E8OlJZkHRDFSpnPgh00FOZ802rh8sT3xJhHNLN 0hTsW/8+CZKlsqE65VcPpkkCRquWPzYYivVP8T6+UiymC/1jnbYnQki+2jCseKJA70mXRyCM4 IVm9aa3/h0U+6Tg3xfTNN7OYBq7/a5T5cldcwDBJw3MzGq9/a2G1xvzRA/6XwD5lcEotFqX5a bdGYnl54ISenvFpZGCKwRf8L+ptzaUj5Op0UetuqzalD7AJNWwTBR0wAEzzGMTIviR9KrxjKy 1+VEpALFrib7FgjAvHgXcoawqhrAA6p7qYXCcRes8+GYCdcp4tSA7TunlV6pvYpzSIs/MNmho WWi9o08bpE8KHBYmmbheyraGn21LyLhUBxWDeu5VyX15wbwVFcRm46A4Qy4Z4ZjZkBF0Pro8b tfnQ/wJK0aloOcD+E43HiioLINuSyHj3HSZvIfU0rq94KSAZ4eYB99LH+Pqd0cvEiNx8PzZPg cBQhsAxAryL/4iMuhfvr2/Hz/2ZhpjTmuGo8m9kak4I6WUGwhKGxU0tT9ZZnYY51uKBwXSeHA mfaEtuLh0CmGDtIyhJwcOfxUzjQ/I3glzKr+cIK7O2hmMfVnZnR2fapc2RORU4mCiRdmhVB16 dJqBgjHen+L0ygL4R3COPrwtmYzdRMXqzf3xuAqGxm2hthGbZ2JTWmKFLPPK6Rlk9fEnp+szk D+gPURAyvCR57Ngarep6Rj2d3a5wnZyrcN1kjtlm2AiIkKErQqbTh1fxn+qkSms6We2D2UlgE xMWXdnRPm24shoU221z0JY7gFcRuBukikOqjs89njBnY4x9LltHeQ3Pc6RSL1mdrwB7oAAO
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ZwyS2vjFDMfTXfLpmKLYN94lhDA>
Subject: [alto] ALTO@IETF-109
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: Wed, 30 Sep 2020 11:29:24 -0000

Dear all,

ALTO has a slot at IETF 109.  We would like to devote the entire slot to 
the re-charter discussion that started in IETF 108. However, we would 
like to advise that the presentation for re-charter discussion be more 
focused in this iteration as compared to the previous one, where we had 
more than 11 presentations.

It will be helpful if the re-chartering team can cluster the different 
pieces of work now proceeding as individual drafts towards a small set 
of concrete work items/milestones.  Also, a proposed new charter would 
be very helpful.

Thus, the re-chartering team can use (perhaps no more than) half an hour 
to go through the drafts, then present a proposal for a new charter, and 
then we can open up the floor for general recharter discussion, so the 
majority of the time is spent soliciting, discussing, and shaping the 
new charter and subsequent deliverables.

  - Vijay & Jan