draft-ietf-lwig-cellular-01.txt | draft-ietf-lwig-cellular-02.txt | |||
---|---|---|---|---|
Network Working Group J. Arkko | Network Working Group J. Arkko | |||
Internet-Draft A. Eriksson | Internet-Draft A. Eriksson | |||
Intended status: Informational A. Keranen | Intended status: Informational A. Keranen | |||
Expires: August 17, 2014 Ericsson | Expires: February 14, 2015 Ericsson | |||
February 13, 2014 | August 13, 2014 | |||
Building Power-Efficient CoAP Devices for Cellular Networks | Building Power-Efficient CoAP Devices for Cellular Networks | |||
draft-ietf-lwig-cellular-01 | draft-ietf-lwig-cellular-02 | |||
Abstract | Abstract | |||
This memo discusses the use of the Constrained Application Protocol | This memo discusses the use of the Constrained Application Protocol | |||
(CoAP) protocol in building sensors and other devices that employ | (CoAP) protocol in building sensors and other devices that employ | |||
cellular networks as a communications medium. Building communicating | cellular networks as a communications medium. Building communicating | |||
devices that employ these networks is obviously well known, but this | devices that employ these networks is obviously well known, but this | |||
memo focuses specifically on techniques necessary to minimize power | memo focuses specifically on techniques necessary to minimize power | |||
consumption. | consumption. | |||
skipping to change at page 1, line 36 | skipping to change at page 1, line 36 | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | 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 Notice | |||
Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 9, line 8 | skipping to change at page 9, line 8 | |||
connected to the network and that it is reachable at a given IP | connected to the network and that it is reachable at a given IP | |||
address. | address. | |||
The registration part is easy; a resource directory or mirror proxy | The registration part is easy; a resource directory or mirror proxy | |||
can be used. The device should perform the necessary registration | can be used. The device should perform the necessary registration | |||
with these devices, for instance, as specified in | with these devices, for instance, as specified in | |||
[I-D.ietf-core-resource-directory] and [I-D.vial-core-mirror-proxy]. | [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 | In order to do this registration, the device needs to know its CORE | |||
Link Format description, as specified in [RFC6690]. In essence, the | Link Format description, as specified in [RFC6690]. In essence, the | |||
registration process involves performing a GET on .well-known/core/ | registration process involves performing a GET on .well-known/ | |||
?rt=core-rd at the address of the resource directory (or rt=core-mp | core/?rt=core-rd at the address of the resource directory (or | |||
for mirror proxies), and then doing a POST on the path of the | rt=core-mp for mirror proxies), and then doing a POST on the path of | |||
discovered resource. | the discovered resource. | |||
However, current CoAP specifications provide limited support for | However, current CoAP specifications provide limited support for | |||
discovering the resource directory or mirror proxy. Local multicast | discovering the resource directory or mirror proxy. Local multicast | |||
discovery only works in LAN-type networks, but not in these public | discovery only works in LAN-type networks, but not in these public | |||
cellular networks. Our recommended alternate methods for discovery | cellular networks. Our recommended alternate methods for discovery | |||
are the following: | are the following: | |||
Manual Configuration | Manual Configuration | |||
The DNS name of the resource directory or mirror proxy is manually | The DNS name of the resource directory or mirror proxy is manually | |||
skipping to change at page 14, line 7 | skipping to change at page 14, line 7 | |||
[RFC6690] Shelby, Z., "Constrained RESTful Environments (CoRE) Link | [RFC6690] Shelby, Z., "Constrained RESTful Environments (CoRE) Link | |||
Format", RFC 6690, August 2012. | Format", RFC 6690, August 2012. | |||
[I-D.ietf-core-coap] | [I-D.ietf-core-coap] | |||
Shelby, Z., Hartke, K., and C. Bormann, "Constrained | Shelby, Z., Hartke, K., and C. Bormann, "Constrained | |||
Application Protocol (CoAP)", draft-ietf-core-coap-18 | Application Protocol (CoAP)", draft-ietf-core-coap-18 | |||
(work in progress), June 2013. | (work in progress), June 2013. | |||
[I-D.ietf-core-observe] | [I-D.ietf-core-observe] | |||
Hartke, K., "Observing Resources in CoAP", draft-ietf- | 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] | [I-D.vial-core-mirror-proxy] | |||
Vial, M., "CoRE Mirror Server", draft-vial-core-mirror- | Vial, M., "CoRE Mirror Server", draft-vial-core-mirror- | |||
proxy-01 (work in progress), July 2012. | proxy-01 (work in progress), July 2012. | |||
[I-D.ietf-core-resource-directory] | [I-D.ietf-core-resource-directory] | |||
Shelby, Z., Bormann, C., and S. Krco, "CoRE Resource | Shelby, Z., Bormann, C., and S. Krco, "CoRE Resource | |||
Directory", draft-ietf-core-resource-directory-01 (work in | Directory", draft-ietf-core-resource-directory-01 (work in | |||
progress), December 2013. | progress), December 2013. | |||
skipping to change at page 15, line 16 | skipping to change at page 15, line 16 | |||
Castellani, A. and S. Loreto, "CoAP Alive Message", draft- | Castellani, A. and S. Loreto, "CoAP Alive Message", draft- | |||
castellani-core-alive-00 (work in progress), March 2012. | castellani-core-alive-00 (work in progress), March 2012. | |||
[I-D.fossati-core-publish-monitor-options] | [I-D.fossati-core-publish-monitor-options] | |||
Fossati, T., Giacomin, P., and S. Loreto, "Publish and | Fossati, T., Giacomin, P., and S. Loreto, "Publish and | |||
Monitor Options for CoAP", draft-fossati-core-publish- | Monitor Options for CoAP", draft-fossati-core-publish- | |||
monitor-options-01 (work in progress), March 2012. | monitor-options-01 (work in progress), March 2012. | |||
[Android-Bundle] | [Android-Bundle] | |||
"Optimizing Downloads for Efficient Network Access", | "Optimizing Downloads for Efficient Network Access", | |||
Android developer note http://developer.android.com/ | Android developer note | |||
training/efficient-downloads/ | http://developer.android.com/training/efficient-downloads/ | |||
efficient-network-access.html, February 2013. | efficient-network-access.html, February 2013. | |||
Appendix A. Acknowledgments | Appendix A. Acknowledgments | |||
The authors would like to thank Zach Shelby, Jan Holler, Salvatore | The authors would like to thank Zach Shelby, Jan Holler, Salvatore | |||
Loreto, Matthew Vial, Thomas Fossati, Mohit Sethi, Jan Melen, Joachim | Loreto, Matthew Vial, Thomas Fossati, Mohit Sethi, Jan Melen, Joachim | |||
Sachs, Heidi-Maria Rissanen, Sebastien Pierrel, Kumar Balachandran, | Sachs, Heidi-Maria Rissanen, Sebastien Pierrel, Kumar Balachandran, | |||
Muhammad Waqas Mir, Cullen Jennings, Markus Isomaki, Hannes | Muhammad Waqas Mir, Cullen Jennings, Markus Isomaki, Hannes | |||
Tschofenig, and Anna Larmo for interesting discussions in this | Tschofenig, and Anna Larmo for interesting discussions in this | |||
problem space. | problem space. | |||
End of changes. 6 change blocks. | ||||
11 lines changed or deleted | 11 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |