CoAP Time Scale Option
draft-toutain-core-time-scale-00

Document Type Active Internet-Draft (individual)
Last updated 2017-10-27
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        A. Minaburo
Internet-Draft                                                    Acklio
Intended status: Informational                                L. Toutain
Expires: April 29, 2018                Institut Mines Telecom Atlantique
                                                        October 26, 2017

                         CoAP Time Scale Option
                    draft-toutain-core-time-scale-00

Abstract

   SCHC compression mechanism for LPWAN network enables IPv6 on devices
   connected to a constrained network (LPWAN).  They can communicate
   with a CoAP server located anywhere in the Internet.  LPWAN network
   characteristics limits the number of exchanges and may impose a long
   RTT.  The CoAP server must be aware of these properties to manage
   correctly requests.  The Time Scale option allows a device to inform
   a CoAP server of the duration the message ID value should be kept in
   memory to manage correctly message duplication.

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 https://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 April 29, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (https://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

Minaburo & Toutain       Expires April 29, 2018                 [Page 1]
Internet-Draft           CoAP Time Scale Option             October 2017

   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.

1.  CoAP Message ID

   Constraint Application Protocol (CoAP) [RFC7252] implements a simple
   reliable transport mechanism based on ARQ.  Each CoAP message
   contains a 16 bit Message ID (noted afterward MID).  A client selects
   a MID in a CON message and expects an ACK message containing the same
   MID value.  A timer makes the client resend the request if no ACK is
   received during a pre-defined period.

   To avoid a second process of duplicated requests by the server, a
   list of messages ID already acknowledged must be maintained for a
   period of time.  If the message ID is already in the list, the
   message is just acknowledged and not processed by upper layer.
   Therefore, the client cannot use this MID value in another request
   during the same period of time.

               client                              server
                 |           CON MID = XXXX          |
                 |---------------------------------->|=> process
    EXCHANGE   ^ |           ACK MID = XXXX          |  ^
    LIFETIME   | |                  <----------------|  | EXCHANGE
               | |                                   |  | LIFETIME
     XXXX      | |           CON MID = XXXX          |  |
     cannot    | |---------------------------------->|  | XXXX in
     be reused | |           ACK MID = XXXX          |  | memory
               | |<----------------------------------|  |
               | |                                   |  |
               v |                                   |  v
    XXXX can be  .                                   .
    reused       .                                   .
                 .                                   .
                 |           CON MID = XXXX          |
                 |---------------------------------->|=> process
               ^ |           ACK MID = XXXX          |  ^
               | |<----------------------------------|  |
                 .                                   .

                      Figure 1: Delayed transmission.

   [RFC7252] calls the period a MID is assigned to a request the
   EXCHANGE_LIFETIME.  The value is based on the worst case scenario

Minaburo & Toutain       Expires April 29, 2018                 [Page 2]
Show full document text