Re: [httpapi] Martin Duke's Block on charter-ietf-httpapi-00-00: (with BLOCK)

Martin Duke <martin.h.duke@gmail.com> Thu, 10 September 2020 18:38 UTC

Return-Path: <martin.h.duke@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D613A0BFA; Thu, 10 Sep 2020 11:38:09 -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 P3i3_PP4dzsZ; Thu, 10 Sep 2020 11:38:08 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 47FAA3A0B70; Thu, 10 Sep 2020 11:38:08 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id u126so8218237iod.12; Thu, 10 Sep 2020 11:38:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LWs50hKOYpE1YY/tRBuByRDJ63YYwOUDQRYVZP/xdZA=; b=Rlldyn8kbskw3QLC/5pEaw2ujXbijtwzw43YiASUXdwAvw+qHer2gy8YVER41NqRej hVUWEmHjtp0AaqDQmrb2fOn/8WZ/0NN9S73dEWhd4YutqtzB8cR+X6GVyhcDdJKNaLH9 tPdWLPPinNBUDT+aGkiGe7+Xo1eDcXgkPQ/Z3o6waPp4KJEQozhsHy2DMZG1MKfBy8FK uA/w8XJMHR2L3NitpouhzL36+MymlD2oWwolFaDjWFcxJ1ZzsBoNK3Ysfu3Tu5GKns/d tiLrELB61BM9elVqko5yZp4b+EpbdG7N0aZP/jYGt8KbMV4qv5nJSiwYy9jCH5m2qinj aPHg==
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=LWs50hKOYpE1YY/tRBuByRDJ63YYwOUDQRYVZP/xdZA=; b=GPMTRlZWDi/hoIKBEVaIiYv4wXhCeLtKT9yhXPCScIO1UacZRuhmwPHBbyCUdyzEvF IS/OgTu1+kGRTyaJ/t3g1vc/vETMQ1QrG671L1utAQ1qXoCt0nyC2XWvDcchRCF9z0iA ScFnL6d0MnihocJ3y+s+IrAfSlzAOJdggN8JyGTtMe24WtU8wN46NC/3K2anxnCMG903 ok+X4x7DRf8psRIbKrjCu3ESh6kgZoSQHvoafHCDi9FNMibZQPTkbX9qWlacvwAlGQpc YM2Bm3EbD9VOWsKYnxmbLVVnhcL4vPbaBNhIMcRLCq+jX25v8AD0MA8Mr6mnEjL0LgYk cFBA==
X-Gm-Message-State: AOAM5317T7MmwuEBzpkdjohuHluCQqBhdukKzKkCMSfj2oZk/u9xd8vZ wkmcahSMA+dggMof7I5p/cyslyJwqggZZyE9r4M=
X-Google-Smtp-Source: ABdhPJweqzqr0E+D7ElW0yHJc41M7XtNcTNM086ruODDOl4/41ONIJwFt24fn3lANTt9abfDTcojpShOGJQBIpM//C8=
X-Received: by 2002:a05:6602:2d86:: with SMTP id k6mr8868422iow.20.1599763087433; Thu, 10 Sep 2020 11:38:07 -0700 (PDT)
MIME-Version: 1.0
References: <159958075822.806.6403222206022210649@ietfa.amsl.com> <CALaySJ+avKC05HEkRXiw9qwgzMvGtwqaj=mreCc+k3WkNem99Q@mail.gmail.com> <CAM4esxT-JH5VqAnn+J+JRYMLEAGsM4-XCE+Nd8kiH_NAT42W_g@mail.gmail.com> <CALaySJLmh7RUFAwJzWmZwODm2UxzCgKpcMSy2QYfHYtOF5K5Lg@mail.gmail.com> <CAM4esxQPbMgeY=LKSpRr-016A3b4UFx-Pq3s56ggkM=NNQNUqw@mail.gmail.com> <CALaySJJgD93pAtAJRadFDKW2n9zimACufAhjpze78zum6Kc=wQ@mail.gmail.com>
In-Reply-To: <CALaySJJgD93pAtAJRadFDKW2n9zimACufAhjpze78zum6Kc=wQ@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Thu, 10 Sep 2020 11:37:57 -0700
Message-ID: <CAM4esxRus1VpFkF5QeChAJrrT_qEvmkA6tittwOkTqt_qO6oBg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>, httpapi@ietf.org, httpapi-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008d225805aef9dea9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/cLzTSAoN9acFJ_NztQbfO_TfZ4E>
Subject: Re: [httpapi] Martin Duke's Block on charter-ietf-httpapi-00-00: (with BLOCK)
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2020 18:38:10 -0000

That seems like a well-thought-out reason. Carry on.

On Thu, Sep 10, 2020 at 11:28 AM Barry Leiba <barryleiba@computer.org>
wrote:

> >> What do the two of you think about a provision to review the charter
> >> and WG progress annually, at each year's 3rd IETF meeting?
> >
> > If that's in there, I would remove my BLOCK.
>
> Thanks, Martin.
>
> > However, I wonder why we wouldn't just hold a WG forming BOF to figure
> out what
> > they're going to do, rather than form the WG and then figure out the
> initial objectives.
> > The latter has the same first meeting while also having less
> organizational overhead.
>
> Part of the point of this working group is to involve a community that
> we know is there and has work to do, but that wouldn't normally go to
> an IETF BoF.  It's not that there isn't work to do, nor that there
> aren't people prepared to do it, but that the process of getting work
> started in the IETF doesn't rope in that community.  We could try
> pushing them into that process for a BoF for this working group... or
> we can do a slight adaptation for them.  I think the latter is the
> better approach, and I think we'll need to look, moving into the
> future, at how to continue adapting in order to include different
> communities better.
>
> And I do think a "let's check and make sure this is working" thing is
> a good idea, so thanks, Martin and Alissa, for pushing on that.
>
> Barry
>