[httpapi] Roman Danyliw's No Objection on charter-ietf-httpapi-00-00: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 09 September 2020 18:51 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 6DF733A0C99; Wed, 9 Sep 2020 11:51:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw 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: Roman Danyliw <rdd@cert.org>
Message-ID: <159967746837.8437.7601380417417968185@ietfa.amsl.com>
Date: Wed, 09 Sep 2020 11:51:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/5VkSuBYUgdnaSDN0tHxiiIlQ4DQ>
Subject: [httpapi] Roman Danyliw's No Objection on charter-ietf-httpapi-00-00: (with 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 18:51:09 -0000
Roman Danyliw has entered the following ballot position for charter-ietf-httpapi-00-00: No Objection 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/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- ** (Like Martin and Alissa) I’m having trouble discriminating what work comes to HTTPbis as opposed to this proposed WG. As written, does all HTTP for web browser go to HTTPbis; and machine-to-machine comes here? ** Per “Proposals for new HTTP status codes, methods, or other generic extensions, to be considered by the HTTP Working Group”, why would this WG propose new work for HTTPbis, instead of doing it? ** How do when know when this WG is done? ** Can the initial milestones please be added
- [httpapi] Roman Danyliw's No Objection on charter… Roman Danyliw via Datatracker
- Re: [httpapi] Roman Danyliw's No Objection on cha… Barry Leiba
- Re: [httpapi] Roman Danyliw's No Objection on cha… Mark Nottingham
- Re: [httpapi] Roman Danyliw's No Objection on cha… Barry Leiba