[alto] Re-chartering guidance
Vijay Gurbani <vijay.gurbani@gmail.com> Thu, 16 July 2020 22:25 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 A812A3A0B0E for <alto@ietfa.amsl.com>; Thu, 16 Jul 2020 15:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, URIBL_BLOCKED=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 BabT1OacfUdH for <alto@ietfa.amsl.com>; Thu, 16 Jul 2020 15:25:47 -0700 (PDT)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 07AF43A0915 for <alto@ietf.org>; Thu, 16 Jul 2020 15:25:46 -0700 (PDT)
Received: by mail-ed1-x52f.google.com with SMTP id d16so5970872edz.12 for <alto@ietf.org>; Thu, 16 Jul 2020 15:25:46 -0700 (PDT)
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=wAJT7qFUOtkhqxGKILxtAW0D1ZnsSId66bbWkpqu+8Y=; b=bWoQ29sj1I5BBl0lu4pp5I2+aUYbcvUkTzHS8fD2DgVDgMP6/mK9FbOoy5tYJ2lNZK Ejco3O7d1ZNriFx3sHaf2q4kTEFQ9VOfq7XiqYnYA9lBoufnNpDgq6Q6ykxauF+/0RM2 PBuXJet/Kj5FiR5K3g+QZJ5xmajHb1Vu+QcAfjnVzK96XUINqbiXVWKsbKvi/XDzZnMs CvYN0JnPsGtmGLVYQJbvvHGQBaSyR7VNoCZ41xtQUYG2ypDlXI2Jat4Os69Z4VnSYt9e 5Nu75qA1l6KCkZRdSPKcpZ5uG3vxrpyHXkMthizkz1vKVcND1v/B30l7YygiHBy3otrF A1nw==
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=wAJT7qFUOtkhqxGKILxtAW0D1ZnsSId66bbWkpqu+8Y=; b=qOBWiyNB400zcclzLXUzYEVFDWgGYXW2Rnh1uCT/3/iyEwwI04LPISqp7MV+OinmGk 20Zb6nqCEt8NAMXQqAtkWsn1vt227ZKWiLJ9yOd/lVdLDQ+/EyexYnKAjLOf9Zy94Jue bDCKxWNI3XZT1QSIV63dyzEJ9EhWaJ5vU9gvh8h6Ryvmr6qO7SUassTXkp/c3I4RTXAM ly+hob8YHAT9k4480utb0RfKAX/+tzrwSkVgdlVvn1UOZbssGIGCLvS7QAwjqCHF2PTx nHmp4xYuTpII4k/Mk6CnF5246E9ka+oRolLkhmRIkOx7wA4ubNodDMJVLQn80fd/vp99 zw1Q==
X-Gm-Message-State: AOAM531H6W1nz+YNLXHdt2vlmFMSzCh/Wu4FKdKuTPuNOnF+jdvZDzwc t1GmOPjP6yYeCF2Ys/me0YZx09RRgPfGiZ0nAi/49Anw
X-Google-Smtp-Source: ABdhPJyTEVCNUb67eNwGMQQ7VC2IrGQBFPOxsmGfHPowAIdT8oWYKxTjRlWjuSL8hI1/FJdaZU4EhZLp45pUmPm5+hc=
X-Received: by 2002:a50:d09c:: with SMTP id v28mr6499123edd.58.1594938344893; Thu, 16 Jul 2020 15:25:44 -0700 (PDT)
MIME-Version: 1.0
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Thu, 16 Jul 2020 17:24:32 -0500
Message-ID: <CAMMTW_K+EOBUqozE2J=vRhqJ_Y55zp3_HoKSWeA=wxK6pojMOw@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007c750b05aa968504"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/JncRIRMqFxTREwJewsi211nNkuo>
Subject: [alto] Re-chartering guidance
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, 16 Jul 2020 22:25:49 -0000
All: As you may have noticed from the ALTO agenda, the last hour of our meeting time is devoted to re-chartering discussion. At issue is how to best use that time? I laid out the two approaches on how to use this time in [1], and subsequent to that, Jan, Martin, and I have had a quick chat on providing some guidance to the principals so the hour can be used in the most optimal manner. To summarize [1], here are the two ways: One, have individual speakers talk about their specific pieces of work, and then have a recharter discussion that tries to weave in all of the presentations. Or two, have one presenter present a coherent rechartering discussion that includes works from others, and then lead the larger discussion. The former approach has been used in the past during BoFs, but may not be as applicable to us here for reasons enunciated in [2]. This leaves the second option: have a discussion leader who will summarize existing threads of work being sought in a recharter, and drive the discussion forward. We think this is the best way to move forward on rechartering discussion. Therefore, here is a concrete proposal: - Choose one person to lead the discussion. (Call him or her the discussion leader. I note that a subset of you have started a Google doc [3] that starts collecting potential recharter discussion items.) - The discussion leader leads the discussion, and everyone who wants to contribute a presentation that will have impact on the rechartering discussion should produce 1 slide (and 1 slide only, no title slide, just a single slide that includes architecture, results, and discussions on their specific work item for rechartering). The creators of this 1-slide send it to the discussion leader [4]. - The creator of the slide may come up to the mic and speak to their slide for 1 minute (and 1 minute only). This limit will be enforced by the chairs (apologies in advance). - The remaining time after a series of 1 minute presentations will be left for the broader discussion on rechartering. We hope that this provides some structure and guidance to the rechartering discussions. Please let Jan and me know if you have any questions, and please let us know who the discussion leader will be. [1] https://mailarchive.ietf.org/arch/msg/alto/rmBGzkM6hPPXLs1r5ngplxe-7ak/ [2] We eschew the BoF approach primarily driven by time constraints: consider that I counted at least 11 drats that were identified possible recharter discussion, and a separate request for a 20 minute slot. Assuming we allocate 5 minutes to each draft, we are looking at 55 minutes already! Not to mention the 20 minute slot. Therefore, allocating time for presentations will not be possible if we want to devote most of the time to discussing the recharter. [3] https://docs.google.com/document/d/1qP9jf-CMXvNiEE3YAnApTczAE4QkBW23Q1Eg99uOaEQ/edit [4] While I do not relish being the creator of these 1 minute slides, I have found them to be very effective at focusing on the main message itself instead of meandering around. Consider these the equivalent of an "elevator pitch". Thanks, - vijay
- [alto] Re-chartering guidance Vijay Gurbani
- Re: [alto] Re-chartering guidance Y. Richard Yang
- Re: [alto] Re-chartering guidance(Internet mail) yanniszhang(张云飞)