[Jmap] Barry Leiba's Yes on charter-ietf-jmap-02-00: (with COMMENT)

Barry Leiba via Datatracker <noreply@ietf.org> Tue, 03 December 2019 14:07 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 681B112004F; Tue, 3 Dec 2019 06:07:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: jmap-chairs@ietf.org, jmap@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.111.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <157538205135.24843.17780384774128724876.idtracker@ietfa.amsl.com>
Date: Tue, 03 Dec 2019 06:07:31 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/uu0KcvqvkeqFoWyrksxYpI2ygsQ>
Subject: [Jmap] Barry Leiba's Yes on charter-ietf-jmap-02-00: (with COMMENT)
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 03 Dec 2019 14:07:32 -0000

Barry Leiba has entered the following ballot position for
charter-ietf-jmap-02-00: Yes

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.)



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



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

Actually, "Yes, but..."

The concrete deliverables at the bottom include JSCalendar but not JSContact;
please add one for the latter.

That would make five concrete deliverables, of which only two (websockets and
MDNs) have milestones listed.  It would be nice to have milestones for the
others.

And there's a milestone for which there's no listed deliverable (the
implementation guidance).  I'm ambivalent here: does it make sense to list it
as a deliverable?  Or maybe it's better just to have it in the milestones, as
there is a "catch-all" deliverable that will cover it.