Last Call Review of draft-ietf-extra-sieve-mailboxid-06
review-ietf-extra-sieve-mailboxid-06-secdir-lc-weiler-2020-12-16-00

Request Review of draft-ietf-extra-sieve-mailboxid
Requested revision No specific revision (document currently at 09)
Type IETF Last Call Review
Team Security Area Directorate (secdir)
Deadline 2020-12-02
Requested 2020-11-18
Authors Bron Gondwana
I-D last updated 2021-06-30 (Latest revision 2021-03-16)
Completed reviews Secdir IETF Last Call review of -06 by Sam Weiler (diff)
Genart IETF Last Call review of -05 by Pete Resnick (diff)
Assignment Reviewer Sam Weiler
State Completed
Request IETF Last Call review on draft-ietf-extra-sieve-mailboxid by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/k4YKt8wAniMv5vLAxrpi2W4RFno
Reviewed revision 06 (document currently at 09)
Result Has issues
Completed 2020-12-16
review-ietf-extra-sieve-mailboxid-06-secdir-lc-weiler-2020-12-16-00
Thank you for the well-written document!

I'm concerned about the user experience of this extension.

I imagine confusion will arise when the opaque :mailboxid takes precedence over
the human readable mailbox name.   I don't see any feedback mechanism to show
that the mail is going to a mailbox other than the one that is human readable -
feedback that could prompt updating of the script.  As a human trying debug
this, it may not be obvious where mail went - the script says "INBOX.foo" and
the mail simply isn't there.  Is there a way to make this more debuggable?  Or
is there useful advice to provide to the Sieve UI implementer, like "this is
for special cases and should probably be off by default"?

Minor: I'd like section 3 to point at what "require" means:
https://tools.ietf.org/html/rfc5228#section-2.10.5