Re: [Jmap] draft-ietf-jmap-smime reference to RFC 5257

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 22 October 2021 09:58 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 26B243A07AA for <jmap@ietfa.amsl.com>; Fri, 22 Oct 2021 02:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001, 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 dcMRiK4Q1xdu for <jmap@ietfa.amsl.com>; Fri, 22 Oct 2021 02:58:14 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 189183A07B2 for <jmap@ietf.org>; Fri, 22 Oct 2021 02:58:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1634896692; d=isode.com; s=june2016; i=@isode.com; bh=QGynNPQB+8NVeoiqsdQms7GAApKmYXRuHuQxy92CAaI=; 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=unHuhF3PdPMDH8Vk1gn0cK10iNGZzrv5hXsuKOzcQmfRPjIN42mcggo0HhiF/PB2v3TtGf xSxfoXJzUgOxmc94vAM3TjG+xAc0pS0PpbZFXsvEmVAQB5l/DvGA6UHou4tVmUC7I66Roz /5xgki10xYQjFHCAc2MyzGm47eI78PY=;
Received: from [192.168.1.222] (host5-81-100-13.range5-81.btcentralplus.com [5.81.100.13]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <YXKLMgABR3M-@waldorf.isode.com>; Fri, 22 Oct 2021 10:58:12 +0100
To: Bron Gondwana <brong@fastmailteam.com>, jmap@ietf.org
References: <CAL0qLwYfeXSc7KedMvXJagZeG30y53yFCEYsTUnbh9MSE8H7MQ@mail.gmail.com> <b89db747-41b9-41e9-89b0-ea2abcc52a27@dogfood.fastmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <d2bdc40f-8186-54bf-de60-9eba9882209b@isode.com>
Date: Fri, 22 Oct 2021 10:58:02 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
In-Reply-To: <b89db747-41b9-41e9-89b0-ea2abcc52a27@dogfood.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------A88738E48D450D4CBCEC9DE7"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/eVpnvdcrv0A7kDJ5KTRnyAv6sic>
Subject: Re: [Jmap] draft-ietf-jmap-smime reference to RFC 5257
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: Fri, 22 Oct 2021 09:58:20 -0000

On 22/10/2021 00:31, Bron Gondwana wrote:

> On Fri, Oct 22, 2021, at 01:45, Murray S. Kucherawy wrote:
>> Hi, me again,
>>
>> The IESG just evaluated draft-ietf-jmap-smime and the topic of its 
>> downref to RFC 5257 came up.  There's nothing wrong with the downref, 
>> we just discussed the process in this particular case because there 
>> was prior talk that this RFC should be upgraded to the standards 
>> track.  I seem to recall the vibe about this when I first asked about 
>> it was "Yes, we should do this, but not at this time." Accordingly, 
>> the IESG will be adding it to the downref registry.
>>
>> Just checking: Does JMAP plan to take up that work at some point, or 
>> is the sentiment more like "This is ripe for the standards track, and 
>> someone should do this someday, but not us"?
>>
>> Perhaps it's more aligned with EXTRA's charter?
>
> Yes, I'd say that EXTRA is the place to do the work.
Agreed.
> I'd be particularly interested in having feedback from servers that 
> don't implement it about why they haven't, if we were to do more than 
> just bless the exact existing design as non-experimental.

Implementation complexity and the need to have some kind of database was 
a concern for me when I looked at implementing this. I suppose if there 
are clients that really need this, I can be swayed.

Best Regards,

Alexey