Folks, I've been asked to sponsor draft-ietf-sieve-autoreply because
your customary area director is a co-author of this document. Here is my
AD review.
Overall this is a fine document and a creative re-use of existing Sieve
extensions.
I found a few of the sentences a bit difficult to parse, but I also
didn't find an easy way to rephrase them, so feel free to ignore this
comment. :)
The introduction references the last paragraph of the security
considerations, but as far as I can see that paragraph doesn't have
anything to do with security and I think it would make more sense to
include this text in the introduction...
Finally, users of any auto-reply mechanism should really think about
whether automatic replies are necessary, and at what interval they
make sense when they are. Email is not Instant Messaging, and
senders generally expect that replies might take a while. Consider
whether it's truly important to tell people that you'll read their
mail in an hour or so, or whether that can just be taken as how email
works. There are times when this makes sense, but let's not use it
to exacerbate information overload.
This document normatively references several other I-Ds. Does the WG
have any concerns that the referenced I-Ds will change materially? It
seems perhaps safer to advance the referenced I-Ds first, just in case.
Peter
--
Peter Saint-Andre
https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
sieve mailing list
sieve(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/sieve