[httpapi] Magnus Westerlund's No Objection on charter-ietf-httpapi-00-00: (with COMMENT)

Magnus Westerlund via Datatracker <noreply@ietf.org> Mon, 07 September 2020 13:24 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 1A31D3A0C2E; Mon, 7 Sep 2020 06:24:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Magnus Westerlund via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: httpapi-chairs@ietf.org, httpapi@ietf.org, httpapi@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.15.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <159948508855.23108.4995171934432420015@ietfa.amsl.com>
Date: Mon, 07 Sep 2020 06:24:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/Rz-a-AMfHmmcqipupxEpnVVUw3E>
Subject: [httpapi] Magnus Westerlund'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: Mon, 07 Sep 2020 13:24:49 -0000

Magnus Westerlund 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:
----------------------------------------------------------------------

I find this bullet creating some questions:

    • Proposals for new HTTP status codes, methods, or other generic
        extensions, to be considered by the HTTP Working Group

As this is output. So this is basically a WG consensus proposal (Internet
Draft) in HTTPAPI that is then thrown over the fence to the HTTPbis WG for
consideration? In this consideration then it is up to the HTTPbis WG to do what
ever they feel about this proposal? And the status in HTTPbis will basically
that this is from the HTTPAPI WG and have the level of consensus it had. Is
there a need to actually move this bullet from the output list to instead
detail how the HTTPAPI WG can propose chagnes in HTTPbis WG scope and establish
its WG consensus prior to handing it over? Also are this expected to be
technical solutions or primarily an problem solving idea for further
development with solid use case(s) and requirements from HTTPAPI?