Re: [Jmap] Roman Danyliw's No Objection on draft-ietf-jmap-smime-09: (with COMMENT)

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 18 November 2021 19:21 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 B42C23A09E5; Thu, 18 Nov 2021 11:21:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.951
X-Spam-Level:
X-Spam-Status: No, score=-3.951 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=-1.852, 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 b6tl9qE63-o7; Thu, 18 Nov 2021 11:21:24 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 63A9B3A09E1; Thu, 18 Nov 2021 11:21:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1637263277; d=isode.com; s=june2016; i=@isode.com; bh=+FBajyf7C+mNWjUfKEkQ0V+A1kRVJUPdFI/Ms9yVXzM=; 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=S8P6nKL5nJ8GzAebeSk8JJ0Q+C5mIwGfvbaZPoIgyzHdWpmGVbKUIpiYqF0XLAi7O625vi gSpQyT7RuLtLRt38IrotjgKYM0yv/B2gkXhll2n35ypdbHpgYF7dce5YQzQX6i4sGrVs1P KorpTDenl8LX2sp5TPgGlGMYCiMOkaU=;
Received: from [192.168.0.5] ((unknown) [94.3.228.58]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <YZanrAAF4sAF@waldorf.isode.com>; Thu, 18 Nov 2021 19:21:17 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <1eec30c5-eca1-6b16-91f1-22a36648b01f@isode.com>
Date: Thu, 18 Nov 2021 19:21:16 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: jmap@ietf.org, draft-ietf-jmap-smime@ietf.org, jmap-chairs@ietf.org, brong@fastmailteam.com
References: <163460214370.19974.15716909300314956596@ietfa.amsl.com> <002266b6-50e4-846b-e325-86721eea8769@isode.com>
In-Reply-To: <002266b6-50e4-846b-e325-86721eea8769@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/3ltwgDtK2MBAKQY_xga7HwK38b4>
Subject: Re: [Jmap] Roman Danyliw'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, 18 Nov 2021 19:21:28 -0000

Hi Roman,

On 21/10/2021 15:16, Alexey Melnikov wrote:

> Hi Roman,
>
> On 19/10/2021 01:09, Roman Danyliw via Datatracker wrote:
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> ** Section 4.1.   Recommend sticking to verification practices by 
>> citation when
>> defining the semantics of “smimeStatus”
>>
>> OLD
>> signed/verified:  S/MIME signed message and the sender's signature
>>        was successfully verified, the sender matches the From header
>>        field, and the sender's certificate (and the certificate 
>> chain) is
>>        trusted for signing.
>>
>>     signed/failed:  S/MIME signed message, but the signature failed to
>>        verify.
>>
>> NEW
>> signed/verified:  S/MIME signed message and the sender's signature was
>> successfully verified per the verification process in [RFC8551] and 
>> [RFC8550].
>>
>> signed/failed:  S/MIME signed message, but the signature failed 
>> to      verify
>> per the processes in [RFC8551] and [RFC8550].
> [RFC8551] and [RFC8550] are already listed earlier on when smimeStatus 
> is described in more general terms, so implementing your suggestion 
> becomes less urgent. Let me think a bit more about the best way of 
> updating the draft to reflect this comment.

This should be clarified in -11.

Best Regards,

Alexey