Speeding Up CoAP Block-wise Transfer
draft-zcao-core-speedy-blocktran-00

Document Type Active Internet-Draft (individual)
Last updated 2018-11-07
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)
CORE WG                                                           Z. Cao
Internet-Draft                                                    K. Jin
Intended status: Informational                                     B. Fu
Expires: May 11, 2019                                           D. Zhang
                                                                  Huawei
                                                        November 7, 2018

                  Speeding Up CoAP Block-wise Transfer
                  draft-zcao-core-speedy-blocktran-00

Abstract

   This document specifies a method to speed up block-wise transfer in
   CoAP.  With this, the client can indicate its willingness to be
   responded with a sequence of blocks without issuing request for each
   block one by one.

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 May 11, 2019.

Copyright Notice

   Copyright (c) 2018 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
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Cao, et al.               Expires May 11, 2019                  [Page 1]
Internet-Draft            Speedy Block Transfer            November 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   2
   3.  Speedy Blockwise Transfer . . . . . . . . . . . . . . . . . .   2
     3.1.  The Speedy Block Option . . . . . . . . . . . . . . . . .   2
     3.2.  Example Follow-chart  . . . . . . . . . . . . . . . . . .   4
     3.3.  Retransmission Considerations . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   When performing the block-wise CoAP transfer as defined in [RFC7959]
   , the Client needs to continuously send requests to the Server, using
   the BLOCK options to specify the exact segment that is expected.  As
   a consequence, the Server can only acknowledge different blocks one
   by one according to the request.  Such a design was a reasonable
   choice since the server can be implemented to be truly stateless and
   lightweight.  However, there are some cases where the server is
   capable of keeping necessary states so that the transfer can be
   performed in a more efficiently and faster way, e.g., the server
   being a firmware upgrade device without constraints defined for CoAP.
   This document describes such a proposal that is used to speed up the
   CoAP block transfer.

2.  Conventions used in this document

   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 [RFC2119].

3.  Speedy Blockwise Transfer

3.1.  The Speedy Block Option

   We introduce a new option called 'BlockS', the format being specified
   in Figure 1.  The client can include this option in the payload of
   the request to indicate its willingness to fetch the block content in
   a speedy way.

Cao, et al.               Expires May 11, 2019                  [Page 2]
Internet-Draft            Speedy Block Transfer            November 2018

   +-----+---+---+---+---+--------+--------+--------+---------+
   | No. | C | U | N | R | Name   | Format | Length | Default |
   +-----+---+---+---+---+--------+--------+--------+---------+
   | TBD | C | U | - | - | BlockS | uint   |    0-4 | (none)  |
   +-----+---+---+---+---+--------+--------+--------+---------+
Show full document text