--- 1/draft-ietf-hip-rfc4423-bis-11.txt	2015-06-23 06:14:59.594264304 -0700
+++ 2/draft-ietf-hip-rfc4423-bis-12.txt	2015-06-23 06:14:59.674266230 -0700
@@ -1,19 +1,19 @@
 
 Network Working Group                                  R. Moskowitz, Ed.
 Internet-Draft                                            HTT Consulting
 Obsoletes: 4423 (if approved)                                    M. Komu
 Intended status: Informational                                  Ericsson
-Expires: October 15, 2015                                 April 13, 2015
+Expires: December 25, 2015                                 June 23, 2015
 
                   Host Identity Protocol Architecture
-                     draft-ietf-hip-rfc4423-bis-11
+                     draft-ietf-hip-rfc4423-bis-12
 
 Abstract
 
    This memo describes a new namespace, the Host Identity namespace, and
    a new protocol layer, the Host Identity Protocol, between the
    internetworking and transport layers.  Herein are presented the
    basics of the current namespaces, their strengths and weaknesses, and
    how a new namespace will add completeness to them.  The roles of this
    new namespace in the protocols are defined.
 
@@ -30,21 +30,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 October 15, 2015.
+   This Internet-Draft will expire on December 25, 2015.
 
 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