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 17:41 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 2D11A3A0F56; Thu, 10 Sep 2020 10:41:21 -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 VyLc7TYIDHig; Thu, 10 Sep 2020 10:41:19 -0700 (PDT)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 391CE3A0F55; Thu, 10 Sep 2020 10:41:19 -0700 (PDT)
Received: by mail-il1-x133.google.com with SMTP id f82so1807765ilh.8; Thu, 10 Sep 2020 10:41:19 -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=wEikYWVa8h+kJNjVeijmCgkzR5L+0E2XMuAigTRvWpA=; b=ippTuUerx9DSfGHTZMvc4OaIdwkRJA8iUZM0jz40qDr6jr0c81rUAWRrMIA2vbstpj wQsG7hmKWBY5lbgvTPydpvw+A735OFNqrc91JWZ/186lVsFYlSrWv8ijiujimkeBlVry uz9YQGQ6JkAOr36XvIQETVORkSNoV+w+I04oQbcHQvybG166VDLo7fLxipEYb5OTR7GQ PgyJBYhT7JSIKnkkLTk9itIkZcHa/DerHmeSdcEFmfvjurnOguzFNXQgNa/rABWOuUe4 HtgbZ1Bx1mrOfjrxBdz5Z/nGnLTMv19UbapXN6zG3og52dlvQ64Gmki0O5RIE+ivzLod vJXg==
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=wEikYWVa8h+kJNjVeijmCgkzR5L+0E2XMuAigTRvWpA=; b=I+CI0z/RPL7nb1guXibcXoNLp8qH9TCYIe22GqoHDBaAbK2UrchRir5AdFQA21JZim jbTlE38dRH1OkJ6di8JNtp+S8KG9zzDR9erw0hzpDOt2yZySn5ALrvTmu+YPCT6gHV3z OTOLMhNp5vEt2pSS3qAyfm0E+d7uaOMFKKRl9QFkWUhR7mCGwkT7nX2D4pD/tH47PY2l 7aFwx3ESGNrpdaZLMYmY8/ec/f5EAXc5Eaz/sXbgTYnBjiOwJgx6Mib5yGSpgez0i74a emB5iiKEjf/66jC64rvlkMe5o28AMck5WCF5Ud55ky+KUnEBDVKPUQSit2LWjTo6l932 ihTQ==
X-Gm-Message-State: AOAM531nQezDb/dGigg2HMI0aum5dIjKuXQ3lQFrNwhCjDYALv0+EmXb Y6AQpxoy4kNN9VqcwLH83o+YB1BRfYKM/iaw1+A=
X-Google-Smtp-Source: ABdhPJy4haeNJszi8Zc2r3g1At004CpPrIxRcXLD4/otPtCW8z6oeXneegepuH+kuCL+q3YZ/aIyl3OFHTXhdNH1p8Y=
X-Received: by 2002:a92:6906:: with SMTP id e6mr8904822ilc.249.1599759678481; Thu, 10 Sep 2020 10:41:18 -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>
In-Reply-To: <CALaySJLmh7RUFAwJzWmZwODm2UxzCgKpcMSy2QYfHYtOF5K5Lg@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Thu, 10 Sep 2020 10:41:08 -0700
Message-ID: <CAM4esxQPbMgeY=LKSpRr-016A3b4UFx-Pq3s56ggkM=NNQNUqw@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="0000000000005ca94d05aef913f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/gdKLQ5vzDfVjh_jDQg8_XI7zk4E>
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 17:41:21 -0000

If that's in there, I would remove my BLOCK.

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.

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

> > I'm in the same boat as Alissa. I can live with this is a provisional
> standing WG that takes
> > whatever comes in, for now, but if there's a probation period it should
> be in the charter.
>
> 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?
>
> Barry
>
> > On Thu, Sep 10, 2020 at 9:31 AM Barry Leiba <barryleiba@computer.org>
> wrote:
> >>
> >> The -00-01 version of the proposed charter includes Mark's latest
> >> edits.  Martin, will you check it and let us know what you think?
> >>
> >> On Tue, Sep 8, 2020 at 11:59 AM Martin Duke via Datatracker
> >> <noreply@ietf.org> wrote:
> >> >
> >> > Martin Duke has entered the following ballot position for
> >> > charter-ietf-httpapi-00-00: Block
> >> >
> >> > When responding, please keep the subject line intact and reply to all
> >> > email addresses included in the To and CC lines. (Feel free to cut
> this
> >> > introductory paragraph, however.)
> >> >
> >> >
> >> >
> >> > The document, along with other ballot positions, can be found here:
> >> > https://datatracker.ietf.org/doc/charter-ietf-httpapi/
> >> >
> >> >
> >> >
> >> > ----------------------------------------------------------------------
> >> > BLOCK:
> >> > ----------------------------------------------------------------------
> >> >
> >> > I certainly support creation of a working group of this nature;
> however, from
> >> > the charter I have no idea what portion of this large problem space
> constitutes
> >> > the short-term objectives of this group.
> >> >
> >> >
> >> >
> >> >
> >> >
>