Re: [Jmap] Francesca Palombini's No Objection on draft-ietf-jmap-smime-09: (with COMMENT)
Alexey Melnikov <alexey.melnikov@isode.com> Thu, 21 October 2021 13:55 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 3418C3A16B5; Thu, 21 Oct 2021 06:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 wUF01EPn3PBQ; Thu, 21 Oct 2021 06:55:11 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id B24B63A16B3; Thu, 21 Oct 2021 06:55:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1634824505; d=isode.com; s=june2016; i=@isode.com; bh=qx3OVXLp4Ks2+Im0GTgd/zQIf4kIKNLXmxmWwlCgYyI=; 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=FAIeLQigxOxEMsUK23OI9vumgW2O0HxJRSLMu3hcXp78eOB3WpQ0F2Llik8q5NWm9Oxq2R oLxsTxjCuJxx23UzAy6sZSbDFiPUeHsW8NEnsmjEX6i1z5Gfu9+doEc9hn5CEwAO7Hh6yF uhIkubtAtGp2D4E7E2u2DSU+0TLJRNQ=;
Received: from [172.27.249.49] (connect.isode.net [172.20.0.43]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <YXFxOQABRy53@waldorf.isode.com>; Thu, 21 Oct 2021 14:55:05 +0100
To: Francesca Palombini <francesca.palombini@ericsson.com>, The IESG <iesg@ietf.org>
Cc: jmap@ietf.org, draft-ietf-jmap-smime@ietf.org, jmap-chairs@ietf.org, kirsty.p@ncsc.gov.uk, brong@fastmailteam.com
References: <163472447159.26572.6026957953687413364@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <c599d204-1c94-ea84-5b06-de7dd98d30e3@isode.com>
Date: Thu, 21 Oct 2021 14:55:04 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
In-Reply-To: <163472447159.26572.6026957953687413364@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/q2ba2uUC16Yd09Xbc7f4vBRCpZ4>
Subject: Re: [Jmap] Francesca Palombini's No Objection on draft-ietf-jmap-smime-09: (with COMMENT)
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: Thu, 21 Oct 2021 13:55:18 -0000
Hi Francesca, Thank you for your comments. On 20/10/2021 11:07, Francesca Palombini via Datatracker wrote: > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thank you for the work on this document. Many thanks to Kirsty Paine for the > ART ART review, and thank you Alexey for addressing Kirsty's comments. > > I have one non-DISCUSS question to which I'd really like an answer nonetheless. > Given the following text: > > [RFC8551] and [RFC8550]. Possible string values of the property are > listed below. Servers MAY return other values not defined below, as > defined in extensions to this document. > > Would it make sense to define an IANA registry for the allowed values, to > guarantee interoperability of implementations? Ok, the only thing missing from the list of choices in this document (IMHO) is encrypted+signed/verified and encrypted+signed/failed, because this document doesn't cover automatic decryption. (These are hopefully will be documented in a followup document.) I am fine with creating an IANA registry, if people prefer. Best Regards, Alexey
- [Jmap] Francesca Palombini's No Objection on draf… Francesca Palombini via Datatracker
- Re: [Jmap] Francesca Palombini's No Objection on … Alexey Melnikov