Re: [Last-Call] Artart last call review of draft-ietf-extra-imap-uidonly-06

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Barry,

On Wed, 13 Mar 2024 19:52:21 +0000 (GMT Standard Time), Barry Leiba via Datatracker wrote:
Reviewer: Barry Leiba
Review result: Ready with Issues

— Section 3 —

 Once the UIDONLY extension is enabled (see Section 3.1), the client
 MUST NOT use message sequence numbers (including the special marker
 "*") in any arguments to IMAP commands, and the server MUST return
 tagged BAD response if the client uses message sequence numbers.  The
 server SHOULD include the UIDREQUIRED response code in such BAD
 responses (see below).

I see nothing below that says why this is SHOULD rather than MUST, and I can’t
imagine any justification for not including it.  Why is this SHOULD?

Historically server inclusion of many IMAP response codes was a quality of implementation issue. In this case the client is clearly doing something wrong - it can't accidentally enable UIDONLY and then not use UIDs anyway. I suppose UIDREQUIRED can just be required, as it will help client implementers and server operators.

Best Regards,
Alexey

--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux