Re: [Jmap] Mirja Kühlewind's Block on charter-ietf-jmap-01-01: (with BLOCK)

["Alexey Melnikov" <[e-mail]>]

On Thu, May 2, 2019, at 3:39 PM, Mirja Kuehlewind wrote: 
> 
> > On 2. May 2019, at 15:52, Alexey Melnikov <[e-mail]> wrote:
> > 
> > On Thu, May 2, 2019, at 2:43 PM, Mirja Kühlewind via Datatracker wrote:
> >> Mirja Kühlewind has entered the following ballot position for
> >> charter-ietf-jmap-01-01: 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:
> >> ----------------------------------------------------------------------
> >> 
> >> I actually have a question about this how new transport part:
> >> "New transports for transporting JMAP will have security properties
> >>   comparable to HTTPS. In particular they have to require TLS."
> >> Is the intention actually to have a "transport other https" or rather something
> >> on top of https? I really would like to see further explanation here what this
> >> is heading to!
> > 
> > Honestly, we only care about WSS (Websocket over TLS) transport. So maybe the charter should just say that?
> > 
> Yes, please!

Check the latest text, I just updated the Charter to read:

Extensions to the existing core and mail JMAP specifications are also
within scope for this working group, for example any additional parts
of SIEVE, IMAP, SMTP submission, as well as transport of JMAP over
WSS (WebSocket over TLS, RFC 6455).

and I removed 4).