From neilj@fastmailteam.com Thu Apr 11 19:33:54 2024 Return-Path: X-Original-To: jmap@ietfa.amsl.com Delivered-To: jmap@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2338CC14F694; Thu, 11 Apr 2024 19:33:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.095 X-Spam-Level: X-Spam-Status: No, score=-7.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b="hY4QlxEd"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="WvGT7ZQE" Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kNbJ1rpng3jN; Thu, 11 Apr 2024 19:33:49 -0700 (PDT) Received: from fhigh4-smtp.messagingengine.com (fhigh4-smtp.messagingengine.com [103.168.172.155]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 141C7C14F689; Thu, 11 Apr 2024 19:33:45 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 25F8511401EE; Thu, 11 Apr 2024 22:33:45 -0400 (EDT) Received: from imap43 ([10.202.2.93]) by compute5.internal (MEProxy); Thu, 11 Apr 2024 22:33:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=cc:cc:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1712889225; x=1712975625; bh=xV2X8fp+2pCKvU3iuXiFBAstewcv76kxiiFUkZ7GKek=; b= hY4QlxEdGfesLYDgcIhPJvedwnCvgFNOixerLUVfhl0fHBxOroar73LJAw7A+YWW xEyGun+FR/AYfdQpkSgIUjIC9h0mfcKMUm2U0tj9YkSplQBSmIhAgyuG7LgDCArW X5MfFlG5wW/ZuQ2V9pyFhbMcS/II6xUC/VxUfVxdBt1MQ3vtGQB7RoBryww6/Bkr MI2GTjFcadUWsmiz+r+ZYZopOpQiIEq/opSGhzAbNmVZ4vZAS8NDf47LXAIDE/af xlxICEMmSwQG1fkn05j+StJOiU+fO6vIxyd8jvS90a1fouueo5NyBihUECD7nnbp PoZ0V2AMxtME2YZETi3S2Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1712889225; x=1712975625; bh=xV2X8fp+2pCKvU3iuXiFBAstewcv 76kxiiFUkZ7GKek=; b=WvGT7ZQEpwS+ob/nnhMtCv45uKDdZenmhxKwVtsmD5PP d9pAWyDqeaYx7lS8NBnIgr8Sp1jPGBvHQYyBNQDWVmPS5ESEzIVvlNbH+nGYu+fL qMsiHSCMYvhGNjFPteYojDEh1sFqNxhXet0J2oPqYDIStPnQby2GR8cSNsDMf8Iu VMkEGOoqGXoU/J1aBnizEVJTa3yvsstAi+IBDAKGjNff8rpqDfA1BDfeIiBQ+lOm 4WclXDPWwvWtP1HGB60UAP3GuKEFICJKZHI++qLXzChfik1KnsD6jOqIfeqWH5v5 LsrlXm1tM9n1QXQJ6JYgT7jzl8pdcQPg03wmo3j+2Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudeitddgvdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtsegrtderreerredtnecuhfhrohhmpedfpfgv ihhlucflvghnkhhinhhsfdcuoehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomh eqnecuggftrfgrthhtvghrnhepkedvudethfehudelfeeitddvkeetledtjedugfffveej vdejgeethfetfefggeeunecuffhomhgrihhnpehivghtfhdrohhrghenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhm rghilhhtvggrmhdrtghomh X-ME-Proxy: Feedback-ID: ibc614277:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id C10CC2D4007D; Thu, 11 Apr 2024 22:33:44 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.11.0-alpha0-379-gabd37849b7-fm-20240408.001-gabd37849 MIME-Version: 1.0 X-ThreadId: Tae8f3c8c03ed13f8 Message-Id: <8aed9135-5aeb-4fa5-b256-47c2ca719161@localhost:3000> In-Reply-To: <171276826915.3331.16058249245659792160@ietfa.amsl.com> References: <171276826915.3331.16058249245659792160@ietfa.amsl.com> Date: Fri, 12 Apr 2024 12:33:00 +1000 From: "Neil Jenkins" To: "Linda Dunbar" , ops-dir@ietf.org Cc: draft-ietf-jmap-sharing.all@ietf.org, "IETF JMAP Mailing List" , last-call@ietf.org Content-Type: multipart/alternative; boundary=859ef615745b46ae895669e02df67cfe Archived-At: Subject: Re: [Jmap] Opsdir last call review of draft-ietf-jmap-sharing-07 X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Apr 2024 02:33:54 -0000 --859ef615745b46ae895669e02df67cfe Content-Type: text/plain Hi Linda, > 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. I'm struggling a little to work out exactly what you're looking for here. This document describes a data model for sharing to be used within the JMAP (RFC8620 ) protocol, which already defines fairly comprehensively how errors should be represented at the request level , method level , and set (create/update/destroy) level . Could you possibly be more specific about where this document introduces a new error handling requirement so I can address it? Cheers, Neil. --859ef615745b46ae895669e02df67cfe Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Hi Linda,

M= ajor 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.
<= /div>

I'm struggling a little to work ou= t exactly what you're looking for here. This document describes a data m= odel for sharing to be used within the JMAP (RFC8620) protocol, which already define= s fairly comprehensively how errors should be represented at the req= uest level, method level, and set (create/update/destroy) level. Could you possibly be more specific about where this document introdu= ces a new error handling requirement so I can address it?
--859ef615745b46ae895669e02df67cfe--