[regext] Murray Kucherawy's No Objection on draft-ietf-regext-rfc7482bis-02: (with COMMENT)
Murray Kucherawy via Datatracker <noreply@ietf.org> Thu, 18 February 2021 08:29 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B38033A0DCD; Thu, 18 Feb 2021 00:29:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-regext-rfc7482bis@ietf.org, regext-chairs@ietf.org, regext@ietf.org, Mario Loffredo <mario.loffredo@iit.cnr.it>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <161363697070.28175.8388619274210761410@ietfa.amsl.com>
Date: Thu, 18 Feb 2021 00:29:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/hdNieZrfc1c0iS4c9kL5XFChBvs>
Subject: [regext] Murray Kucherawy's No Objection on draft-ietf-regext-rfc7482bis-02: (with COMMENT)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2021 08:29:31 -0000
Murray Kucherawy has entered the following ballot position for draft-ietf-regext-rfc7482bis-02: 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/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-regext-rfc7482bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I concur with Alissa and others that this should make the disposition of RFC 7482 more explicit. "REST" in the glossary is only ever used to defined the next term in it, "RESTful". It seems to me these could be consolidated. In Section 4.1: If a server receives a search request but cannot process the request because it does not support a particular style of partial match searching, it SHOULD return an HTTP 422 (Unprocessable Entity) [RFC4918] response. Why's that only a SHOULD? What else might an implementer choose to do, and why might that be a reasonable thing to do? Or if there's no good answer to this, maybe that should be a MUST? Thanks for including Section 7.
- [regext] Murray Kucherawy's No Objection on draft… Murray Kucherawy via Datatracker
- Re: [regext] Murray Kucherawy's No Objection on d… Hollenbeck, Scott
- Re: [regext] Murray Kucherawy's No Objection on d… Murray S. Kucherawy
- Re: [regext] Murray Kucherawy's No Objection on d… Jasdip Singh
- Re: [regext] Murray Kucherawy's No Objection on d… Mario Loffredo