
From nobody Wed Sep  1 01:13:36 2021
Return-Path: <noreply@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 85BF63A0E74; Wed,  1 Sep 2021 01:13:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Menachem Dodge via Datatracker <noreply@ietf.org>
To: <ops-dir@ietf.org>
Cc: draft-ietf-jmap-smime.all@ietf.org, jmap@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <163048401349.30297.15336218793544457746@ietfa.amsl.com>
Reply-To: Menachem Dodge <menachemdodge1@gmail.com>
Date: Wed, 01 Sep 2021 01:13:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/LIEsHR6yHCMS3APC_pMazDLNTTs>
Subject: [Jmap] Opsdir last call review of draft-ietf-jmap-smime-07
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 01 Sep 2021 08:13:34 -0000

Reviewer: Menachem Dodge
Review result: Has Nits

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

The document explains the need to add an extension to JMAP for returning S/MIME
signature verification status. The document is written clearly.

Please consider whether the document header should indicate "Updates: 8621".

Nits:

1. Section 4:  Paragraph 5 - *smimeStatusAtDelivery*:
The brackets:

OLD==> (It effectively the same as "smimeStatus" value
 calculated at the date/time of deliver, as specified by
 "receivedAt".)
Suggested==> (It is effectively the same as the "smimeStatus" value
 calculated at the date/time of delivery, as specified by "receivedAt".)

2. Section 4: Paragraph 7 beginning with ' smimeStatus: "String|null". '
OLD==> ' Client MUST treat unrecognized values as "unknown" or "signed/failed".
' SUGGESTED==> ' Clients MUST treat unrecognized values as "unknown" or
"signed/failed". '

3. Section 4: Paragraphs 8,9,10 and 11. Missing colon following the first word
of the paragraph, this word being the possible string values of the property.
 Suggest that it be:        "unknown:" , "signed:" , signed/verified:", 
 "signed/failed:"

4. It would be useful to add additional actual examples of  messages - and to
refer to them in the text. So for the paragraph on "smimeErrors" it would be
useful to refer to the Example 2 below. It would be good to have an additional
example  showing the case where: "For example, the signing certificate might be
 expired and the message From email address might not correspond to
 any of the email addresses in the signing certificate."

5. In section 6 "Security Considerations" - it would be nice to have some
additional explanation of the recommendation to cache the results for 10
minutes. Is this to be done on the server side or at the client? Should there
be a reference here to other documents on signature verification?

Thank you kindly.

Menachem Dodge



From nobody Wed Sep  1 11:48:22 2021
Return-Path: <session-request@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9568E3A1409; Wed,  1 Sep 2021 11:48:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: fenton@bluepopcorn.net, jmap-chairs@ietf.org, jmap@ietf.org, superuser@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <163052209879.14324.135071027269155470@ietfa.amsl.com>
Date: Wed, 01 Sep 2021 11:48:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/8wJImBZcJwrqE5Q8aoy-46kg8iU>
Subject: [Jmap] jmap - New Meeting Session Request for IETF 112
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 01 Sep 2021 18:48:20 -0000

A new meeting session request has just been submitted by Jim Fenton, a Chair of the jmap working group.


---------------------------------------------------------
Working Group Name: JSON Mail Access Protocol
Area Name: Applications and Real-Time Area
Session Requester: Jim Fenton


Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 20
Conflicts to Avoid: 








People who must be present:
  Alexey Melnikov
  Kenneth Murchison
  Murray Kucherawy
  Michael Douglass
  Jim Fenton
  Neil Jenkins
  Bron Gondwana
  Mario Loffredo
  Robert Stepanek
  Rene Cordier
  Joris Baum
  Hans-Jorg Happel

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Thu Sep  2 17:44:20 2021
Return-Path: <brong@fastmailteam.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 8C5613A1A2E; Thu,  2 Sep 2021 17:43:55 -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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=Na3Xhv+7; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Z6YXvx6I
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 D3362SeeEjfC; Thu,  2 Sep 2021 17:43:50 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 440943A1A2D; Thu,  2 Sep 2021 17:43:50 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 3F77832009AF; Thu,  2 Sep 2021 20:43:48 -0400 (EDT)
Received: from imap43 ([10.202.2.93]) by compute6.internal (MEProxy); Thu, 02 Sep 2021 20:43:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:date:from:to:subject :content-type; s=fm3; bh=8zNOr4bHDddzTzOFe87n3BUCVN/pXNypy4ohaJI 0eUI=; b=Na3Xhv+7NvpFUzHTn3iVc+ijM5LDq6CvLCy7dv2yTXkg+TQ8Iiq/UZi +b9QJxBjw83WFsCY8C2qU5EyEq0Qk+JcjpP3Qjezx1i9p0FUonAX5EPpB/pOVPtW 1Zphu7AflrzAcRneT8//vqdoBDGBSfZv2bGH2fUr88umaupUD74nuZKOuyhlnF99 UtnYNESQTIgeKuTI+gqE+1VZdgnBC4ZeswgEyuG/g8tsKSXuuocPg5KCQvDCpUbR aEWsi0n2Qm3lg8HLKLqxnYHLy6QfXbUeQOSwQsT/JGcb9Y1GAHHM4eXGY4sXtww7 qyIqIUS+gjuKX7oa0MhXvwAHknTBcWw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=8zNOr4bHDddzTzOFe87n3BUCVN/pX Nypy4ohaJI0eUI=; b=Z6YXvx6I+1BhhReWgTC1JCRnZD22HiAdOhzi+6csJNXV/ aB7vKc2ROJpEtcgBO8jw1NMLFgXjTTNAELh8sHfEo7kt1AUj7DTWdeYikufwtJGS WXLlqn4XaCTYUiPFH3pTIOCRUgL2x83OpskC3WV3kwhBAJ18mfr+gKH3vd5KzseA sgadVfoQa7b62jXRP35J7CjJIHf0ZvwwCYB9PQy6gpY1NpLvoo4hveI4lwe/jx9v AnT+pKs/2h/DnnXj4ZvvjJbfeNBQMknWXKdANrqKhn2mnL0usn4s1CMBPanDQnu/ OA0yFDMNJxB/CUtDyP8kCSby51TSIEVSvMgCNzJ1w==
X-ME-Sender: <xms:wm8xYTLLiCuU9C5G9-XY0qzH93LgHh96sxnQKg7M8Wz5rzMLMEiGew> <xme:wm8xYXKM22XJGC_pe4F-xyIEN5cjLKlJl9mnPLDlW1JeTO85WCeDn_QxBJQPRws_n RUNXujCHeU>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddruddviedgfeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsegrtderre erreejnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghesfhgr shhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpedtleefgeduteethf ehgedtleevhfduudfhieejgeehtdeviedttdeugfegvdejheenucffohhmrghinhepihgv thhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:wm8xYbuQIeuLlExOzN2oiwWRwUup5S122Mfs97umUdbIl5X4D8xiUA> <xmx:wm8xYcYNmiCSNPvFwHN0sUUNBwoK-15o22DObWo-35Rz_AW365fmnQ> <xmx:wm8xYaaFw-zOxJQAIaSbkPpPPYKaGmn_vdX6o_S-sZ43ejECeU9z8Q> <xmx:w28xYdzLXvUlWzZatuuTLL4cZsSvndawP_fXOq2KT5KP7rjPiP7HsA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id C9840AC0362; Thu,  2 Sep 2021 20:43:46 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-1126-g6962059b07-fm-20210901.001-g6962059b
Mime-Version: 1.0
x-forwarded-message-id: <163033223438.8507.13442799687479808565@ietfa.amsl.com>
Message-Id: <d2f32528-c4bf-4429-87f2-e08762811ea3@dogfood.fastmail.com>
Date: Fri, 03 Sep 2021 10:43:13 +1000
From: "Bron Gondwana" <brong@fastmailteam.com>
To: jmap@ietf.org, extra@ietf.org, calsify@ietf.org, sedate@ietf.org
Content-Type: multipart/alternative; boundary=b2fa47127c7f448e9ef7e1b3234a60f7
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/PtG8FgXlwOzcHnRs6GiAj_vygxM>
Subject: [Jmap] Fwd: NomCom 2021-2022 Call for Nominations
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, 03 Sep 2021 00:43:56 -0000

--b2fa47127c7f448e9ef7e1b3234a60f7
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi all members of the multiple working groups where I'm a co-chair!  I'm=
 bulk sending to all the groups in the hope that your mail client may de=
duplicate by message-id so you don't have to read this multiple times!

This is really important.  The Nomcom is seeking nominations for the lea=
dership of the IETF.  This process is how we choose who makes decisions,=
 so - if you're willing and able to serve in a leadership role at the IE=
TF, put your name up for consideration - or if you know someone who woul=
d be great - nominate them!

Also - not for now - but for next IETF, please consider volunteering for=
 the nomcom.  If you're selected it is a bunch of work, but it's the wor=
k that keeps the IETF strong and functioning - and we want the widest po=
ssible pool of volunteers in order to get a representative nomcom - so y=
our ticking that box is valuable and appreciated, even if you're not sel=
ected.

Cheers,

Bron.

P.S. please don't nominate me, I really actually don't have time to take=
 on more responsibilities.

----- Original message -----
From: NomCom Chair 2021 <nomcom-chair-2021@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: NomCom 2021-2022 Call for Nominations
Date: Tuesday, August 31, 2021 00:03

Finally! The moment we've all been waiting for:

   C A L L       F O R       N O M I N A T I O N S  ! ! !

The 2021-22 IETF Nominating Committee (NomCom) is seeking nominations=20
from now until Monday, October 11, 2021.=20

The open positions and more information are found at the NomCom web site:

https://datatracker.ietf.org/nomcom/2021/=20

They are also included below for convenience.

Nominations may be made by selecting the Nominate link at the top of the
NomCom 2021 home page, or by visiting the following URL:=20

https://datatracker.ietf.org/nomcom/2021/nominate/

