datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Enhanced Sleepy Node Support for CoAP
draft-rahman-core-sleepy-05

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-02-11
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

CORE WG                                                        A. Rahman
Internet-Draft                          InterDigital Communications, LLC
Intended status: Standards Track                       February 12, 2014
Expires: August 16, 2014

                 Enhanced Sleepy Node Support for CoAP
                      draft-rahman-core-sleepy-05

Abstract

   CoAP is a specialized web transfer protocol for constrained devices.
   These devices typically have some combination of limited battery
   power, small memory footprint and low throughput links.  It is
   expected that in CoAP networks there will be a certain portion of
   devices that are "sleepy" and which may occasionally go into a sleep
   mode (i.e. go into a low power state to conserve power) and
   temporarily suspend CoAP protocol communication.  This document
   proposes a minimal and efficient mechanism building on the Resource
   Directory (RD) functionality to enhance sleepy node support in CoAP
   networks.  The RD functionality may be incorporated as part of a CoAP
   Proxy.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 16, 2014.

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

Rahman                   Expires August 16, 2014                [Page 1]
Internet-Draft        Enhanced Sleepy Node Support         February 2014

   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
   described in the Simplified BSD License.

Table of Contents

   1.  Terminology and Conventions . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Proposal  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  RD Based Sleep Tracking . . . . . . . . . . . . . . . . .   4
     3.2.  Example of Synchronous RD Based Sleep Tracking  . . . . .   5
     3.3.  Example of Asynchronous RD Based Sleep Tracking . . . . .   7
     3.4.  RD Caching Proxy  . . . . . . . . . . . . . . . . . . . .  11
   4.  Performance Results . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  Prototype Setup . . . . . . . . . . . . . . . . . . . . .  11
     4.2.  Initial Results . . . . . . . . . . . . . . . . . . . . .  13
     4.3.  Comparison with Observe . . . . . . . . . . . . . . . . .  13
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Terminology and Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

   This document assumes readers are familiar with the terms and
   concepts that are used in [I-D.ietf-core-coap] and [RFC6690].  In
   addition, this document defines the following terminology:

   Sleepy Node
      A sleepy node is a CoAP client or server that may sometimes go
      into a sleep mode (i.e. go into a low power state to conserve
      power) and temporarily suspend CoAP protocol communication.  A
      sleepy node will otherwise remain in a fully powered on state

[include full document text]