Re: Last Call: draft-ietf-imapext-sort (INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS) to Proposed Standard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Last Call: draft-ietf-imapext-sort (INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS) to Proposed Standard



On Wed, 27 Feb 2008, Timo Sirainen wrote:
> I don't see a point in breaking a lot of client and server
> implementations that implement the draft in its current form. The draft
> has stayed almost the same for at least 5 years (I implemented it then
> the first time).

Thank you Timo.

>> I don't think that "But that doesn't match the behavior of a previous
>> version of the draft" is a useful argument at Last Call time.
> I think these changes should have been discussed long before reaching
> last call. The draft is over 10 years old already!

Thank you for this as well.

Not only is the draft over 10 years old, but it documents functionality 
which is far older.  Pine first offered sorting years before the SORT 
extension was first defined.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
IETF mailing list
IETF at ietf.org
https://www.ietf.org/mailman/listinfo/ietf



Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.