Self-nomination is welcome!=20

Note:  Nominations made using the web tool require an ietf.org datatrack=
er=20
account. You can create a datatracker ietf.org account if you don't have=
 one=20
already by visiting the following URL:=20

https://datatracker.ietf.org/accounts/create/

If you are unable to use the web form, nominations may instead be made b=
y email=20
to nomcom-2021 at ietf dot org. If using email, please include the word =
"Nominate"=20
in the Subject and indicate in the email who is being nominated, their e=
mail=20
address (to confirm acceptance of the nomination), and the position for =
which you=20
are making the nomination. If you are nominating someone other than your=
self,=20
please tell us if we may tell the nominee that you were the one who made=
 the=20
nomination. If you wish to nominate someone via email for more than one=20
position, please use separate emails to do so.

Willing nominees will be asked to fill out a questionnaire specific to t=
he position=20
for which they are nominated. The finalized questionnaires will be avail=
able no=20
later than Monday, September 6, 2021 (preliminary versions are already p=
osted)=20
and have a submission deadline of Monday, October 18, 2021.=20

NomCom 2021-22 will follow the policy for "Open Disclosure of Willing=20
Nominees" described in BCP 10/RFC 8713: "The list of=20
nominees willing to be considered for positions under review in the curr=
ent=20
NomCom cycle is not confidential". Willing nominees for each position wi=
ll be=20
listed in a publicly accessible way, e.g., anyone with a datatracker acc=
ount may=20
access the lists. Additionally, the nomination form asks if we may share=
 your own=20
name with the nominee. In all other ways, the confidentiality requiremen=
ts of BCP=20
10 remain in effect. All feedback and all NomCom deliberations will rema=
in=20
confidential and will not be disclosed.

There is a field on the form you can mark in order to allow the NomCom t=
o tell=20
the nominee that you were the one who made the nomination. This defaults=
 to=20
=E2=80=9Cno=E2=80=9D - so if you don't mark the field we won=E2=80=99t t=
ell.

In order to ensure time to collect sufficient community feedback about e=
ach of=20
the willing nominees, nominations must be received by the NomCom on or b=
efore=20
Monday, October 11, 2021.

Please submit your nominations as early as possible for the sake of your=20
nominees. Note that nominations should not wait for nominee management=20
permission, as it is easier to decline the nomination than put one in la=
te.

The NomCom appoints individuals to fill open slots on the IAB, IESG, the=
 IETF=20
Trust and the LLC Board:

ART AD: 1 position
INT AD: 1 position
OPS AD: 1 position
RTG AD: 1 position
SEC AD: 1 position
TSV AD: 1 position
IETF Trust: 1 position
IETF LLC: 1 position
IAB: 6 positions

The list of people and posts whose terms end with the=20
March 2022 IETF meeting, and thus the positions for which this NomCom is=20
responsible, is:

[An asterisk (*) next to a person's name indicates they do not intend to=
 accept=20
renomination.]

LLC Board (3-year term)
Jason Livingood

IETF Trust (3-year term)
Kathleen Moriarty

IAB (2-year term)
Ben Campbell *
Cullen Jennings
Mirja K=C3=BChlewind
Jared Mauch
Tommy Pauly
Jiankang Yao

IESG (2-year term)
Murray Kucherawy, ART AD
Erik Kline, INT AD
Robert Wilton, OPS AD
Martin Vigoureux, RTG AD
Benjamin Kaduk, SEC AD *
Martin Duke, TSV AD

Please be resourceful in identifying possible candidates for these posit=
ions, as=20
developing our talent is a very crucial requirement for the IETF, and al=
so, please=20
consider accepting a nomination. You'll find extensive information about=
 specific=20
positions, in individual tabs at:=20

https://datatracker.ietf.org/nomcom/2021/requirements/=20

In addition to nominations, the NomCom seeks community input on the posi=
tions=20
themselves. We need and welcome the community's views and input on the j=
obs=20
within each organization. If you have ideas on the positions=E2=80=99 re=
sponsibilities=20
(more, less, different), please let us know.

Please send suggestions and feedback about this to nomcom-2021 at ietf d=
ot org.=20

Thank you for your help in identifying qualified nominees!=20

Thanks,

Gabriel Montenegro
IETF NomCom Chair 2021-22
nomcom-chair-2021 at ietf dot org



--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--b2fa47127c7f448e9ef7e1b3234a60f7
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">Hi all members of the multiple working groups where I'm a =
co-chair!&nbsp; I'm bulk sending to all the groups in the hope that your=
 mail client may deduplicate by message-id so you don't have to read thi=
s multiple times!<br></div><div style=3D"font-family:Arial;"><br></div><=
div style=3D"font-family:Arial;">This is really important.&nbsp; The Nom=
com is seeking nominations for the leadership of the IETF.&nbsp; This pr=
ocess is how we choose who makes decisions, so - if you're willing and a=
ble to serve in a leadership role at the IETF, put your name up for cons=
ideration - or if you know someone who would be great - nominate them!<b=
r></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-f=
amily:Arial;">Also - not for now - but for next IETF, please consider vo=
lunteering for the nomcom.&nbsp; If you're selected it is a bunch of wor=
k, but it's the work that keeps the IETF strong and functioning - and we=
 want the widest possible pool of volunteers in order to get a represent=
ative nomcom - so your ticking that box is valuable and appreciated, eve=
n if you're not selected.<br></div><div style=3D"font-family:Arial;"><br=
></div><div style=3D"font-family:Arial;">Cheers,<br></div><div style=3D"=
font-family:Arial;"><br></div><div style=3D"font-family:Arial;">Bron.<br=
></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-fa=
mily:Arial;">P.S. please don't nominate me, I really actually don't have=
 time to take on more responsibilities.<br></div><div style=3D"font-fami=
ly:Arial;"><br></div><div>----- Original message -----<br></div><div>Fro=
m: NomCom Chair 2021 &lt;<a href=3D"mailto:nomcom-chair-2021@ietf.org">n=
omcom-chair-2021@ietf.org</a>&gt;<br></div><div>To: IETF Announcement Li=
st &lt;<a href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org<=
/a>&gt;<br></div><div>Cc:&nbsp;<a href=3D"mailto:ietf@ietf.org">ietf@iet=
f.org</a><br></div><div>Subject: NomCom 2021-2022 Call for Nominations<b=
r></div><div>Date: Tuesday, August 31, 2021 00:03<br></div><div><br></di=
v><div type=3D"cite" id=3D"qt" style=3D""><div style=3D"font-family:Aria=
l;">Finally! The moment we've all been waiting for:<br></div><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">&nbsp;&=
nbsp; C A L L&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; F O R&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; N O M I N A T I O N S&nbsp; ! ! !<br></div><div styl=
e=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">The=
 2021-22 IETF Nominating Committee (NomCom) is seeking nominations&nbsp;=
<br></div><div style=3D"font-family:Arial;">from now until Monday, Octob=
er 11, 2021.&nbsp;<br></div><div style=3D"font-family:Arial;"><br></div>=
<div style=3D"font-family:Arial;">The open positions and more informatio=
n are found at the NomCom web site:<br></div><div style=3D"font-family:A=
rial;"><br></div><div style=3D"font-family:Arial;"><a href=3D"https://da=
tatracker.ietf.org/nomcom/2021/">https://datatracker.ietf.org/nomcom/202=
1/</a>&nbsp;<br></div><div style=3D"font-family:Arial;"><br></div><div s=
tyle=3D"font-family:Arial;">They are also included below for convenience=
.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"fon=
t-family:Arial;">Nominations may be made by selecting the Nominate link =
at the top of the<br></div><div style=3D"font-family:Arial;">NomCom 2021=
 home page, or by visiting the following URL:&nbsp;<br></div><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"><a href=
=3D"https://datatracker.ietf.org/nomcom/2021/nominate/">https://datatrac=
ker.ietf.org/nomcom/2021/nominate/</a><br></div><div style=3D"font-famil=
y:Arial;"><br></div><div style=3D"font-family:Arial;">Self-nomination is=
 welcome!&nbsp;<br></div><div style=3D"font-family:Arial;"><br></div><di=
v style=3D"font-family:Arial;">Note:&nbsp; Nominations made using the we=
b tool require an ietf.org datatracker&nbsp;<br></div><div style=3D"font=
-family:Arial;">account. You can create a datatracker ietf.org account i=
f you don't have one&nbsp;<br></div><div style=3D"font-family:Arial;">al=
ready by visiting the following URL:&nbsp;<br></div><div style=3D"font-f=
amily:Arial;"><br></div><div style=3D"font-family:Arial;"><a href=3D"htt=
ps://datatracker.ietf.org/accounts/create/">https://datatracker.ietf.org=
/accounts/create/</a><br></div><div style=3D"font-family:Arial;"><br></d=
iv><div style=3D"font-family:Arial;">If you are unable to use the web fo=
rm, nominations may instead be made by email&nbsp;<br></div><div style=3D=
"font-family:Arial;">to nomcom-2021 at ietf dot org. If using email, ple=
ase include the word "Nominate"&nbsp;<br></div><div style=3D"font-family=
:Arial;">in the Subject and indicate in the email who is being nominated=
, their email&nbsp;<br></div><div style=3D"font-family:Arial;">address (=
to confirm acceptance of the nomination), and the position for which you=
&nbsp;<br></div><div style=3D"font-family:Arial;">are making the nominat=
ion. If you are nominating someone other than yourself,&nbsp;<br></div><=
div style=3D"font-family:Arial;">please tell us if we may tell the nomin=
ee that you were the one who made the&nbsp;<br></div><div style=3D"font-=
family:Arial;">nomination. If you wish to nominate someone via email for=
 more than one&nbsp;<br></div><div style=3D"font-family:Arial;">position=
, please use separate emails to do so.<br></div><div style=3D"font-famil=
y:Arial;"><br></div><div style=3D"font-family:Arial;">Willing nominees w=
ill be asked to fill out a questionnaire specific to the position&nbsp;<=
br></div><div style=3D"font-family:Arial;">for which they are nominated.=
 The finalized questionnaires will be available no&nbsp;<br></div><div s=
tyle=3D"font-family:Arial;">later than Monday, September 6, 2021 (prelim=
inary versions are already posted)&nbsp;<br></div><div style=3D"font-fam=
ily:Arial;">and have a submission deadline of Monday, October 18, 2021.&=
nbsp;<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">NomCom 2021-22 will follow the policy for "Open Dis=
closure of Willing&nbsp;<br></div><div style=3D"font-family:Arial;">Nomi=
nees" described in BCP 10/RFC 8713: "The list of&nbsp;<br></div><div sty=
le=3D"font-family:Arial;">nominees willing to be considered for position=
s under review in the current&nbsp;<br></div><div style=3D"font-family:A=
rial;">NomCom cycle is not confidential". Willing nominees for each posi=
tion will be&nbsp;<br></div><div style=3D"font-family:Arial;">listed in =
a publicly accessible way, e.g., anyone with a datatracker account may&n=
bsp;<br></div><div style=3D"font-family:Arial;">access the lists. Additi=
onally, the nomination form asks if we may share your own&nbsp;<br></div=
><div style=3D"font-family:Arial;">name with the nominee. In all other w=
ays, the confidentiality requirements of BCP&nbsp;<br></div><div style=3D=
"font-family:Arial;">10 remain in effect. All feedback and all NomCom de=
liberations will remain&nbsp;<br></div><div style=3D"font-family:Arial;"=
>confidential and will not be disclosed.<br></div><div style=3D"font-fam=
ily:Arial;"><br></div><div style=3D"font-family:Arial;">There is a field=
 on the form you can mark in order to allow the NomCom to tell&nbsp;<br>=
</div><div style=3D"font-family:Arial;">the nominee that you were the on=
e who made the nomination. This defaults to&nbsp;<br></div><div style=3D=
"font-family:Arial;">=E2=80=9Cno=E2=80=9D - so if you don't mark the fie=
ld we won=E2=80=99t tell.<br></div><div style=3D"font-family:Arial;"><br=
></div><div style=3D"font-family:Arial;">In order to ensure time to coll=
ect sufficient community feedback about each of&nbsp;<br></div><div styl=
e=3D"font-family:Arial;">the willing nominees, nominations must be recei=
ved by the NomCom on or before&nbsp;<br></div><div style=3D"font-family:=
Arial;">Monday, October 11, 2021.<br></div><div style=3D"font-family:Ari=
al;"><br></div><div style=3D"font-family:Arial;">Please submit your nomi=
nations as early as possible for the sake of your&nbsp;<br></div><div st=
yle=3D"font-family:Arial;">nominees. Note that nominations should not wa=
it for nominee management&nbsp;<br></div><div style=3D"font-family:Arial=
;">permission, as it is easier to decline the nomination than put one in=
 late.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">The NomCom appoints individuals to fill open slots =
on the IAB, IESG, the IETF&nbsp;<br></div><div style=3D"font-family:Aria=
l;">Trust and the LLC Board:<br></div><div style=3D"font-family:Arial;">=
<br></div><div style=3D"font-family:Arial;">ART AD: 1 position<br></div>=
<div style=3D"font-family:Arial;">INT AD: 1 position<br></div><div style=
=3D"font-family:Arial;">OPS AD: 1 position<br></div><div style=3D"font-f=
amily:Arial;">RTG AD: 1 position<br></div><div style=3D"font-family:Aria=
l;">SEC AD: 1 position<br></div><div style=3D"font-family:Arial;">TSV AD=
: 1 position<br></div><div style=3D"font-family:Arial;">IETF Trust: 1 po=
sition<br></div><div style=3D"font-family:Arial;">IETF LLC: 1 position<b=
r></div><div style=3D"font-family:Arial;">IAB: 6 positions<br></div><div=
 style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;=
">The list of people and posts whose terms end with the&nbsp;<br></div><=
div style=3D"font-family:Arial;">March 2022 IETF meeting, and thus the p=
ositions for which this NomCom is&nbsp;<br></div><div style=3D"font-fami=
ly:Arial;">responsible, is:<br></div><div style=3D"font-family:Arial;"><=
br></div><div style=3D"font-family:Arial;">[An asterisk (*) next to a pe=
rson's name indicates they do not intend to accept&nbsp;<br></div><div s=
tyle=3D"font-family:Arial;">renomination.]<br></div><div style=3D"font-f=
amily:Arial;"><br></div><div style=3D"font-family:Arial;">LLC Board (3-y=
ear term)<br></div><div style=3D"font-family:Arial;">Jason Livingood<br>=
</div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-fam=
ily:Arial;">IETF Trust (3-year term)<br></div><div style=3D"font-family:=
Arial;">Kathleen Moriarty<br></div><div style=3D"font-family:Arial;"><br=
></div><div style=3D"font-family:Arial;">IAB (2-year term)<br></div><div=
 style=3D"font-family:Arial;">Ben Campbell *<br></div><div style=3D"font=
-family:Arial;">Cullen Jennings<br></div><div style=3D"font-family:Arial=
;">Mirja K=C3=BChlewind<br></div><div style=3D"font-family:Arial;">Jared=
 Mauch<br></div><div style=3D"font-family:Arial;">Tommy Pauly<br></div><=
div style=3D"font-family:Arial;">Jiankang Yao<br></div><div style=3D"fon=
t-family:Arial;"><br></div><div style=3D"font-family:Arial;">IESG (2-yea=
r term)<br></div><div style=3D"font-family:Arial;">Murray Kucherawy, ART=
 AD<br></div><div style=3D"font-family:Arial;">Erik Kline, INT AD<br></d=
iv><div style=3D"font-family:Arial;">Robert Wilton, OPS AD<br></div><div=
 style=3D"font-family:Arial;">Martin Vigoureux, RTG AD<br></div><div sty=
le=3D"font-family:Arial;">Benjamin Kaduk, SEC AD *<br></div><div style=3D=
"font-family:Arial;">Martin Duke, TSV AD<br></div><div style=3D"font-fam=
ily:Arial;"><br></div><div style=3D"font-family:Arial;">Please be resour=
ceful in identifying possible candidates for these positions, as&nbsp;<b=
r></div><div style=3D"font-family:Arial;">developing our talent is a ver=
y crucial requirement for the IETF, and also, please&nbsp;<br></div><div=
 style=3D"font-family:Arial;">consider accepting a nomination. You'll fi=
nd extensive information about specific&nbsp;<br></div><div style=3D"fon=
t-family:Arial;">positions, in individual tabs at:&nbsp;<br></div><div s=
tyle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">=
<a href=3D"https://datatracker.ietf.org/nomcom/2021/requirements/">https=
://datatracker.ietf.org/nomcom/2021/requirements/</a>&nbsp;<br></div><di=
v style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial=
;">In addition to nominations, the NomCom seeks community input on the p=
ositions&nbsp;<br></div><div style=3D"font-family:Arial;">themselves. We=
 need and welcome the community's views and input on the jobs&nbsp;<br><=
/div><div style=3D"font-family:Arial;">within each organization. If you =
have ideas on the positions=E2=80=99 responsibilities&nbsp;<br></div><di=
v style=3D"font-family:Arial;">(more, less, different), please let us kn=
ow.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"f=
ont-family:Arial;">Please send suggestions and feedback about this to no=
mcom-2021 at ietf dot org.&nbsp;<br></div><div style=3D"font-family:Aria=
l;"><br></div><div style=3D"font-family:Arial;">Thank you for your help =
in identifying qualified nominees!&nbsp;<br></div><div style=3D"font-fam=
ily:Arial;"><br></div><div style=3D"font-family:Arial;">Thanks,<br></div=
><div style=3D"font-family:Arial;"><br></div><div style=3D"font-family:A=
rial;">Gabriel Montenegro<br></div><div style=3D"font-family:Arial;">IET=
F NomCom Chair 2021-22<br></div><div style=3D"font-family:Arial;">nomcom=
-chair-2021 at ietf dot org<br></div><div style=3D"font-family:Arial;"><=
br></div><div style=3D"font-family:Arial;"><br></div></div><div style=3D=
"font-family:Arial;"><br></div><div id=3D"sig56629417"><div class=3D"sig=
nature">--<br></div><div class=3D"signature">&nbsp; Bron Gondwana, CEO, =
Fastmail Pty Ltd<br></div><div class=3D"signature">&nbsp; brong@fastmail=
team.com<br></div><div class=3D"signature"><br></div></div><div style=3D=
"font-family:Arial;"><br></div></body></html>
--b2fa47127c7f448e9ef7e1b3234a60f7--


From nobody Tue Sep  7 00:01:10 2021
Return-Path: <noreply@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A64DF3A0D03; Tue,  7 Sep 2021 00:00:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Peter Yee via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: draft-ietf-jmap-smime.all@ietf.org, jmap@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <163099800356.27114.17325354179624408978@ietfa.amsl.com>
Reply-To: Peter Yee <peter@akayla.com>
Date: Tue, 07 Sep 2021 00:00:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Oyjtiqutp1W7PkeZoGCrT0lRh4E>
Subject: [Jmap] Genart last call review of draft-ietf-jmap-smime-07
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 07 Sep 2021 07:00:05 -0000

Reviewer: Peter Yee
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-jmap-smime-07
Reviewer: Peter Yee
Review Date: 2021-09-06
IETF LC End Date: 2021-09-06
IESG Telechat date: Not scheduled for a telechat

Summary: This document provides a JMAP extension that allows the JMAP server to
provide its thoughts on the verification of a messages S/MIME signature.  While
the details of the extension seem fine, I'm not convinced that the rationale
for it and the consequences of trusting the server to perform the verification
are well described. [Ready with issues]

Major issues: None

Minor issues:

