[Jmap] Benjamin Kaduk's Block on charter-ietf-jmap-01-00: (with BLOCK)

Benjamin Kaduk via Datatracker <noreply@ietf.org> Thu, 02 May 2019 00:08 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: <155675571560.2931.9840518132194126377.idtracker@ietfa.amsl.com>
Date: Wed, 01 May 2019 17:08:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/VjJXwp5dTeyRb8gdEygCyryO4Uk>
Subject: [Jmap] Benjamin Kaduk's Block on charter-ietf-jmap-01-00: (with BLOCK)

Benjamin Kaduk has entered the following ballot position for
charter-ietf-jmap-01-00: Block

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/



----------------------------------------------------------------------
BLOCK:
----------------------------------------------------------------------

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 Block on charter-ietf-jma… Benjamin Kaduk via Datatracker
Re: [Jmap] Benjamin Kaduk's Block on charter-ietf… Alexey Melnikov