Re: [Jmap] Call for adoption of SMIME for JMAP - reply by April 15

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 26 March 2019 12:57 UTC

Return-Path: <alexey.melnikov@isode.com>
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 74911120043 for <jmap@ietfa.amsl.com>; Tue, 26 Mar 2019 05:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 gq06hJUA9iQy for <jmap@ietfa.amsl.com>; Tue, 26 Mar 2019 05:57:24 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 63D8D120003 for <jmap@ietf.org>; Tue, 26 Mar 2019 05:57:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1553605043; d=isode.com; s=june2016; i=@isode.com; bh=twjdQmngRLI0B2PlBTkrWQMhpMf1gdC9EXj1PIduucs=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=WcFcaYDAjXGPoEdUIvE8mUsLPinJMBAEr327Al9ml+yFx1YAfKZCmgcmVbdltsbS2xPm94 AWY3tBwp4ZcIvw+QbH6lqyU36aXBu5+QkR9CrHwWv2alYbF4HYYRhZU4nkMbQkE10gOgJt ViyWjpIdXWki+0Fw0+A1IVQwL80YVGI=;
Received: from [10.7.122.94] ((unknown) [85.255.235.119]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <XJohswB61z2g@waldorf.isode.com>; Tue, 26 Mar 2019 12:57:23 +0000
X-SMTP-Protocol-Errors: NORDNS
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <b2149b39-3c75-401d-9240-1746aee0714d@gulbrandsen.priv.no>
Date: Tue, 26 Mar 2019 13:57:21 +0100
Cc: jmap@ietf.org
Message-Id: <845A6246-83F8-4870-A461-96EC84520F42@isode.com>
References: <70e1c3ec-12b0-45c0-b029-03cff062eda1@www.fastmail.com> <303176d4-1856-4b03-ab8b-d8bcf3e48ea3@gulbrandsen.priv.no> <fbb2e3bf-4933-8ad1-a07c-1559f5ffc5d7@isode.com> <b2149b39-3c75-401d-9240-1746aee0714d@gulbrandsen.priv.no>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/EgiqtWoKnGqVNoI6Gm4Df-66jv8>
Subject: Re: [Jmap] Call for adoption of SMIME for JMAP - reply by April 15
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 26 Mar 2019 12:57:33 -0000

> On 26 Mar 2019, at 13:48, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> wrote:
> 
>> On Tuesday 26 March 2019 13:40:06 CET, Alexey Melnikov wrote:
>> This would be a JMAP extension optional to implement. So I think this is
>> given.
> 
> As I understand it, you're saying that if an incoming S/MINE message is read by an S/MIME-ignorant JMAP client, then no part of the server's output for that message depends on whether the server implements this extension. Right? Then good.

Client will need to indicate that it wants this information.