Page 2, section 1: There really ought to be a description of why a client would
want to do this and why it would trust the results. This is taking a decision
on something that is normally an end-to-end property of a message and
delegating its verification to a server. Is signature verification so onerous?

Page 4, smimeErrors, 3rd sentence: the error may also be in the certificate
chain.

Page 5 and 6 examples: Put an introduction before each example so the reader
knows that it is an example and what it intends to show.

Page 7, section 6: I think a stronger description of the implications of doing
server-side verification is merited. The document is written as though it is a
forgone conclusion that a client would want to do this without much explanation.

Nits/editorial comments:

General:

The use of asterisks and underscores for emphasis or for offsetting various
items is not explained. The usage is also inconsistent. I note that RFC 8621
does some of this as well, but I think it would be preferable to abstain from
extravagant use of these characters unless their significance is explained.
Sometimes items are marked with asterisks, other times with quotation marks. I
find it all rather off-putting and could not find anything in the RFC Editor's
Style Guide indicating a standardized meaning for the characters.

Do not put a colon after the title of each example (e.g., "Example 1:")

Specific:

Page 2, section 1, 2nd paragraph: insert "the" before "multipart/signed media"
and "application/pkcs7-mime".

Page 2, section 3, 1st sentence: change "the JMAP spec" to "[RFC8621]". This
obviates the need to use underscores around the following "this".

Page 3, section 4, 1st paragraph, 1st sentence: insert "the" before "Email/get".

Page 3, *smimeStatus*: insert "the" before the final '"smimeStatus"'.

Page 3, *smimeErrors*: insert "the" before the final '"smimeErrors"'.

Page 3, *smimeVerifiedAt*: insert "the" before the final '"smimeVerifiedAt"'.

Page 3, *smimeStatusAtDelivery*, 1st sentence: insert "the" before the final
'"smimeStatusAtDelivery"'.

Page 3, *smimeStatusAtDelivery*, 2nd sentence: insert "is" before "effectively
". Insert "the" before '"smimeStatus"'. Change "deliver" to "delivery".

Page 3, smimeStatus, 2nd real sentence: change "This" to "Otherwise, this".

Page 3, smimeStatus, 4th real sentence: change "Client" to "Clients".

Page 3, smimeStatus, unknown, 1st sentence: delete the comma after "signed".

Page 3, smimeStatus, unknown, 2nd sentence: insert "an" before "unknown".

Page 3, smimeStatus, signed, 2nd sentence: insert "a" before "signature".

Page 3, smimeStatus, signed/verified: insert "the" before "sender matches".
Append a comma after "field".

Page 4, 1st non-status paragraph, 1st sentence: delete the comma after
'"smimeStatus"'. Insert "is" before "calculated".

Page 4, 1st non-status paragraph, 2nd sentence: insert "the" before "S/MIME".
Change "it helps to" to "to help".

Page 4, smimeErrors, 1st sentence: insert "the" before "S/MIME".

Page 4, smimeErrors, 2nd sentence: append a comma after "I.e.".

Page 4, smimeErrors, 3rd sentence: insert "the" before "Content-Language ".

Page 4, smimeErrors, 6th sentence: insert "a" before "CRL".

Page 4, smimeVerifiedAt, 2nd sentence: insert "the" before "S/MIME".

Page 4, smimeVerifiedAt, 3rd sentence: insert "an" before "S/MIME".

Page 4, last paragraph, 1st sentence: change "it's" to "its".

Page 5, 1st paragraph: append a comma after "server".

Page 6, 1st paragraph after Example 2, 1st sentence: insert "the" before
"Email/query".

Page 7, section 6, 1st paragraph, 1st sentence: change "Server side" to
"Server-side". Insert "the" before "server".

Page 7, section 6, 2nd paragraph, 1st sentence: insert "a" before "Denial".

Page 7, section 6, 2nd paragraph, 2nd sentence: append a comma after "reason".



From nobody Tue Sep  7 05:10:15 2021
Return-Path: <brong@fastmailteam.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 367EE3A1D1D; Tue,  7 Sep 2021 05:10:06 -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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=xyYi+l1b; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ihG/hEPf
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 LzgnZXIxd4qb; Tue,  7 Sep 2021 05:10:00 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE7303A1D1B; Tue,  7 Sep 2021 05:09:55 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 823175C00B1; Tue,  7 Sep 2021 08:09:54 -0400 (EDT)
Received: from imap43 ([10.202.2.93]) by compute6.internal (MEProxy); Tue, 07 Sep 2021 08:09:54 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm3; bh=EXhN UtyZeE+wbxIUj+zDvIKPY+28VO4ZJZC5NSmcLXA=; b=xyYi+l1boFyg0UG4vHgi 0O2HiwEs9ToeIVKnkWT60I6g4peih3l3hHAFx2d1awVVvRqNAI+1ssex2hmDCmSz UEG1rx5d8jLNDOM/u7HBTghxD6rnDEefNfbfmaBMOtnVp09kP/SWylmNU7cCucpe lWQR6RIptdODR2nsD6fNFybQOdK+4ylCyz+hNMMssebj52sncfbdbSgQwzSN2D2P PK2rAcHafUE1m429uryeKhiinrYuk3uKgtMw7+v7sBXLcxVSjYataKMCiZGtyJMv Bsf6z7VP+4GgQXb+shonka2vwkMWnGNgepwQsuYUI9MF4OlkLtMk12lCwESk5mNv KQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=EXhNUt yZeE+wbxIUj+zDvIKPY+28VO4ZJZC5NSmcLXA=; b=ihG/hEPfsoUCBBq0Sm2GB0 mxKLvA0CDktGG/qJsZ3UECQxlYihInQLz3wKiGHeyVKpck/faMYxknUNGnT2L4Eq 583RYrUNRR07J4yFoRJikqXJUbgkDgzY26ZE6+XOT9jC28X3NjCsms1ow8uV8/mF D+9RqwfAsTb/SuALKRrTlKZPVEQg5KcYAStgBxD2GlZWIpnZcUa1ZzzRo28xIV3r /LibYnLXb6xH/ERtR/fcSa9+kj2oVltiZjbFGsVs6NMi/C7kUvthg1ak9PvR/GWo 72y/Yh1mnMDqwVGjviXcMifO/nbQFEHbxcz/lKYmEE/rdD6FIvknoCcsUBtiK4DQ ==
X-ME-Sender: <xms:klY3YVRbTW7LbwQOdIfxyIn941HkwFMJ_90YOFikaBeq-s8uiJM1Rg> <xme:klY3Yex2Y8im6yMnWrqpx4S75SDoeHPrQ61tAIxUVeJlR7w8w7u6e1E11GKwdaq-S 3yOqcdDZmA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudefhedghedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdeurhho nhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh eqnecuggftrfgrthhtvghrnhepvdduueeihefgvdehueeujeejuedugfeigfevteefleet feffgfdtjeejgfeuuddvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:klY3Ya0CIvD2nJMQxxbasGodJMHqYeeMSWiM_b2-KgcHc4F9wS4pTQ> <xmx:klY3YdD9QY9Tp4NYm-dD87-RppIXFdAym7uV6kV2lM_5I6J4q-u8Nw> <xmx:klY3Yei1JeH2xaaCOzMtnT49hYQvdiPJyQagQPUsP_O9oLkNB91Rgg> <xmx:klY3YRuYKpEWUT_TOKpHfM8gr43VdCE_q48Ul3iC8Vxnn70o-Jr_tw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 011BBAC0362; Tue,  7 Sep 2021 08:09:53 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-1215-g0d2d495392-fm-20210907.001-g0d2d4953
Mime-Version: 1.0
Message-Id: <ba27f05d-e2e6-42c0-8762-fa8846dcb163@dogfood.fastmail.com>
In-Reply-To: <163099800356.27114.17325354179624408978@ietfa.amsl.com>
References: <163099800356.27114.17325354179624408978@ietfa.amsl.com>
Date: Tue, 07 Sep 2021 22:09:32 +1000
From: "Bron Gondwana" <brong@fastmailteam.com>
To: "Peter Yee" <peter@akayla.com>, gen-art@ietf.org
Cc: draft-ietf-jmap-smime.all@ietf.org, jmap@ietf.org, last-call@ietf.org
Content-Type: multipart/alternative; boundary=5e097a4714564ce683a59f03d7334d95
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/noSdppvpW-_SJnc7XEarM4_kleQ>
Subject: Re: [Jmap] Genart last call review of draft-ietf-jmap-smime-07
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: Tue, 07 Sep 2021 12:10:07 -0000

--5e097a4714564ce683a59f03d7334d95
Content-Type: text/plain

On Tue, Sep 7, 2021, at 17:00, Peter Yee via Datatracker wrote:
> Summary: This document provides a JMAP extension that allows the JMAP server to
> provide its thoughts on the verification of a messages S/MIME signature.  While
> the details of the extension seem fine, I'm not convinced that the rationale
> for it and the consequences of trusting the server to perform the verification
> are well described. [Ready with issues]

Thanks for the detailed review Peter!  I'll leave the specific nits to Alexey as author.  Good point with the "rationale for trusting the server".  We did discuss this during the early meetings when this draft came up, and considered that this would most likely be used within an organisation which controls both the client and the server.  JMAP is particularly well suited to very simple and light-weight clients.

It's envisioned that JMAP clients may even be a simple widget which displays some details like mailbox counters or previews of the most recent few messages.  By having the server side do S/MIME validation, a client can simply check a property to display an icon next to a preview without being a full S/MIME client.  Obviously this isn't something you would do where you didn't trust the server absolutely!

It seems reasonable to me to add some text that summarizes this understanding in the introduction, along with the existing "requires the client to trust server verification code" in the security considerations.

Cheers,

Bron.


--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--5e097a4714564ce683a59f03d7334d95
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">On Tue, Sep 7, 2021, at 17:00, Peter Yee via Datatracker w=
rote:<br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><div style=
=3D"font-family:Arial;">Summary: This document provides a JMAP extension=
 that allows the JMAP server to<br></div><div style=3D"font-family:Arial=
;">provide its thoughts on the verification of a messages S/MIME signatu=
re.&nbsp; While<br></div><div style=3D"font-family:Arial;">the details o=
f the extension seem fine, I'm not convinced that the rationale<br></div=
><div style=3D"font-family:Arial;">for it and the consequences of trusti=
ng the server to perform the verification<br></div><div style=3D"font-fa=
mily:Arial;">are well described. [Ready with issues]<br></div></blockquo=
te><div style=3D"font-family:Arial;"><br></div><div style=3D"font-family=
:Arial;">Thanks for the detailed review Peter!&nbsp; I'll leave the spec=
ific nits to Alexey as author.&nbsp; Good point with the "rationale for =
trusting the server".&nbsp; We did discuss this during the early meeting=
s when this draft came up, and considered that this would most likely be=
 used within an organisation which controls both the client and the serv=
er.&nbsp; JMAP is particularly well suited to very simple and light-weig=
ht clients.<br></div><div style=3D"font-family:Arial;"><br></div><div st=
yle=3D"font-family:Arial;">It's envisioned that JMAP clients may even be=
 a simple widget which displays some details like mailbox counters or pr=
eviews of the most recent few messages.&nbsp; By having the server side =
do S/MIME validation, a client can simply check a property to display an=
 icon next to a preview without being a full S/MIME client.&nbsp; Obviou=
sly this isn't something you would do where you didn't trust the server =
absolutely!<br></div><div style=3D"font-family:Arial;"><br></div><div st=
yle=3D"font-family:Arial;">It seems reasonable to me to add some text th=
at summarizes this understanding in the introduction, along with the exi=
sting "requires the client to trust server verification code" in the sec=
urity considerations.<br></div><div style=3D"font-family:Arial;"><br></d=
iv><div style=3D"font-family:Arial;">Cheers,<br></div><div style=3D"font=
-family:Arial;"><br></div><div style=3D"font-family:Arial;">Bron.<br></d=
iv><div style=3D"font-family:Arial;"><br></div><div style=3D"font-family=
:Arial;"><br></div><div id=3D"sig56629417"><div class=3D"signature">--<b=
r></div><div class=3D"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty=
 Ltd<br></div><div class=3D"signature">&nbsp; brong@fastmailteam.com<br>=
</div><div class=3D"signature"><br></div></div><div style=3D"font-family=
:Arial;"><br></div></body></html>
--5e097a4714564ce683a59f03d7334d95--


