--- 1/draft-ietf-ippm-checksum-trailer-03.txt	2015-11-08 23:15:13.537058030 -0800
+++ 2/draft-ietf-ippm-checksum-trailer-04.txt	2015-11-08 23:15:13.569058813 -0800
@@ -1,17 +1,17 @@
 Network Working Group                                         T. Mizrahi
 Internet Draft                                                   Marvell
 Intended status: Experimental
-Expires: April 2016                                     October 14, 2015
+Expires: May 2016                                       November 9, 2015
 
                 UDP Checksum Complement in OWAMP and TWAMP
-                  draft-ietf-ippm-checksum-trailer-03.txt
+                  draft-ietf-ippm-checksum-trailer-04.txt
 
 Abstract
 
    The One-Way Active Measurement Protocol (OWAMP) and the Two-Way
    Active Measurement Protocol (TWAMP) are used for performance
    monitoring in IP networks. Delay measurement is performed in these
    protocols by using timestamped test packets. Some implementations use
    hardware-based timestamping engines that integrate the accurate
    transmission timestamp into every outgoing OWAMP/TWAMP test packet
    during transmission.  Since these packets are transported over UDP,
@@ -36,21 +36,21 @@
    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."
 
    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt.
 
    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.
 
-   This Internet-Draft will expire on April 14, 2016.
+   This Internet-Draft will expire on May 9, 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
@@ -365,25 +365,27 @@
    This document does not impose new requirements on the receiving end
    of an OWAMP/TWAMP test packet.
 
    The UDP layer at the receiving end verifies the UDP Checksum of
    received test packets, and the OWAMP/TWAMP layer SHOULD treat the
    Checksum Complement as part of the Packet Padding.
 
 3.3. Interoperability with Existing Implementations
 
    The behavior defined in this document does not impose new
-   requirements on the reception behavior of an OWAMP receiver or a
-   TWAMP reflector, since the existence of the Checksum Complement is
-   transparent from the perspective of the receiver/reflector. Thus, the
-   functionality described in this document allows interoperability with
-   existing implementations that comply to [OWAMP] or [TWAMP].
+   requirements on the reception behavior of OWAMP/TWAMP test packets.
+   The protocol stack of the receiving host performs the conventional
+   UDP checksum verification, and thus the existence of the Checksum
+   Complement is transparent from the perspective of the receiving host.
+   Therefore, the functionality described in this document allows
+   interoperability with existing implementations that comply to [OWAMP]
+   or [TWAMP].
 
 3.4. Using the Checksum Complement with or without Authentication
 
    Both OWAMP and TWAMP may use authentication or encryption, as defined
    in [OWAMP] and [TWAMP].
 
 3.4.1. Checksum Complement in Authenticated Mode
 
    OWAMP and TWAMP test packets can be authenticated using an HMAC
    (Hashed Message Authentication Code). The HMAC covers some of the