Fwd: New Version Notification for draft-bosch-sieve-duplicate-02.txt

Hi,

I made a new version of the "duplicate" draft. It should address the 
comments by Ned, Kristin and Alexey. I added the example I gave to Alexey.

This resulted in quite a bit of restructuring in the description of the 
new test command, so it is best to review at least that section entirely.

There is one thing I thought of and haven't addressed so far. My current 
implementation makes a new entry in the duplicate tracking list 
irrespective of whether one exists already, overwriting the old one and 
thereby resetting the expiry time to whatever is configured using 
":seconds". This will make example 3 in the draft yield unexpected 
results; if duplicates arrive within the expiry time, the total expiry 
time is in effect extended. The semantic difference here is that the 
expiry time is either measured relative to the initial message or 
relative to the last duplicate. This means that the 30 minutes in the 
example can stretch indefinitely if duplicates keep arriving before the 
expiry deadline. So, for the scenario of example 3, such behavior is 
quite obviously wrong. However, would there be an application for having 
the expiry time be relative to the last message received with the 
specified ID rather than the initial one? How would we accommodate for that?

Regards,

Stephan.

_______________________________________________
sieve mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sieve