--- 1/draft-ietf-dmarc-interoperability-10.txt	2015-11-12 14:15:04.957774246 -0800
+++ 2/draft-ietf-dmarc-interoperability-11.txt	2015-11-12 14:15:05.001775313 -0800
@@ -1,25 +1,25 @@
 
 DMARC                                                     F. Martin, Ed.
 Internet-Draft                                                  LinkedIn
 Intended status: Informational                              E. Lear, Ed.
-Expires: May 12, 2016                                 Cisco Systems GmbH
+Expires: May 15, 2016                                 Cisco Systems GmbH
                                                          T. Draegen, Ed.
                                                           dmarcian, inc.
                                                           E. Zwicky, Ed.
                                                                    Yahoo
                                                         K. Andersen, Ed.
                                                                 LinkedIn
-                                                        November 9, 2015
+                                                       November 12, 2015
 
      Interoperability Issues Between DMARC and Indirect Email Flows
-                  draft-ietf-dmarc-interoperability-10
+                  draft-ietf-dmarc-interoperability-11
 
 Abstract
 
    DMARC introduces a mechanism for expressing domain-level policies and
    preferences for email message validation, disposition, and reporting.
    The DMARC mechanism can encounter interoperability issues when
    messages do not flow directly from the author's administrative domain
    to the final recipients.  Collectively these email flows are referred
    to as indirect email flows.  This document describes interoperability
    issues between DMARC and indirect email flows.  Possible methods for
@@ -33,21 +33,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 http://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 May 12, 2016.
+   This Internet-Draft will expire on May 15, 2016.
 
 Copyright Notice
 
    Copyright (c) 2015 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
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -791,21 +791,21 @@
       there are three possibilities:
 
       1.  change it to put the mailing list email address,
 
       2.  change it to a locally-defined address which will be forwarded
           back to the original sender, or
 
       3.  "break" the address by modifying the domain to a non-existent
           domain (such as by adding a suffix like ".invalid".)
 
-      The later modification may create issues because it is an invalid
+      The latter modification may create issues because it is an invalid
       domain name, and some MTAs may pay particular attention to the
       validity of email addresses in RFC5322.From and the reputation of
       the domains present there.
 
    o  Configuring the MLM to "wrap" the message in a MIME message/rfc822
       part and to send as the Mailing List email address.  Many email
       clients (as of August 2015), especially mobile clients, have
       difficulty reading such messages and this is not expected to
       change soon.