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

Raphaël Ouazana <rouazana@linagora.com> Thu, 10 December 2020 18:24 UTC

Return-Path: <rouazana@linagora.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 4B0923A1184; Thu, 10 Dec 2020 10:24:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 4xiSHzBR4Uvs; Thu, 10 Dec 2020 10:24:25 -0800 (PST)
Received: from smtp.linagora.com (smtp.linagora.com [54.36.8.78]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 797C03A118B; Thu, 10 Dec 2020 10:24:20 -0800 (PST)
Received: from [192.168.0.37] (unknown [91.168.246.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.linagora.com (Postfix) with ESMTPSA id BE26E484AC; Thu, 10 Dec 2020 19:24:17 +0100 (CET)
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: jmap@ietf.org, brong@fastmailteam.com, draft-ietf-jmap-mdn@ietf.org, jmap-chairs@ietf.org
References: <160195663247.26202.9916738287258170843@ietfa.amsl.com>
X-LINAGORA-Copy-Delivery-Done: 1
From: =?UTF-8?Q?Rapha=c3=abl_Ouazana?= <rouazana@linagora.com>
Message-ID: <5aa5e288-0c15-5000-fecc-87d569dc4050@linagora.com>
Date: Thu, 10 Dec 2020 19:23:49 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <160195663247.26202.9916738287258170843@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/paRYH2VE1cz57wjFf39OaWtHasU>
Subject: Re: [Jmap] Roman Danyliw's No Objection on draft-ietf-jmap-mdn-15: (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, 10 Dec 2020 18:24:27 -0000

> ** Section 2.  Per “This property MUST NOT be null for "MDN/send", but may be
> null in the response from the "MDN/parse" method”, should a normative MAY be
> used here instead (or would that conflict with RFC8098)
Fixed.
> ** Section 2.  The guidance to reference RFC8098 for further details is
> helpful.  In addition to the guidance on case sensitivity, I would have also
> would have benefit from a bit of prose on how to convert the fields names
> between this document and RFC8098.
In other cases this is only String types, so the conversion seems very 
straightforward to me: just use the same value. But maybe I'm missing 
something?