[secdir] SECDIR review of draft-ietf-extra-imap-objectid-04

Chris Lonvick <lonvick.ietf@gmail.com> Sat, 21 July 2018 21:25 UTC

References: <1531858198.2510671.1444040480.5D771E87@webmail.messagingengine.com>
To: "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, draft-ietf-extra-imap-objectid.all@ietf.org
From: Chris Lonvick <lonvick.ietf@gmail.com>
Message-ID: <5B53A4CA.1050109@gmail.com>
Date: Sat, 21 Jul 2018 16:25:30 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <1531858198.2510671.1444040480.5D771E87@webmail.messagingengine.com>
Content-Type: multipart/alternative; boundary="------------040903070307050508050902"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/B9vTUOMCsV6liDDliOVBsgyZtGw>
Subject: [secdir] SECDIR review of draft-ietf-extra-imap-objectid-04
Precedence: list

Hi Bron,

Thanks for the update. All looks good now.

I have re-reviewed this document as part of the security directorate's 
ongoing effort to review all IETF documents being processed by the IESG. 
These comments were written primarily for the benefit of the security 
area directors. Document editors and WG chairs should treat these 
comments just like any other last call comments.

The summary of the review is READY.

Thanks,
Chris

-------- Forwarded Message --------
Subject: 	new version of objectid draft uploaded
Date: 	Wed, 18 Jul 2018 06:09:58 +1000
From: 	Bron Gondwana <brong@fastmailteam.com>
To: 	extra@ietf.org
CC: 	Pete Resnick <presnick@qti.qualcomm.com>, Chris Lonvick 
<lonvick.ietf@gmail.com>, Alexey Melnikov <alexey.melnikov@isode.com>



Hi All,

I've just uploaded draft-ietf-extra-imap-objectid-04, based on multiple 
reviews. Thanks to:

Alexey (AD)
Pete (GenArt)
Chris (SecDir)

Here's the set of changes:

* described NIL THREADID in more detail (ad review)
* made RFC5256 a normative reference (ad review)
* fixed ABNF missing quote (ad review)
* documented hash upgrade process (ad review)
* referenced RFC3501 for INBOX rename (ad review)
* referenced RFC3501 security considerations (secdir review)
* turned mealy-mouthed "SHOULDs" in to "MUSTs" on immutability (genart 
review)
* remove suggested algorithms which are no longer legitimate (genart review)
* updated proxy advice to suggest rewriting ids (genart review)
* fixed minor gramatical issues (genart review)
* required that EMAILID and THREADID are not identical (own decision)

====

Of particular interest is that EMAILID and THREADID now MUST be 
different (just prefix them if they may otherwise clash!) and a whole 
lot of SHOULD turned into MUST.  Everyone who's going to implement this 
already has stable storage for their IDs, and it means clients can 
really rely on these IDs.

I would appreciate any further reviews!

Thanks,

Bron.

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

[secdir] SECDIR review of draft-ietf-extra-imap-o… Chris Lonvick