Re: [alto] Re-chartering guidance

"Y. Richard Yang" <yry@cs.yale.edu> Thu, 16 July 2020 23:51 UTC

Return-Path: <yang.r.yang@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 D38FE3A0E15 for <alto@ietfa.amsl.com>; Thu, 16 Jul 2020 16:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Rnr28ERUAtmb for <alto@ietfa.amsl.com>; Thu, 16 Jul 2020 16:51:55 -0700 (PDT)
Received: from mail-vs1-f51.google.com (mail-vs1-f51.google.com [209.85.217.51]) (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 A60393A0DF9 for <alto@ietf.org>; Thu, 16 Jul 2020 16:51:55 -0700 (PDT)
Received: by mail-vs1-f51.google.com with SMTP id j186so3948338vsd.10 for <alto@ietf.org>; Thu, 16 Jul 2020 16:51:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nb/o60u8dwuC+NXXgh23m/DyJjlTTKiex9XmxsYw8Ys=; b=LAcN56Tjct3r58pY+U/Pps+teU9LwgF8QfCmU4UotZSp4Crq+vfA7+oLInyNKqat26 THG9i3yzI0R9iXo+tbb2qf3s6hjfVe/BrFbdTIDT+PXBe77FlVgiv8j77/Lyb6pp23z0 n8jt4lCcNvLKELnLOrA4ai2Mws81nbquRLgqXyOqVbtp+hpeevVIXFaWMlt5pawKtMHN dM+k09EFgzv1H1ksttOvbFM7S7ufLbD/ksNMZOeGZjasaThNThWteCcQxp2YuZ0cndO6 U5eaLS8rOP51D/dYzrVbr6ICA7gd1YV87A/ONmjyg1cJL/dPLEVdnnnuECtMcS1vdAoJ ykFw==
X-Gm-Message-State: AOAM533AtNZS8T7zEaLXS3o+dcGYCsTZZRMa0OLMVyRKmcga1pVyWIBj 5iWGmdXPTD6M9G3bAKLv+e4ElDlKuv52eYh+BoM=
X-Google-Smtp-Source: ABdhPJwIZoq1fUGfXQ0d6ECwjLZosrrAo1TOtFAsuJJ7alTGt3i5o2cawRQwy+ZiKCvuoU1ZWYEozDmllX/A0AwHFlI=
X-Received: by 2002:a67:ce08:: with SMTP id s8mr5285037vsl.103.1594943514559; Thu, 16 Jul 2020 16:51:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAMMTW_K+EOBUqozE2J=vRhqJ_Y55zp3_HoKSWeA=wxK6pojMOw@mail.gmail.com>
In-Reply-To: <CAMMTW_K+EOBUqozE2J=vRhqJ_Y55zp3_HoKSWeA=wxK6pojMOw@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Thu, 16 Jul 2020 19:51:43 -0400
Message-ID: <CANUuoLrZ-YHRgrwoU1A4EA_nJbD6vtr0H1asJ-MdksPBgxaYLw@mail.gmail.com>
To: Vijay Gurbani <vijay.gurbani@gmail.com>
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009f48f605aa97b988"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/l-JM_0GlnHWknEl3_S2tyUf2tcI>
Subject: Re: [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 23:51:58 -0000

Hi Vijay, Jan, Martin,

Thanks a lot! Personally, I like the decision. It can be more efficient and
then lead to better results.

As for the discussion leader, you can be a good, natural choice :-) Other
potential candidates I see can include Sabine, Luis, Yunfei, and me, as
these four people are already quite familiar with the existing documents,
and also engaged in the many side meetings---there are multiple other
younger candidates attending the many side meetings as well, but we may
reduce their burden a bit.

My proposal is that the chairs and the AD just approach one, and I have a
strong belief that the others will just support---one very nice thing,
which I like a lot about the alto WG, is that the members have strong
collaborations and provide each other with very strong support. Hence, I
see no problem with picking any of the five. These people come from
different "segments": Sabine (Nokia, equipment), Luis (Telefonica, ISP),
Yunfei (Tencent, app), Vijay (chair), and me (academia), and a single
"leader" need the support of other segments anyway.

Just my 2cents.
Richard



On Thu, Jul 16, 2020 at 6:26 PM Vijay Gurbani <vijay.gurbani@gmail.com>
wrote:

> 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 mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>


-- 
-- 
 =====================================
| Y. Richard Yang <yry@cs.yale.edu>   |
| Professor of Computer Science       |
| http://www.cs.yale.edu/~yry/        |
 =====================================