On Sat, Jul 28, 2018, at 03:57, Pete Resnick wrote:
Reviewer: Pete ResnickReview result: Ready with NitsI am the assigned Gen-ART reviewer for this draft. The General AreaReview Team (Gen-ART) reviews all IETF documents being processedby the IESG for the IETF Chair. Please wait for direction from yourdocument shepherd or AD before posting a new version of the draft.For more information, please see the FAQ atDocument: draft-ietf-extra-imap-objectid-06Reviewer: Pete ResnickReview Date: 2018-07-27IETF LC End Date: 2018-07-13IESG Telechat date: 2018-08-02Summary: Ready with NitsMajor issues: NoneMinor issues: NoneNits/editorial comments:Thanks for the changes responding to my review. Good work.§5.2, ¶6:OLDTHREADID is optional, if the server doesn't support THREADID or isNEWTHREADID is OPTIONAL; if the server doesn't support THREADID or is
Yep, fixed.
§5.2 ¶7:Not clear to me why the THREADID and EMAILID can't be the same. I assume giventhe MUST it's going to be some sort of interoperability problem, but it doesseem odd. But don't change it on my account.
This is basically a "developers will make assumptions about relatedness which may not always hold". We even XOR our THREADID against a constant after calculating it from the EMAILID in our server now, so that developers don't get lazy and make shortcuts.
§8.2 ¶2:s/backend object collide/backend object identifiers
Fixed this too.
Thanks again for great feedback,
Bron.
--
Bron Gondwana, CEO, FastMail Pty Ltd
brong@xxxxxxxxxxxxxxxx