From nobody Tue Sep  7 21:19:45 2021
Return-Path: <peter@akayla.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 0E0553A1609 for <jmap@ietfa.amsl.com>; Tue,  7 Sep 2021 21:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 87lMYT_aJTNU for <jmap@ietfa.amsl.com>; Tue,  7 Sep 2021 21:19:37 -0700 (PDT)
Received: from p3plsmtpa11-06.prod.phx3.secureserver.net (p3plsmtpa11-06.prod.phx3.secureserver.net [68.178.252.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A1893A1605 for <jmap@ietf.org>; Tue,  7 Sep 2021 21:19:37 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by :SMTPAUTH: with ESMTPSA id Np3gmyLzGzpsBNp3gm8QJy; Tue, 07 Sep 2021 21:19:36 -0700
X-CMAE-Analysis: v=2.4 cv=ZPYSJV3b c=1 sm=1 tr=0 ts=613839d8 a=PF7/PIuz6ZQ4FM3W1XNKAQ==:117 a=PF7/PIuz6ZQ4FM3W1XNKAQ==:17 a=DAwyPP_o2Byb1YXLmDAA:9 a=y5BvQB8iAAAA:8 a=soKBErP5AAAA:8 a=48vgC7mUAAAA:8 a=I5x1dzxZdRBEZrdVDdMA:9 a=CjuIK1q_8ugA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=XJYP7Q1AlP6hLWnz4eQA:9 a=gNsl12zxfbZoM5ie:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=0MZqME3klBJT9LKN1Q1A:22 a=HCcp_izDSj6DkKgPSDQm:22 a=w1C3t2QeGrPiZgrLijVG:22
X-SECURESERVER-ACCT: peter@akayla.com
From: "Peter Yee" <peter@akayla.com>
To: "'Bron Gondwana'" <brong@fastmailteam.com>, <gen-art@ietf.org>
Cc: <draft-ietf-jmap-smime.all@ietf.org>, <jmap@ietf.org>, <last-call@ietf.org>
References: <163099800356.27114.17325354179624408978@ietfa.amsl.com> <ba27f05d-e2e6-42c0-8762-fa8846dcb163@dogfood.fastmail.com>
In-Reply-To: <ba27f05d-e2e6-42c0-8762-fa8846dcb163@dogfood.fastmail.com>
Date: Tue, 7 Sep 2021 21:19:39 -0700
Message-ID: <005e01d7a468$bded5280$39c7f780$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005F_01D7A42E.118E7A80"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQEQWYMLf0bjUIJ3HTZqSXgZ2tNjWgJbuGForRU//ZA=
Content-Language: en-us
X-CMAE-Envelope: MS4xfEHuCZ0Is2KW8xODywYZoZBgIJR7FyQSnmdndfATyUedosvDh2d0Sf9Iuc6yZ078C90lf9jXY5PwN45rCEg+v3u4ctRZZCaBdt/vL7kqpIyyJeooBja/ V8ZMsZHPxxqEBN7l494+dvoJlKre05fySakOEBGS23RK6X0CuE+xAuUsS/3XOwU1TMgn760mQvc0sevJ2DECDkp1ML1rkf7n+ly3+h/z2REkQSk7HTXC5hjy QiUp3Ik7I37yvH+vCynXeMisa3pXpQTnDbiJ8zXo3ixoGIt0Bl4tD6/PCeLYUXr5wAsXoivSCr2jKLLRUgqtLw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/QCczm4WzeBhBSuce3VgB9ujNZxk>
Subject: Re: [Jmap] Genart last call review of draft-ietf-jmap-smime-07
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: Wed, 08 Sep 2021 04:19:42 -0000

This is a multipart message in MIME format.

------=_NextPart_000_005F_01D7A42E.118E7A80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Thanks for that Bron. I suspected there was a discussion about this topic in
the WG, but that it simply wasn't reflected in the I-D. For those of us who
haven't kept up, adding a little bit of that discussion into the
introductory material would help a lot. 

 

                                Kind regards,

                                -Peter

 

From: Bron Gondwana <brong@fastmailteam.com> 
Sent: Tuesday, September 07, 2021 5:10 AM
To: Peter Yee <peter@akayla.com>; gen-art@ietf.org
Cc: draft-ietf-jmap-smime.all@ietf.org; jmap@ietf.org; last-call@ietf.org
Subject: Re: Genart last call review of draft-ietf-jmap-smime-07

 

On Tue, Sep 7, 2021, at 17:00, Peter Yee via Datatracker wrote:

Summary: This document provides a JMAP extension that allows the JMAP server
to

provide its thoughts on the verification of a messages S/MIME signature.
While

the details of the extension seem fine, I'm not convinced that the rationale

for it and the consequences of trusting the server to perform the
verification

are well described. [Ready with issues]

 

Thanks for the detailed review Peter!  I'll leave the specific nits to
Alexey as author.  Good point with the "rationale for trusting the server".
We did discuss this during the early meetings when this draft came up, and
considered that this would most likely be used within an organisation which
controls both the client and the server.  JMAP is particularly well suited
to very simple and light-weight clients.

 

It's envisioned that JMAP clients may even be a simple widget which displays
some details like mailbox counters or previews of the most recent few
messages.  By having the server side do S/MIME validation, a client can
simply check a property to display an icon next to a preview without being a
full S/MIME client.  Obviously this isn't something you would do where you
didn't trust the server absolutely!

 

It seems reasonable to me to add some text that summarizes this
understanding in the introduction, along with the existing "requires the
client to trust server verification code" in the security considerations.

 

Cheers,

 

Bron.

 

 

--

  Bron Gondwana, CEO, Fastmail Pty Ltd

  brong@fastmailteam.com <mailto:brong@fastmailteam.com> 

 

 


------=_NextPart_000_005F_01D7A42E.118E7A80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Thanks for =
that Bron. I suspected there was a discussion about this topic in the =
WG, but that it simply wasn&#8217;t reflected in the I-D. For those of =
us who haven&#8217;t kept up, adding a little bit of that discussion =
into the introductory material would help a lot. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Kind =
regards,<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-Peter<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b>From:</b> Bron Gondwana =
&lt;brong@fastmailteam.com&gt; <br><b>Sent:</b> Tuesday, September 07, =
2021 5:10 AM<br><b>To:</b> Peter Yee &lt;peter@akayla.com&gt;; =
gen-art@ietf.org<br><b>Cc:</b> draft-ietf-jmap-smime.all@ietf.org; =
jmap@ietf.org; last-call@ietf.org<br><b>Subject:</b> Re: Genart last =
call review of draft-ietf-jmap-smime-07<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>On Tue, Sep 7, 2021, at 17:00, =
Peter Yee via Datatracker wrote:<o:p></o:p></span></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt' id=3Dqt><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>Summary: This document provides =
a JMAP extension that allows the JMAP server =
to<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>provide its thoughts on the =
verification of a messages S/MIME signature.&nbsp; =
While<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>the details of the extension =
seem fine, I'm not convinced that the =
rationale<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>for it and the consequences of =
trusting the server to perform the =
verification<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>are well described. [Ready with =
issues]<o:p></o:p></span></p></div></blockquote><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>Thanks for the detailed review =
Peter!&nbsp; I'll leave the specific nits to Alexey as author.&nbsp; =
Good point with the &quot;rationale for trusting the server&quot;.&nbsp; =
We did discuss this during the early meetings when this draft came up, =
and considered that this would most likely be used within an =
organisation which controls both the client and the server.&nbsp; JMAP =
is particularly well suited to very simple and light-weight =
clients.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>It's envisioned that JMAP =
clients may even be a simple widget which displays some details like =
mailbox counters or previews of the most recent few messages.&nbsp; By =
having the server side do S/MIME validation, a client can simply check a =
property to display an icon next to a preview without being a full =
S/MIME client.&nbsp; Obviously this isn't something you would do where =
you didn't trust the server =
absolutely!<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>It seems reasonable to me to =
add some text that summarizes this understanding in the introduction, =
along with the existing &quot;requires the client to trust server =
verification code&quot; in the security =
considerations.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>Cheers,<o:p></o:p></span></p></d=
iv><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'>Bron.<o:p></o:p></span></p></div=
><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v><div id=3Dsig56629417><div><p =
class=3DMsoNormal>--<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp; Bron Gondwana, CEO, Fastmail Pty =
Ltd<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp; <a =
href=3D"mailto:brong@fastmailteam.com">brong@fastmailteam.com</a><o:p></o=
:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial",sans-serif'><o:p>&nbsp;</o:p></span></p></di=
v></div></body></html>
------=_NextPart_000_005F_01D7A42E.118E7A80--


From nobody Fri Sep 10 07:22:15 2021
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 C25D53A0781; Fri, 10 Sep 2021 07:22:12 -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 ofQwJ39NS-MS; Fri, 10 Sep 2021 07:22:08 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 031443A077E; Fri, 10 Sep 2021 07:22:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1631283725; d=isode.com; s=june2016; i=@isode.com; bh=VrqX1tcHsYPKCWOZBrpf1Ja5FEg6T2abFsMsolRmIiA=; 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=cxufgtw+9jDJmFn/GfxADYTwEr8wYzMQEaWmbDJOlrW9ntflyFgwa6uIOGiS2jETKiD3F0 JgXQx/k2FXZFHpIHzNMPoTiXLJdNjjaHjT05XIuAhiAJsZbub5Miw7Pv1lWFJPDmMpb2Fy 3puCfgRozer5HCy2kwqkxncbQ7OB5no=;
Received: from [192.168.1.222] (host5-81-100-126.range5-81.btcentralplus.com [5.81.100.126])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YTtqDAABR2DJ@waldorf.isode.com>; Fri, 10 Sep 2021 15:22:04 +0100
To: Peter Yee <peter@akayla.com>, gen-art@ietf.org
Cc: draft-ietf-jmap-smime.all@ietf.org, jmap@ietf.org, last-call@ietf.org
References: <163099800356.27114.17325354179624408978@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <c17f4340-8bc5-8c98-0538-72332b223378@isode.com>
Date: Fri, 10 Sep 2021 15:21:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
In-Reply-To: <163099800356.27114.17325354179624408978@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/_wS5ojPe1oqhH21TzlwLspuV0kw>
Subject: Re: [Jmap] Genart last call review of draft-ietf-jmap-smime-07
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, 10 Sep 2021 14:22:13 -0000

Hi Peter,

Thank you for your review.

On 07/09/2021 08:00, Peter Yee via Datatracker wrote:
> Reviewer: Peter Yee
> Review result: Ready with Issues
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-jmap-smime-07
> Reviewer: Peter Yee
> Review Date: 2021-09-06
> IETF LC End Date: 2021-09-06
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: This document provides a JMAP extension that allows the JMAP server to
> provide its thoughts on the verification of a messages S/MIME signature.  While
> the details of the extension seem fine, I'm not convinced that the rationale
> for it and the consequences of trusting the server to perform the verification
> are well described. [Ready with issues]
>
> Major issues: None
>
> Minor issues:
>
> Page 2, section 1: There really ought to be a description of why a client would
> want to do this and why it would trust the results. This is taking a decision
> on something that is normally an end-to-end property of a message and
> delegating its verification to a server. Is signature verification so onerous?
I think this depends on the goals. There is cost of writing/testing the 
code, as well as the cost of bandwidth. For clients that try to minimize 
bandwidth used to display a message, client side S/MIME signature 
verification in the most generic case is very expensive, as it requires 
downloading the whole message, even body parts that the user doesn't 
necessarily care about. (JMAP's philosophy is to only download 
information that is needed, which is much smaller than the whole message 
content).
> Page 4, smimeErrors, 3rd sentence: the error may also be in the certificate
> chain.
Added, thanks.
> Page 5 and 6 examples: Put an introduction before each example so the reader
> knows that it is an example and what it intends to show.
Added.
> Page 7, section 6: I think a stronger description of the implications of doing
> server-side verification is merited. The document is written as though it is a
> forgone conclusion that a client would want to do this without much explanation.
Fair enough. I think your exchange with Bron has some good suggestions.
> Nits/editorial comments:
>
> General:
>
> The use of asterisks and underscores for emphasis or for offsetting various
> items is not explained. The usage is also inconsistent. I note that RFC 8621
> does some of this as well, but I think it would be preferable to abstain from
> extravagant use of these characters unless their significance is explained.
> Sometimes items are marked with asterisks, other times with quotation marks. I
> find it all rather off-putting and could not find anything in the RFC Editor's
> Style Guide indicating a standardized meaning for the characters.
I copied this from the original JMAP draft, but I agree that this should 
be reviewed/rationalized.
> Do not put a colon after the title of each example (e.g., "Example 1:")
I expected these to appear above the block. So I removed them now.
> Specific:

Thank you, I addressed all of your nits.

Best Regards,

Alexey


From nobody Fri Sep 10 07:25:45 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CCF3F3A07B1; Fri, 10 Sep 2021 07:25:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: jmap@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: jmap@ietf.org
Message-ID: <163128394272.5658.844103542497726415@ietfa.amsl.com>
Date: Fri, 10 Sep 2021 07:25:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/clpnEx2UIgjVXLZg4L-RaZLF8v4>
Subject: [Jmap] I-D Action: draft-ietf-jmap-smime-08.txt
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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, 10 Sep 2021 14:25:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the JSON Mail Access Protocol WG of the IETF.

        Title           : S/MIME signature verification extension to JMAP
        Author          : Alexey Melnikov
	Filename        : draft-ietf-jmap-smime-08.txt
	Pages           : 9
	Date            : 2021-09-10

Abstract:
   This document specifies an extension to JMAP for returning S/MIME
   signature verification status.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-jmap-smime/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-jmap-smime-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-smime-08


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Sep 13 09:39:07 2021
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 995A33A0989; Mon, 13 Sep 2021 09:38:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: jmap@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <163155113550.2313.13740798731552144374@ietfa.amsl.com>
Date: Mon, 13 Sep 2021 09:38:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/c6RFU3Q6B7M-X5q4ymH-N_dJUiA>
Subject: [Jmap] JSON Mail Access Protocol (jmap) WG Virtual Meeting: 2021-10-21
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 13 Sep 2021 16:38:56 -0000

The JSON Mail Access Protocol (jmap) WG will hold
a virtual interim meeting on 2021-10-21 from 03:00 to 04:30 America/New_York (07:00 to 08:30 UTC).

Agenda:
Zoom meeting:

Meeting ID: 853 8970 4050
Passcode: 889430

Agenda TBA

Information about remote participation:
https://us02web.zoom.us/j/85389704050?pwd=TUt0UHROWGZwWk45Q29Pb0pab0l2dz09


From nobody Wed Sep 22 09:59:08 2021
Return-Path: <noreply@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 22E323A2960; Wed, 22 Sep 2021 09:58:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Kirsty Paine via Datatracker <noreply@ietf.org>
To: <art@ietf.org>
Cc: draft-ietf-jmap-smime.all@ietf.org, jmap@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.38.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <163232991808.32122.9195451729619651354@ietfa.amsl.com>
Reply-To: Kirsty Paine <kirsty.p@ncsc.gov.uk>
Date: Wed, 22 Sep 2021 09:58:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/j0Q5HZx7-C6QjVAYvLji82VIOjw>
Subject: [Jmap] Artart last call review of draft-ietf-jmap-smime-08
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 22 Sep 2021 16:58:39 -0000

Reviewer: Kirsty Paine
Review result: Ready with Issues

I'm the assigned reviewer for the ART area. Apologies for the delay in my
review - I was on holiday.

In summary, I think the draft could do with being clearer in a few places and
having a more logical ordering in Section 4. That said, most of my comments are
nits or common ART review issues, so I think the draft is essentially Ready.

Abstract
•       it could be worth including the RFC reference to the protocol being
extended here, or expanding the acronym "JMAP". S/MIME is probably well-known
enough by now though :)

Introduction
•       RFC8621 specifies "JMAP for email", JMAP is specified by RFC8620. So
should this be "JMAP for Email [RFC8621]" or "JMAP [RFC8620]" rather than "JMAP
[RFC8620]" as it currently is? •       The first sentence in the second
paragraph in the introduction could benefit from more specific references too.
As an example, you could rephrase like "when the multipart/signed media type is
used [RFC1847], the client is not required to download… and when the
application/pkcs7-mime media type is used [RFC8551 Sec. 3.2]" •       Missing
words: "assumes that *the/a* JMAP client trusts *the/a* JMAP server…" •      
I'm not sure that "this JMAP extension assumes" makes much sense – is it really
the extension that assumes this trust relationship? Perhaps more accurately,
the use of the extension implies the client trusts the server's configuration
and code… Or that when this extension is in use, the threat model must assume
that the client trusts the server's configuration and signature verification
code.

Section 2:
•       I see this document follows the conventions in Section 1.1 of RFC8621.
However, if there are particular meanings for words and asterisks later in the
document, it might be helpful to reference Section 1.1 at the point of use too,
so that the specific normative meaning isn't lost on those unfamiliar with the
editorial conventions (e.g. for "server-set" in Section 4).

Section 3:
•       It might be worth highlighting where exactly in RFC8620 one can find
details about the capabilities object, since it's a 90-page RFC and it's not a
section header. The capabilities object and Session object referenced are
defined in Section 2 of RFC8620. •       Is this a hidden requirement: "The
value of this property is an empty object"? For example, you could reword to
say "the value of the urn:ietf:params:jmap:smimeverify property MUST be an
empty object" or "must be set to" or similar.

Section 4:
•       In the second sentence of Section 4, "This document" refers to the
current document you're writing in, not RFC8621, if I understand correctly. Try
to make that clearer :) •       There's no sentence introducing the unknown,
signed, signed/verified and signed/failed messages, and they don't form a
bullet point list as you have above, so I found this difficult to parse. It
could be a good idea to include something like "The smimeStatus value can only
be one of the following four messages". This would help readability, and it
might be worth adding a colon after these messages or indenting more, because
it's not very clear, e.g. "unknown:   S/MIME message" read to me as "unknown
S/MIME message…" •       For unknown, you use the present tense "is" but for
the other smimeStatus responses, you use "was". I would suggest making it the
same for them all. •       You probably don't need to say "compliant with this
document", just say "JMAP servers SHOULD…" •       Structurally for Section 4,
it might be helpful to have sub-headings for the four different property values
and then group all the text about it in one place. And then another section for
the FilterCondition object too perhaps. •       I find it odd that the bullet
points are in a different order to the text that follows, e.g. the bullets are
smimeStatus, smimeErrors, smimeVerifiedAt, smimeStatusAtDelivery; the text
orders it smimeStatus, smimeStatusAtDelivery, smimeErrors, smimeVerifiedAt. •  
    The "string" values that are allowed for smimeStatus and smimeErrors do not
