--- 1/draft-ietf-extra-sieve-fcc-07.txt	2018-12-04 09:14:08.230200475 -0800
+++ 2/draft-ietf-extra-sieve-fcc-08.txt	2018-12-04 09:14:08.274201529 -0800
@@ -1,19 +1,19 @@
 
 EXTRA                                                       K. Murchison
 Internet-Draft                                               B. Gondwana
 Updates: 5230, 5435 (if approved)                               FastMail
-Intended status: Standards Track                       November 29, 2018
-Expires: June 2, 2019
+Intended status: Standards Track                        December 4, 2018
+Expires: June 7, 2019
 
                 Sieve Extension: File Carbon Copy (Fcc)
-                     draft-ietf-extra-sieve-fcc-07
+                     draft-ietf-extra-sieve-fcc-08
 
 Abstract
 
    The Sieve Email Filtering Language provides a number of action
    commands, some of which can generate additional messages on behalf of
    the user.  This document defines an extension to such commands to
    allow a copy of any generated message to be filed into a target
    mailbox.
 
    This document updates RFC5230 and RFC5435 by adding a new tagged
@@ -27,21 +27,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on June 2, 2019.
+   This Internet-Draft will expire on June 7, 2019.
 
 Copyright Notice
 
    Copyright (c) 2018 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -181,21 +181,26 @@
    If both the optional ":specialuse" and ":create" arguments are
    specified with ":fcc", the Sieve interpreter is instructed to create
    the target mailbox per Section 4.1 of
    [I-D.ietf-extra-sieve-special-use], if needed.
 
 3.2.  Collected Grammar
 
    For convenience, the "FCC" syntax element is defined here using ABNF
    [RFC5234] so that it can be augmented by other extensions.
 
+   Note that the following is the grammar of "FCC" after it has been
+   lexically interpreted.  No whitespace or comments appear below.
+
    FCC         = ":fcc" string *FCC-OPTS
+                   ; per Section 2.6.2 of RFC5228,
+                   ; the tagged arguments in FCC may appear in any order
 
    FCC-OPTS    = CREATE / IMAP-FLAGS / SPECIAL-USE
                    ; each option MUST NOT appear more than once
 
    CREATE      = ":create"
    IMAP-FLAGS  = ":flags" string-list
    SPECIAL-USE = ":specialuse" string
 
 4.  Format of File Carbon Copied Messages
 
@@ -249,22 +254,22 @@
                      [":mime"]
                      [":handle" string]
                      <reason: string>
 
    Example (with fileinto extensions):
 
    require ["vacation", "fcc", "mailbox", "special-use", "imap4flags"];
 
    vacation :days 7
             :from "hemingway@example.com" "Gone Fishin'"
-            :fcc "INBOX.Sent" :flags ["\\Seen"]
-                              :specialuse "\\Sent" :create;
+            :specialuse "\\Sent" :create
+            :fcc "INBOX.Sent" :flags ["\\Seen"];
 
    Vacation auto-reply messages are MIME-compliant and can be filed into
    the target mailbox without modification.
 
 6.  Interaction with the Notify Action
 
    This document extends the "notify" [RFC5435] action to optionally
    store a copy of the notification messages into a target mailbox.
 
    Usage:   notify [FCC]
@@ -534,20 +538,27 @@
    [2] http://www.cyrusimap.org/
 
    [3] http://www.cmu.edu/computing/
 
    [4] https://www.oracle.com/industries/communications/enterprise/
        products/messaging-server/index.html
 
 Appendix A.  Change History (To be removed by RFC Editor before
              publication)
 
+   Changes since draft-ietf-extra-sieve-fcc-07:
+
+   o  Added comments regarding FCC ABNF per Alexey Melnikov.
+
+   o  Reordered arguments in the "vacation" example to show ":fcc"
+      appearing amongst FCC-OPTS.
+
    Changes since draft-ietf-extra-sieve-fcc-06:
 
    o  Reorganized sections.
 
    o  Switched to using proper ABNF for FCC and fileinto extensions.
 
    o  Fcc into INBOX if specified target mailbox doesn't exist.
 
    o  Editorial changes from Alexey Melnikov.