--- 1/draft-ietf-mpls-flow-ident-00.txt	2016-06-10 12:16:28.846910999 -0700
+++ 2/draft-ietf-mpls-flow-ident-01.txt	2016-06-10 12:16:28.878911817 -0700
@@ -1,24 +1,24 @@
 
 MPLS                                                           S. Bryant
 Internet-Draft                                               Independent
 Intended status: Informational                              C. Pignataro
-Expires: June 20, 2016                                     Cisco Systems
+Expires: December 12, 2016                                 Cisco Systems
                                                                  M. Chen
                                                                    Z. Li
                                                                   Huawei
                                                                G. Mirsky
                                                                 Ericsson
-                                                       December 18, 2015
+                                                           June 10, 2016
 
                 MPLS Flow Identification Considerations
-                     draft-ietf-mpls-flow-ident-00
+                     draft-ietf-mpls-flow-ident-01
 
 Abstract
 
    This memo discusses the desired capabilities for MPLS flow
    identification.  The key application that needs this is in-band
    performance monitoring of user data packets.
 
 Status of This Memo
 
    This Internet-Draft is submitted in full conformance with the
@@ -27,25 +27,25 @@
    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 June 20, 2016.
+   This Internet-Draft will expire on December 12, 2016.
 
 Copyright Notice
 
-   Copyright (c) 2015 IETF Trust and the persons identified as the
+   Copyright (c) 2016 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
    carefully, as they describe your rights and restrictions with respect
    to this document.  Code Components extracted from this document must
    include Simplified BSD License text as described in Section 4.e of
    the Trust Legal Provisions and are provided without warranty as
@@ -418,22 +418,22 @@
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119,
               DOI 10.17487/RFC2119, March 1997,
               <http://www.rfc-editor.org/info/rfc2119>.
 
 15.2.  Informative References
 
    [I-D.tempia-ippm-p3m]
               Capello, A., Cociglio, M., Fioccola, G., Castaldelli, L.,
               and A. Bonda, "A packet based method for passive
-              performance monitoring", draft-tempia-ippm-p3m-02 (work in
-              progress), October 2015.
+              performance monitoring", draft-tempia-ippm-p3m-03 (work in
+              progress), March 2016.
 
    [RFC5331]  Aggarwal, R., Rekhter, Y., and E. Rosen, "MPLS Upstream
               Label Assignment and Context-Specific Label Space",
               RFC 5331, DOI 10.17487/RFC5331, August 2008,
               <http://www.rfc-editor.org/info/rfc5331>.
 
    [RFC5420]  Farrel, A., Ed., Papadimitriou, D., Vasseur, JP., and A.
               Ayyangarps, "Encoding of Attributes for MPLS LSP
               Establishment Using Resource Reservation Protocol Traffic
               Engineering (RSVP-TE)", RFC 5420, DOI 10.17487/RFC5420,