explicitly mention the allowable charsets (standard ART area guidance). In IETF
protocols, UTF-8 is preferred - see RFC 2277 (BCP 18), Sections 3.1 and 3.2.
Please reference this and make it explicit what characters are allowed. •      
Similarly, this draft has protocol elements that contain human-readable text,
so you need to specify language tags for those fields, or justify why language
tagging is not needed. There is text that alludes to this in smimeErrors,
saying "in the language specified in the Content-Language header field, if any"
– but there's no language stipulation for others, e.g. smimeStatus where it
says "Servers MAY return other values not defined below." For details, see RFC
2277 (BCP 18), Section 4.2. •       Suggest adding some words for readability:
*In one* example, the signing certificate might be expired and the message From
email address might not correspond to any of the email addresses in the signing
certificate. *In another example*, the certificate might be expired and the
JMAP server might be unable to retrieve a CRL for the certificate. •       The
smimeVerifiedAt value is described as "server-set". I was unsure if all of
these four are server-set, on reflection this could be because I missed the
particular definition of 'server-set' in RFC8621. •       Re: "UTCDate", please
make sure you define the details of its syntax (standard ART area guidance).
Even if you reference something like RFC 3339 (which is generally recommended
for IETF specifications), make sure that you document all the details about
various options, such as use of non-UTC time zones and fractional seconds. •   
   "(but see below about result caching)" – do you mean in the Security
Considerations or later in this paragraph? I'd suggest just removing this
bracket, it doesn't help with understanding nor does it contradict that the
value is calculated when the request was processed. •       Missing word(?): In
all cases "smimeVerifiedAt" is set to *the* time when "smimeStatus" and
"smimeErrors" were last updated. •       Should the IDs match? You have
f123u987 in the request but f123u457 in the response (even if they don't need
to match, I'm still twitching that "f123u457" isn't "f123u456"…)

Section 5.1
•       should this be "smimeverify" and not "smime", i.e. instead of "IANA is
requested to register the "smime" JMAP Capability as follows", it should be
"IANA is requested to register the "smimeverify" JMAP Capability as follows"

Section 6
•       I think you're missing a word - "server verification code" ought to be
"server *signature* verification code" as it is in the Introduction. •       I
suggest it's more of a trade-off than described currently, it's more subtle
than "the client trusts the server's configuration". The client trusts the
server's configuration and signature verification code *more than* the
inefficiency/work/bandwidth required to download the signature body part and
all signed body parts or to download and decode CMS. •       I'm not sure why
10 minutes specifically is recommended – it seems to be landed there without
rationale and without conveying why it's not longer/shorter.

I hope this review is helpful to the authors and, finally, thanks for your work
and I wish you all the best for this draft as it continues its IETF journey.




From nobody Fri Sep 24 04:40:14 2021
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 5BF783A253E; Fri, 24 Sep 2021 04:39:57 -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, 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 X_vP_7CxG3Ch; Fri, 24 Sep 2021 04:39:51 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id AA0113A2541; Fri, 24 Sep 2021 04:39:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1632483589; d=isode.com; s=june2016; i=@isode.com; bh=Jkr8Qd2AgcAF5dtLYfXTmSvzaS4SjEbxJjoukH8NC+M=; 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=CRdlbGpB27ikdgEed3UyDl09509Ys8ppbloGcu10p+Fa8JBTP6O1Wig1a8ekuB+vSBx8q9 pBrnqqLAd+IOpVGTUugkF5lcM2JhTVb+RNzHa6MsQJz2TFGViF7lg8d2YEFP04or7WyLy7 2pwIV/TnQxIDdpJpds+e28EEWawq0Ow=;
Received: from smtpclient.apple ((unknown) [185.69.144.156])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <YU25BQBY=w-5@statler.isode.com>; Fri, 24 Sep 2021 12:39:49 +0100
X-SMTP-Protocol-Errors: NORDNS
From: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <163232991808.32122.9195451729619651354@ietfa.amsl.com>
Date: Fri, 24 Sep 2021 12:39:47 +0100
Cc: art@ietf.org, jmap@ietf.org, draft-ietf-jmap-smime.all@ietf.org, last-call@ietf.org
Message-Id: <8C7AC576-1748-4AAC-B720-45206A1051E7@isode.com>
References: <163232991808.32122.9195451729619651354@ietfa.amsl.com>
To: Kirsty Paine <kirsty.p@ncsc.gov.uk>
X-Mailer: iPad Mail (18G82)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Pj4za9FdmnXw6W3JdRUXbh2m1DU>
Subject: Re: [Jmap] [art] Artart last call review of draft-ietf-jmap-smime-08
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, 24 Sep 2021 11:39:58 -0000

Kirsty,
Thank you for your thorough review.
Quickly replying to a couple of your points and I will reply in more details=
 in a separate email.

> On 22 Sep 2021, at 18:00, Kirsty Paine via Datatracker <noreply@ietf.org> w=
rote:
 [snip]
>=20
> Section 4:
>  =E2=80=A2 =20
>    The "string" values that are allowed for smimeStatus and smimeErrors do=
 not
> explicitly mention the allowable charsets (standard ART area guidance). In=
 IETF
> protocols, UTF-8 is preferred - see RFC 2277 (BCP 18), Sections 3.1 and 3.=
2.
> Please reference this and make it explicit what characters are allowed. =E2=
=80=A2     =20
> Similarly, this draft has protocol elements that contain human-readable te=
xt,
> so you need to specify language tags for those fields, or justify why lang=
uage
> tagging is not needed. There is text that alludes to this in smimeErrors,
> saying "in the language specified in the Content-Language header field, if=
 any"
> =E2=80=93 but there's no language stipulation for others, e.g. smimeStatus=
 where it
> says "Servers MAY return other values not defined below."
smimeStatus use tokens, not free form human readable text, so use of languag=
e tags is not appropriate for it. But I will check if this can be clarified.=


 [snip]

> Section 6
> =E2=80=A2       I'm not sure why
> 10 minutes specifically is recommended =E2=80=93 it seems to be landed the=
re without
> rationale and without conveying why it's not longer/shorter.

It seemed like a reasonable default and making it configurable seemed like o=
verkill (and a way to introduce unnecessary complexity into the protocol).
To be honest the proposed default hasn=E2=80=99t been discussed in the WG, s=
o if you have an alternative proposal, it would be great to hear.

Best Regards,
Alexey



From nobody Thu Sep 30 09:44:27 2021
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 F36223A0DB4; Thu, 30 Sep 2021 09:44:25 -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 XZ02LmhAjzhH; Thu, 30 Sep 2021 09:44:21 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id EEFC03A0DB3; Thu, 30 Sep 2021 09:44:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1633020256; d=isode.com; s=june2016; i=@isode.com; bh=E6PyZrPQOHq0KvQOp8zD/0lfjsIXi4TqSyKhNpSiJJQ=; 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=ODVFrbuukT4bSb6M1mEB4Tbe17/AIEAxv2ZJfU8p7mbsxyGPHQxe4AH92Zw755kX7P4qrk JIojGjjByUxcgfiPn4tCIUBVgUxo59SqMzYeGgPtQlSlCXT4aBdjnIPQ2/oT6F00PmeJVZ os8Cxt420p71iRiHvJ/n69fhteLxj8c=;
Received: from [192.168.0.5] ((unknown) [94.3.228.58])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <YVXpXwABR339@waldorf.isode.com>; Thu, 30 Sep 2021 17:44:16 +0100
X-SMTP-Protocol-Errors: NORDNS
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Kirsty Paine <kirsty.p@ncsc.gov.uk>, art@ietf.org
Cc: jmap@ietf.org, draft-ietf-jmap-smime.all@ietf.org, last-call@ietf.org
References: <163232991808.32122.9195451729619651354@ietfa.amsl.com>
Message-ID: <003af00e-d7e4-1f50-9a7a-3d312f700df2@isode.com>
Date: Thu, 30 Sep 2021 17:44:09 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
In-Reply-To: <163232991808.32122.9195451729619651354@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/bXXE0coPfz-6qKy323-yJKo6v2I>
Subject: Re: [Jmap] Artart last call review of draft-ietf-jmap-smime-08
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, 30 Sep 2021 16:44:26 -0000

Hi Kirsty,

Thank you for your review.

