[Jmap] Opsdir last call review of draft-ietf-jmap-sharing-07

Linda Dunbar via Datatracker <noreply@ietf.org> Wed, 10 April 2024 16:57 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 28F33C14F698; Wed, 10 Apr 2024 09:57:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-jmap-sharing.all@ietf.org, jmap@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171276826915.3331.16058249245659792160@ietfa.amsl.com>
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Date: Wed, 10 Apr 2024 09:57:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/JFGJnZPGzeiq06BT4Gv8Z61P1AE>
Subject: [Jmap] Opsdir last call review of draft-ietf-jmap-sharing-07
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.39
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2024 16:57:49 -0000

Reviewer: Linda Dunbar
Review result: Has Issues

I have reviewed this document as part of the Ops area directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Ops area directors.
Document editors and WG chairs should treat these comments just like any other
last-call comments.

Summary: This document specifies a data model for sharing data between users
using JMAP (JSON Meta Application Protocol), aiming to establish a consistent
model for sharing across various data types.

Major Issue: I think it is necessary to have a section on Error Handling to
outline common error scenarios, categorization of error types, and recommended
actions for error resolution.

Thank you very much,

Linda Dunbar