Sieve Extension: Copying Without Side Effects
draft-degener-sieve-copy-03

[Ballot discuss]
This document would really benefit from an editing pass that looks at
this from the perspective of a general reader that doesn't already
have a lot of knowledge about  seive.

Please come up with a better title, one aimed at general reader.

Abstract could be better as well.

intro needs some intro context... just dives into the details... I.e,
the document assumes reader knows what seive is.

[Ballot comment]
The entire security considerations section says:
  >
  > The "copy" extension makes it easier to eavesdrop on a user's
  > message stream without the user noticing.
  >
  It would be really nice for the section to provide some guidance on
  practices, procedures, or technology that can help overcome the
  increased vulnerability.

[Note]: 'Although this is an individual submission it is unlikely
in the extreme to be at all controversial. Since my
time on the IESG is limited I've requested a two week
last call rather than four so I can wrap this up expeditiously.
' has been cleared by Ned Freed

[Note]: 'Although this is an individual submission it is unlikely
in the extreme to be at all controversial. Since my
time on the IESG is limited I''ve requested a two week
last call rather than four so I can wrap this up expeditiously.
' added by Ned Freed

AD review comments:

(1) An example showing the use of  the extentsion is needed. In particular,
    I've found that it really helps to have something that shows people what
    needs to be in the "reauire" clause.

(2) There needs to be an IANA considerations section telling IANA what
    to do. Something like this should appear as a section after the security
    considerations:

5 IANA Considerations
   
    The following template specifies the IANA registration of the copy Sieve
    extension specified in this document:
   
    To: iana@iana.org
    Subject: Registration of new Sieve extension

    Capability name: copy
    Capability keyword: copy
    Capability arguments: N/A
    Standards Track/IESG-approved experimental RFC number: this RFC
    Person and email address to contact for further information:

      Jutta Degener
      Sendmail, Inc.
      6425 Christie Ave, 4th Floor
      Emeryville, CA 94608

      Email: jutta@sendmail.com

    This information should be added to the list of sieve extensions
    given on http://www.iana.org/assignments/sieve-extensions.
   
(3) IPR boilerplate is missing and needs to be added as a separate section
    just before the copyright:

    The IETF takes no position regarding the validity or scope of any
    intellectual property or other rights that might be claimed to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; neither does it represent that it
    has made any effort to identify any such rights.  Information on the
    IETF's procedures with respect to rights in standards-track and
    standards-related documentation can be found in BCP-11.  Copies of
    claims of rights made available for publication and any assurances
    of licenses to be made available, or the result of an attempt made
    to obtain a general license or permission for the use of such
    proprietary rights by implementors or users of this specification
    can be obtained from the IETF Secretariat.

The title of Appendix A needs to be changed to
"Appendix A. Normative references". Sorry about that.