From nobody Fri Sep 4 12:27:07 2020 Return-Path: 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 645683A0F50; Fri, 4 Sep 2020 12:27:01 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 7.15.1 Auto-Submitted: auto-generated Precedence: bulk CC: barryleiba@gmail.com, jmap@ietf.org, Bron Gondwana , brong@fastmailteam.com, draft-ietf-jmap-mdn@ietf.org, jmap-chairs@ietf.org Reply-To: last-call@ietf.org Sender: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-ID: <159924762131.32008.8044576029454770723@ietfa.amsl.com> Date: Fri, 04 Sep 2020 12:27:01 -0700 Archived-At: Subject: [Jmap] Last Call: (Handling Message Disposition Notification with JMAP) to Proposed Standard X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Sep 2020 19:27:02 -0000 The IESG has received a request from the JSON Mail Access Protocol WG (jmap) to consider the following document: - 'Handling Message Disposition Notification with JMAP' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2020-09-18. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document specifies a data model for handling Message Disposition Notifications (MDNs, RFC 8098) in the JSON Meta Application Protocol (JMAP, RFCs 8620 and 8621). The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-jmap-mdn/ No IPR declarations have been submitted directly on this I-D. From nobody Sun Sep 6 05:46:31 2020 Return-Path: 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 8B0FB3A0DD1; Sun, 6 Sep 2020 05:46:30 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.15.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <159939639047.12479.7539337766278478433@ietfa.amsl.com> Date: Sun, 06 Sep 2020 05:46:30 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-sieve-00.txt X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Sep 2020 12:46:30 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the JSON Mail Access Protocol WG of the IETF. Title : JMAP for Sieve Scripts Author : Kenneth Murchison Filename : draft-ietf-jmap-sieve-00.txt Pages : 15 Date : 2020-09-04 Abstract: This document specifies a data model for managing Sieve scripts on a server using JMAP. Open Issues o Do we need/want both "content" and "blobId" in the SieveScript object? It may be simpler to have just one way of specifying content and "blobId" is more versatile and doesn't require JSON- encoding of the content. Furthermore, use of the forthcoming(?) Blob/set method would avoid the extra roundtrip of having to upload the blob first. o Should changes made by onSuccessActivateScript be reported in the response to the client-initiated request, or via a second implicit SIeveScript/set response? o The strawman for SieveScript/test only uses blobIds. Will this have to change once the issue regarding content/blobId in SieveScript is resolved? The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-sieve/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-jmap-sieve-00 https://datatracker.ietf.org/doc/html/draft-ietf-jmap-sieve-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Sep 11 13:21:13 2020 Return-Path: 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 3C4C53A0928; Fri, 11 Sep 2020 13:21:06 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Joel Halpern via Datatracker To: Cc: draft-ietf-jmap-mdn.all@ietf.org, jmap@ietf.org, last-call@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.16.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <159985566621.15440.12924528546650487167@ietfa.amsl.com> Reply-To: Joel Halpern Date: Fri, 11 Sep 2020 13:21:06 -0700 Archived-At: Subject: [Jmap] Genart last call review of draft-ietf-jmap-mdn-15 X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Sep 2020 20:21:06 -0000 Reviewer: Joel Halpern Review result: Ready I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at . Document: draft-ietf-jmap-mdn-15 Reviewer: Joel Halpern Review Date: 2020-09-11 IETF LC End Date: 2020-09-18 IESG Telechat date: Not scheduled for a telechat Summary: This document is ready for publication as a Proposed Standard Major issues: N/A Minor issues: N/A Nits/editorial comments: N/A From nobody Mon Sep 14 04:35:29 2020 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 D64BF3A08CF for ; Mon, 14 Sep 2020 04:35:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.12 X-Spam-Level: X-Spam-Status: No, score=-2.12 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=DMCms4W2; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CUOy+4Pi Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ojANpSKehJgP for ; Mon, 14 Sep 2020 04:35:25 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9BA63A08CB for ; Mon, 14 Sep 2020 04:35:24 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4A2165C00A3 for ; Mon, 14 Sep 2020 07:35:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 14 Sep 2020 07:35:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm3; bh=T ds5lDjKr0b1TfF9bTsEc9JbiNTDkDbvZZcG+Vklr7U=; b=DMCms4W2iulHyYvZm 54WNkwVymXsO5dtFg/K/s9jHBt1FOeV30EXwd+REg26z+v4BHea3JF5BiIKbcDR8 tPckzQIAET9rX0aU53peawSkX3AOwzL9ZixCsrOQQp7Zwxm6mNXyD5UkWQUDQ0Ql jMyt6MuTFnK/C6OHY9Cvx5a21njoYzb7/Ld+vaTyTBwMsfkT7II66gCm2ryGGgco rzpFkPnqcwnyIQ11hkp7q1kjmuCCyMadrbLuBsAuRckMUHvQnW94lVOpbSTN25U0 rlXt5G8CResxah53K08d8k+sRIbM0XtKYqDVAxdI7ha/tLmXNbKD9ub8oVx2jMNy wavXw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=Tds5lDjKr0b1TfF9bTsEc9JbiNTDkDbvZZcG+Vklr 7U=; b=CUOy+4Pi4RscEc6AW/5BEFFTiyqHL0pxb/s6g2C7+lwYzwHVC8KLyx83e uq0IJxYm6HgTPxPDreKPdkcWrck/gl2IOeifYmLAkTLGLWh9FP3YMhzL6KjLRRxy 0dcRRVj9MpGoukFtagK0ZJqvkfrbDPr2WyVelkL6wFZZ5mwknjm7miCsY1CqhMZy i2D+DvoJkhdMehP0DhC6pGEAXqxo2K47+9cLS3hIL8HnyyisQ5dcFiZm3nFDCIUS Z6xWMheBB7NB1vVeicCIzXtZ0gnt/kLi5pvmgqX+G0ZKyP5Or9Nvw9rk9TEOWjRs bybbW93yD3Jee2ZWGK6bXjjmHYHHw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudeiiedggedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpefmvghnucfouhhrtghhihhsohhnuceomhhurhgthhesfhgr shhtmhgrihhlrdgtohhmqeenucggtffrrghtthgvrhhnpedvueetudegieffieetvdfhie dutedvgeejkeekudetvddvvdduteejvefghfdvkeenucffohhmrghinhepihgvthhfrdho rhhgnecukfhppeejgedrjeejrdekhedrvdehtdenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmuhhrtghhsehfrghsthhmrghilhdrtghomh X-ME-Proxy: Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id CB4AE3064682 for ; Mon, 14 Sep 2020 07:35:23 -0400 (EDT) To: jmap@ietf.org References: <159939639047.12479.7539337766278478433@ietfa.amsl.com> From: Ken Murchison Message-ID: <0493fb7f-4070-5bf7-3346-2839118b4385@fastmail.com> Date: Mon, 14 Sep 2020 07:35:23 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <159939639047.12479.7539337766278478433@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [Jmap] I-D Action: draft-ietf-jmap-sieve-00.txt X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2020 11:35:27 -0000 Note that in the process of implementing SIeveScript/test I have decided that the list of actions in the response should be an array of objects rather than an array of strings.  I will create a -01 draft with these changes soonish. On 9/6/20 8:46 AM, internet-drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the JSON Mail Access Protocol WG of the IETF. > > Title : JMAP for Sieve Scripts > Author : Kenneth Murchison > Filename : draft-ietf-jmap-sieve-00.txt > Pages : 15 > Date : 2020-09-04 > > Abstract: > This document specifies a data model for managing Sieve scripts on a > server using JMAP. > > Open Issues > > o Do we need/want both "content" and "blobId" in the SieveScript > object? It may be simpler to have just one way of specifying > content and "blobId" is more versatile and doesn't require JSON- > encoding of the content. Furthermore, use of the forthcoming(?) > Blob/set method would avoid the extra roundtrip of having to > upload the blob first. > > o Should changes made by onSuccessActivateScript be reported in the > response to the client-initiated request, or via a second implicit > SIeveScript/set response? > > o The strawman for SieveScript/test only uses blobIds. Will this > have to change once the issue regarding content/blobId in > SieveScript is resolved? > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-jmap-sieve/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-jmap-sieve-00 > https://datatracker.ietf.org/doc/html/draft-ietf-jmap-sieve-00 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > From nobody Tue Sep 22 11:35:34 2020 Return-Path: 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 3AA193A09FD; Tue, 22 Sep 2020 11:35:32 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.17.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <160079973219.9216.17349013185550397825@ietfa.amsl.com> Date: Tue, 22 Sep 2020 11:35:32 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-sieve-01.txt X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2020 18:35:32 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the JSON Mail Access Protocol WG of the IETF. Title : JMAP for Sieve Scripts Author : Kenneth Murchison Filename : draft-ietf-jmap-sieve-01.txt Pages : 20 Date : 2020-09-22 Abstract: This document specifies a data model for managing Sieve scripts on a server using JMAP. Open Issues o Do we need/want both "content" and "blobId" in the SieveScript object? It may be simpler to have just one way of specifying content and "blobId" is more versatile and doesn't require JSON- encoding of the content. Furthermore, use of the forthcoming(?) Blob/set method would avoid the extra roundtrip of having to upload the blob first. o The strawman for SieveScript/test only uses blobIds. Will this have to change once the issue regarding content/blobId in SieveScript is resolved? o Should ":fcc" and associated arguments (e.g., ":flags", ":create":, etc) reported in the /test response be in their own "fcc" sub-object rather than listed inline with the rest of the arguments for the action? The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-sieve/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-jmap-sieve-01 https://datatracker.ietf.org/doc/html/draft-ietf-jmap-sieve-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-sieve-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Sep 22 20:24:23 2020 Return-Path: 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 68B3F3A0B7D; Tue, 22 Sep 2020 20:24:21 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: brong@fastmailteam.com, jmap@ietf.org, jmap-chairs@ietf.org, barryleiba@computer.org X-Test-IDTracker: no X-IETF-IDTracker: 7.17.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <160083146090.23908.10220603788297352699@ietfa.amsl.com> Date: Tue, 22 Sep 2020 20:24:21 -0700 Archived-At: Subject: [Jmap] jmap - New Meeting Session Request for IETF 109 X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2020 03:24:21 -0000 A new meeting session request has just been submitted by Bron Gondwana, a Chair of the jmap working group. --------------------------------------------------------- Working Group Name: JSON Mail Access Protocol Area Name: Applications and Real-Time Area Session Requester: Bron Gondwana Number of Sessions: 1 Length of Session(s): 1 Hour Number of Attendees: 15 Conflicts to Avoid: Chair Conflict: calext extra Technology Overlap: uta httpbis emailcore dmarc People who must be present: Barry Leiba Alexey Melnikov Jim Fenton Neil Jenkins Bron Gondwana Resources Requested: Special Requests: --------------------------------------------------------- From nobody Tue Sep 29 06:53:38 2020 Return-Path: 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 EE2983A0CAE; Tue, 29 Sep 2020 06:53:33 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= To: "The IESG" Cc: draft-ietf-jmap-mdn@ietf.org, jmap-chairs@ietf.org, jmap@ietf.org, Bron Gondwana , brong@fastmailteam.com X-Test-IDTracker: no X-IETF-IDTracker: 7.17.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= Message-ID: <160138761394.8744.17976022504395989638@ietfa.amsl.com> Date: Tue, 29 Sep 2020 06:53:33 -0700 Archived-At: Subject: [Jmap] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ietf?= =?utf-8?q?-jmap-mdn-15=3A_=28with_COMMENT=29?= X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2020 13:53:34 -0000 Éric Vyncke has entered the following ballot position for draft-ietf-jmap-mdn-15: 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-jmap-mdn/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for the work put into this document. It is clear and easy to read. Please find below a couple of non-blocking COMMENT points. I hope that this helps to improve the document, Regards, -éric -- Section 2 -- While I can guess what is meant by "foreign (non-Internet) message", a more formal description would probably be welcome. -- Section 2.1 -- Wondering whether the values in this section are case sensitive? Section 2 clearly specifies that the fields must be lowercase. Is it useful to specify whether case is important in this section? From nobody Tue Sep 29 09:01:26 2020 Return-Path: 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 597DE3A0EDF; Tue, 29 Sep 2020 09:01:20 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Murray Kucherawy via Datatracker To: "The IESG" Cc: draft-ietf-jmap-mdn@ietf.org, jmap-chairs@ietf.org, jmap@ietf.org, Bron Gondwana X-Test-IDTracker: no X-IETF-IDTracker: 7.17.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Murray Kucherawy Message-ID: <160139528034.2924.9672441697416964848@ietfa.amsl.com> Date: Tue, 29 Sep 2020 09:01:20 -0700 Archived-At: Subject: [Jmap] Murray Kucherawy's No Objection on draft-ietf-jmap-mdn-15: (with COMMENT) X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2020 16:01:21 -0000 Murray Kucherawy has entered the following ballot position for draft-ietf-jmap-mdn-15: 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-jmap-mdn/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- There are several places in the document where "header" should be changed to "header field". In Section 2.1, I think this could be a bit clearer: OLD: The following already registered SetError would mean: NEW: In this context, the existing SetError values defined in [reference] are interpreted as follows: In Sections 2.1 and 2.2: This is totally a personal nit, and you're free to ignore me, but since I keep tripping on it I'll mention it: In various places, "id" is used as a word rather than an initialism, as in "The id of the account to use." I keep reading this as the English term from psychoanalysis rather than a truncation of "identifier". I'd probably be happier if the full word was used. Also, in the first bullet of Section 2, it's capitalized as "Id"; we should probably be consistent. In Section 3: a) s/guaranty/guarantee/ (multiple instances) b) There's an extension in Section 3.1 starting with "X-" that should probably be revisited given BCP 178. From nobody Tue Sep 29 09:19:30 2020 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 F15C13A0F03; Tue, 29 Sep 2020 09:19:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.65 X-Spam-Level: X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SczXIv8XyCMq; Tue, 29 Sep 2020 09:19:24 -0700 (PDT) Received: from mail-ej1-f47.google.com (mail-ej1-f47.google.com [209.85.218.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76C853A11E2; Tue, 29 Sep 2020 09:17:44 -0700 (PDT) Received: by mail-ej1-f47.google.com with SMTP id i26so15827091ejb.12; Tue, 29 Sep 2020 09:17:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yBUb+UvyTiR1rOtrn41yj0yOAl78GgNOvGliGEXJOSc=; b=Ln4M26qxIL52MjX/imdQ+J/wpyBgr5SlkXHoZK7klVIKuizW/HtdwFsarOYo1YiOkR wgVedS99baNcMfEdYLjGlUoWmIH9d3aEg5ef/VluxEWO5KxSfAvqCfGrjfGES0wQ9Fc/ xZVDhFSQMzXfh2uCvX1OpSZuifrHYeiIpi8F+6xpFQ5uLdmZ1Y8fd2+HXuIrOk2DfSPs jdYBIfpjSnTPwVjIgUB2DSYb3yg0Q7gB7VlxMhdSdPiuXLW2HgskCEIpMEve9nQPX4db WXXvGbwF6tqb+ndnsC5qghSvTL7zbwojSkIwWzIE+6Fgl1J0Ld7vcWsj2KtVeLo8DaHb ZCHg== X-Gm-Message-State: AOAM531jN3xrCNWlQYCnrsS/63yos/Wtt9VFyS+u2ju4FclNC3hRHD03 68600igefnzbNS2u16zdWyudWUmG5pviFQihn40pZXwy4olVcw== X-Google-Smtp-Source: ABdhPJyHpt+Ki+A0C7QgBSL1SJuziQtzptfcBctHPtSUP2mKGKjAtGJHU7NwBsAgrc6ee+ECTYswLvvZkTH49nLvUbI= X-Received: by 2002:a17:906:d97b:: with SMTP id rp27mr4878434ejb.18.1601396262696; Tue, 29 Sep 2020 09:17:42 -0700 (PDT) MIME-Version: 1.0 References: <160139528034.2924.9672441697416964848@ietfa.amsl.com> In-Reply-To: <160139528034.2924.9672441697416964848@ietfa.amsl.com> From: Barry Leiba Date: Tue, 29 Sep 2020 12:17:30 -0400 Message-ID: To: Murray Kucherawy Cc: The IESG , IETF JMAP Mailing List , Bron Gondwana , draft-ietf-jmap-mdn@ietf.org, jmap-chairs@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jmap] Murray Kucherawy's No Objection on draft-ietf-jmap-mdn-15: (with COMMENT) X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2020 16:19:25 -0000 Coupla comments: > There are several places in the document where "header" should be changed to > "header field". > b) There's an extension in Section 3.1 starting with "X-" that should probably > be revisited given BCP 178. Yes, indeed, and I'm sorry I missed these in my review. Flrg. > This is totally a personal nit, and you're free to ignore me, but since I keep > tripping on it I'll mention it: In various places, "id" is used as a word > rather than an initialism, as in "The id of the account to use." I keep > reading this as the English term from psychoanalysis rather than a truncation > of "identifier". I'd probably be happier if the full word was used. I agree that we should simply spell out "identifier", and I strongly encourage that change. > a) s/guaranty/guarantee/ (multiple instances) How US-centric of you, Murray! Barry