[httpapi] Zaheduzzaman Sarker's No Objection on draft-ietf-httpapi-rfc7807bis-05: (with COMMENT)

Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> Wed, 15 February 2023 10:39 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 0891AC187985; Wed, 15 Feb 2023 02:39:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zaheduzzaman Sarker via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-httpapi-rfc7807bis@ietf.org, httpapi-chairs@ietf.org, httpapi@ietf.org, darrel@tavis.ca, darrel@tavis.ca
X-Test-IDTracker: no
X-IETF-IDTracker: 9.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>
Message-ID: <167645756402.56154.7528181575532667830@ietfa.amsl.com>
Date: Wed, 15 Feb 2023 02:39:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/opXtQmyXV4YCSqHZzRqaibbyAh8>
Subject: [httpapi] Zaheduzzaman Sarker's No Objection on draft-ietf-httpapi-rfc7807bis-05: (with COMMENT)
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
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, 15 Feb 2023 10:39:24 -0000

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-httpapi-rfc7807bis-05: 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.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-httpapi-rfc7807bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for working on this specification. I must say the problem details would
be equally helpful for human and non-human consumers :-).

I have following comments, where I think it will improve the document if
addressed -

  # I was expecting the examples to show one usage of the "status" member.

  # Is there a constrains that the intermediary or caches cannot be consumer of
  the problem details and must not change the contents of the problem details
  from origin server? The security considerations and the description of
  "status" member seems to expect that no one changes the problem details on
  path and consumer receives that original problem details from the origin
  server. However, I have not seen such requirement in this specification.

  # This specification needs to refer to RFC7807

  # Section 4.2, says - "When evaluating requests, the Expert(s) should
  consider community feedback, how well-defined the problem type is, and this
  specification's requirements."

    Here, the boundary of the community need to be defined specially when the
    idea is to have designated experts to do the allocation.

    Also it says - "Specification documents should be published in a stable,
    freely available manner (ideally located with a URL), but need not be
    standards".

    Here, this "need not be standards" part seems to be unnecessary as
    Specification required does not need a standard as per RFC8126, Section
    4.6. May be just better to remove the whole sentence.