On 22/09/2021 17:58, Kirsty Paine via Datatracker wrote:
> Reviewer: Kirsty Paine
> Review result: Ready with Issues
>
> I'm the assigned reviewer for the ART area. Apologies for the delay in my
> review - I was on holiday.
>
> In summary, I think the draft could do with being clearer in a few places =
and
> having a more logical ordering in Section 4. That said, most of my comment=
s are
> nits or common ART review issues, so I think the draft is essentially Read=
y.
>
> Abstract
> =E2=80=A2       it could be worth including the RFC reference to the proto=
col being
> extended here, or expanding the acronym "JMAP". S/MIME is probably well-kn=
own
> enough by now though :)
I changed "JMAP" to "JMAP for Mail (RFC 8621)".
> Introduction
> =E2=80=A2       RFC8621 specifies "JMAP for email", JMAP is specified by R=
FC8620. So
> should this be "JMAP for Email [RFC8621]" or "JMAP [RFC8620]" rather than =
"JMAP
> [RFC8620]" as it currently is?
Sure. I used "JMAP for Mail [RFC8621]", to match the title of RFC 8621.
>   =E2=80=A2       The first sentence in the second
> paragraph in the introduction could benefit from more specific references =
too.
> As an example, you could rephrase like "when the multipart/signed media ty=
pe is
> used [RFC1847], the client is not required to download=E2=80=A6 and when t=
he
> application/pkcs7-mime media type is used [RFC8551 Sec. 3.2]"
Added, thanks.
> =E2=80=A2       Missing
> words: "assumes that *the/a* JMAP client trusts *the/a* JMAP server=E2=80=
=A6"
Fixed, thanks.
> =E2=80=A2
> I'm not sure that "this JMAP extension assumes" makes much sense =E2=80=93=
 is it really
> the extension that assumes this trust relationship? Perhaps more accuratel=
y,
> the use of the extension implies the client trusts the server's configurat=
ion
> and code=E2=80=A6 Or that when this extension is in use, the threat model =
must assume
> that the client trusts the server's configuration and signature verificati=
on
> code.
Yes, good point.
> Section 2:
> =E2=80=A2       I see this document follows the conventions in Section 1.1=
 of RFC8621.
> However, if there are particular meanings for words and asterisks later in=
 the
> document, it might be helpful to reference Section 1.1 at the point of use=
 too,
> so that the specific normative meaning isn't lost on those unfamiliar with=
 the
> editorial conventions (e.g. for "server-set" in Section 4).
Ok, I will review.
> Section 3:
> =E2=80=A2       It might be worth highlighting where exactly in RFC8620 on=
e can find
> details about the capabilities object, since it's a 90-page RFC and it's n=
ot a
> section header. The capabilities object and Session object referenced are
> defined in Section 2 of RFC8620.
Ok.
> =E2=80=A2       Is this a hidden requirement: "The
> value of this property is an empty object"? For example, you could reword =
to
> say "the value of the urn:ietf:params:jmap:smimeverify property MUST be an
> empty object" or "must be set to" or similar.
It is the same thing without using RFC 2119 language.
> Section 4:
> =E2=80=A2       In the second sentence of Section 4, "This document" refer=
s to the
> current document you're writing in, not RFC8621, if I understand correctly=
. Try
> to make that clearer :)
Yes. Any suggestions how to make this clearer? I've seen "this document"=20
used frequently in RFCs.
>   =E2=80=A2       There's no sentence introducing the unknown,
> signed, signed/verified and signed/failed messages, and they don't form a
> bullet point list as you have above, so I found this difficult to parse.

They should be a bullet list. This might be a rendering issue.

They are introduced by "Possible=C2=A0string=C2=A0values=C2=A0of=C2=A0the=C2=
=A0property=C2=A0are=20
listed=C2=A0below."

> It could be a good idea to include something like "The smimeStatus value c=
an only
> be one of the following four messages".
This is actually not true, as there is a sentence saying=20
"Servers=C2=A0MAY=C2=A0return=C2=A0other=C2=A0values=C2=A0not=C2=A0defined=
=C2=A0below". In particular my=20
implementation also emits "encrypted+signed/verified".
> This would help readability, and it
> might be worth adding a colon after these messages or indenting more, beca=
use
> it's not very clear, e.g. "unknown:   S/MIME message" read to me as "unkno=
wn
> S/MIME message=E2=80=A6"
Good point, added.
> =E2=80=A2       For unknown, you use the present tense "is" but for
> the other smimeStatus responses, you use "was". I would suggest making it =
the
> same for them all.
Changed.
> =E2=80=A2       You probably don't need to say "compliant with this
> document", just say "JMAP servers SHOULD=E2=80=A6" =E2=80=A2       Structu=
rally for Section 4,
> it might be helpful to have sub-headings for the four different property v=
alues
> and then group all the text about it in one place. And then another sectio=
n for
> the FilterCondition object too perhaps.
Ok, I will try to improve this.
> =E2=80=A2       I find it odd that the bullet
> points are in a different order to the text that follows, e.g. the bullets=
 are
> smimeStatus, smimeErrors, smimeVerifiedAt, smimeStatusAtDelivery; the text
> orders it smimeStatus, smimeStatusAtDelivery, smimeErrors, smimeVerifiedAt=
.
Good point, reordered.
> =E2=80=A2
>      The "string" values that are allowed for smimeStatus and smimeErrors =
do not
> explicitly mention the allowable charsets (standard ART area guidance). In=
 IETF
> protocols, UTF-8 is preferred - see RFC 2277 (BCP 18), Sections 3.1 and 3.=
2.
> Please reference this and make it explicit what characters are allowed.

This is defined by reference: "String" is defined as JSON string, which=20
means UTF-8.

smimeStatus is not subject to internationalization (its values are=20
tokens), but I clarified that they should be in ASCII.

> =E2=80=A2
> Similarly, this draft has protocol elements that contain human-readable te=
xt,
> so you need to specify language tags for those fields, or justify why lang=
uage
> tagging is not needed. There is text that alludes to this in smimeErrors,
> saying "in the language specified in the Content-Language header field, if=
 any"
> =E2=80=93 but there's no language stipulation for others, e.g. smimeStatus=
 where it
> says "Servers MAY return other values not defined below."
See above, this doesn't apply to smimeStatus.
> For details, see RFC
> 2277 (BCP 18), Section 4.2. =E2=80=A2       Suggest adding some words for =
readability:
> *In one* example, the signing certificate might be expired and the message=
 From
> email address might not correspond to any of the email addresses in the si=
gning
> certificate. *In another example*, the certificate might be expired and th=
e
> JMAP server might be unable to retrieve a CRL for the certificate.
Clarified.
> =E2=80=A2       The
> smimeVerifiedAt value is described as "server-set". I was unsure if all of
> these four are server-set, on reflection this could be because I missed th=
e
> particular definition of 'server-set' in RFC8621.
'server-set' is defined in Section 1.1 of RFC 8620.
>   =E2=80=A2       Re: "UTCDate", please
> make sure you define the details of its syntax (standard ART area guidance=
).
> Even if you reference something like RFC 3339 (which is generally recommen=
ded
> for IETF specifications), make sure that you document all the details abou=
t
> various options, such as use of non-UTC time zones and fractional seconds.
This is fully defined in Section 1.4 of RFC 8620.
> =E2=80=A2
>     "(but see below about result caching)" =E2=80=93 do you mean in the Se=
curity
> Considerations or later in this paragraph?
Later in the same paragraph.
> I'd suggest just removing this
> bracket, it doesn't help with understanding nor does it contradict that th=
e
> value is calculated when the request was processed.
I was trying to say that "it is calculated at the time of the request,=20
unless it has been less than 10 minutes since the last request to the=20
same values". I am open to suggestions about the best way of saying this.
> =E2=80=A2       Missing word(?): In
> all cases "smimeVerifiedAt" is set to *the* time when "smimeStatus" and
> "smimeErrors" were last updated.
Yes.
> =E2=80=A2       Should the IDs match? You have
> f123u987 in the request but f123u457 in the response (even if they don't n=
eed
> to match, I'm still twitching that "f123u457" isn't "f123u456"=E2=80=A6)
Well spotted. Yes, they need to match.
> Section 5.1
> =E2=80=A2       should this be "smimeverify" and not "smime",
Yes. Fixed.
> i.e. instead of "IANA is
> requested to register the "smime" JMAP Capability as follows", it should b=
e
> "IANA is requested to register the "smimeverify" JMAP Capability as follow=
s"
>
> Section 6
> =E2=80=A2       I think you're missing a word - "server verification code"=
 ought to be
> "server *signature* verification code" as it is in the Introduction.
Yes, good point.
> =E2=80=A2       I
> suggest it's more of a trade-off than described currently, it's more subtl=
e
> than "the client trusts the server's configuration". The client trusts the
> server's configuration and signature verification code *more than* the
> inefficiency/work/bandwidth required to download the signature body part a=
nd
> all signed body parts or to download and decode CMS.

Ok. I will try to wordsmith this.

Best Regards,

Alexey


From nobody Thu Sep 30 09:48:44 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A3913A005C; Thu, 30 Sep 2021 09:48:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: jmap@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.38.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: jmap@ietf.org
Message-ID: <163302050735.28477.2005424187094172108@ietfa.amsl.com>
Date: Thu, 30 Sep 2021 09:48:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/ExYow6muhLuyeq4a8QbpVQXBUbs>
Subject: [Jmap] I-D Action: draft-ietf-jmap-smime-09.txt
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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, 30 Sep 2021 16:48:28 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the JSON Mail Access Protocol WG of the IETF.

        Title           : S/MIME signature verification extension to JMAP
        Author          : Alexey Melnikov
	Filename        : draft-ietf-jmap-smime-09.txt
	Pages           : 9
	Date            : 2021-09-30

Abstract:
   This document specifies an extension to JMAP for Mail (RFC 8621) for
   returning S/MIME signature verification status.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-jmap-smime/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-jmap-smime-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-smime-09


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


