--- 1/draft-ietf-lwig-cellular-01.txt	2014-08-13 14:14:32.002718101 -0700
+++ 2/draft-ietf-lwig-cellular-02.txt	2014-08-13 14:14:32.038718967 -0700
@@ -1,19 +1,19 @@
 
 Network Working Group                                           J. Arkko
 Internet-Draft                                               A. Eriksson
 Intended status: Informational                                A. Keranen
-Expires: August 17, 2014                                        Ericsson
-                                                       February 13, 2014
+Expires: February 14, 2015                                      Ericsson
+                                                         August 13, 2014
 
       Building Power-Efficient CoAP Devices for Cellular Networks
-                      draft-ietf-lwig-cellular-01
+                      draft-ietf-lwig-cellular-02
 
 Abstract
 
    This memo discusses the use of the Constrained Application Protocol
    (CoAP) protocol in building sensors and other devices that employ
    cellular networks as a communications medium.  Building communicating
    devices that employ these networks is obviously well known, but this
    memo focuses specifically on techniques necessary to minimize power
    consumption.
 
@@ -25,21 +25,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 August 17, 2014.
+   This Internet-Draft will expire on February 14, 2015.
 
 Copyright Notice
 
    Copyright (c) 2014 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
@@ -376,24 +376,24 @@
    connected to the network and that it is reachable at a given IP
    address.
 
    The registration part is easy; a resource directory or mirror proxy
    can be used.  The device should perform the necessary registration
    with these devices, for instance, as specified in
 
    [I-D.ietf-core-resource-directory] and [I-D.vial-core-mirror-proxy].
    In order to do this registration, the device needs to know its CORE
    Link Format description, as specified in [RFC6690].  In essence, the
-   registration process involves performing a GET on .well-known/core/
-   ?rt=core-rd at the address of the resource directory (or rt=core-mp
-   for mirror proxies), and then doing a POST on the path of the
-   discovered resource.
+   registration process involves performing a GET on .well-known/
+   core/?rt=core-rd at the address of the resource directory (or
+   rt=core-mp for mirror proxies), and then doing a POST on the path of
+   the discovered resource.
 
    However, current CoAP specifications provide limited support for
    discovering the resource directory or mirror proxy.  Local multicast
    discovery only works in LAN-type networks, but not in these public
    cellular networks.  Our recommended alternate methods for discovery
    are the following:
 
    Manual Configuration
 
       The DNS name of the resource directory or mirror proxy is manually
@@ -613,21 +613,21 @@
    [RFC6690]  Shelby, Z., "Constrained RESTful Environments (CoRE) Link
               Format", RFC 6690, August 2012.
 
    [I-D.ietf-core-coap]
               Shelby, Z., Hartke, K., and C. Bormann, "Constrained
               Application Protocol (CoAP)", draft-ietf-core-coap-18
               (work in progress), June 2013.
 
    [I-D.ietf-core-observe]
               Hartke, K., "Observing Resources in CoAP", draft-ietf-
-              core-observe-11 (work in progress), October 2013.
+              core-observe-14 (work in progress), June 2014.
 
    [I-D.vial-core-mirror-proxy]
               Vial, M., "CoRE Mirror Server", draft-vial-core-mirror-
               proxy-01 (work in progress), July 2012.
 
    [I-D.ietf-core-resource-directory]
               Shelby, Z., Bormann, C., and S. Krco, "CoRE Resource
               Directory", draft-ietf-core-resource-directory-01 (work in
               progress), December 2013.
 
@@ -669,22 +669,22 @@
               Castellani, A. and S. Loreto, "CoAP Alive Message", draft-
               castellani-core-alive-00 (work in progress), March 2012.
 
    [I-D.fossati-core-publish-monitor-options]
               Fossati, T., Giacomin, P., and S. Loreto, "Publish and
               Monitor Options for CoAP", draft-fossati-core-publish-
               monitor-options-01 (work in progress), March 2012.
 
    [Android-Bundle]
               "Optimizing Downloads for Efficient Network Access",
-              Android developer note http://developer.android.com/
-              training/efficient-downloads/
+              Android developer note
+              http://developer.android.com/training/efficient-downloads/
               efficient-network-access.html, February 2013.
 
 Appendix A.  Acknowledgments
 
    The authors would like to thank Zach Shelby, Jan Holler, Salvatore
    Loreto, Matthew Vial, Thomas Fossati, Mohit Sethi, Jan Melen, Joachim
    Sachs, Heidi-Maria Rissanen, Sebastien Pierrel, Kumar Balachandran,
    Muhammad Waqas Mir, Cullen Jennings, Markus Isomaki, Hannes
    Tschofenig, and Anna Larmo for interesting discussions in this
    problem space.