IETF Logo Mail Archive

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

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Tue, 26 March 2019 12:48 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
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 83ADF120043 for <jmap@ietfa.amsl.com>; Tue, 26 Mar 2019 05:48:14 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no
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 G3rqygBb0og4 for <jmap@ietfa.amsl.com>; Tue, 26 Mar 2019 05:48:13 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAFF112000F for <jmap@ietf.org>; Tue, 26 Mar 2019 05:48:12 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 4BD5CC05E5; Tue, 26 Mar 2019 12:50:14 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1553604614; bh=cTilkVIeLDkWbW0/h+NfsVHqBBnj28XBrSB+7t433A8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=AG8F2gCAiPv2XwnoyrSKnLCdpdAzgRKb5Wmt3O1BjtHcpd10gCCm6zL3OU8qB5EsC x9bY02mcD40UQrD2NyI1IEghbP+fxwYWuKCqVi/b5tvDp6Cf50j6Lbg8VEBVvp789F MNaxDfQUdJIlndRnOK13J9tDJbd7ToeoTbysOy8g=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1553604613-26265-2661/9/81; Tue, 26 Mar 2019 12:50:13 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: jmap@ietf.org
Date: Tue, 26 Mar 2019 13:48:09 +0100
Mime-Version: 1.0
Message-Id: <b2149b39-3c75-401d-9240-1746aee0714d@gulbrandsen.priv.no>
In-Reply-To: <fbb2e3bf-4933-8ad1-a07c-1559f5ffc5d7@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>
User-Agent: Trojita/0.7; Qt/5.7.1; xcb; Linux; Devuan GNU/Linux 2.0 (ascii)
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/LqDaoMOyvO3nsJ0l2_4VTYsZM5E>
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:48:14 -0000

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.

Arnt

v2.23.0 | Report a Bug | By Email