[Jmap] Benjamin Kaduk's No Objection on charter-ietf-jmap-01-00: (with COMMENT)

Benjamin Kaduk via Datatracker <noreply@ietf.org> Thu, 11 April 2019 14:35 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: jmap-chairs@ietf.org, jmap@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <155499332551.26219.2615821249971397663.idtracker@ietfa.amsl.com>
Date: Thu, 11 Apr 2019 07:35:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/DnhI4U5GB45ISChfpTu7diNXbbo>
Subject: [Jmap] Benjamin Kaduk's No Objection on charter-ietf-jmap-01-00: (with COMMENT)

Benjamin Kaduk has entered the following ballot position for
charter-ietf-jmap-01-00: 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.)



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



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

If we're going to be talking about new transports (e.g., websockets, or the more
generic "different protocols than HTTPS"), we should say something about ensuring
that the appropriate security properties are retained in the new setup(s).

[Jmap] Benjamin Kaduk's No Objection on charter-i… Benjamin Kaduk via Datatracker