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

Raphaël Ouazana <rouazana@linagora.com> Thu, 10 December 2020 18:41 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 235123A11AB; Thu, 10 Dec 2020 10:41:05 -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 8D8fUMg53uRG; Thu, 10 Dec 2020 10:41:00 -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 C91D53A11A8; Thu, 10 Dec 2020 10:40:59 -0800 (PST)
Received: from [192.168.0.37] (91-168-246-100.subs.proxad.net [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 20497484B3; Thu, 10 Dec 2020 19:24:44 +0100 (CET)
To: =?UTF-8?Q?=c3=89ric_Vyncke?= <evyncke@cisco.com>, The IESG <iesg@ietf.org>
Cc: jmap@ietf.org, brong@fastmailteam.com, draft-ietf-jmap-mdn@ietf.org, jmap-chairs@ietf.org
References: <160138761394.8744.17976022504395989638@ietfa.amsl.com>
X-LINAGORA-Copy-Delivery-Done: 1
From: =?UTF-8?Q?Rapha=c3=abl_Ouazana?= <rouazana@linagora.com>
Message-ID: <5c52342d-d2fa-e8ec-bae9-b4b89f96659c@linagora.com>
Date: Thu, 10 Dec 2020 19:24:43 +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: <160138761394.8744.17976022504395989638@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/upEkQU650nu_XW5-EYx8jWe8dhU>
Subject: Re: [Jmap] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ietf?= =?utf-8?q?-jmap-mdn-15=3A_=28with_COMMENT=29?=
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:41:06 -0000

-- Section 2 --
> While I can guess what is meant by "foreign (non-Internet) message", a more
> formal description would probably be welcome.

I'm not sure it makes sense to explain this further, as it is a concept 
directly taken from RFC8098.

>
> -- Section 2.1 --
> Wondering whether the values in this section are case sensitive? Section 2
> clearly specifies that the fields must be lowercase. Is it useful to specify
> whether case is important in this section?
I think this is already explained in RFC8620. Basically fields are 
case-sensitive in JMAP (that differs from RFC8098, hence the explanation 
at the end of Section 2.).