[Jmap] Early draft on S/MIME signature verification to JMAP

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 05 March 2018 17:12 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 DD76412D94F for <jmap@ietfa.amsl.com>; Mon, 5 Mar 2018 09:12:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 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, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, WEIRD_QUOTING=0.001] autolearn=ham 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 R74NDq5e1u_h for <jmap@ietfa.amsl.com>; Mon, 5 Mar 2018 09:12:43 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id C4E3012D86A for <jmap@ietf.org>; Mon, 5 Mar 2018 09:12:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1520269962; d=isode.com; s=june2016; i=@isode.com; bh=/Ow39yfXB5TzRUVEFit2bJlLB/c8DbWxrHQo2ZbP25A=; 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=C3hqamUepG6Rfn6xZVUKl+VVR5sOejQKYykHZHandxv9ETfeOro86+CmYLYDK0Do1cJOLe bCJcsUWqVkcqVSwN+GVbjxXhybsF1NrwjqOovtMR2HH3/N0PDmrd8GC9K1YvlJk56LkEa+ n3P2GMva3Ph94h4Jvk3WkHNoH/TabdQ=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <Wp16igAmxXbd@statler.isode.com>; Mon, 5 Mar 2018 17:12:42 +0000
To: "jmap@ietf.org" <jmap@ietf.org>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <74eab43a-6bed-ea06-14d6-a43a37503d87@isode.com>
Date: Mon, 05 Mar 2018 17:12:39 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------B5220B8BE657A1E1D1FCAC92"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Hz4siMUwc3Sq8WN_LehrrfyWSYs>
Subject: [Jmap] Early draft on S/MIME signature verification to JMAP
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 05 Mar 2018 17:12:46 -0000

Hi,

I wrote a very early draft on how a JMAP server can return S/MIME 
signature verification status to a JMAP client. I would like to submit 
it as a working group document as a concrete proposal to start to a 
proper discussion.

Comments are welcome!


Best Regards,

Alexey