[httpapi] Alissa Cooper's Block on charter-ietf-httpapi-00-00: (with BLOCK and COMMENT)
Alissa Cooper via Datatracker <noreply@ietf.org> Wed, 09 September 2020 14:53 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: httpapi@ietf.org
Delivered-To: httpapi@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 108453A0E4A; Wed, 9 Sep 2020 07:53:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: httpapi-chairs@ietf.org, httpapi@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.16.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <159966323879.8094.15005725001447785927@ietfa.amsl.com>
Date: Wed, 09 Sep 2020 07:53:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/psxmOqrf6gMMt2YW4jGL3QZQf_Y>
Subject: [httpapi] Alissa Cooper's Block on charter-ietf-httpapi-00-00: (with BLOCK and COMMENT)
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 09 Sep 2020 14:53:59 -0000
Alissa Cooper 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 agree with Martin. In particular, I am wondering how the WG will define "specific use cases or applications" as referred to where the text says, "this WG will not take on work items for APIs for specific use cases or applications." ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I agree with Magnus that it is unclear whether the third bullet encompasses work that the WG will do or not. The first sentence is clunky. I would suggest "In addition to its use for web browsing, HTTP is often used for machine-to-machine communication, facilitated by HTTP APIs."
- [httpapi] Alissa Cooper's Block on charter-ietf-h… Alissa Cooper via Datatracker
- Re: [httpapi] Alissa Cooper's Block on charter-ie… Mark Nottingham
- Re: [httpapi] Alissa Cooper's Block on charter-ie… Alissa Cooper
- Re: [httpapi] Alissa Cooper's Block on charter-ie… Barry Leiba
- Re: [httpapi] Alissa Cooper's Block on charter-ie… Alissa Cooper
- Re: [httpapi] Alissa Cooper's Block on charter-ie… Barry Leiba
- Re: [httpapi] Alissa Cooper's Block on charter-ie… Mark Nottingham
- Re: [httpapi] Alissa Cooper's Block on charter-ie… Barry Leiba